Payment reminder automation
Create a small payment-reminder workflow: detect an overdue account, send a WhatsApp reminder with payment instructions, stop when paid, and log the result.
Connect the visible UI to the decision the lesson is teaching.
What you will build
A tiered payment reminder system that sends escalating WhatsApp messages to overdue accounts at Day 1, Day 7, and Day 14 — with payment links, professional tone, and an automatic stop when payment is received.
After deployment: overdue accounts automatically receive a reminder within 24 hours of the due date, a follow-up after 7 days, and a final notice at 14 days — without any manual outreach initiation.
When to use this
You have overdue accounts that would pay with a timely reminder but nobody is sending them consistently.
Your collections team is manually sending the same reminder messages from WhatsApp every week.
You want a documented audit trail of every reminder sent to every account.
You need reminders to stop automatically the moment payment is confirmed.
System components
CRM record: debtor name, phone, balance, due_date, payment_status.
Studio workflow: three-stage reminder sequence with wait nodes and payment detection.
AI message drafting agent: generates professional, compliant reminder text for each stage.
Channels: WhatsApp Send Message for outbound delivery.
Conditional Routing: stops on payment confirmation, escalates after third no-reply.
Max Activity: each message sent, each reply received, payment detected, or escalation triggered.
Step-by-step implementation
1. Confirm CRM records have: debtor phone, balance, due_date, payment_status. These are required before any reminder fires.
2. Create a Studio workflow. Trigger: payment_status changes to 'Overdue' OR due_date has passed and payment_status ≠ 'Paid'.
3. Stage 1 (Day 1): add AI drafting agent node. Pass: debtor name, balance, due date. Draft a friendly first reminder.
4. Add Send Message node (WhatsApp). Include payment link as a variable if available.
5. Add Wait node: 7 days. During wait: monitor for payment_status = 'Paid'. If payment detected → write Max Activity, exit workflow.
6. Stage 2 (Day 7): add AI drafting agent node. Pass same context. Draft a follow-up with slightly more urgency.
7. Add Send Message node. Add Wait node: 7 more days. Monitor for payment.
8. Stage 3 (Day 14): add AI drafting agent. Draft final notice. Send via WhatsApp.
9. After Day 14 no-reply: route to human collector. Write Max Activity with 'Automated sequence complete — no response'.
10. Write Max Activity after every message sent: stage, message preview, delivery status.
Agent prompt
You are drafting a payment reminder WhatsApp message. The tone must be professional, factual, and non-threatening.
Stage 1 (Day 1): friendly, assumes the customer may have overlooked the payment. State the amount and due date. Include payment instructions.
Stage 2 (Day 7): slightly more direct. Acknowledge that the payment is now past due. Offer to help if there is a question about the balance.
Stage 3 (Day 14): clear and firm. State that the account remains overdue and that a resolution is needed. Provide clear next steps.
Never mention legal consequences, credit reporting, or collection agencies unless explicitly authorized by policy. Output only the message text.
Workflow logic
Payment detected (any stage): stop workflow immediately. Write Max Activity as 'Payment received'. Update payment_status = 'Paid'.
Customer replies with question: route to human agent for this account. Pause automated sequence.
Customer promises to pay: capture promise, pause automated sequence, start promise monitoring workflow.
Three stages complete, no reply, no payment: route to collector queue. Write Max Activity with full contact history.
Final operating state
Every overdue account receives 3 reminder messages at consistent intervals without manual initiation.
Reminders stop the moment payment is confirmed — no awkward messages to customers who already paid.
Max Activity shows every message sent and every payment event, creating a compliance-ready audit trail.
After 3 unanswered reminders, accounts escalate to human collectors with the full contact history available.
Common mistakes and troubleshooting
Reminders firing on paid accounts: add a payment_status check at the start of each stage, not just at the trigger. Status can change mid-sequence.
Messages not personalizing correctly: verify the debtor name and balance variables are being passed to the agent node, not hardcoded.
Wait node not detecting payment: confirm the payment detection check runs on a separate monitoring trigger, not only at the end of the Wait node.
All accounts routing to collector after Day 14: this is the correct behavior — verify the escalation is creating the right Max Task for the collector team.
FAQs
What data is required before sending reminders?
Customer name, phone, amount, due date, payment status, owner, and an internal reference such as invoice, deal, or account ID.
When should the workflow stop?
Stop immediately when payment_status is Paid, the customer opts out, the customer disputes the amount, or a teammate takes ownership.
What is the safest first version?
One reminder, one WhatsApp channel, one paid-status guard, one escalation owner, and one Activity log.
Should the AI decide legal or collections policy?
No. Use approved reminder copy and escalate policy-sensitive cases. Do not let the agent invent consequences, fees, or payment rules.