WhatsApp background reminders
Open the WhatsApp Business record's Workflow editor. Connect Incoming WhatsApp Message (Before AI Processing) to Throttled Message (Background).
The background node schedules a separate job and immediately lets the normal AI pipeline continue. Unlike a Delay node in a before-AI path, it does not hold the user's reply for the reminder delay.
Settings
| Setting | Meaning |
|---|---|
| Message | Plain-text reminder, up to 4,000 characters |
| Delay | 1–300 seconds; CChat uses 30 seconds |
| Once per contact | 1–720 hours; CChat uses 24 hours |
| Skip incoming phrases | Comma-separated, case-insensitive phrases; CChat requests skip the reminder |
| Skip visitors who already migrated | Suppresses reminders after a successful channel handoff |
The incoming trigger currently follows the WhatsApp text-message workflow path. It does not run on website widget messages. No extra Source node is required; the custom-agent editor separately already provides a Channel condition.
Reliability and limits
- A unique database row and row lock prevent bursts from reserving multiple reminders for the same workflow/node/contact.
- The cooldown starts when the outgoing reminder is created, not when the timer starts. It persists across Redis/cache restarts.
- Duplicate timer jobs do not create duplicate messages. Actual WhatsApp transport uses the existing delivery queue, retry and billing path; this is not a guarantee of exactly-once delivery by Meta.
- Delays are minimum scheduling delays, not exact arrival times: a busy queue or Meta can deliver later.
- Disabling the workflow or WhatsApp workflow rules, deleting the node, or deactivating the sender suppresses pending reminders. Delivery rechecks ownership and visitor source.
- Jobs whose triggering message is more than 23 hours old are dropped conservatively instead of attempting a free-form message outside the customer-service window.
- If delivery fails, its existing message is retried by the delivery worker. The cooldown remains in place to prevent another reminder being generated.
- Saving this node does not replace or throttle the secure Get CChat command. The command keeps its immediate, one-use migration link.
For CChat, configure reminders on the TCN Iganmu WhatsApp sender only. The separate registration sender is not changed. Administrators can edit the message/timing or disable the workflow from the dashboard; disabling it does not turn off ordinary AI replies.