Swarmhit playbook · November 2026

The WhatsApp Follow-up Playbook

Five automated WhatsApp messages that move deals, with the timing, the message templates, the safety rules and the API calls behind each one.

Start free trialAbout 12 minutes to read

01Where WhatsApp belongs in a deal

LinkedIn and email are where a conversation starts. WhatsApp is where it gets personal: the phone people keep in their pocket, read by the person and not by a filter. That is exactly why it is the wrong place for a first touch, and the right place for the few messages that decide whether a deal moves: the reminder before a call, the recap after it, the follow-up someone asked for.

Use WhatsApp for

  • Confirming and re-booking meetings
  • Sending a recap or a proposal after a call
  • Following up on the date a lead gave you
  • One nudge on a deal that went quiet

Do not use it for

  • A first message to a cold list
  • Long pitches or newsletters
  • A third follow-up nobody answered
  • Anyone who asked you to stop

Five rules

  1. 1

    Only people who already know you

    Someone who replied, booked a call, met you or asked you to come back. WhatsApp expects a linked number to talk to people who know it, and so do your leads.

  2. 2

    One idea, one line to answer

    A WhatsApp message is read in a few seconds. Ask one question that takes one line to answer: a time, a yes, a name.

  3. 3

    The same conversation, not a new one

    Your WhatsApp message must know what was said on LinkedIn and by email. Quote it. “As you asked in June” beats any opener.

  4. 4

    Stop the moment they reply, anywhere

    A reply on LinkedIn, by email or on WhatsApp ends every automated follow-up for that lead. Nobody wants a reminder after they answered.

  5. 5

    Pace every number

    Go slowly, especially on a new number, and keep conversations two-way. A number that blasts gets limited, and the whole channel goes with it.

02The five moments, with templates

Each moment has a trigger, a wait, two templates to start from, the way to automate it and the guard that keeps it from going wrong. Replace the {fields} with what you know about the lead; the more the message quotes the real conversation, the better it works.

Moment 1

Confirm tomorrow's call

Trigger
A meeting is booked.
When to send
The day before, around 10:00 in the lead's time zone.

Templates

Hi {first_name}, quick check that tomorrow at {time} still works for you. Happy to move it if not.

Hi {first_name}, looking forward to tomorrow at {time}. Anything you want me to prepare?

How to automate it: Your booking webhook schedules one WhatsApp send for the day before. On the Smart API, add the lead to a one-step WhatsApp campaign; on the Raw API, call POST /whatsapp/api/v1/chats at the scheduled time.

Guard: Cancel the job when the booking is canceled or moved, and send unless_replied_since set to the booking date.

Moment 2

Re-book a missed call

Trigger
The lead did not show up.
When to send
About an hour after the meeting start. Not five minutes: give them the chance to apologise first.

Templates

Hi {first_name}, looks like today got busy. Want to grab another slot this week? {booking_link}

No worries for today, {first_name}. Does {day} morning work better?

Voice note: A 10-second voice note works well here: friendly, no guilt, one question.

How to automate it: Your calendar's no-show or meeting-ended event triggers the send. Pass a client_id built from the meeting id so a retried webhook never sends twice.

Guard: Only once per meeting. If they rebook, the next moment is a confirmation, not another nudge.

Moment 3

Send the recap after the call

Trigger
The call just ended.
When to send
The same afternoon, while they still remember the call.

Templates

Thanks for the time today, {first_name}. Recap and the pricing we discussed attached. Next step on our side: {next_step}.

Great talking today. Here is the one-pager for {their_boss}, so you do not have to rewrite it.

How to automate it: Send the text with the proposal as a file: multipart with attachments, up to 10 files of 20 MB each, the text becoming the caption of the first document.

Guard: Use the chat that already exists for this person: POST /whatsapp/api/v1/chats reuses it, so the recap lands under your earlier messages.

Moment 4

Keep the “ping me in Q4”

Trigger
“Reach back in Q4”, “after the summer”, “next quarter”, said on any channel.
When to send
On the date they gave you. Not a week early, not a month late.

Templates

Hi {first_name}, it's {month} as promised. How did {their_project} land? Happy to pick up where we left off.

Hi {first_name}, you told me to come back after {event}. Is now a better time?

Voice note: This is where a short voice note is worth it: the lead hears that a person kept the promise.

How to automate it: Store the date your rep or your AI read in the reply, then schedule the send. Write the message from the earlier thread so it quotes what they said.

Guard: unless_replied_since set to the date of their “come back later”: if they wrote since, nothing is sent and you get 409 recipient-replied.

Moment 5

Nudge a deal that went quiet

Trigger
A proposal is out and the email follow-ups got no reply.
When to send
About 7 days after the proposal, after the email steps.

Templates

Hi {first_name}, no rush on the proposal. Anything I can clear up for your team?

Hi {first_name}, is {blocker} still the open question? I can get you an answer today.

How to automate it: On the Smart API, a WhatsApp step goes after the email steps of the same sequence; the engine stops it if the lead replies on any channel. On the Raw API, your sequencer calls the send.

Guard: One nudge. If WhatsApp gets no answer either, the deal needs a call, not a third message.

