Templates · 10 messages
Payment reminder iMessage templates
The payment texts that get paid are short, name the amount and the date, and give the customer a one-tap way to complete the transaction.
Free to copy and adapt, no signup
Ground rules before you send
- The invoice and the client relationship are your consent basis. These are service messages about money they agreed to pay.
- Amount, invoice number, payment link, every time. A reminder that requires finding the original email collects a week slower.
- Assume the oversight until the second miss. The first reminder is a nudge between partners, never a demand.
- Escalate tone by stakes, not by mood: friendly, direct, formal, final, each with a stated next step and date.
- Money conversations stay factual in writing. State amounts, dates and consequences, never frustration; screenshots outlive feelings.
1. The invoice heads-up
hey [first name], invoice [number] for [amount] just went to your inbox, covering [work description]. due [date]. link if texting is easier than digging through email: [link]. any question about a line item, ask here.
When to send: The same hour the invoice goes out.
Why it works: A heads-up text stops the "never saw it" problem before it exists, and putting the payment link in the thread means the invoice can be settled from a phone in traffic. The line-item invitation surfaces disputes now instead of on day 40.
2. The upcoming-due nudge
[first name], friendly one: invoice [number], [amount], comes due [date]. if it's already queued up in your system, ignore me entirely. if it slipped, here's the link: [link].
When to send: Three days before the due date, on invoices above your care-about threshold.
Why it works: "Ignore me entirely" makes the reminder polite to the client who already paid it, which is the tone risk that stops most people from sending pre-due reminders at all. This one text moves a surprising share of payments from late to early.
3. The due-today reminder
hey [first name], invoice [number] for [amount] is due today. takes about a minute from this link: [link]. if something's holding it up on your end, tell me now and we'll sort it before it becomes a thing.
When to send: Morning of the due date, if payment hasn't landed.
Why it works: "Before it becomes a thing" names the shared interest in keeping this boring, and the invitation to flag problems converts silent late-payers into clients with a plan. The one-minute framing removes the last excuse.
4. The first overdue nudge
[first name], invoice [number] ([amount]) slipped past its due date on [date]. no drama, these things fall through cracks. can you get it through this week? link: [link]. if there's a snag, cash flow, an approval chain, whatever, say so and we'll work something out.
When to send: Three days after the due date passes in silence.
Why it works: Naming cash flow as a speakable reason is the unlock: clients hide payment problems until invited not to, and a hidden problem cannot be solved. "This week" sets a soft deadline that most good-faith clients beat.
5. The direct overdue follow-up
[first name], I need to get direct: invoice [number] for [amount] is now [days] days past due and I haven't heard anything. I need one of two things by [date]: payment ([link]), or a call where we agree on a real date. which one can you do?
When to send: Two weeks past due, after the friendly nudge got silence.
Why it works: The either/or demand is firm without being hostile: both options are reasonable, so choosing neither becomes the unreasonable act. Announcing the tone shift ("I need to get direct") marks the escalation clearly, which is what makes the earlier friendliness credible in hindsight.
6. The payment-plan offer
[first name], thanks for being straight with me about the cash crunch. proposal: [amount] split into [number] payments of [amount], first one by [date], done by [date]. if you're good with that, reply yes and I'll send it in writing. it keeps us working together, which is the outcome I want.
When to send: The moment a client admits they can't pay in full.
Why it works: A concrete plan converts an awkward confession into a handshake, and "the outcome I want" reframes the arrangement as partnership rather than mercy. Clients who get offered a plan at their low point become the most loyal accounts on the books.
7. The failed-payment notice
hey [first name], the card on file for [service] bounced this morning, almost always an expiry thing. update link: [link], takes a minute. service keeps running until [date], so there's no fire, but sooner beats later.
When to send: Within hours of a failed subscription or auto-pay charge.
Why it works: "Almost always an expiry thing" removes the embarrassment that makes people avoid the fix, and stating the no-cutoff date builds trust while quietly naming the deadline. Most involuntary churn is exactly this message not being sent fast enough.
8. The renewal-charge notice
[first name], heads up rather than surprise: your [service] renews [date] and the card on file gets charged [amount]. all good? do nothing. want to change anything first, plan, card, scope, reply here before then.
When to send: Seven to ten days before an auto-renewal charge.
Why it works: A payment link in the text removes the "where do I pay?" friction that costs you money. Track open rate and adjust send time.
9. The final notice
[first name], formal one, because we're at that point: invoice [number], [amount], [days] days past due, multiple follow-ups without response. without payment or an agreed plan by [date], the next step is [real consequence: work pauses / the account goes to collections / late terms kick in]. none of that is the outcome I want, and one reply stops all of it. talk to me.
When to send: Thirty to forty-five days past due, after every softer touch has been ignored, and only with a consequence you will actually execute.
Why it works: A named consequence with a date is what separates a final notice from a fourth nudge, and an empty threat destroys every future deadline you set. "One reply stops all of it" keeps the door open to the very end, which is how a real share of final notices still resolve as payments.
10. The payment-received close
[first name], payment landed, thanks for sorting it. receipt's in your email. and for what it's worth: good clients who communicate through a tight month are the ones I go to bat for on scope and timelines. consider it noted.
When to send: The day a late payment or completed plan clears, especially after a hard conversation.
Why it works: The second reminder is direct about consequences and gives a real deadline. Late payments cost more than lost sales.
Questions
When should the first payment reminder go out?
Before the invoice is late: a heads-up when it goes out and a nudge three days before it is due. Pre-due reminders feel awkward and collect dramatically better, because they catch the honest majority whose only problem is a busy inbox. The templates excuse anyone who already has payment queued.
How do I chase payment without damaging the relationship?
Escalate on a stated ladder and invite the real conversation early. Friendly nudge, direct follow-up, formal final notice, each announcing its own tone, reads as professional rather than emotional. Clients hide money problems until asked, and a payment plan in week two beats a collections file in month three.
Can I text clients about unpaid invoices?
Texting your own client about their own invoice is a service message on an existing commercial relationship, which is solid footing. Keep it factual: amount, date, link, next step. Consumer debt collection has its own regulations these templates are not written for.
Keep going
Want reminders that send on schedule without you playing collector?
Book a demo and we'll text you the reminder ladder from a live line while you're on the call, so you see exactly what your clients would see. $249 per line per month, unlimited messages, no A2P registration required.
Book a demo