Share:

Debt Collection Proposal

For the board · prepared 17 September 2026 · every figure is measured from our own Square and CRM records, with the date and source stated. Nothing in this proposal has been started.

What is being asked for

Approve
Eight decisions — listed in full below
Engineering
3–4 weeks of one developer (estimate — needs the team’s own sizing)
People
No new headcount — the existing five-person collections team re-pointed as 3 + 1 + 1
Timeline
12 weeks to fully live, in four phases
At stake
$1,136,232 a year is missed at the first payment alone — 46.9% of every new agreement
Expected return
$57,000–$118,000 a year from the first-payment work, after halving the observed value for customer selection. Two further items are genuinely unquantifiable today and are marked so.
The one-sentence version: nearly half of all new agreements fail their very first payment; the customer then hears nothing for a day, receives two text messages a day apart, and is left alone for a month — while the team who should be calling them averages 34.6 minutes on the phone a day. The evidence says the first 24 hours are worth more than everything that follows put together, and we are not in them.

1. The problem, in numbers

New agreements a year
10,943
on the recurring payment book
Fail their first payment
46.9%
5,127 agreements · $1,136,232
Currently owing
14,109
accounts whose last payment attempt failed
First contact after a failure
23.2h
the fastest one all week; median 24.4h
Never reach collections
20%
12 of 60 failures in the week measured
Answer a message in 30 days
8.3%
across the whole collections book
The three findings that justify this proposal.

1. The first day is worth more than the next nine put together. Of everything a missed payment ever returns within ten days, 48% comes back on day 1, 71% by day 3, 92% by day 7. Today the fastest we contact anybody is 23.2 hours, because the collections system is fed by a once-a-day spreadsheet. We are arriving at the end of the most valuable day we have.

2. Catching it early is worth much more than the payment itself — but not all of the difference is ours to claim. An agreement whose first payment is recovered within ten days goes on to pay $1,165 by day 365; one where it is not pays $243. We are deliberately NOT claiming that $922 gap as the value of rescuing somebody. Much of it is simply who the customer already was: a person whose payment we can recover in a few days is, by nature, a better payer than one we cannot, and they would have paid more anyway. This proposal counts HALF the difference — $461 an agreement — as something the rescue creates, and treats the rest as the customer, not us. That halving is a judgement, not a measurement, and it is the single most important assumption in the financial case. It is still a large number.

3. We are not failing to collect. We are failing to ask. In the week measured, of the people who still had not paid: 22 were sent one message and never followed up, 16 replied to us and nothing happened at all, and 7 were never contacted by anyone. Two of the sixteen were explicitly waiting on us — one asking for a payment link, one telling us they had already paid.

2. What happens today

Every step below is measured against last week’s 60 failed first payments (7–13 September), traced through our own collections system. This is not a characterisation. It is the whole process, end to end.
Hour 0The payment fails, and that is the last attempt of the month
  • Our payment provider attempts the card once, on the due date, and never again — measured at 0.90 failed attempts per missed cycle across the book.
  • Nothing further is attempted on that account until next month’s invoice falls due. There is no second attempt, no retry schedule, nothing automatic. If money arrives, a person made it arrive.
Hours 0–23Nothing happens at all
  • The collections system is fed by a once-a-day spreadsheet drop, so the customer cannot be contacted until the next run.
  • Across all 60 failures, the fastest first contact was 23.2 hours. The median was 24.4 hours. Nothing went out inside twelve hours, all week.
  • Set against the recovery curve, this is the expensive part: 48% of everything a missed payment ever returns comes back on day 1. We arrive at the end of it.
Day 1A text — for most, but not all
  • 12 of the 60 never reached the collections system at all (20%). No workflow can see them, so no text was ever possible.
  • 17 of the 60 were never texted — 71.7% got a message, 28.3% got nothing.
  • The message is identical whatever the bank said. The decline reason never reaches the system that sends it, so a customer whose bank has simply blocked recurring payments gets the same words as one with no money.
Day 2A reminder — and then it stops
  • The median customer receives exactly two texts. 25 of the 43 who were contacted got two and no more.
  • The median span from first message to last is 1.0 days. 39 of the 43 had every contact they will ever get inside two days.
  • After that the account goes quiet until the next invoice fails a month later, by which point the chance of the next payment succeeding has almost halved.
If they replyRoughly a third do — and we do not handle it properly
  • 19 people replied — 44.2% of those texted, 31.7% of all 60 failures. That is a good response rate to a debt message and it is being wasted.
  • 6 of those 19 got no answer back from us at all. They wrote to us about a missed payment and the conversation stopped there.
  • Among those still unpaid, the pattern is worse: 16 had replied and no money followed. Two were plainly waiting on us — one asking for a payment link, one saying they had already paid.
PhoneWe cannot tell — and that is itself the finding
  • We cannot say how many times any of these 60 customers was rung, because nothing records it. Our phone system reports call volumes per agent per day and nothing else — no customer, no number. It does not write back into the collections record either, so the account shows nothing.
  • Do not read that as “nobody rang them”. The team made 5,709 calls in 30 days and those calls reached somebody. Some may well have been these people. We simply have no way to know.
  • What we can say is about the team as a whole: over the same period the six collections lines averaged 34.6 minutes of talk time per person per day, the busiest made 58 outbound calls a day, one line recorded no activity at all, and between all of them they produced 20.3 conversations of two minutes or more per day.
  • Being unable to answer “has this customer been called?” is a serious gap in its own right. It means no manager can check whether a queue was worked, and no measurement of any of this can separate a call that happened from one that did not. Closing it is a Phase 0 item.
Put plainly: a customer misses their first payment, hears nothing for a day, gets two text messages a day apart, and is then left alone for a month. A third of them write back, and one in three of those gets no reply. Meanwhile the collections team averages 34.6 minutes of talk time a day and says it is not busy — and we cannot even establish whether any of these particular customers was ever called. This is not a collections process that is underperforming. It is the absence of one.
 TodayProposed
First contact23.2 hours at bestWithin 2 hours, worded by what the bank actually said
Who gets contacted71.7% — a fifth never even reach the system100%, reconciled daily
Messages sent2, one day apartA planned sequence to day 30, and a text after every call attempt
How long contact lasts1 day30 days, to the next invoice
Phone callsUnknown — nothing records who was called2 a day on days 1–3, one on day 5, every attempt logged against the account
If they reply1 in 3 gets no answerNamed owner, answered the same working day
Staff34.6 minutes of talk time a daySame five people, re-pointed

3. What we are proposing

One contact process with three entry points, replacing what is currently a single once-a-day list.

The evidence for treating it as one process is strong and it was a surprise: the reason the bank gives for refusing the payment is almost identical across all three groups — roughly 85% is “not enough money / over a limit” whether the customer is brand new, three weeks in, or a year lapsed. The groups do not differ by why the card failed. They differ by how long ago anybody asked, and whether anybody asked at all.
GroupSizeMoneyWhat we would do differently
New agreements
first payment fails
5,127
a year
$1,136,232 Prevent what we can at the till, message before the payment is taken, then contact within hours rather than a day. This is where the money is.
First two months
missing payments early on
849
of 1,599 live
$254,182 One message, placed in front of the second missed payment. After one miss the next payment succeeds 44% of the time; after two, 23.5%. Nothing sits in that gap today.
Long-lapsed
four or more failures running
9,801$14,601,622 Stop charging the dead ones, then a priced settlement offer to the 1,469 who have paid us before. Not a calling list — it is the largest number here and the worst use of an hour.
The biggest number is the worst place to spend the effort, and the board should expect that to feel counter-intuitive. The long-lapsed group is $14,601,622 on paper. But $6,691,378 of it belongs to 4,687 accounts that never paid us a single cent, and 3,936 of the group last paid something over 240 days ago. The new-agreement group is a fraction of the size on paper and worth far more per hour of effort, because of the $922 difference above.
One genuinely encouraging finding. Of the 11,622 accounts that have ever gone four or more payments down, 2,286 — 19.7% — later paid us again, contributing $1,024,771 after they had lapsed, an average of $448 each. A lapsed account is not a dead one. Every one of those recoveries happened because a person made contact: nothing in our systems ever attempts a card a second time by itself.

4. What has to change, in order

Phase 0Weeks 1–4Plumbing. Nothing customer-facing changes.
  • Event-driven feed into the collections system, replacing the once-a-day spreadsheet drop
  • Carry the bank’s decline reason through, so a message can say something true about why the payment failed
  • Daily reconciliation so nobody falls out of the process unnoticed
  • A named owner and a same-working-day answer for anyone who replies
  • Fix the reply-rate measurement (phone reactions are currently counted as replies)
  • Log calls against the customer record — today the phone system reports totals per agent per day and nothing else, so nobody can tell whether a given account has ever been rung
Who: Engineering  ·  Effect: No revenue effect on its own. Everything after this depends on it.
Phase 1Weeks 3–6Stop the bleed, and build the tools the calls need.
  • Nightly sweep to stop charging the 2,867 dead agreements
  • Apply the payment-portal credit that is promised on screen today and never applied — blocking for anything that sends the link
  • The one-button follow-up text, wired to the call record
  • Point the existing notification code at the collections account it was always meant to use
Who: Engineering + Finance  ·  Effect: Cost and risk reduction, not new revenue. Should pay for itself in avoided chargebacks.
Phase 2Weeks 5–10The first ten days after a missed payment.
  • Same-day message, routed by what the bank actually said, carrying the payment link and its credit
  • Two calls a day on days 1, 2 and 3, one on day 5 — the highest-value hours on the book
  • A one-button “we tried to reach you” text after every single call attempt
  • A day-7 message that offers three replies, one of which is “not this month”
  • A day-21 warning in front of the second missed payment
  • Re-point the team 3 + 1 + 1 and hand each role a ready-made list each morning
Who: Collections + Engineering  ·  Effect: This is where the money is. See the financial case.
Phase 3Weeks 8–12Prevention, and the back book.
  • Pre-payment messages at day −5 and day −1, with the 10% control group
  • Card-quality step at the point of sale
  • Priced settlement campaign on the 1,469 lapsed accounts that have paid us before
Who: Sales + Collections  ·  Effect: Prevention compounds; the settlement campaign is one-off.
Phase 0 is not optional and cannot be skipped to get to the revenue faster. If we begin sending more messages before the reply handling and the reconciliation are fixed, we will increase the number of customers who contact us and get no answer. That is measurably worse than the current position, because it spends goodwill we cannot convert. In the week measured, sixteen people replied to a message about a missed payment and nothing came back.

5. Why the payments actually fail — and the one lever that costs nothing

We used to think most first-payment failures were a technical problem. They are not. Roughly 85% of them are the bank saying there is not enough money, and that share is almost identical whether the customer is brand new, three weeks in, or a year lapsed. But who the customer banks with predicts failure better than almost anything else we hold — and unlike affordability, that is something we can influence, at the till, for nothing.

What the bank tells us when it refuses

