Follow-up Automation

When someone goes quiet, the agent nudges them on the channel they were already using. Each channel has its own schedule and its own units, because a two-day gap is normal in email and rude on WhatsApp.

How it works#

  • Follow-ups are scheduled the moment a conversation needs one, each as its own timed job - so they fire at the right moment rather than being swept up by a periodic scan.
  • Each step is written fresh with the conversation's context. It isn't a canned template with the name swapped in.
  • A step follows the same auto-send rules as any other reply: high confidence and channel auto-reply on means it sends, otherwise it lands in your inbox as a draft.
  • Steps that were scheduled but no longer make sense are cancelled rather than sent late.

Async channels only. Website chat and live phone calls don't get follow-ups - a live conversation either continues or ends.

Email schedule#

Email follow-ups use day offsets from the last contact. The default is day 2, day 5, day 10: a check-in, something useful, then a soft close.

  • Configure the offsets per agent - add, remove or change any of them.
  • Clear them all to switch email follow-ups off entirely.
  • Offsets are days after the last contact, not days after the first message, so a reply resets the sequence.

WhatsApp#

WhatsApp has two layers because Meta's rules split at 24 hours from the customer's last message:

LayerUnitWhat's sent
Inside the 24-hour windowHoursFree-form messages the agent writes, like any other reply. Set offsets such as 2h, 6h, 12h.
Outside the windowDaysOnly a Meta-approved template can be sent. Splice schedules the templates you configured.

Hour offsets are ignored where they can't apply

Scheduling in hours only makes sense inside a messaging window, so those steps are only created on chat channels. Day offsets are for email.

WhatsApp templates#

Templates are synced from your connected WhatsApp Business Account - Splice never invents a template name. For each step you pick an approved template and its language, map each numbered placeholder to a lead or agent field (or fixed text), and optionally add a condition so the step only runs when it applies.

Free-form outside the window fails, then falls back

If a free-form message is attempted outside the window, Meta rejects it with error 131047. Splice then sends the first matching configured template instead. With no template configured, the step is cancelled rather than retried - so an empty template list means silence after 24 hours.

Instagram#

Instagram follows the same in-window model with hour offsets, but Meta provides no template equivalent. Once the window closes, the conversation waits for the customer to write again.

When follow-ups stop#

EventWhat happens
The customer repliesPending steps are cancelled. A new sequence starts if needed.
The conversation reaches a terminal stageAuto follow-up switches off by itself and the automation card says which stage stopped it.
A human takes overThe agent stops, including its follow-ups.
You pause follow-ups on that conversationNothing further is scheduled for that thread.
The agent is pausedEverything stops workspace-wide for that agent.

Meeting-aware suppression#

A follow-up that ignores what was agreed on a call is worse than no follow-up. Where meeting context is available, a drafted follow-up is checked against the last meeting before it goes:

SituationOutcome
The draft contradicts a decision from the callEscalated for human review - shown as 'Needs review - contradicts call.'
The rep owes the next step and the draft ignores itSkipped, with 'Paused - waiting on rep next step.'
The agent owes the next step but the draft doesn't reference itHeld for context rather than sent.
A meeting happened but its transcript hasn't landed yetHeld, asking for call notes so it can be re-scored.
Nothing conflictsSends normally.

The full logic is in Follow-up Sequences.

Pausing them#

The automation card in the inbox side panel has an auto follow-up switch that affects that one conversation only. To change the schedule for everyone, edit the agent's follow-up settings. To stop everything at once, pause the agent.

Good defaults

  • Two or three email steps, not six. Sequences that keep going past a soft close get marked as spam.
  • On WhatsApp, one in-window nudge at a few hours beats three.
  • Configure at least one approved template if you rely on WhatsApp - otherwise every conversation goes quiet at the 24-hour mark.
  • Leave the terminal-stage suppression alone. Chasing someone who already said no is how you get complaints.