If your business invoices or collects in instalments, you know where the money gets stuck: not with customers who refuse to pay, but with customers who forget or lose the email. A dental clinic, a school collecting tuition, a gym, a software subscription: all of them send the same reminder every month and chase the same handful of late payers. This playbook covers how to run those reminders on WhatsApp, with a payment link in the message, without breaking Meta's rules or annoying the people who pay you.
Why send payment reminders on WhatsApp instead of email or SMS?
Because the customer is already there. An email reminder lands in a tab the customer opens when they have time. An SMS arrives from a number they do not recognise, with a link they have been told not to tap. A WhatsApp message arrives in the app they use with family and suppliers, in a thread that may already hold their last appointment. Three practical differences follow:
The customer can answer in one tap. "Can I pay on Friday?" is a normal thing to type in WhatsApp and an awkward thing to do by replying to an invoice email.
The payment link opens on the phone the customer is holding, with the card or account they already use there.
The whole exchange stays in one thread: reminder, reply, link, confirmation.
Not every customer pays on the first nudge, but the reminder is read where decisions are made, and replying is easy.
What rules apply to payment reminders on WhatsApp?
WhatsApp is not an open channel for outbound messages, and collections is where businesses get this wrong. Three rules carry most of the weight.
Reminders go out as approved templates. If the customer has not written to you in the last 24 hours, you cannot send free text. The reminder must be a message template reviewed by Meta, in the utility category, with placeholders for name, amount and due date. Meta prices templates by country and category, and utility sits well below marketing; see Meta's WhatsApp Business Platform pricing documentation and our post on WhatsApp Business API pricing in 2026, by country. Once the customer replies you have a 24-hour window for free-form messages, which since October 1, 2026 Meta bills per message after the first 1,000 per phone number per month.
Write the template as utility. "Your instalment of $120 is due on October 15, here is your link" is utility. Add "and get 10% off your next plan" and it is reclassified as marketing, at the higher rate.
Consent and no harassment. The WhatsApp Business Messaging Policy requires the customer's opt-in before you message them, that you honour requests to stop, and that automated conversations offer a "prompt, clear, and direct" path to a person. Collect the opt-in when the customer signs the contract, not after the first missed payment, and keep the cadence to one message per step.
What reminder cadence works for a small business?
A cadence is a schedule plus a tone. The schedule below fits most monthly billing; the tone moves from friendly to formal as the days pass. Each step is one template.
Three days before the due date, friendly. "Hi Laura, a quick heads-up from Clínica Norte: your October instalment of $120 is due on the 15th. You can pay here whenever it suits you: [link]. Reply here if you have any questions."
On the due date, neutral. "Hi Laura, your instalment of $120 is due today. Here is the payment link: [link]. If you have already paid, thank you, and please ignore this message."
Three days late, direct. "Hi Laura, we have not received your payment of $120, due on October 15. You can settle it here: [link]. If you need a few more days, reply and we will note the date."
Seven days late, formal. "Dear Laura, your account with Clínica Norte shows a balance of $120, overdue since October 15. Please pay by October 25 using this link: [link], or reply to arrange a payment date."
Fifteen days late, final notice. "Dear Laura, this is a final reminder about your overdue balance of $120. Please reply here or call [phone] so we can agree on a solution before the account is referred for further action."
The amount and the date appear in every message, because a customer should never have to ask what they owe. And the last step invites a conversation rather than threatening one: escalating an account is a decision for a person.
How do you put a payment link in the reminder?
Two ways to include the link:
A link in the template. Stripe and Mercado Pago both let you create a payment link for a fixed amount. Put it in the template body or a URL button; it works for recurring amounts that rarely change.
A link generated when the customer replies. When the customer writes "ok, send me the link", an AI agent connected to Stripe or Mercado Pago generates a link for the agreed amount and sends it in the same conversation. Better when amounts vary.
Mercado Pago is the natural choice for customers in Latin America; Stripe fits the US and billing in several currencies. Either way, send the link from the same number that sent the reminder, so it sits in a thread the customer recognises.
What happens when the customer replies?
Replies fall into a few buckets. Decide in advance who handles each one.
"Send me the link" or "how much do I owe?" An AI agent answers with the link or the balance.
"I'll pay on Friday." A promise to pay. Record the date on the contact, in a label or custom attribute, and follow up the day after only if nothing has arrived.
"I already paid." If the payment came through the link, the Stripe or Mercado Pago connector confirms it in the chat. If it came by bank transfer or cash, a person checks before anyone sends another reminder.
"This amount is wrong." A dispute. The AI agent hands the conversation to billing, with the thread attached, and no further reminder goes out until a person has resolved it.
"Stop messaging me." Honour it. Mark the contact, remove them from the campaign audience and hand the account to a person.
How do you send reminders in batches?
A cadence is really a set of audiences: everyone due in three days, everyone due today, everyone three days overdue, and so on. A campaign tool lets you filter contacts by those attributes, pick the template, preview who will receive it and see the estimated Meta cost before you press send. Run them at a fixed hour: early enough that the customer can pay the same day, late enough that nobody gets a reminder at 7 a.m.
When should a person handle the account instead?
Automate the schedule, not the judgment. Some accounts should never receive an automated step beyond the due-date reminder:
Customers with an open dispute or a complaint about the service itself.
Large balances, or customers who represent a large share of revenue.
Customers who have asked for a payment arrangement before.
Anyone who has mentioned a hardship.
Keep those in a view a person owns, and let the AI agent handle routine instalments.
What should you measure?
You need four numbers per billing cycle, by step:
Delivered and read per reminder.
Replies, and what kind: link requests, promises, disputes, stop requests.
Promises kept: of the customers who gave a date, how many paid by it. This is the number that tells you whether tone and timing are right.
Paid before the next step, so you can see which reminder moves the money and drop the ones that do not.
Compare cycles, not days. If the seven-day message gets most replies and the three-day message gets none, move it earlier or reword it.
What about local collections rules?
Collections is regulated, and the rules differ by country: Colombia, Mexico and the US each set their own limits on contact hours, frequency, wording and what you may say about consequences. This post is a messaging playbook, not legal advice. Check the rules that apply where your customers are, keep the wording factual, and give every reminder an easy way to reach a person.
How this works in HellouOne
HellouOne is built around this loop; the collections goal page describes the setup.
Templates and campaigns. You submit the reminder templates from the inbox and send them as campaigns to a filtered audience, with an audience preview and a cost estimator showing the expected Meta fees. HellouOne adds 0% markup on Meta's fees.
Payment links in the chat. With the Stripe or Mercado Pago connector on, the WhatsApp AI agent generates a payment link for the agreed amount inside the conversation and confirms when the payment lands. With Alegra or PortaBilling it can also say which invoices are open. All connectors are on the integrations page.
Replies answered by an AI agent. The agent handles "how much do I owe" and "send me the link" on its own, and its inactivity window can be set as long as seven days, for replies that arrive after payday.
Handover areas. Disputes, payment plans and stop requests go to the billing team through a handover area, with the full thread and private notes; the agent's instructions set which topics always go to a person.
Promise-to-pay tracking. The promised date goes into a custom attribute and a label, so the team filters by it and follows up on the right day.
CRM sync and reports. Contacts and conversations sync both ways with HubSpot, Pipedrive, GoHighLevel and DataCRM, and the campaign report shows delivered, read, replied and failed per campaign.
Templates are available from the Starter plan; outbound campaigns come with Scale. The 7-day free trial needs no card, so you can submit your first reminder template and send it to yourself first.