What the bank saidShareWhat it actually means
Over a limit on the account55%A money code, not a technical one. It recovers at the same rate as “insufficient funds”, and when we ask customers to pick a reason themselves, almost all choose “money is a bit tight”.
Refused, no reason given23%The issuer told us nothing. A conversation is the only way to find out.
Not enough money10%Exactly what it says.
Bank has blocked recurring payments on the card7%The only code with a thirty-second customer-side fix — a toggle in their banking app. Nobody is ever told this, because the reason never reaches the people making contact.
Card expired, wrong details, or the bank refused the instalment5%Genuinely technical. Needs new card details.
A claim we previously made and have withdrawn — the board should hear it from us rather than from somewhere else. We used to say “87% of customers who miss their first payment are not broke”, because the biggest code is a limit rather than insufficient funds. That was wrong. Checked properly, a limit decline recovers at 20.9% within 30 days and an insufficient-funds decline at 21.3% — indistinguishable. The big code is a money code. This proposal is built on affordability and timing, not on telling customers their bank made a mistake.

The finding that matters most: which bank the card comes from

Measured across 3,733 first instalments between 1 May and 31 August 2026, matched to the issuing bank. “App bank” means the sponsor banks behind the app-based accounts that release wages up to two days early — Cash App, Chime, SoFi, Varo, Dave and similar.
Card is fromFirst instalmentsFailedShare of ALL failures
An early-access app bank694 (18.6%)81.1%31.6%
Any other bank3,039 (81.4%)40.1%68.4%
Under a fifth of our new customers, and nearly a third of everything that fails. They also recover worse afterwards — 18.8% are back within ten days against 25.2%, and 28.3% ever pay against 43.3%. Failing more often and recovering less compounds.

It is the bank, not the prepaid card — we checked

CardFirst instalmentsFailed
App bank, ordinary card38076.1%
App bank, prepaid card31487.3%
High-street bank, ordinary card2,98439.7%
High-street bank, prepaid card5561.8%
An ordinary, non-prepaid card from an app bank still fails 76.1% against 39.7% for the same kind of card from a high-street bank. Prepaid adds roughly ten points on top of that, and about twenty points at a traditional bank — a second, smaller effect. So this is not a “prepaid cards are bad” finding. It is about the account behind the card.

A second, separate signal: credit beats debit

Among high-street banks onlyFirst instalmentsFailed
Credit card78627.2%
Debit card2,25144.7%
Compared like with like, with the app banks stripped out, so this is not the same finding twice. The best card we can be handed — a high-street credit card — fails 27.2%. The worst — an app-bank debit card — fails 82.5%. A threefold difference, settled in the ninety seconds when the card is taken.
The honest caveat, and it is the same one that halved the financial case. Somebody who offers a high-street credit card is, on average, in a better financial position than somebody offering an app-bank debit card. Asking for a different card does not turn one customer into the other. The real and smaller opportunity is the customers who hold both and hand over whichever is nearest — for them, taking the better card is free. This is why decision 7 asks for a trial and a measurement, not a rollout.

Named banks, so the sales floor knows what it is looking at

Issuing bankFirst instalmentsFailed
Sutton Bank — Cash App, Chime30887.3%
The Bancorp Bank — various app accounts11276.8%
Stride Bank — Chime9974.7%
Navy Federal Credit Union14055.7%
Wells Fargo22044.5%
Bank of America37740.1%
JPMorgan Chase — debit38236.6%
JPMorgan Chase — credit1246.5%
One theory we tested and had to drop — do not move charge dates on it. The obvious explanation for the app-bank failures is that those customers are paid early, run out early, and should therefore be charged on a different day. The data does not support it. Across 78,016 charges both groups peak on the same day of the week and trough on the same day. What differs is the size of the swing — 1.78 times best-to-worst against 1.14 — so these accounts run empty faster, they are not on a different clock. Moving their charge date would cost effort and change nothing.

6. The operating model — who does what, and does it fit

No new headcount. The five collections people are re-pointed, three ways. The evidence for this is the team’s own call records: over 30 working days to 16 September they averaged 34.6 minutes of talk time per person per day, the busiest made 58 outbound calls a day, and one line recorded no activity at all. Between all of them the team produced 20.3 conversations of two minutes or more per day. The hours exist. They are pointed at the oldest, coldest accounts on the book.
PeopleOn whatVolumeWhy they sit there
3The back book
everything four or more payments down
9,801 accountsThe existing job, plus the settlement campaign. Largest pile, lowest return per hour — so it gets the people, not the priority.
1Missed first payments
the first ten days
~100 a weekThe highest-value hour on the book. Needs one person whose whole job is speed, because the value halves within days.
1Irregular missers
first two months, missing here and there
~119 a weekCatching the second missed payment before it happens. After one miss the next payment succeeds 44% of the time; after two, 23.5%.

The contact rhythm — two calls a day, and nobody is left wondering

Every call attempt is followed by a text. Not typed by hand — one button in the system that sends “we tried to reach you” with the customer’s own payment link on it. A missed call on an unknown number is nothing; a missed call plus a text is a message.
WhenWhat happensBy whom
Day 0, within 2 hoursText, worded by what the bank actually said, carrying the payment link and the creditAutomated
Day 12 calls, each followed by a one-button textPerson
Day 22 calls + textsPerson
Day 32 calls + textsPerson
Day 51 call + textPerson
Day 7Three-button message — pay / arrange / not this monthAutomated
Days 10, 14, 21, 25, 30Arrangement offer, check-in, the warning before the next payment, pre-notice, next payment falls dueAutomated
Does one person actually fit 100 a week at that rhythm? Yes — and the arithmetic is shown rather than asserted.

20 arrive per working day. Running two calls on days 1–3 and one on day 5 means about 80 accounts live at any moment and 140 dial attempts a day. At the team’s own measured outbound contact rate of 9.1% — not the 20% a textbook would assume — that is 12.7 real conversations a day. Costed at 1.5 minutes a dial, 9 minutes a conversation, 3 minutes of notes and 15 seconds for a one-button text, the day comes to 6.6 hours. It fits.

What the board should know: 140 dials a day is roughly two and a half times what the busiest collector does today. The hours are there, but this is a real change in how the day is worked, and it only holds if the list is handed to them ready — which is what Phase 0 buys.
The irregular-misser role is lighter and that is deliberate. About 71 dials a day, 6.5 conversations, 3.4 hours. The remaining time is the buffer for the first-payment role on a heavy week — arrivals swing from 43 to 144 a week, so a rota built on the average is underwater one week in four.

7. What the board is being asked to decide

1. Engineering time for five plumbing fixes
Approve
Three of them are blocking: nothing else in this proposal reaches its stated value without them. Estimated 3–4 weeks of one developer, and that estimate needs the team’s own sizing before it is relied on.
Why: Without this the first contact after a failed payment cannot leave inside 23 hours, and day 1 is 48% of everything a missed payment ever returns.
2. Re-point the collections team — 3 + 1 + 1, no new headcount
Approve
Three people stay on the existing back book. One takes new missed first payments (about 100 a week). One takes irregular missers — customers in their first two months who miss here and there. The capacity is already in the building; it is pointed at the wrong things.
Why: Measured over 30 working days to 16 September, the six collections lines averaged 34.6 minutes of talk time per person per day, and the busiest made 58 outbound calls a day. One line recorded no activity at all across the whole period. The team produces 20.3 conversations of two minutes or more per day between all of them. This is not a team without hours.
3. The payment link, the credit on it, and a follow-up text after every call
Approve and fund the build
Every call attempt is followed by a text saying we tried to reach them, sent with one button from the system rather than typed. The text carries the customer’s own payment link with the bonus credit already applied — pay in full and 15% is credited to the balance, 75% earns 10%, 50% earns 5%.
Why: The portal already exists and already shows this offer. It has never once applied it. The credit is written into a note and nothing else — no ledger entry, no credit, no change to what the customer owes. We checked all 83,623 recurring payments taken in 2026: not one carries it. Nobody has been short-changed yet because no traffic has been sent there, but this must be fixed before a single link goes out.
4. A settlement policy with a hard ceiling
Approve the policy
Settlement opens at day 40, capped at 25% of balance. Anything deeper needs a named approver and only after day 60. Nothing before day 31 is discountable at all.
Why: Measured on our own book: a reduction under 25% returned $0.74 per $1 given away; at 50–75% it returned $0.14; clearing a balance outright returned −$0.03. And 600 of the 945 accounts we have reduced had no failed charge at all — 72% of the money given away went to people who were never struggling.
5. Stop charging agreements that cannot pay
Approve
A nightly sweep to stop attempting 2,867 accounts whose cards have failed four or more times running. Square cannot end a recurring series through its API, so this has to be a sweep rather than a switch.
Why: 3,100 failed charges were fired at these accounts in the last 30 days and $611,841 a cycle is being attempted into the void. This is a chargeback and processing exposure, and it is also a revenue-recognition question the board should see rather than an operational one.
6. Contact customers BEFORE the first payment
Approve in principle
A short service message five days before and one day before the first instalment. Nobody sends anything today — not us, and not Square. No pay-now link, because a duplicate payment on top of a stored card is the fastest route to a chargeback there is.
Why: This is the only step in the whole process that reaches a customer while nothing has gone wrong. Its effect is UNKNOWN and could be negative, which is why decision 8 matters.
7. A card-quality step at the point of sale
Approve a TRIAL
Where the card offered is an app-bank card or a debit card, ask whether they have another — a high-street card, or a credit card. One sentence in the sales conversation. Trial it and measure it; do not roll it out on the raw numbers alone.
Why: App-bank cards are 18.6% of first instalments and 31.6% of every failure, failing 81.1% against 40.1%. Separately, among high-street banks alone, credit fails 27.2% against debit 44.7%. Best card to worst is 27.2% against 82.5%. It costs nothing to ask — but it changes the sales conversation, and part of the gap is the customer rather than the card, which is why this asks for a trial.
8. Hold back a control group
Approve — and this is the uncomfortable one
Deliberately send 10% of customers nothing at the new steps, so the effect can be measured against a like-for-like group.
Why: We have never run an automated pre-notice or an automated warning message, so their conversion rates do not exist. Without a control they get measured against a human conversation rate and will look like failures however well they do. The cost is real: a small number of people who might have paid will not be contacted.

8. The financial case

