Client Gone Silent After the Invoice? The Ghosting Playbook

Silence is the hardest state in accounts receivable, because it carries no information and your brain fills the vacuum with the worst available story. Are they insolvent? Furious about something? Simply disorganized? After twelve years of finance and hundreds of gone-quiet accounts, here is the base rate that should calm you before we get tactical: most invoice ghosting is logistical, not hostile. The contact left, the email filters to a folder, the approver is on leave, the company restructured AP. Genuine deadbeats are the minority. But the playbook has to work for all cases, so it escalates through information-gathering before it escalates through pressure.

Rule one: silence changes the medium, not the tone

The instinct after three unanswered emails is to write a fourth, longer, sharper email. Resist it. Emails four and five to a silent address have close to zero marginal effect; whatever swallowed the first three will swallow them too. The move is lateral: change the channel, then change the human.

Channel switch: the phone. Two unanswered emails is my trigger to call. Not to ambush, to diagnose: a two-minute call resolves what five emails cannot, because voicemail-and-phone bypasses whatever email problem may exist, and because ignoring a pleasant human voice requires active rudeness in a way ignoring an inbox does not. I wrote the full call structure and script here; the one-line version is: open with curiosity, not accusation.

Human switch. If your contact stays dark, they may be the blockage: departed, sidelined, or embarrassed. One professional note to a second person, the owner, the finance lead, whoever LinkedIn suggests, reroutes around dead contacts: "I have been unable to reach Tom regarding invoice 4521 and wanted to check whether he is still the right contact before I escalate further. Could you point me to the right person?" That email is polite, factual, impossible to characterize as aggressive, and it produces answers within days with startling reliability, partly because nobody inside a company wants a vendor telling their boss they went dark.

The closing-the-file email

Sales teams have long known that the "breakup email" outperforms the follow-up email, and the same psychology works in collections. When channel and human switches have both failed, send this:

"Hi Tom, I have tried reaching you several times about invoice 4521 for $8,400 without a response, so I am going to close the file on my side and move this to our formal process, which I would honestly rather avoid. If there is something going on, a dispute, a cash situation, anything, this is the moment to tell me, because after Friday it is out of my hands."

The phrase "closing the file" triggers responses that six polite reminders could not, because it converts open-ended nagging, which costs the silent party nothing, into an ending, which costs them optionality. And note what the email offers alongside the deadline: an explicit invitation to disclose a problem. A meaningful share of ghosting is embarrassment about cash trouble, and the customer who finally admits it can be moved to a structured plan you control instead of a write-off you absorb.

Reading the silence itself

While you run the ladder, the account's history is talking. A previously chatty customer who went silent immediately after receiving the invoice may have a dispute they have not voiced; probe for it directly ("if anything about the invoice looks wrong, tell me and we fix it today"). A customer who made a promise and then went dark has told you the promise was a stall. And silence combined with other signals, staff departures you noticed on LinkedIn, their own customers complaining publicly, is not a communication problem at all; it is insolvency risk, and it moves you straight to the formal ladder: final notice with a date, then the collections decision made on triggers, not temper.

Tracking which accounts have gone quiet, for how long, and against which promises is exactly the kind of ambient memory that leaks when you have thirty customers, which is the honest reason we built silence detection into RevCollect: it flags the account whose reply pattern broke, and drafts the channel-switch step with the history attached. Bias disclosed. The ladder stands on its own: two emails, then the phone, then a different human, then the closing-the-file email, then the formal process. Most ghosts resolve at step two or three, and the ones that do not were never going to answer email number six anyway.

FAQ

How many unanswered emails before I call about an invoice? Two. Further emails into silence have near-zero marginal effect; the phone diagnoses what email cannot.

Is it appropriate to contact someone else at the client company? Yes, after your contact has ignored two emails and a call. Keep it factual and procedural: you are verifying the right contact before escalating, which no reasonable company resents.

What if the client opened my emails but never replies? Treat read-but-silent as probable avoidance of a difficult message, often a dispute or cash trouble. Invite the disclosure explicitly and pair it with a deadline; the closing-the-file email is built for exactly this case.

When does ghosting justify collections or legal action? When the full ladder is exhausted and a final notice with a specific date has passed in silence. Silence through a stated deadline is an answer, and the formal process is the correct response to it.