Collections·
Collections on WhatsApp — communication and cash are the same problem
Firm reminders, not aggressive ones. How to build a collections sequence with templates, tags, and workflows.
If your collections live in “when I remember,” your cash flow does too.
WhatsApp is the channel where customers already talk to you about deliveries and quotes — it can also be where the payment cycle closes, if you run it as a process.
Principles
- Clear and early — the first reminder isn’t a threat.
- Context — amount, reference, link; not a blank “did you deposit yet?”
- Escalation — Day 0 friendly → Day 3 firm → human on Day 7.
- Record — tag
payment_due/ pipeline stage; nothing stuck in one person’s head. - Right channel — WhatsApp template or formal email (Resend) depending on the customer.
Example sequence
| Day | Action |
|---|---|
| 0 (due date) | Template “Your payment of is due today” + link |
| +2 | Short reminder + payment-methods FAQ |
| +5 | Tag collections_risk + assign to a human |
| Paid | Tag current, stage Won, thank-you message |
In Wroups
Workflows + templates + past-due segments + inbox for exceptions. Optional: a collections pipeline.
AI first response — without losing human control
Agents with your OpenAI key for the first touch; escalate to the inbox when the conversation gets serious.
WhatsApp pricing shifted again — what inbound teams should actually change
July 2026 rate updates hit some marketing and utility markets. Service replies inside the window stay free. Here’s how to keep costs predictable without pausing the inbox.