LinePer yearThe assumption behind it
First-payment recovery improves by 5 percentage points
from 26.4% to 31.4% recovered within 30 days
$57,000–$118,000 5,127 failures a year × 5 points = 256 more agreements rescued. The lower figure values each at the missed payment alone (about $222). The upper values each at $461 — half the $922 whole-agreement difference we can observe, because much of that difference is the customer rather than the rescue: somebody we can recover quickly was always the better payer. Halving it is a judgement, and it is the assumption most worth arguing about. Both ends depend entirely on Phase 0.
Second-miss warning messagenot quantified Deliberately left blank. 353 agreements are sitting one payment down right now and the success rate halves at the second. But we have never sent this message, so its effect is unknown, and borrowing a rate from our collectors’ results would measure a human conversation rather than an automated message. Decision 8 is how we find out.
Stop charging dead agreementscost, not revenue 3,100 failed attempts in 30 days against cards that cannot succeed. Saves processing fees and, more importantly, reduces chargeback exposure — $385,210 was put at already-dead cards in a single quarter.
Settlement campaign on lapsed payers~$130,000 pool 1,469 accounts × the measured 19.7% return rate × $448 average. Read this as the size of the pool, not as new money — 19.7% is what the book already achieves with the effort already spent. Whether a priced offer beats that is untested.
CostNo new headcount
+ 3–4 dev weeks
The people are already employed — this is a re-pointing, not a hire, and the capacity check in section 6 shows the two new roles fit inside a working day at the team’s own measured contact rate. The only new cash cost is the engineering. The board should note the opposite risk: if the back book is left with three people rather than five, the recovery on the oldest accounts will fall, and that reduction is not modelled here.

9. What this proposal does not claim

It does not claim a return on the two new automated messages. We have never sent a pre-payment notice or a second-miss warning. Their effect is unknown, and could be negative — telling somebody a payment is coming also gives them the opportunity to move the money. That is why a control group is decision 7 rather than an afterthought.
It does not claim the whole observed value of an early rescue. Customers whose first payment we recover quickly go on to pay far more than those we cannot — but they are also, by nature, better payers, and would have paid more regardless. We have halved the observed gap to keep only what is plausibly ours. If the board thinks that is still generous, the lower end of the range assumes we recover nothing but the missed payment itself, and the case is positive there too.
It does not claim that contacting people causes recovery. Customers who pay immediately never get chased, so any comparison of “contacted” against “not contacted” is distorted at both ends. We are proposing this because of the timing evidence, which is not distorted in that way, not because contacted customers pay more often.
It does not assume anything recovers itself. Our payment provider attempts a card once, on the due date, and never again — measured at 0.90 attempts per missed cycle. There is no automatic second attempt anywhere in this business. Every pound in this proposal arrives because a person asked for it, which is why the headcount line is not optional.
It cannot say whether any individual customer has been telephoned. Our phone system reports call counts per agent per day and nothing else — no customer, no number — and it does not write back into the collections record. So every per-customer contact figure in this paper covers text messages only, and nothing here should be read as evidence that a particular person was or was not called. The team-level call figures are sound; the per-account ones do not exist. Closing that is a Phase 0 item, and until it is closed none of the measures in section 10 can separate a call that happened from one that did not.

10. How we will know whether it worked

MeasureTodayWhat good looks like
Time from failed payment to first contact23.2 hours at bestUnder 2 hours for the automated step; a call attempt inside 48 hours
Share of failures that enter the process at all80%100%, reconciled daily with an alarm on the gap
Customers who reply and then receive an answerNot measured, and 16 went unanswered in one week100% answered the same working day
First payment recovered within 30 days26.4%31.4% — the basis of the financial case
Answering a message within 30 days8.3%Rising — and measured excluding phone reactions, which currently inflate it
Second missed payment after a first56% go on to miss againFalling — measured against the held-back control group
Call attempts per person per day58 at the busiest line; 34.6 minutes of talk time~140 on the first-payment role, with the follow-up text sent on every one
Calls attributable to a customerNone — the phone system records per agent per day onlyEvery attempt logged against the account, so a queue can be audited
Call attempts that get a follow-up textNone — there is no such step today100%, one button, logged against the account
Payment-link credit actually applied0 of 83,623 payments in 2026Every payment made through the link
A note on how these numbers were produced. Everything here comes from our own payment records and collections system, measured between 1 and 17 September 2026, and each figure is reproducible from the detail behind this page. Where two ways of counting the same thing disagree, both are shown in the underlying analysis rather than averaged. Nothing in this proposal has been implemented, no customer has been contacted as part of it, and no system has been changed.
Supporting detail is on the other tabs of this page: the week that was measured, whether anyone chased those customers, the conversations verbatim, the full three-group analysis, and a worked calling list of 90 people. Prepared 2026-09-21.
Debt collection proposal — built 2026-09-21 09:21 UTC by scripts/reports/report_proposal.js

Failed first payments — the week of 2026-11-09 to 2026-11-15

Every agreement whose opening instalment failed in the last seven complete days, the reason the issuer gave Square, and whether the debt-collection GHL then actually texted them. 163 agreements took their first charge in this window; 83 of them failed — 50.9%. The per-person list is a key-gated CSV; this page carries counts only.
Failed first payments
83
of 163 agreements opened · 50.9% failed
Not collected
$17,096
$17095.68 of opening instalments
In the debt GHL
3 3.6%
80 are not there at all
Texted after the failure
0 0.0%
83 were never texted
Texted us back
0
0.0% of those texted · 0.0% of all 83
Money in since
10 12.0%
$1,763 banked — read the caveat on the reply tab

By day

DayFailed openingsMissedTextedRepliedMoney in since
Mon, 2026-11-097$1394.990 0.0%—2 28.6%
Tue, 2026-11-106$1015.670 0.0%—2 33.3%
Wed, 2026-11-114$850.400 0.0%—2 50.0%
Thu, 2026-11-125$4490.620 0.0%—1 20.0%
Fri, 2026-11-1326$3563.960 0.0%—2 7.7%
Sat, 2026-11-143$650.000 0.0%—0 0.0%
Sun, 2026-11-1532$5130.040 0.0%—1 3.1%

By city

CityFailed openingsMissedIn debt GHLTextedReplied
Texas30$5551.571 3.3%0 0.0%—
Boston9$754.441 11.1%0 0.0%—
New York5$680.410 0.0%0 0.0%—
Florida11$2095.910 0.0%0 0.0%—
Chicago15$2474.641 6.7%0 0.0%—
Nashville13$5538.710 0.0%0 0.0%—
Why the count jumps around the week. Charge dates cluster — the 1st and the 15th are the two biggest days on the recurring book, so a week containing one of them carries a spike that is a calendar effect, not a deterioration. Compare like-for-like weeks, not adjacent ones.

What the issuer actually said

Straight off the Square payment record — card_details.errors on the failed opening charge. One row per code, with what it means on this book rather than what the Square docs call it.
ReasonFailuresMissedMoney in sinceTextedRepliedWhat it means here
Transaction limit
TRANSACTION_LIMIT
42 50.6%$10205.724 9.5%0 0.0%—
The issuer refused it against a limit on the account. On this book it behaves as a MONEY code, not a technical one — it recovers at the same rate as INSUFFICIENT_FUNDS, and of the customers who answered our text and picked an option, almost all picked "money is a bit tight".
Insufficient funds
INSUFFICIENT_FUNDS
22 26.5%$3461.403 13.6%0 0.0%—
Not enough money in the account on the day.
Generic decline
GENERIC_DECLINE
11 13.3%$2170.423 27.3%0 0.0%—
The issuer refused and told us nothing. No script follows from this code on its own — the text is the only way to find out why.
Cardholder permissions
CARDHOLDER_INSUFFICIENT_PERMISSIONS
7 8.4%$1079.570 0.0%0 0.0%—
The issuer has fenced this card off from recurring card-not-present charges. ONLY THE CARDHOLDER CAN LIFT IT, usually a toggle in their banking app. This is the one code on the list where "check your bank app" is the correct script — and it is heavily concentrated in the early-access neobanks.
Issuer instalment error
ISSUER_INSTALLMENT_ERROR
1 1.2%$178.570 0.0%0 0.0%—
The issuer rejected the charge specifically as an INSTALMENT. It is not a balance problem and not a dead card — the bank would not take this card on a payment plan. The card has to be replaced with one that will; asking them to "try again" with the same card does nothing.
The two codes worth separating. Cardholder permissions is the only one on this list a customer can fix in thirty seconds — the issuer has fenced the card off from recurring charges and a toggle in their banking app lifts it. Nobody is told that, because the decline reason never reaches GHL at all: the outbound text is identical whatever the issuer said. Transaction limit is the opposite trap — it reads like a technical block and behaves like no money.

By card brand

BrandFailuresMissedMoney in since
VISA59 71.1%$12571.934 6.8%
MASTERCARD19 22.9%$3747.384 21.1%
DISCOVER4 4.8%$681.932 50.0%
AMERICAN_EXPRESS1 1.2%$94.440 0.0%

Still not paid

Of the 83 agreements whose opening instalment failed last week, 73 have had no money banked since — $15233.86. "Since" means any completed charge on that customer after the failed opening, not just the opening amount. The per-person list is the key-gated CSV: /first-miss-week-unpaid.csv.
Still owing
73
of 83 failed openings · 88.0%
Still not collected
$15,234
$15233.86 of opening instalments
Never asked at all
73 100.0%
no text went out after the failure
Asked and silent
0 0.0%
texted, never answered
Answered, still owing
0 0.0%
engaged with us and no money followed

Who could still be worked

Where they standPeopleOwingWhat it means
Never reached the GHL70 95.9%$14807.19
Nobody can chase them — they are not in the sub-account. Getting them in is the fix.
In the GHL, never texted3 4.1%$426.67
The contact exists and nothing went out. Check whether the feed dropped them or the workflow did.
Texted, no reply0 0.0%$0.00
Asked once and silent. This is the calling list — a text has already failed on them.
Texted, replied, still no money0 0.0%$0.00
They ENGAGED and still have not paid. Warmest of the four and the one nobody is working.
The four groups need four different actions, and only one of them is a calling list. The people who replied and still have not paid are the warmest names on the page — they answered a text about a missed payment and then nothing happened. The people who were never asked at all are not a performance problem, they are a plumbing problem: nobody has spoken to them yet.

How long they have been owing

Days since the charge failedPeopleOwing
3 days or less34 46.6%$5634.21
4–5 days28 38.4%$7662.08
6–7 days6 8.2%$1015.08
8 days or more5 6.8%$922.49

By reason

Square's reasonStill owingOwingShare of that reasonTexted
Transaction limit38 52.1%$9519.8938 90.5%0 0.0%
Insufficient funds19 26.0%$2990.5719 86.4%0 0.0%
Generic decline8 11.0%$1465.268 72.7%0 0.0%
Cardholder permissions7 9.6%$1079.577 100.0%0 0.0%
Issuer instalment error1 1.4%$178.571 100.0%0 0.0%

By city

CityStill owingOwingShare of that cityTexted
Texas27 37.0%$5088.2427 90.0%0 0.0%
Boston8 11.0%$689.448 88.9%0 0.0%
New York5 6.8%$680.415 100.0%0 0.0%
Florida9 12.3%$1665.089 81.8%0 0.0%
Chicago12 16.4%$1611.9812 80.0%0 0.0%
Nashville12 16.4%$5498.7112 92.3%0 0.0%
This list will shrink on its own, and not because anything is automated. Money still arrives on these accounts — a collector gets hold of someone, or a customer acts on a text. Nothing on this book charges a card a second time by itself, so every name that drops off did so because a person made it happen. Re-run the report to see the current position rather than working from a saved copy.
This week — built 2026-11-17 20:08 UTC by scripts/reports/report_first_miss_week.js

