Verified against ChatGPT · 2026-08-10
Write an invoice follow-up sequence that escalates differently for a strategic account than a small one
Produces a staged overdue-invoice follow-up sequence with tone and escalation calibrated to account tier, so a strategic account doesn't get the same blunt reminder cadence as a small overdue client.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Write a follow-up sequence for an overdue invoice. I need this calibrated by account tier — a strategic account and a small transactional account should not get the identical escalation path, because damaging one relationship costs the business far more than the other. INVOICE DETAILS Invoice #INV-4471, $18,400, due July 15, 2026 DAYS OVERDUE 22 days overdue as of today ACCOUNT TIER Strategic account — top-5 by annual contract value, two-year relationship RELATIONSHIP CONTEXT Our usual AP contact there is out on leave; a new contact just took over invoicing PRIOR PAYMENT HISTORY Always pays within 5-10 days of due date historically, no prior late-payment pattern Build a three-stage sequence: a first reminder (friendly, assumes oversight), a second follow-up (firmer, references the first message, asks for a specific commitment), and a final notice (states the next concrete step if payment doesn't arrive by a stated date). Calibrate tone and timing gaps between stages based on account tier and relationship context — a strategic account with a clean payment history should get more benefit-of-the-doubt language and a longer gap before the firmer stage, while a small account with a pattern of late payment in its history should move to firmer language sooner. Every stage must ask for a specific, checkable commitment (a payment date, or an explanation with a new date) rather than a vague "please remit at your earliest convenience," since an open-ended ask is easy to ignore and doesn't create anything to follow up against next time. Reference the actual invoice number and amount in every stage, not just the first — a recipient scanning a follow-up sequence should not have to dig up the original invoice. WHAT NOT TO DO Do not use identical escalation language across tiers — a template that ignores relationship context defeats the purpose of asking for it. Do not threaten a specific consequence (late fees, collections, service suspension) unless I've told you that's actually our policy — ask me to confirm rather than assuming a standard one. OUTPUT FORMAT Three labeled email drafts (Stage 1, 2, 3) each with a subject line, and a one-line note before each stage giving the recommended gap in business days before sending it and why that gap fits this account tier.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Calibrating tone and stage-gap by account tier and payment history directly targets a real cost asymmetry that a generic follow-up template ignores: the business cost of over-escalating with a strategic account that simply had an internal process hiccup is much higher than the cost of moving faster to firmness with a small account that has a documented late-payment pattern, and a one-size-fits-all sequence optimizes for neither case well. Requiring a specific, checkable commitment in every stage — a date, not "at your earliest convenience" — matters mechanically because an open-ended ask gives the recipient nothing concrete to be held to next time, whereas a stated date creates an unambiguous trigger for whether stage two is warranted at all; this is the difference between a follow-up sequence that actually resolves and one that just repeats the same soft ask three times. Referencing the invoice number and amount in every single stage rather than only the first prevents a common real failure where a recipient who missed or deleted the first email has to reconstruct context from a later, firmer-toned message with no reference point, which reads as needlessly aggressive out of context. The explicit instruction not to threaten a consequence unless the user has confirmed it's actual policy is a guard against GPT-5.1's tendency to fill in a plausible-sounding standard business practice (late fees, a collections referral) when asked to write a "final notice" — that's a specific claim about consequences that could be untrue for this business and would misrepresent policy to a customer if sent as written.
What you get back
Stage 1 (send now, day 22): "Hi [contact] — hope the transition is going smoothly. Just flagging that Invoice #INV-4471 ($18,400, due July 15) hasn't come through yet — could you confirm a payment date on your end?" Stage 2 (send in 5 business days if no response): firmer, references Stage 1, asks for a specific date or explanation by end of week. Stage 3 (send in 5 more business days): states the next concrete step — to be confirmed with the business's actual overdue-account policy before finalizing.
Verified against
ChatGPT GPT-5.1 · 2026-08-10
Changelog
- 2026-08-10 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
