CoreD Journal

Design a WhatsApp follow-up that knows when to stop

Connect a business number to your CRM with a record of permission, approved messages and a clear handoff to staff.

Messaging workflows4 min read

An unbranded phone showing abstract chat bubbles and a pause indicator

Short answer

Start with a business number, a record of opt-in and templates where required. Before every send, check whether the contact has replied, booked, opted out or been taken over by a person. Any of those events should pause the follow-up.

Record permission before the first message

Use an approved WhatsApp business number. Record who opted in, when they did it and what they agreed to receive. Do not assume that a phone number collected for an unrelated purpose can be used for WhatsApp follow-ups.

Check the WhatsApp Business Messaging Policy and use approved templates when required. Keep the template name, version and message purpose in the workflow so staff can see what was sent. Confirm channel charges with your provider before setting a volume target.

Check the contact before every send

Give each contact a single workflow owner. Before sending, confirm the current permission and check whether the contact has replied, booked, opted out or been taken over by a staff member. Check again at send time, because a reply can arrive while a reminder is waiting.

Write outbound messages and incoming replies to the CRM against the same contact. If a person opts out, mark the contact as suppressed. If the provider retries a message event, use its identifier to avoid recording or sending the same action twice.

Hand over the conversation with context

When a reply needs a person, show the salesperson the original enquiry, the last message and the reason it was handed over. A staff takeover should pause queued follow-ups until the owner makes a deliberate decision to resume.

Before launch, use internal test contacts. Check a normal reply, an opt-out, a booking, a duplicate event and a staff takeover. Ask someone who did not build the workflow to find the record and pick up the conversation.

Write down what cancels a scheduled message

Imagine an enquiry arrives Monday and a reminder is planned for Wednesday. If the customer replies Tuesday, the inbound event pauses the reminder and assigns the conversation. A second check just before the scheduled send protects against a reply that arrived while the reminder was queued.

Define what “booked” means. One team may use a calendar confirmation; another requires staff to approve the slot first. Use the confirmed status as a stop signal. If a meeting is cancelled, let the owner decide whether to resume instead of restarting the old sequence automatically.

Build a launch checklist the owner can run

Have staff run an approved test contact through a normal reminder, a late reply, a duplicate provider notification, a booking, an opt-out and a manual takeover. Compare the CRM activity with the provider’s send log. A paused reminder should have no outgoing message.

Decide who reviews rejected templates and delivery errors. Set a starting volume your team can handle. If the workflow creates more replies than staff can review, reduce the volume or adjust assignment before adding contacts.

Can you follow up automatically after someone replies?

For a sales reminder sequence, pause when a reply arrives. Staff can decide whether to send a separate response or resume the original sequence. Check the platform’s current messaging rules and the contact’s permission before starting a different workflow.

References

Explore CRM and WhatsApp automation

Keep reading