Did we text them, and did they answer

Cross-checked live against the US Debt Collection GHL sub-account (pcTyOadbzBqZO7v3cbwn) — matched on phone number, then email, then name. Read-only: this page sends nothing and enrols nobody.
Failed first payments
83
the whole week
Reached the debt GHL
3 3.6%
80 never arrived
A text actually went out
0 0.0%
3 are in the GHL and were still not texted
Replied
0
0.0% of those texted
Fastest text out
—
median — · slowest —
Undelivered texts
0
of 0 sent · 0 by the workflow, 0 typed by a person

How long after the failure the first text went out

Time from failure to first textPeople
Same day (under 12h)0 0.0%
12–24h0 0.0%
1–2 days0 0.0%
2–4 days0 0.0%
4 days+0 0.0%
Nobody is contacted on the day. The fastest text in this week left — hours after the charge failed and the median was — hours — the feed into this sub-account is a daily Google-Sheet drop, so day 0 does not exist. That is the expensive part: measured over four months, day 1 is 48% of everything a missed opening ever returns inside ten days, and the first text lands at the end of it.

What they said back

The workflow's opening text asks for a reason and offers three numbered options: 1 card issue · 2 money is a bit tight · 3 something else. This is the only part of a reply this report reads, and no message body is ever stored.
ReplyPeople
1 — Card issue0 0.0%
2 — Money is a bit tight0 0.0%
3 — Something else0 0.0%
Wrote something instead of picking0 0.0%
The customers agree with the money reading of TRANSACTION_LIMIT. Of the people who picked an option, the large majority picked "money is a bit tight", and nearly all of those had a TRANSACTION_LIMIT decline — not a card-issue one. 0 said card issue. Whatever the code looks like, the people answering are telling us it is affordability.
Do not read the recovery column as an effect of texting. 10 of the 83 have money in since, but the people who pay straight back are exactly the people who never needed chasing — and some of them are out of the texting list precisely because they had already paid. The comparison is selected at both ends. Nothing on this book charges a card a second time on its own; every later payment is a person acting — a collector on the phone, or the customer following up a text.

Where the chase leaks

Two separate holes, and they need different fixes. One group never reaches the debt sub-account at all; the other is sitting in it with no text sent.
Never reached the GHL
80
$16,669 · no phone-number match in the sub-account
In the GHL, no text sent
3
$427 · contact exists, nothing went out
Total not contacted
83 100.0%
$17,096 of missed openings with no text
Emails sent
0
SMS is the only channel this sub-account uses
Calls logged in GHL
0
the team dials from GoTo, which does not write back here — absence is not proof nobody rang

The gap, by day

DayFailed openingsNever reached GHLIn GHL, not textedMissed, uncontacted
Mon, 2026-11-0977 100.0%0$1394.99
Tue, 2026-11-1065 83.3%1 16.7%$1015.67
Wed, 2026-11-1144 100.0%0$850.40
Thu, 2026-11-1255 100.0%0$4490.62
Fri, 2026-11-132626 100.0%0$3563.96
Sat, 2026-11-1432 66.7%1 33.3%$650.00
Sun, 2026-11-153231 96.9%1 3.1%$5130.04

Never reached the GHL, by city

CityFailed openingsNever reached GHLMissed
Texas3029 96.7%$5461.57
Boston98 88.9%$559.44
New York55 100.0%$680.41
Florida1111 100.0%$2095.91
Chicago1514 93.3%$2332.97
Nashville1313 100.0%$5538.71
Checked, not assumed. Every one of the 80 was probed on the phone number, the email address and the name. The phone probe returned zero contacts for each of them — they are genuinely absent from the sub-account, not a formatting miss.

In the GHL but not texted — when the contact was created

Contact createdPeople
2026-09-271
2026-10-121
2026-10-151
A contact created today has not had time to be texted — the feed is a daily drop, so the tail of this table is lag rather than a miss. Anything created before yesterday and still untexted is a real gap.
The chase — built 2026-11-17 20:08 UTC by scripts/reports/report_first_miss_week.js

Did the handover actually land?

Every failed opening payment from 2026-10-20 to 2026-11-16, followed through four links: Square recorded the failure → they still owed a day later → they were in our daily handover file → a contact exists in the debt-collection GHL → a text actually went out. Nothing checked this end to end before.
Failed openings
352
→
Still owed next day
327
→
In our file
268
→
In the debt GHL
154
→
Texted
145
45 of those people fall on days we have no handover file for, so whether they were in it is unknown — those days read “no file” in the table and are not counted as a miss. 14 were genuinely absent from a file that does exist.
Fixed it themselves inside 24h
25 7.1%
correctly never handed over — the feed is an outstanding-balance snapshot taken about a day after the charge, so by the time it ran these people owed nothing
Needed chasing, reached the GHL
154 47.1%
of the 327 who genuinely still owed
A text went out
145 44.3%
of those who needed chasing — the honest coverage number, measured against people who still owed rather than against every failure
Never reached the GHL
173
$34824.91 · 155 of them have never paid anything since
Whole days lost
6
56 people, $12941.61 — days where people needed chasing and not one was created in the GHL
A DROPPED DAY IS PERMANENT — nothing backfills it. The people lost on 4 September had still never been created in the debt GHL thirteen days later, and 14 of those 15 have never paid anything since. No sweep picks up a day the upload missed. That is why this is a daily check rather than a one-off answer: if a row below reads NOTHING LANDED, that day's file has to be loaded by hand and those people contacted, because it will not fix itself.

Day by day — where the chain breaks

One row per day, and the verdict is per day on purpose. Blended across the window the coverage reads 47.1% into the GHL and 44.3% texted, which looks healthy — but the failures are not spread evenly. They are whole days on which nothing loaded at all, and a rate hides an outage.
DayFailed openingsSelf‑fixed <24h Needed chasingIn our fileIn the GHLTexted LostVerdict
Tue, 2026-10-201211181111—landed
Wed, 2026-10-211331071010—landed
Thu, 2026-10-22954444—landed
Fri, 2026-10-2328127262727—landed
Sat, 2026-10-24918888—landed
Sun, 2026-10-2513—13121313—landed
Mon, 2026-10-26725555—landed
Tue, 2026-10-2711110101010—landed
Wed, 2026-10-2813112121212—landed
Thu, 2026-10-290—00———no failures
Fri, 2026-10-303—33003 $572.50NOTHING LANDED
Sat, 2026-10-3191487858279 $15514.26part of it landed
Sun, 2026-11-0110—10101010—landed
Mon, 2026-11-025—5555—landed
Tue, 2026-11-030—00———no failures
Wed, 2026-11-04321111—landed
Thu, 2026-11-05716666—landed
Fri, 2026-11-0617—17171717—landed
Sat, 2026-11-072—2222—landed
Sun, 2026-11-082—2222—landed
Mon, 2026-11-097165006 $1109.99NOTHING LANDED
Tue, 2026-11-106—66105 $925.67part of it landed
Wed, 2026-11-114132003 $720.40NOTHING LANDED
Thu, 2026-11-125—54005 $4490.62NOTHING LANDED
Fri, 2026-11-1326—26260026 $3563.96NOTHING LANDED
Sat, 2026-11-143—32102 $508.33part of it landed
Sun, 2026-11-1532—32no file1031 $4935.04part of it landed
Mon, 2026-11-1614113no file0013 $2484.14NOTHING LANDED

The days that lost their whole handover

DayNeeded chasingOur file that day Of them, in our fileNever created in GHLMissed Never paid since
Fri, 2026-10-30321 in the file33$572.502
Mon, 2026-11-09693 in the file56$1109.995
Wed, 2026-11-11366 in the file23$720.402
Thu, 2026-11-125101 in the file45$4490.624
Fri, 2026-11-1326119 in the file2626$3563.9624
Mon, 2026-11-1613no file built013$2484.1413
Our side is not where it broke. On both lost days the handover file existed and held those customers — the file was built and they were in it. What never happened is the load into the GHL: no contact was created, so no workflow could fire and no text could go out. That points at the upload step between the file and the sub-account, not at the report and not at the data. Every person counted as missing has a phone number on their Square record, so none of these are data-quality failures either.

In the GHL and still not texted

A contact exists, so the handover did reach the sub-account — but no message ever went out after the failure. A contact created in the last day or so is lag rather than a miss; anything older is a real gap.
In the GHL, never texted
9
$1755.82 across the window
Needed chasing and got no text at all
182 55.7%
$36580.73 of missed openings with no message

By city

CityNeeded chasingNever reached the GHLTexted
Texas11453 46.5%59 51.8%
Boston3019 63.3%10 33.3%
New York2312 52.2%10 43.5%
Florida6944 63.8%22 31.9%
Chicago4926 53.1%22 44.9%
Nashville4219 45.2%22 52.4%

How this is measured

A failed opening is a customer's first-ever charge attempt across the six Square Recurring* locations, taken from the whole attempt history, that did not complete. Same definition as the This week tab, so the two pages cannot disagree.

“Needed chasing” excludes anyone who paid inside 24 hours of the failure. The feed into the debt GHL is an outstanding-balance snapshot taken about a day after the charge, so someone who clears it themselves is correctly never handed over. Measured 7–13 September, the two groups do not overlap at all: none of the 45 people texted had paid inside 24h, and all of the absentees who had paid, had paid inside 24h. That is what makes this exclusion safe rather than convenient — and it is why a raw “texted / all failures” number understates coverage.

Matched on phone, then email, then exact name, against pcTyOadbzBqZO7v3cbwn. Phone is the only field that has ever produced a match in this sub-account; the other two are probed so an “absent” verdict is never really a formatting miss.

Read-only. Square GET, GHL GET. This page sends no message, enrols nobody and uploads nothing.

What this page deliberately does NOT do is compare recovery between the texted and the untexted. Nothing on this book charges a card a second time on its own — every later payment is a person — and the people who pay straight back drop out of the chase, so that comparison is selected at both ends and cannot measure the effect of a text.

The row-level fallout list is a CSV, never on this page — every person in the window who either never reached the GHL or never got a text, with the day, the city, the reason and whether they have paid since: https://reports.iconicbyai.com/chase-coverage/dropped.csv
Built 2026-11-17 20:09 UTC by scripts/reports/report_chase_coverage.js.
Did it land — built 2026-11-17 20:09 UTC by scripts/reports/report_chase_coverage.js

11 people who answered us and still have not paid

Their opening instalment failed in the week of 2026-11-02 to 2026-11-08, we texted them, they texted back, and no money has arrived since. Every SMS below is verbatim, oldest first, with the GHL owner of the contact and of each opportunity card. Read-only — nothing here was sent, moved or assigned by this page. Source: /first-miss-week.
This page carries customer names, phone numbers and their own words about their money. It is key-gated and is never committed, never linked from the dashboard and never indexed. Do not paste its contents anywhere that is not.
People
11
answered, still owing
Owed
$2568.32
opening instalments only
Nobody owns them
0
no assigned user on the contact
We spoke last
8
our text was the final message
THEY spoke last
3
they wrote and nothing came back

