A finance problem with a messaging component
Debtor days — the average time between invoicing and payment — is mostly a commercial and process problem: payment terms, early-payment discounts, dunning policy, credit control. Messaging is one lever inside that, not the whole answer. Verified channels can reduce friction and make a reminder easier to trust and act on. They do not guarantee shorter debtor days, and any collections program that treats messaging as the fix instead of the terms, the credit decision, and the escalation process will be disappointed.
This is a practical rundown of how to structure a collections message sequence, what controls it needs, and what to measure honestly.
Why plain SMS and email under-perform for this use case
- Email — routinely lands in a spam or promotions folder for transactional finance content, and there's no reliable signal that it was seen.
- Plain SMS — works as a channel, but a bare number with no branding is harder to distinguish from a scam text, especially once a market is saturated with promotional SMS.
- Voice calls — expensive per contact and dependent on someone answering.
None of this means verified channels solve collections. It means the reminder is more likely to be read and trusted if the recipient can see who it's actually from and can act in one step.
What "verified" means here
Verified SMS / RCS Business — a registered sender with a displayed brand name and logo, and support for structured content and buttons. The recipient sees a verification mark and your brand identity instead of an unfamiliar number.
WhatsApp Business templates — pre-approved message templates sent from a verified business account, which can include action buttons such as "pay now" or "request more time".
Both require registration and approval before use, and the timeline for that varies by market, by vendor, and by how complete your business verification documents are — it is not a fixed number of days you can plan a launch date around. Budget for review and possible rejection-and-resubmission cycles rather than assuming a single pass.
A message sequence, not a single reminder
A collections sequence works better as a small number of distinct messages, each with a clear job, rather than the same reminder repeated with mounting urgency words.
1. Pre-due reminder (a few days before the due date)
- Say: the invoice number, amount, due date, and a link to pay or view the invoice.
- Don't say: anything implying the invoice is overdue or that action is required — it isn't due yet.
- Depends on: the invoice being unpaid and the due date being in the future. If payment posts before send time, this message must not go out.
2. Due-date notice (on or the day after the due date)
- Say: a neutral statement that the invoice is now due, the amount, and the payment link.
- Don't say: anything that reads as a threat or implies consequences — this is a routine notice, not an escalation.
- Depends on: invoice state still unpaid at send time, checked as close to send time as your systems allow.
3. Overdue reminder (some days after due, timing set by your credit policy)
- Say: that the invoice is now overdue, restate the amount and any applicable terms (late fees, if contractually agreed), and the payment link.
- Don't say: anything not backed by the actual contract terms — don't imply legal action, credit reporting, or fees that aren't contractually provided for.
- Depends on: unpaid state, and ideally a check for whether the customer has already made contact (a support ticket, a promise to pay, a dispute) — don't send an automated overdue notice over an open conversation.
4. Escalation
- Say: whatever your credit policy actually specifies happens next — this is usually a move to human contact (a call or account manager) rather than another automated message, sometimes alongside a more formal written notice.
- Don't say: this step is not a place to introduce new claims by template; it should follow your existing escalation and, where relevant, statutory/collections process, not invent one in message copy.
- Depends on: invoice remaining unpaid after the prior steps, and on whatever internal sign-off your credit policy requires before escalation.
Adjust exact intervals to your credit terms and jurisdiction — there's no universal cadence that fits every invoice type or customer relationship.
Payment-state suppression: the failure mode to avoid
The most damaging failure in an automated collections flow is chasing an invoice that has already been paid. It happens when:
- Payment status is read from a system that updates on a delay (e.g. a nightly batch) while reminders are scheduled to run more frequently than that.
- A partial payment is recorded but the reminder logic only checks a binary paid/unpaid flag.
- A payment is applied to the wrong invoice or account and the mismatch isn't caught before the next scheduled send.
The fix is architectural, not a messaging setting: treat invoice/payment state as the single source of truth, check it as close to send time as your systems support, and make the messaging layer a consumer of that state rather than an independent scheduler working off a stale snapshot. If your payment system can't give you near-real-time state, build in a manual hold option and be conservative about automated sends near the payment deadline.
Consent and lawful basis
Collections messages are not automatically exempt from consent and marketing rules just because they concern an unpaid invoice. Depending on jurisdiction and channel:
- Service/transactional messaging about an existing debt generally has a different legal basis than marketing, but the specifics (what counts as transactional, what disclosures are required, what opt-out must be offered) vary by country and by channel — WhatsApp and RCS in particular have their own template-category rules on top of general messaging law.
- Where a channel requires opt-in (WhatsApp Business templates in most configurations), you need a lawful basis to have that number and a record of how consent for that channel was obtained.
- Quiet hours — restrictions on contacting someone outside certain hours — apply in a number of markets, sometimes explicitly for debt collection contact, and should be encoded as a rule the sending system enforces rather than left to campaign-by-campaign judgement.
This isn't a substitute for legal advice specific to your markets. Flowstates can help you implement these as operational controls — timing rules, consent records, category classification, suppression logic — but it does not provide legal compliance itself; that determination sits with you and your counsel.
Channel fallback
Verified RCS and WhatsApp coverage is not universal — handset support, carrier rollout, and per-recipient opt-in status all vary. A workable sequence needs a fallback path when the verified channel isn't available for a given recipient: typically plain SMS or email carrying the same core information (amount, due date, payment link) without assuming the richer formatting will render. Decide this fallback logic in advance rather than silently dropping the reminder when the primary channel fails.
What to measure
Track outcomes, not vanity delivery numbers:
- Payment completion rate — proportion of reminders that are followed by payment, over a defined window.
- Time-to-payment — how long after a given message payment occurs, if it occurs.
- Click-to-payment — of the people who click the payment link, how many complete payment, and where they drop off if they don't.
- Reply, complaint, and opt-out rate — a rising complaint or opt-out rate on collections messages is a signal to review cadence and tone, not something to route around.
- False-reminder rate — how often a reminder was sent for an invoice already paid or in dispute. This should be close to zero; track it explicitly, because it's the clearest indicator that your suppression logic is failing.
None of these numbers will be the same across industries, invoice sizes, or customer relationships, and we don't publish target ranges because we don't have a dataset we'd stand behind as representative of your book. Use your own baseline before and after a channel change as the comparison that matters.
Where the messaging layer fits
The teams that run this well treat the reminder sequence as one component of a broader collections workflow, not a bolt-on:
- A single source of truth for invoice and payment state.
- Cross-channel awareness (don't message someone through a second channel after they've already replied or paid through the first).
- Suppression on payment, on dispute, and on active human contact.
- A defined escalation path that a human, not a template, ultimately owns.
Flowstates can operate the messaging layer here — sending through verified channels where available, managing sender registration and template approval, enforcing suppression and quiet-hours rules, and falling back cleanly when a channel isn't available — whether that's on capacity we sell directly, routes you already have contracts for, or a mix of both.