How to automate payment collection over WhatsApp, end to end

Chasing a customer for a payment is one of the most awkward jobs in any small business. You write the "hi, how's everything going?", you wait, you send the reminder, you wait again, and you end up spending half the morning collecting money you're already owed. The good news: you can automate payment collection over WhatsApp for almost that entire cycle, without sounding like a robot and without chasing anyone.

In this guide I'll walk you through the full cycle, end to end —invoice, reminder, payment and reconciliation— with what you can actually do today in LATAM. No inflated promises: I'll tell you what exists, what doesn't yet, and where it pays to keep the human touch.

What "automating payment collection over WhatsApp" means (and what it doesn't)

Automating collections isn't setting up a bot that pesters your customers every two hours. It's building an orderly flow where the system handles the repetitive part —letting them know there's an invoice, reminding them as the due date gets close, sending the payment link— and you only step in when a case really calls for it.

The difference from what you do today is that the reminder goes out on its own, on time and from a business number, not whenever you happen to remember and from your personal WhatsApp. The customer gets a clear message, with the amount and the payment method one tap away. No chasing.

The "pay inside WhatsApp" myth: what's real in LATAM

We need to be honest here, because there's a lot of misinformation going around. Native payments inside WhatsApp —where the customer pays without leaving the chat, with the money moving through WhatsApp itself— only exist in India (with UPI) and Brazil (with Pix). In the rest of LATAM —Mexico, Colombia, Venezuela— there is no WhatsApp Pay. Don't let anyone sell you otherwise.

So how do you get paid? With a payment link or a gateway built into the chat. Inside the conversation, the customer gets a link that takes them to pay with their usual method, and then they come back. Depending on the country, that means:

• Mexico: MercadoPago and other gateways with payment links.
• Colombia: Nequi and gateway links.
• Peru: Yape and payment links.
• Brazil: Pix (which, on top of that, does have a native integration).
• Venezuela: Pago Móvil, the rail everybody uses.

For the customer the result is almost the same —they pay from the chat in a few taps— but the plumbing underneath is a payment link, not "WhatsApp Pay". With that cleared up, let's look at the cycle.

The automated collection cycle, step by step

A collection flow that works has four stages. The idea is that each one triggers the next without you having to push.

1. The invoice gets recorded in the CRM

Everything starts here. When you issue the invoice, it gets loaded into the system with its amount, its customer and its due date. That date is what later triggers the reminders. If your invoicing lives in a stray spreadsheet or in the owner's head, there's nothing to automate: the system needs to know who owes, how much and by when.

2. Automatic reminder at 3 / 7 / 15 days

This is the heart of it. Instead of you remembering to write, the system sends scheduled reminders based on how overdue the invoice is. One message on day 3, another on day 7, and a firmer one on day 15. Each one with the amount and the payment link ready to go.

Part of your overdue balance gets collected on its own with the day-3 reminder: a lot of people simply forgot, and a friendly heads-up at the right time is enough. The longer stretches are for the ones who need an extra nudge.

3. Payment link inside the same conversation

The reminder is useless if the customer has to ask you "so how do I pay you?". That's why the message already includes the payment link —or the Pago Móvil details in Venezuela— right in the same chat. The fewer steps between "I remember I owe" and "I've paid", the more you collect.

4. Automatic payment reconciliation

The stage almost everyone forgets. When the customer pays, the system has to mark the invoice as paid on its own, without someone checking the bank by hand and crossing it off a spreadsheet. In Klienz, with built-in Pago Móvil payments (validated against the reference number and the BCV exchange rate), the payment is reconciled against the invoice and the reminders stop going out automatically. If this doesn't happen, you risk continuing to pester someone who has already paid —the most expensive mistake of all for your reputation.

Which kind of reminder to send at each stage

Not all reminders are the same. The tone changes with the days overdue, and —this matters for your wallet— so does the type of template you should use (I'll explain why in a moment). A practical guide:

When	Message tone	Template type
When the invoice is issued	Informative: "here's your invoice and how to pay it"	Utility
Day 3 overdue	Friendly, assumes they forgot: "just a reminder that this is still pending"	Utility
Day 7	Clear and direct: amount, due date and link	Utility
Day 15	Firm but respectful: consequences and payment options	Utility
Customer replies in the chat	Conversational, human if needed	24h window (free)

Why "utility" templates protect your wallet

Since July 2025, WhatsApp has changed how it charges: it no longer bills per conversation, but per template message sent. And not all templates cost the same. Utility templates —payment reminders, invoice notices, updates on an ongoing transaction— are cheaper than marketing ones. A collection reminder falls squarely into utility.

The logic is simple: use utility templates for automatic notices, and make the most of the 24h window for everything conversational. That way the flow pays for itself. If you want the details of the pricing table, check out how WhatsApp now charges per message.

When you should NOT automate

Automating doesn't mean putting all your customers on the same conveyor belt. There are cases where an automatic reminder does more harm than good:

• The long-time customer who expects a personal touch. For someone who's been buying from you for a decade, an automatic message on day 3 can feel cold. That one, you call yourself.
• Large or sensitive accounts. When the amount or the relationship carries weight, the human touch collects more and protects the relationship.
• Delicate situations. If you know the customer is going through a rough patch, automating the collection notice is the worst possible read.

The healthy rule: automate the volume —the small and mid-sized invoices, the typical oversights— and save your time for the exceptions that truly need a conversation. Automation frees you up for that; it doesn't replace you there.

How to set this up in practice

For the cycle to work you need three connected pieces: invoicing (to know who owes and when it's due), WhatsApp Business API (to send scheduled templates from a business number) and built-in payments (for the payment link and reconciliation). When all three live in the same place, the flow closes itself.

That's exactly the approach of a CRM with WhatsApp: if you're still not clear on what it is and what it solves, start with what a CRM with WhatsApp is and why your SMB needs one. And if you want collections to stop being an isolated event and become part of your sales process, see how to organize your sales pipeline so that getting paid is the natural last stage, not a fight.

In short

Automating collections over WhatsApp isn't magic or a single button: it's organizing four stages —invoice, reminder, payment and reconciliation— so the repetitive part runs on its own. Remember the essentials: in LATAM, "paying inside the chat" means a payment link (or Pago Móvil in Venezuela), not WhatsApp Pay; reminders are best sent as utility templates so you spend less; and always leave a door open to the human touch where the relationship calls for it.

Done right, you stop chasing customers and part of your overdue balance collects itself. That's time you get back for yourself.