Who owns them

GHL ownerPeopleOwed
Emily Lewis4$1063.16
Maria R5$1057.66
Princess Roni1$285.00
Charles C1$162.50

The 11 at a glance

NameOwnerOwingDaysSquare reasonRepliesLast heard from themWho spoke last
Faith BeckmonEmily Lewis$296.008ISSUER_INSTALLMENT_ERROR22026-11-09THEY did
Katarina AmparoPrincess Roni$285.008GENERIC_DECLINE12026-11-09we did
Andre MoralesMaria R$280.008TRANSACTION_LIMIT12026-11-09we did
Melani RosarioEmily Lewis$263.008TRANSACTION_LIMIT22026-11-10we did
Reaging HyppoliteEmily Lewis$258.339TRANSACTION_LIMIT12026-11-06we did
Adde Kate SaintEmily Lewis$245.8312CARD_EXPIRED12026-11-07we did
Jacqueline ThomasMaria R$245.008TRANSACTION_LIMIT22026-11-09THEY did
Parker AnthonyMaria R$220.838INSUFFICIENT_FUNDS32026-11-09THEY did
Joseph DassattiMaria R$166.009TRANSACTION_LIMIT12026-11-09we did
Esther JasmineCharles C$162.508INSUFFICIENT_FUNDS12026-11-09we did
Paris PageMaria R$145.8312GENERIC_DECLINE12026-11-03we did
“Who spoke last” is the column to work from. Where THEY spoke last, the customer typed something and nothing came back — that is a dropped conversation, not a reluctant debtor. Read the message before acting on the flag, though: a closing pleasantry (“thanks, you too”) ends a thread perfectly well, while “send me the link” or “I already paid this” is somebody still waiting on us. Only the second kind is a job.

iMessage tapbacks are excluded from that column — a Loved “…” reaction arrives as an ordinary inbound SMS, and counting it as a reply puts a thumbs-up on an invoice link into the “we never answered” pile. They are still shown in the thread, greyed, marked as reactions.

“Owner” is who holds the record TODAY, not who sent the messages. A contact reassigned this morning shows this morning's owner against a conversation somebody else had, so use it to decide who picks it up, never to decide who let it go.
Faith Beckmon +13865236043 Owner: Emily Lewis $296.00 owing · 8 days · Boston · ISSUER_INSTALLMENT_ERROR · replied 2× · picked free text
Debt(Emily) → Assigned to you · owner Emily Lewis · open · last moved 2026-11-09
Mon 2026-11-09 14:51 UTC · US · automated workflow"Hi Faith, This is Studio 1 — I noticed your payment didn't go through this month. Can you let me know the main reason so we can get the right person to help and get you back on track. 1- Card issue 2- Money is a bit tight 3- Something else Regards, Finance Department END
Mon 2026-11-09 14:54 UTC · THEMWe have moved out of state and no longer interested I left several voicemails but no one contacted me back.
Mon 2026-11-09 14:55 UTC · activity opportunityOpportunity created
Mon 2026-11-09 14:55 UTC · US · automated workflowFaith Thank you for time. We will be in touch as soon as possible. Regards, Finance Department
Mon 2026-11-09 14:56 UTC · US · typed by Caet SHi Faith, we do not show any voicemails being received by our team. Please be sure you're contacting us at 617-466-9980. Kindly note that as all materials outlined in your agreement have been delivered, we cannot cancel the order. We can still assist you with the portfolio and modeling endeavors even if you're out of state.
Mon 2026-11-09 14:57 UTC · THEMOur house has burnt down we move with family we just don't have the funds for it I'm sorry
Katarina Amparo +14073402372 Owner: Princess Roni $285.00 owing · 8 days · Florida · GENERIC_DECLINE · replied 1× · picked 2 Money is a bit tight
Debt AI(Veronica) → Call back · owner Princess Roni · open · last moved 2026-11-09
Mon 2026-11-09 15:19 UTC · US · automated workflow"Hi Katarina, This is Studio 1 — I noticed your payment didn't go through this month. Can you let me know the main reason so we can get the right person to help and get you back on track. 1- Card issue 2- Money is a bit tight 3- Something else Regards, Finance Department END
Mon 2026-11-09 15:22 UTC · THEM2
Mon 2026-11-09 15:23 UTC · activity opportunityOpportunity created
Mon 2026-11-09 15:23 UTC · US · automated workflowKatarina Thank you for time. We will be in touch as soon as possible. Regards, Finance Department
Mon 2026-11-09 15:58 UTC · US · typed by Princess RoniHi Katarina this is Veronica I do understand that money is tight right now, your monthly payments are scheduled for $285 I can reduce this payment to $142.50 so that you can get current. If you need it to be reduced more please let me know in what amount
Mon 2026-11-09 15:58 UTC · activity opportunityOpportunity updated
Andre Morales +17862611918 Owner: Maria R $280.00 owing · 8 days · Florida · TRANSACTION_LIMIT · replied 1× · picked 2 Money is a bit tight
Debt AI(Veronica) → Other · owner Maria R · open · last moved 2026-11-09
Mon 2026-11-09 14:47 UTC · US · automated workflow"Hi Andre, This is Studio 1 — I noticed your payment didn't go through this month. Can you let me know the main reason so we can get the right person to help and get you back on track. 1- Card issue 2- Money is a bit tight 3- Something else Regards, Finance Department END
Mon 2026-11-09 14:51 UTC · THEM2
Mon 2026-11-09 14:52 UTC · activity opportunityOpportunity created
Mon 2026-11-09 14:52 UTC · US · automated workflowAndre Thank you for time. We will be in touch as soon as possible. Regards, Finance Department
Mon 2026-11-09 15:04 UTC · activity opportunityOpportunity updated
Mon 2026-11-09 15:10 UTC · activity opportunityOpportunity updated
Mon 2026-11-09 15:13 UTC · activity opportunityOpportunity updated
Melani Rosario +17737290621 Owner: Emily Lewis $263.00 owing · 8 days · Chicago · TRANSACTION_LIMIT · replied 2× · picked free text
Debt(Emily) → Payment agreement · owner Emily Lewis · open · $2520.00 · last moved 2026-11-16
Mon 2026-11-09 15:15 UTC · US · automated workflow"Hi Melani, This is Studio 1 — I noticed your payment didn't go through this month. Can you let me know the main reason so we can get the right person to help and get you back on track. 1- Card issue 2- Money is a bit tight 3- Something else Regards, Finance Department END
1 day later
Tue 2026-11-10 15:16 UTC · US · automated workflow"I don't want to bother you, but we do need to resolve this. Would a 5-minute call later today be okay?" Regards, Finance Department
Tue 2026-11-10 15:25 UTC · THEMI would like to see what my full balance is an pay it all off if possible
Tue 2026-11-10 15:31 UTC · US · automated workflowMelani Thank you for time. We will be in touch as soon as possible Regards, Finance Department
Tue 2026-11-10 15:31 UTC · activity opportunityOpportunity created
Tue 2026-11-10 15:32 UTC · THEMIs there a way I Can process the payment electronically i am working all day and will not be available
1 day later
Wed 2026-11-11 17:08 UTC · US · typed by Emily LewisHello sorry - just seeing this message ~ Emily @ the Photo Studio My hours are 9-5 EST *Finance Department 929) 367 0754
4 days later
Mon 2026-11-16 15:29 UTC · activity opportunityOpportunity updated
Reaging Hyppolite +16315268680 Owner: Emily Lewis $258.33 owing · 9 days · New York · TRANSACTION_LIMIT · replied 1× · picked 2 Money is a bit tight
Debt(Emily) → Money is Tight · owner Emily Lewis · open · last moved 2026-11-06
Fri 2026-11-06 14:18 UTC · US · automated workflow"Hi Reaging, This is Studio 1 — I noticed your payment didn't go through this month. Can you let me know the main reason so we can get the right person to help and get you back on track. 1- Card issue 2- Money is a bit tight 3- Something else Regards, Finance Department END
Fri 2026-11-06 14:26 UTC · THEM2 money is a bit tight. I am pay maybe by next week.
Fri 2026-11-06 14:27 UTC · activity opportunityOpportunity created
Fri 2026-11-06 14:27 UTC · US · automated workflowReaging Thank you for time. We will be in touch as soon as possible. Regards, Finance Department
Adde Kate Saint +16622799502 Owner: Emily Lewis $245.83 owing · 12 days · Nashville · CARD_EXPIRED · replied 1× · picked free text
Debt(Emily) → Assigned to you · owner Emily Lewis · open · last moved 2026-11-07
Tue 2026-11-03 14:14 UTC · US · automated workflow"Hi Adde, This is Studio 1 — I noticed your payment didn't go through this month. Can you let me know the main reason so we can get the right person to help and get you back on track. 1- Card issue 2- Money is a bit tight 3- Something else Regards, Finance Department END
1 day later
Wed 2026-11-04 14:14 UTC · US · automated workflow"I don't want to bother you, but we do need to resolve this. Would a 5-minute call later today be okay?" Regards, Finance Department
2 days later
Sat 2026-11-07 01:03 UTC · THEMI can't do this. I paid $1000 when the ad beforehand said $399 and there is nothing being done to pay for. I can look it all up my self. I have already been out six hundred for nothing.
Sat 2026-11-07 01:08 UTC · US · automated workflowAdde Thank you for time. We will be in touch as soon as possible Regards, Finance Department
Sat 2026-11-07 01:08 UTC · activity opportunityOpportunity created
Jacqueline Thomas +12677747715 Owner: Maria R $245.00 owing · 8 days · Florida · TRANSACTION_LIMIT · replied 2× · picked 2 Money is a bit tight
Debt AI (Maria) → Money is Tight · owner Maria R · open · last moved 2026-11-09
Mon 2026-11-09 14:41 UTC · US · automated workflow"Hi Jacqueline, This is Studio 1 — I noticed your payment didn't go through this month. Can you let me know the main reason so we can get the right person to help and get you back on track. 1- Card issue 2- Money is a bit tight 3- Something else Regards, Finance Department END
Mon 2026-11-09 15:37 UTC · THEM2
Mon 2026-11-09 15:37 UTC · activity opportunityOpportunity created
Mon 2026-11-09 15:37 UTC · US · automated workflowJacqueline Thank you for time. We will be in touch as soon as possible. Regards, Finance Department
Mon 2026-11-09 15:51 UTC · US · typed by Maria RHello Jacqueline, to help make things more manageable, we are willing to extend your remaining balance of ($2450) over (16) months. This would reduce your monthly installment to ($153.12)
Mon 2026-11-09 15:51 UTC · US · typed by Maria RPlease let me know if this would be more convenient for you.
Mon 2026-11-09 17:54 UTC · THEMI am in the process of getting some legal documents drawn up because I don't feel I was treated fair with this company. You guys told me that you were not a modeling agency, but you could help find me work. No one has called. No one has gotten in touch with me the only time I hear from you is when you need your money
Parker Anthony +14143096594 Owner: Maria R $220.83 owing · 8 days · Chicago · INSUFFICIENT_FUNDS · replied 3× · picked 2 Money is a bit tight
Debt AI (Maria) → Sent to Customer Service · owner Maria R · open · last moved 2026-11-09
Mon 2026-11-09 14:56 UTC · US · automated workflow"Hi Parker, This is Studio 1 — I noticed your payment didn't go through this month. Can you let me know the main reason so we can get the right person to help and get you back on track. 1- Card issue 2- Money is a bit tight 3- Something else Regards, Finance Department END
Mon 2026-11-09 14:56 UTC · THEM2
Mon 2026-11-09 14:57 UTC · THEMCan I cancel my subscription
Mon 2026-11-09 14:57 UTC · activity opportunityOpportunity created
Mon 2026-11-09 14:57 UTC · US · automated workflowParker Thank you for time. We will be in touch as soon as possible. Regards, Finance Department
Mon 2026-11-09 15:00 UTC · call(no body — an activity entry, not a message)
Mon 2026-11-09 15:00 UTC · call(no body — an activity entry, not a message)
Mon 2026-11-09 15:03 UTC · US · typed by Maria RHello Tea, I am sorry I missed your call. You can give me a call back at 929-367-0755 and I will be happy to assist you. H
Mon 2026-11-09 15:08 UTC · US · typed by Maria RHello Tea, you can contact our customer service department via email at inquiries@mapsstudio.nyc. Have a nice day.
Mon 2026-11-09 15:09 UTC · THEMThank you
Mon 2026-11-09 15:09 UTC · activity opportunityOpportunity updated
Joseph Dassatti +16036305999 Owner: Maria R $166.00 owing · 9 days · Boston · TRANSACTION_LIMIT · replied 1× · picked free text
Debt AI (Maria) → Assigned to you · owner Maria R · open · last moved 2026-11-09
Fri 2026-11-06 14:30 UTC · US · automated workflow"Hi Joseph, This is Studio 1 — I noticed your payment didn't go through this month. Can you let me know the main reason so we can get the right person to help and get you back on track. 1- Card issue 2- Money is a bit tight 3- Something else Regards, Finance Department END
2 days later
Mon 2026-11-09 14:11 UTC · US · automated workflow"I don't want to bother you, but we do need to resolve this. Would a 5-minute call later today be okay?" Regards, Finance Department
Mon 2026-11-09 14:12 UTC · THEMSorry I can resolve tomorrow dealing with a family matter with family in the hospital I meant to last week and things hit the fan
Mon 2026-11-09 14:22 UTC · US · automated workflowJoseph Thank you for time. We will be in touch as soon as possible Regards, Finance Department
Mon 2026-11-09 14:22 UTC · activity opportunityOpportunity created
1 day later
Tue 2026-11-10 14:47 UTC · US · typed by Maria RHello Katelyn, I understand. You can reach me by phone at 929-367-0755 or by replying to this message and I iwll be happy to assist you.
2 days later
Thu 2026-11-12 17:47 UTC · US · typed by Maria RHello Katelyn, this is Maria from the Studio Finance Department. We recently tried reaching you because we noticed that your payment of ($166) due (11/05) was not processed. Could we process it today? Please give us a call back at 929-367-0755 or reply to this message so we can assist you.
Esther Jasmine +19205009119 Owner: Charles C $162.50 owing · 8 days · Chicago · INSUFFICIENT_FUNDS · replied 1× · picked 2 Money is a bit tight
Debt AI(Charles) → Money is Tight · owner Charles C · open · last moved 2026-11-09
Mon 2026-11-09 14:28 UTC · US · automated workflow"Hi Esther, This is Studio 1 — I noticed your payment didn't go through this month. Can you let me know the main reason so we can get the right person to help and get you back on track. 1- Card issue 2- Money is a bit tight 3- Something else Regards, Finance Department END
Mon 2026-11-09 15:14 UTC · THEM2
Mon 2026-11-09 15:15 UTC · activity opportunityOpportunity created
Mon 2026-11-09 15:15 UTC · US · automated workflow · sentEsther Thank you for time. We will be in touch as soon as possible. Regards, Finance Department
Paris Page +15028210274 Owner: Maria R $145.83 owing · 12 days · Nashville · GENERIC_DECLINE · replied 1× · picked 1 Card issue
Debt AI (Maria) → Card Issue · owner Maria R · open · last moved 2026-11-03
Tue 2026-11-03 14:26 UTC · US · automated workflow"Hi Paris, This is Studio 1 — I noticed your payment didn't go through this month. Can you let me know the main reason so we can get the right person to help and get you back on track. 1- Card issue 2- Money is a bit tight 3- Something else Regards, Finance Department END
Tue 2026-11-03 14:28 UTC · THEM1
Tue 2026-11-03 14:28 UTC · activity opportunityOpportunity created
Tue 2026-11-03 14:28 UTC · US · automated workflowParis Thank you for time. We will be in touch as soon as possible Regards, Finance Department
Tue 2026-11-03 14:31 UTC · US · typed by Maria RHello Alexia, no problem. Are you available for a quick call so I can assist you?
Tue 2026-11-03 17:32 UTC · US · typed by Maria R · failedHello Alexia, no problem. Are you available for a quick call so I can assist you?
Wed 2026-11-04 16:47 UTC · US · typed by Maria RHello Alexia, this is Maria from the Studio Finance Department. We recently tried reaching you because we noticed that your payment of ($145.83) due (11/02) was not processed. Could we process it today? Please give us a call back at 929-367-0755 or reply to this message so we can assist you.
Thu 2026-11-05 14:52 UTC · US · typed by Maria RHello Alexia, this is Maria from the Studio Finance Department. We recently tried reaching you because we noticed that your payment of ($145.83) due (11/02) was not processed. Could we process it today? Please give us a call back at 929-367-0755 or reply to this message so we can assist you.
1 day later
Fri 2026-11-06 14:53 UTC · US · typed by Maria RHello Alexia, this is Maria from the Studio Finance Department. We have attempted to reach you regarding the overdue balance on your account. Prompt attention to this matter is required. Please call us at 929-367-0755 or reply to this message to settle your outstanding balance.
Built 2026-11-17T02:23:38.448Z by scripts/reports/report_first_miss_chats.js from the debt sub-account pcTyOadbzBqZO7v3cbwn. Re-run it for the current position — money still arrives on these accounts because a person makes it happen, and names drop off this list without anything here changing.
The conversations — built 2026-11-17 02:23 UTC by scripts/reports/report_first_miss_chats.js
This section was last built 60 days ago (2026-09-17 22:00 UTC). Refresh it with node scripts/reports/report_money_plan.js, then re-run node scripts/reports/report_money.js.

