> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to structure sales follow-up on WhatsApp
- URL: https://blog.jestor.com/sales-follow-up-on-whatsapp/
- Published: 2026-09-16T18:52:55.000Z
- Updated: 2026-09-16T18:52:55.000Z
- Author: Bruno Bannach

Effective **sales follow-up on WhatsApp** is triggered by what happened in the pipeline, not by a rep remembering. In **Jestor**, an automation can send an approved template when a deal reaches a stage or a date passes, through the official **Meta** **API**, with the message personalized from the record.

## Why follow-up fails in both directions

Reps under pressure either forget to follow up, or follow up identically with everyone until prospects stop replying. Both come from the same cause: follow-up depends on memory rather than on the process.

Automating it badly makes the second problem worse, which is why the trigger matters more than the automation.

What structured follow-up fixes:

- Deals going quiet with nobody noticing
- Identical messages sent regardless of context
- Follow-up depending on which rep is organized
- No record of what was sent and when
- Messages that cannot be delivered because the window closed

## Trigger design

| Trigger                           | Message intent              | Risk if misused                  |
| --------------------------------- | --------------------------- | -------------------------------- |
| Proposal sent, no reply in X days | A gentle check in           | Too frequent becomes noise       |
| Deal reaches negotiation          | Supporting information      | Generic content wastes the touch |
| Proposal validity approaching     | A genuine deadline          | Fake urgency damages trust       |
| Deal marked lost                  | A thank you and open door   | Sounding automated               |
| Manual button                     | Anything requiring judgment | None, a person decided           |

## Step by step to configure it

1. **Define the moments** in your pipeline that genuinely warrant a message.
2. **Write and submit the templates**, since Meta approves them before use.
3. **Map the variables** to record fields, so each message carries real context.
4. **Set the trigger**, whether a stage change, a date or a manual button.
5. **Add a condition** so nobody receives two messages in a short window.
6. **Keep the manual button** for anything needing judgment.
7. **Review reply rates per template**, and retire the ones that do not work.

## Why the 24 hour window shapes the design

Outside the window, only an approved template can be delivered. That constraint is useful: it forces you to decide in advance which moments deserve an outbound message, rather than sending whenever someone feels like it.

## Why choose Jestor

**Jestor** sends templates through native automations on the official Meta API, triggered by a stage change, an event or a button, with variables filled from the record. Each conversation stays a card with its full history, several numbers can serve different areas, and the window status is visible before anyone tries to send.

## Frequently Asked Questions

### Why do I need a template for follow-up?

Outside the 24 hour window, a template is the only message that can be delivered. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Can the message be personalized?

Yes. Template variables are filled from fields on the record.

### Can a person still send manually?

Yes. A button automation keeps the decision with the rep.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.