Workflow guide

Turn a WhatsApp sales update into follow-up work

See how a rep can send ordinary WhatsApp context after a call and receive structured company, contact, task, and draft information without opening the CRM first.

Who this guide is for

This guide is for a salesperson or founder who already uses WhatsApp for customer context and wants the operational result captured without a second data-entry pass. It is also useful for a manager evaluating what the assistant returns to the rep before any customer-facing message is sent.

Before you start

Use only the verified business contact supplied for your Followups workspace and avoid sending real customer data into a test environment. The recording is an example using sample company and contact details. A live workflow also needs its CRM, channel, allowed actions, and approval boundary configured by the team responsible for those systems.

Workflow steps

  1. Open the verified WhatsApp Business conversation for the Followups workspace. The contact identity is part of the access boundary; do not rely on a forwarded or similarly named account.
  2. Send a plain-language post-call update with the company, what the customer said, and the next action. In the recording, the rep adds the company and contact details needed to structure the work.
  3. Wait for Followups to return the company and contact it identified plus the follow-up task it prepared. Read those details before accepting them as the CRM update.
  4. Review the proposed task and the prompt to draft the customer email. The returned summary is a checkpoint where incorrect company, owner, deadline, or recipient details can be corrected.
  5. For updates that are faster to explain aloud, send a voice note. The recording shows Followups acknowledging the audio and returning a short confirmation rather than requiring a separate form.

Expected result

The conversation produces structured context that a rep and manager can inspect: the identified company and contact, a named follow-up task, and a clear prompt before a customer-facing draft is prepared. The useful outcome is not the chat reply by itself; it is the reviewable work that can be written to the configured sales systems after the workflow rules are applied.

Troubleshooting

If the reply identifies the wrong company, contact, or task, correct the context in the conversation before approving downstream work. If no reply arrives, confirm that the number is the connected business account and that the channel is enabled for the workspace. If a voice note lacks enough detail, follow it with the company name and intended next action instead of assuming the missing fields will be inferred.