The money plan — three populations, one engine

The day−5-to-collections ladder we built for the opening instalment, re-cut against what /first-miss-week and /first-miss-week-chats measured this week, and extended to the two populations it never covered. Every figure here is dated and names the measurement behind it.
The single most useful thing the numbers say: these are not three different problems. The decline-reason mix is almost identical in all three — roughly 85% soft (money, limit, issuer said no) in the never-started pile, in the stumblers, and in the zombies alike. They do not differ by why the card failed. They differ by how long ago anybody last asked, and whether anybody asked at all. So the answer is not three collection strategies. It is one contact engine with three entry points and three different economics — and the entry point decides almost everything, because the earlier it fires the more it is worth.

What each population is worth

PopulationAccountsMoney on the floorScaleThe play in one line
1 · New contracts
the opening instalment
5,127 a year$1,136,23246.9% of 10,943 openedPrevent it, then own the first ten days.
2 · Early life
opened 10–60 days ago
849 of 1,599 live$254,18253.1% have missed at least onceFinish what the opening started. Two very different halves.
3 · Zombie
4+ consecutive failed charges
9,801$14,601,6222,867 still being chargedTriage, not chase. Stop the bleed first.
Priority is not the same as size. Population 3 is the biggest number on that table and the worst place to spend the next hour. $6,691,378 of it belongs to 4,687 accounts that never paid a single cent, and 3,936 of the zombie pile last paid us something over 240 days ago. Population 1 is a third the size on paper and worth far more per hour, because an opening instalment caught inside ten days is followed by $922 more per agreement by day 365 — of which we count HALF as ours ($1,165 against $243 — /opening-payment, 16 Sep 2026).

The five things this week changed

What we foundWhat it breaksWhat the plan does about it
Day 0 does not exist. The fastest text all week left 23.2 hours after the charge failed; median 24.4h; nothing inside 12h ever. /first-miss-week, 7–13 Sep The ladder's day-0 +2h step — the one sitting on 48% of everything a miss ever returns — is physically impossible today. The feed into the debt sub-account is a daily Google-Sheet drop. Build item 1. Event-driven feed. Nothing else in this plan reaches its stated value until this is done.
The decline reason never reaches GHL at all. No reason field exists on that sub-account. reference_us_debt_collection_ghl Every outbound text is identical whatever the issuer said — so the four-way routing the ladder is built on cannot happen, and the two codes with a real 30-second customer-side fix are never named. Build item 2. Reason + bucket as custom fields, and route on them.
20% never arrive. 12 of the 60 failures last week had no contact in the sub-account at all — probed on digits, last-ten, email and surname. /first-miss-week A fifth of the queue is invisible to every workflow, every report and every collector. They are not being worked badly; they are not being worked. Build item 3. Reconcile the feed daily and alarm on the gap.
Replying is not the finish line. 16 of the 45 still-unpaid answered our text and no money followed. /first-miss-week-chats The ladder measures contact rate, and contact rate was the right first metric — but nothing owns what happens after someone answers. Two of those 16 were plainly waiting on us. Build item 4. A "replied, unpaid" queue with a named owner and a same-working-day SLA.
An iMessage tapback reads as a reply. Loved "…" arrives as an ordinary inbound SMS. /first-miss-week-chats Reply rate — the number the whole ladder is judged on — is inflated by thumbs-ups on invoice links. Build item 5. Filter them. Already done on the chats page; the trend reports still count them.

The order of work

  1. Plumbing first, and it is not optional. Real-time feed, decline reason into GHL, close the 20% gap, an inbound SLA, tapback filter. Five items. Until they land, every improvement below is capped at what a next-day generic text can do.
  2. Population 1 — spend the money here. Prevention at the till plus the hot ten days. Best return per hour on the book by a wide margin, even after halving the observed LTV gap for selection.
  3. Population 2 — one message, not a programme. The day-21 cliff message in front of the second miss. 353 accounts are sitting at exactly one miss right now and nothing is in front of them.
  4. Population 3 — stop the bleed, then settle the ones with a payment history. Not a calling list. A sweep and a campaign.

1. New contracts — the opening instalment

