You send a note about an overdue invoice. Three days later, a reply lands. Most agency owners read it for content: did they say when they're paying? But the content is often the least useful part. The shape of the reply — how fast it came, who sent it, how much they explained — tells you more about whether money is actually coming than any sentence in it.
Here's how to read that, and what to do with each read.
Speed is the strongest signal
A reply inside a few hours almost always means the invoice is on someone's desk and they can act on it. It doesn't guarantee payment, but it means you're talking to a person with the file open. That's the cheapest situation you'll ever be in.
A reply after five to ten days usually means your email sat until someone did an inbox sweep. The invoice isn't in a process. It's in a pile. That's not hostility — it's a filing problem, and filing problems get solved by making it easier to file.
The reply that comes within an hour of your third note, when your first two got nothing, is a different animal. Something changed. Usually it's that the note finally reached someone who can spend money, or the amount finally crossed a threshold that mattered. Note who sent it. That's your new contact.
Specificity beats warmth
This is the one most people get backwards. A short, slightly cold reply that names a date is worth far more than a warm apology that names nothing.
"Processing 3/15" is a commitment. It has a date, and dates create accountability on both sides.
"So sorry about this! Things have been crazy here, I'll look into it and get back to you." is friendly and contains zero information. No date, no amount, no owner. Warmth here is often a substitute for capacity — the person genuinely means it and genuinely cannot make it happen.
When you get the warm-but-vague reply, don't match its energy. Reply with one closed question: "Totally understand — is the 14th realistic, or should I plan around month-end?" You're not pushing. You're converting a feeling into a date.
Who replies tells you where the invoice is
If your account contact replies, the invoice is still on the relationship side of the house. If someone from finance or AP replies, it's entered a system — which is slower but far more reliable. Systems pay. People forget.
The worst version is your contact replying on behalf of finance: "I checked with accounting and they said it's in the queue." That's two layers of hearsay. Ask politely to be connected directly. Most people are relieved to hand it off.
The specific tells worth learning
A few patterns that hold up across hundreds of threads:
Questions about the invoice itself — line items, PO numbers, the wrong billing address — are good news, even though they feel like stalling. Someone read the document. Fix it same day and you usually get paid on the original cycle.
A dispute raised for the first time weeks after the due date is usually about cash flow, not the work. Treat it as such. Asking "would splitting this across two months help?" often gets a faster yes than defending your scope.
Silence after a promised date passes is the clearest negative signal there is — clearer than any harsh reply. Someone who says the 15th and goes quiet on the 16th is avoiding, not disputing. That's the moment to change the channel: a phone call, or a note to a different person at the company.
"Can you resend the invoice?" on the second or third ask is sometimes real and sometimes a reset button. Resend it, but attach it to a short note with the original date and a proposed new one, so the clock doesn't start over.
Turn the read into a rule
The point of reading replies isn't insight. It's deciding what happens next without re-deciding every time. Write down three rules for your shop:
- Reply with a date → note the date, follow up the morning after if nothing lands.
- Reply without a date → one closed question, same day, while you're still in their inbox.
- Promised date passed in silence → escalate the channel, not the tone.
That's most of the work. The tone stays the same throughout — you're a business that expects to be paid, not one that's angry about it. Escalation is about who and how, almost never about volume.
This is exactly the pattern FetchDue automates: it chases from your own mailbox, reads what comes back, distinguishes a real date from a soft one, proposes a payment plan when the reply signals cash flow rather than a dispute — and drafts the next step for you to approve. You still decide what goes out. You just stop being the one who has to notice.