03Automating it: the API calls

Swarmhit links a WhatsApp number as a device of the phone, the way WhatsApp Web does, on an IP in the number’s own country. You link it once with a QR code or a pairing code, then everything runs through a REST API under /whatsapp/api/v1.

Two ways to run it

Smart API: the engine runs it

Attach WhatsApp numbers to a sender, add WhatsApp message steps to the sequence, give leads a phone number. The engine takes care of the sending and stops the follow-ups when the lead replies on any channel.

Raw API: your code runs it

One endpoint per action. Your scheduler decides when a message goes out, and the API refuses anything a runaway loop would do before it reaches WhatsApp.

The “ping me in Q4”, in code

POST /whatsapp/api/v1/chats sends to one person and reuses their chat when it exists. The number is checked to be on WhatsApp first. Three fields do the safety work: client_id, unless_replied_since and the error codes you handle.

// "Ping me in Q4": runs on the date the lead gave you.
const API = "https://console.swarmhit.com/whatsapp/api/v1";
const headers = { "X-API-KEY": process.env.SWARMHIT_KEY, "Content-Type": "application/json" };

export async function pingLater(lead) {
  const res = await fetch(`${API}/chats`, {
    method: "POST",
    headers,
    body: JSON.stringify({
      account_id: lead.repNumberId,            // the rep's number, wa_...
      attendees_ids: lead.phone,               // international format
      text: `Hi ${lead.firstName}, it's Q4 as promised. How did ${lead.project} land?`,
      client_id: `ping-q4-${lead.id}`,       // a retry never sends twice
      unless_replied_since: lead.askedLaterAt, // skip if they wrote since
      typing_duration: "4000",                 // show "typing..." for 4 s
    }),
  });

  if (res.status === 409) return markReplied(lead);  // recipient-replied
  if (res.status === 429 || res.status === 503) {
    const { retry_after_ms } = await res.json();
    return reschedule(lead, retry_after_ms);       // the API says when
  }
  if (!res.ok) throw new Error(`WhatsApp send failed: ${res.status}`);
  return res.json(); // { object: "ChatStarted", chat_id, message_id }
}

Sending a voice note

Send the same call as multipart with a voice_message file. Any audio format works: it is converted to a WhatsApp voice note when needed. Files go the same way, through attachments.

curl -X POST https://console.swarmhit.com/whatsapp/api/v1/chats \
  -H "X-API-KEY: gw_live_..." \
  -F account_id=wa_... \
  -F attendees_ids=33612345678 \
  -F voice_message=@q4-follow-up.m4a \
  -F voice_duration_ms=9000 \
  -F client_id=ping-q4-voice-1042

Before a first message, GET /whatsapp/api/v1/users/{phone} tells you whether the number is on WhatsApp; a 404 means it is not, and the answer is kept a week. Full reference at developer.swarmhit.com.

04Be very careful with your numbers

This is the part that decides whether WhatsApp works for you at all. A WhatsApp number is a person’s phone, and WhatsApp watches how it behaves. A number that sends much more than it receives, or writes to people who never answer, gets limited fast, and a limited number is hard to bring back. Be very, very careful, especially in the first weeks.

1

Receive far more than you send

A healthy number gets many more messages than it starts. Begin with people who already wrote to you, and let the replies build the number's history before any automation.

2

Keep every conversation two-way

WhatsApp is a conversation app. Messages that never get an answer are the clearest sign of a number used the wrong way, so answer fast, from the same number, and stop writing to people who do not write back.

3

Go very slowly with a new number

A freshly linked number has no history. Use it like a person would for a while, with a handful of real conversations, before it sends anything automated, and grow from there step by step.

4

Never a list, never a blast

Even warm leads should not all get the same message at the same minute. Spread sends out, write each one from that lead's conversation, and keep the volume of new chats low.

5

One number per rep

Each rep links their own number from their own phone. Several numbers on one sender are fine; one number shared by a whole team is not.

If WhatsApp pauses new chats on a number, the API tells you so with the time the pause ends. Existing conversations keep working: finish those, and slow down.

Swarmhit links regular WhatsApp numbers as linked devices. It is not Meta’s WhatsApp Business Platform, and Swarmhit is not affiliated with or endorsed by Meta or WhatsApp.

05The checklist

  • Every lead you message on WhatsApp replied, booked, met you or asked to be contacted
  • Leads carry a phone number with its country code
  • One WhatsApp number per rep, linked from their phone, on an IP in the number's country
  • Each send has a client_id built from your own ids
  • Every automated follow-up sends unless_replied_since
  • A reply on any channel stops the follow-ups for that lead
  • New numbers receive more than they send before any automation, and grow slowly
  • Conversations stay two-way: no reply, no further message
  • Messages quote the earlier conversation instead of starting a new one
  • Your code reads refusals and waits, instead of retrying blindly
  • Replies reach your CRM or inbox through webhooks

WhatsApp on Swarmhit

Run these five moments on Swarmhit

LinkedIn, cold email and WhatsApp in one API. Start a free trial and watch the engine run in the playground, with up to 2 senders, before you write any code.