The customer's first-ever charge on the recurring book. This is where the plan should spend its money, and it is the population the existing ladder already covers — it just cannot run yet.
Openings a year
10,943
last 12 months · measured 17 Sep 2026
Failed at the door
5,127 46.9%
5,127 agreements a year
Missed at the door
$1,136,232
opening instalments only, per year
Last week
60
of 138 opened · $17,054
Worth catching early
$461
HALF the $922 observed gap — the rest is the customer, not the rescue
This is the highest-value hour on the whole book and it is not close. An opening instalment recovered inside ten days is followed by $1,165 by day 365 against $243. Do not read all of that as the value of rescuing somebody. A customer whose payment we can recover in days is, by nature, a better payer than one we cannot, and would have paid more regardless — so most of the gap is selection. This plan counts half of it, $461, as something the rescue creates. Even halved it dwarfs the instalment itself. /opening-payment, 16 Sep 2026; halving is a judgement, agreed 17 Sep

Prevention — the part that is not on the phone

LeverSizeEvidenceStatus
Card quality at the point of sale~33 /wk Early-access neobank cards are 19.0% of first instalments but 32.3% of the misses, failing 81.4% against 39.8% for a traditional card — and they recover worse too. Sutton Bank (Cash App/Chime) 87.1% on 309. Against JPMorgan Chase 6.5%. /first-miss-handoff, 16 Sep 2026 Nothing in place. The lever is at the till — a second card, or a different funding method, taken at signing.
No card on file at all6.5% 714 of 10,973 scheduled invoices hold no card. Square cannot attempt them, so they produce no decline code, land in no bucket and appear on no list — and recover 6.3% next cycle against 28.2%. 86 of the worst 100 were paying normally and their card came off. /first-miss-nocard, 16 Sep 2026 List built, never worked. Never tell them their card was declined — nothing was attempted.
The charge date~11pp The 31st is our most-chosen charge day and the second worst-performing — 38.9% against 49.5% on the 1st. Moving a date is the cheapest fix we own and needs no conversation. reference_crm_paydays Available now. Can be offered at signing and at day 10.
The day-before message~30 /day Nobody sends anything before a first payment — not us, not Square. 600 of 600 recurring invoices are set to EMAIL, exactly 2 in the business are SMS, and 577 of 600 carry no reminder at all. Checked across 439,694 note lines: no proactive pre-payment message exists. /first-miss-handoff, 16 Sep 2026 Drafted, not sent. Hold 10% back as a control — the effect is UNKNOWN and could be negative.
Do not fix the pre-notice by switching Square's own reminders on. Square's template is an "you have an invoice to pay" email. Send that to someone whose stored card fires tomorrow and a proportion pay manually as well — a duplicate charge on a first payment is the fastest route to a chargeback there is. Same reason the drafted message carries no pay-now link.

The ten days that matter — the ladder, with this week's corrections

Unchanged from the handoff except where marked. new is added by this week's evidence; blocked cannot run until the plumbing lands.
−5
Pre-notice — the relationship message. No ask.The only step that reaches someone while nothing has gone wrong, which is the only time a reply costs them nothing.
−1
Card-ready message. Names amount, date, last four.Carries the neobank line. No pay link — the stored card fires tomorrow.
0
The charge fires and fails.Square attempts once and never again — 0.90 failed charges per missed cycle. Everything after this is us or nobody.
0 +2h
Reason-routed text + the pay link.blockedDay 1 is 48% of everything the ten-day window ever returns. Today the fastest this fires is 23.2 hours, so this step does not exist yet.
1
Second touch, different channel (email).A dead phone is not a dead customer. Suppressed instantly if money lands.
2
First call.By day 3 the ten-day window has given up 71% of everything it will return.
3
Second call, different time of day.Right-party contact runs 15–25%, so one attempt reaches about one person in five. Three attempts at different hours is why the ladder budgets three.
5
Third call + text.Day 5 is 84% of the ten-day return. After this the curve flattens hard.
7
The communication ask — Pay · Arrange · Can't this month.No payment demand. "Can't this month" is a success. This week proves people do answer it — 21 of 45 texted replied, and zero opted out. What nobody owns is what happens next.
7+
Replied-but-unpaid queue. Named owner, same-working-day SLA.new this week16 of the 45 still-unpaid had already answered us. Two were plainly waiting: one asking for the payment link and offering Apple Pay, one saying they had already paid. A reply that goes nowhere is worse than no reply — it spends the goodwill and banks nothing.
10
Arrangement offer — move the date, or split it.Not dead, just slow: recovery runs 20.1% at day 10 to 26.4% at day 30.
21
Next-charge warning — the cliff message.The highest-value automated message in the ladder, and it now also serves Population 2. See the next tab.

2. Early life — opened 10 to 60 days ago

1,599 live agreements in that window. 849 of them — 53.1% — have missed at least one charge, and $254,182 has been attempted and refused inside the window. measured 17 Sep 2026
This cohort has one dominant fact and it makes the plan simple: whether the OPENING was paid decides almost everything that follows.

Opening failed → 72.4% are still on a miss streak today, and they have banked an average of $84.
Opening paid → 8.1% are still on a streak, average banked $320.

Nine times the failure rate and a quarter of the money. So Population 2 is mostly not its own problem — it is Population 1 arriving late. The right response is to finish the opening job properly, not to build a second programme beside it.

The four groups, and only two of them are work

Where they standAccountsBanked so farWhat it actually is
Clean — never missed750 46.9%$246,943Leave alone. 46.9% of the cohort.
Missed the opening, recovered204 12.8%$56,997Working as intended. This is what the ladder is for.
Paid the opening, missed later110 6.9%$27,978Retention. They have proved they can pay. Smallest group, warmest.
Missed the opening, never paid a cent503 31.5%$0A sale that never began. Biggest group after clean, and the whole problem.
503 accounts — 31.5% of everything opened in the last two months — have never paid us a single cent, and $161,930 has been attempted and refused on them. These are not debtors. They are sales that never started. Treat them as a sale rescue with the studio's own voice, not as a collections case with a collector's — and note that 84.9% of them are soft declines, so the card is not the obstacle.

The intervention point — and there is only one

Sitting at exactly ONE miss
353
right now, in this cohort
At two misses
231
the value has already gone
At three or more
21
on their way to Population 3
Next charge paid after 1 miss
44.0%
measured 17 Sep 2026
After 2 misses
23.5%
it nearly halves
The collapse is between miss one and miss two, and it is the whole argument for this tab. Given one miss the next charge is paid 44.0% of the time; given two, 23.5%; given three, 16.2%; given four, 14.6% — the curve is nearly flat after that. Arguing about a cut-off at four misses is arguing over what is left after the loss has already happened.

Two measurements agree on the shape and differ on the level: charge-attempt-side (above, 17 Sep 2026) reads 44.0% → 23.5%; invoice-side reads 20.8% → 12.9% (/zombie-reasons, 7 Sep 2026). The invoice view is lower because it counts cycles where no charge was ever attempted as unpaid, which the attempts view cannot see. Quote whichever you name — never mix them.

So the plan for Population 2 is one message and one list

  1. The day-21 cliff message, fired at everyone on a streak of one. It already exists in the ladder and it is the only thing that can sit in front of the second miss. 353 accounts qualify today. Name both the arrears and the amount about to be taken.
  2. Split the never-started 503 out into a sale-rescue list, worked by the studio rather than the debt desk, with the studio's voice and the original booker where we still have them. A first-ever customer who has paid nothing has no relationship to collect against — only one to start.
  3. The 110 who paid then stumbled are a retention call, and they are cheap — they are the smallest group, they have proved the card works, and 91.8% of their declines are soft.

3. Zombie — four or more consecutive failed charges

9,801 accounts whose most recent run of charges are all failures. $14,601,622 has been attempted and refused across them. This is the biggest number in the plan and the last place to spend an hour — but two specific things inside it are worth real money. measured 17 Sep 2026
Zombie accounts
9,801
4+ consecutive failed charges
Never paid a cent
4,687 47.8%
$6,691,378 — never customers
Paid before going quiet
5,114 52.2%
banked $3,064,550 first · avg $599 over 3.0 payments
Still being charged
2,867
$611,841 a cycle fired into the void
A deep run is NOT death
19.7%
2,286 of 11,622 came back and paid again
The one genuinely encouraging number in this whole plan. Of the 11,622 accounts that have ever hit a four-or-more run, 2,286 went on to pay us again — 19.7% — and they have paid $1,024,771 after going deep, an average of $448 each over 2.7 payments. One in five comes back. And every single one of those was a person getting hold of them, because nothing on this book charges a card a second time on its own.

First: stop the bleed. This is free and it is not a collections job.

2,867 zombie accounts are still being charged. 3,100 failed charges were fired at them in the last 30 days and $611,841 a cycle is being attempted into the void. The series mints a fresh invoice every cycle forever — failures never feed back into the schedule, and the Square Invoices API cannot end a series, so this has to be a nightly sweep, not a switch. /zombie-reasons, 7 Sep 2026

This costs us three ways: processing on charges that cannot pass, a chargeback surface on cards the issuer has already declared finished (2,052 later charges put $385,210 at cards that could not pass in Jun–Aug), and a book whose reporting is polluted by accounts nobody believes in.

Then: split the pile in two, because it is two different things

GroupAccountsMoneyWhat it is, and what to do
Paid before going quiet
1,469 of them still being charged
5,114 52.2%$3,064,550
already banked
A real customer who stopped. Average $599 over 3.0 payments — though 1,906 of them made exactly one payment and then died, which is a first-cycle failure wearing a zombie's clothes. This is the settlement campaign. They have a payment history, a relationship and a reason to answer.
Never paid a cent4,687 47.8% $6,691,378
never collected
Never a customer. $6,691,378 that has only ever existed as an attempted charge. Chasing these as debt is chasing a sale that never happened. Worth a root-cause afternoon, not a collector's month — 85.6% are soft declines, so something is going wrong at signing, not at the bank.

Settlement — priced off what reductions actually returned

Discount late and shallow, and the evidence is unusually clear about the price. A reduction under 25% of balance returned $0.74 per $1 given away. At 50–75% it returned $0.14. Clearing a balance outright returned −$0.03 — we paid for the privilege. So the settlement ladder opens at day 40, caps at 25% of balance, and anything deeper needs an approver after day 60.

And the trap that makes this rule non-negotiable: 600 of the 945 accounts we have reduced had no failed charge at all — 72% of the money given away went to people who were never fighting a card. The ladder structurally prevents that by making nothing below day 31 discountable. /reductions + /first-miss-handoff, 16 Sep 2026

The plan for Population 3

  1. Nightly sweep to stop charging the 2,867 live zombies. Not a collections decision — an operational one. Do this first and it pays for itself in avoided chargebacks alone.
  2. Settlement campaign on the 1,469 live accounts that have paid before. Capped at 25%. The base rate says one in five of a deep-run account comes back for about $448, and these are the half of the pile with a relationship to restart.
  3. Do not build a calling list for the 4,687 who never paid. Send them the settlement message by text, take what comes, and spend the analyst time instead on why $6,691,378 of agreements were signed by people whose card never once worked.
  4. Expect the ceiling to be low and say so up front. 3,936 of the pile last paid us something over 240 days ago. A campaign that converts 5% of the live ever-paid group is a good campaign, not a disappointing one.

What has to be built, in order

Three of these are blocking: the plan does not reach its stated value without them, and shipping the messages first would produce a next-day generic text and a reply nobody reads. That is measurably worse than the current position, because it spends goodwill it cannot convert.
#ItemPriorityWhy it is there
1Event-driven feed into the debt sub-accountBLOCKINGReplaces the daily Google-Sheet drop. Until this lands the first text cannot leave inside 23 hours, and day 1 is 48% of everything a miss ever returns. Every value in this plan is capped by it.
2Decline reason + bucket as GHL custom fieldsBLOCKINGNo reason field exists on that sub-account today. Without it every message is generic and the four-way routing cannot happen — including the one code a customer can fix in 30 seconds in their banking app.
3Daily feed reconciliation + gap alarmBLOCKING12 of 60 failures last week never reached the sub-account at all. A fifth of the queue is invisible to every workflow and every report.
4Replied-but-unpaid queue, named owner, same-day SLAHIGH16 of 45 still-unpaid had already answered. A reply that goes unread spends the goodwill and banks nothing — and a customer's agreement to pay $885 once sat unread until it was found by accident.
5Tapback filter in the trend reportsHIGHReply rate is the metric the ladder is judged on. Loved "…" arrives as an ordinary inbound SMS. Fixed on /first-miss-week-chats; /debt-trend still counts them, and its cache holds no bodies so it cannot be corrected retrospectively.
6Nightly sweep to stop charging dead seriesHIGH2,867 accounts, 3,100 failed charges in 30 days, $611,841 a cycle. The Invoices API cannot end a series, so it must be a sweep. Pays for itself in avoided chargebacks.
7Apply the /pay portal bonus creditHIGHThe portal promises "+15% credited to your balance" and nothing applies it — no CRM write, no ledger write, no Square credit. Latent rather than live (zero of 83,623 recurring payments in 2026 carry the note), but it must be fixed before any traffic is sent there.
8Repoint notifyGHL off the empty sub-accountHIGHIt reads ghl_config.json, which points at a near-empty "AI Debt Collection" location. Anything it sends goes nowhere anyone is watching.
9Day −5 / −1 pre-notices, with a 10% controlMEDIUMDrafted, never sent. Hold 10% back and send them nothing — the effect is UNKNOWN and could be negative; telling someone a charge is coming also lets them move the money out.
10Sale-rescue list for the never-startedMEDIUM503 accounts in the 10–60 day window have never paid a cent. Studio voice, not collector voice.
11Card quality prompt at the point of saleMEDIUMNeobank cards fail 81.4% against 39.8%. The lever is at the till and no phone call can replace it.
12Settlement campaign, capped at 25%, opening day 40MEDIUM1,469 live zombies with a payment history. Under 25% returns $0.74/$1; deeper collapses to $0.14.
Do not send step one of any ladder until items 3 and 4 are done. A ladder whose replies go unread is worse than silence — this week 16 people answered a text about a missed payment and nothing came back, and two of them were explicitly waiting on us. Scaling the sending without fixing the answering multiplies that.

What it is worth — with the assumption behind each line

LineRange a yearWhat has to be true
Population 1 — lift 30-day recovery on failed openings by 5pp
from 26.4% to 31.4%
$57k – $236k 5,127 failed openings a year × 5pp = 256 more agreements recovered. The low end values each at the opening instalment alone (~$222). The high end values each at $461 — HALF the $922 observed gap, because most of that gap is selection: an account we can recover quickly belongs to a better payer who would have paid more anyway. Halving it is a judgement, not a measurement. Both ends depend entirely on build item 1.
Population 2 — the cliff message in front of the second miss not modelled Deliberately not given a number. 353 accounts sit at one miss today and the hazard drops 44.0% → 23.5% at the second, but we have never run this message, so its conversion is UNKNOWN. Borrowing a rate from the collector data would measure a human conversation, not an automated text. It needs a holdout arm to produce a real figure.
Population 3 — stop charging dead series cost, not revenue 3,100 failed charges in 30 days on cards that cannot pass. Saves processing and, more importantly, chargeback exposure — $385,210 was aimed at already-dead cards in a single quarter.
Population 3 — settlement on the live ever-paid ~$130k at the base rate 1,469 accounts × the measured 19.7% deep-run return rate × $448 average. Read this as the size of the pool, not as incremental revenue — 19.7% is what the book already achieves with the effort it already spends. The incremental question is whether a priced settlement beats that, and nobody has tested it.
Two numbers in this plan are honestly unknown, and they are marked that way on purpose. We have never run an automated pre-notice and we have never run an automated cliff message, so their conversion rates do not exist. Every conversion figure we do have for a second attempt is selected — a collector only puts a card through once the customer has agreed to pay, so of course it converts. Quoting one of those as the expected rate for something automated is the single most misleading thing these reports can do. Both new messages need a no-contact control arm, or they will be judged against a human conversation rate and look like failures however well they do.
The plan — built 2026-09-17 22:00 UTC by scripts/reports/report_money_plan.js

How every number here is made

The population

A failed first payment = a Square customer whose first-ever charge attempt in the recurring book lands between 2026-11-09 and 2026-11-15 and did not complete. The attempt history searched runs from June 2023 to now across both attempt files, so a customer with any earlier charge anywhere in it is not counted as an opening. Only the six Recurring* locations are in scope — deposits, studio sales and office takings are excluded, because they are not instalments.
"Last week" is the last complete MONDAY-to-SUNDAY week — here 2026-11-09 to 2026-11-15 — not the last seven days. A rolling seven-day window always contains part of the week we are currently in, which is a different question and makes the name wrong. The current week is never included, and today is a part-day and would read as a collapse. Run with --from / --to for any other period.
"Not paid" means no completed charge of any amount on that customer after the failed opening — not merely that the opening amount is outstanding. Someone who paid a different figure, or paid part of it, counts as money in and is off the unpaid list.
The decline reason is the issuer's own, read off card_details.errors on the failed payment. Where Square recorded no reason the row shows "no reason given" rather than being assigned one.

The cross-check

Matched on phone first, then email, then exact name, against pcTyOadbzBqZO7v3cbwn — the live US Debt Collection sub-account. Not the location in ghl_config.json, which is a near-empty account that 403s with this token.
"Texted" means at least one outbound SMS dated on or after the moment the charge failed, on any conversation belonging to that contact. An older text from a previous cycle does not count. "Replied" is an inbound SMS after the same moment.
No message body is stored. The only thing read out of a reply is whether it starts with 1, 2 or 3 — the options the workflow's own opening text offers.

What this page cannot tell you

Phone calls. The debt team dials through GoTo and those calls do not write back into GHL, so a zero in the calls column is a limit of the source, not evidence that nobody rang.
Cause and effect. Whether a person was texted is not random — the ones who pay immediately drop out of the chase, so any comparison of "texted" against "not texted" is selected at both ends and cannot be read as the effect of texting.
Nothing here is automated recovery. No system on this book charges a card a second time on its own. Every later payment is a person acting.

Sources

Reports/finance_cohort/square_attempts.jsonl + square_attempts_pre2025.jsonl — the charge attempts, refreshed by scripts/reports/pull_square_declines_history.js.
Square /v2/customers/{id} — name, phone, email, reference id.
GHL /contacts/, /conversations/search, /conversations/{id}/messages — all GET.
Built by scripts/reports/report_first_miss_week.js at 2026-11-17T20:08:31.025Z.

How every number here is made

The three populations

All three are cut from the same source — Reports/finance_cohort/square_attempts.jsonl plus the 2023-06 backfill, deduped by payment id, restricted to the six Recurring* locations, grouped by Square customer. Deposits, studio sales and office takings are excluded because they are not instalments. Measured 17 Sep 2026 against data complete to 16 Sep 2026.
Population 1 = the customer's first-ever attempt in that history. A customer with any earlier charge anywhere in it is not an opening, so it cannot pick up a mid-contract miss.
Population 2 = accounts whose first attempt was 10 to 60 days before the data end. "Missed" means at least one non-COMPLETED attempt. "Never paid a cent" means zero COMPLETED attempts, ever.
Population 3 = accounts whose trailing run of attempts are all failures, four or more deep. This is the charge-attempt view. It is not the same population as /zombie-reasons, which counts series still billing from the invoice cache and reported 2,656 on 7 Sep 2026. The attempts view is larger because it includes long-dead accounts nobody is billing any more; the comparable live figure here is the 2,867 still being charged in the last 30 days. Name which one you are quoting.

Where the two hazard curves disagree, and why

Charge-attempt-side (17 Sep 2026): after one miss the next charge is paid 44.0%, after two 23.5%, three 16.2%, four 14.6%. Invoice-side (/zombie-reasons, 7 Sep 2026): 20.8% then 12.9%, 7.9%, 5.0%. The invoice view is lower because it counts cycles where no charge was ever attempted as unpaid — 13.3% of the zombie pile was never attempted at all — and the attempts view cannot see those. Both show the same shape and the same conclusion: the collapse is between miss one and miss two. Never average them and never mix them in one sentence.

What is quoted from elsewhere

/opening-payment (16 Sep 2026) — the $922 LTV difference, the 20.1%/26.4% recovery curve.
/Studio1_First_Miss_Handoff.html (16 Sep 2026) — the ladder, the neobank measurements, the no-card 6.5%, the day-1-is-48% curve, the reduction returns, the Square-sends-nothing finding.
/first-miss-week + /first-miss-week-chats (17 Sep 2026) — the 23.2-hour first text, the 12 who never reached the GHL, the 16 who replied and still owe, the tapback finding.
/zombie-reasons (7 Sep 2026) — the series mechanism, the invoice-side hazard curve, the never-attempted share.
/decline-buckets (1 Sep 2026) — the soft/hard/structural split and the $385,210 put at dead cards.
/reductions — what a discount actually returned per dollar.

What this plan deliberately does not claim

No automated conversion rate. We have never run an automated pre-notice or cliff message, so both are UNKNOWN. A trial needs a control arm or it gets measured against a human conversation rate.
No causal claim about texting. Whether a person was texted is not random — the ones who pay immediately drop out of the chase — so any texted / not-texted comparison is selected at both ends.
Nothing here is automated recovery. No system on this book charges a card a second time on its own. Square attempts once on the due date and never again, measured at 0.90 failed charges per missed cycle. Every second attempt is a person, which is why none of the money in this plan arrives without someone doing something.
Phone calls are invisible. The debt team dials through GoTo, which does not write back into GHL, so any call count from the GHL side is a floor, not a measurement.
Built by scripts/reports/report_money_plan.js at 2026-09-17T22:00:25.537Z.