No answer
Record the attempt and follow the approved retry rule. Avoid assuming silence is interest or adding every channel automatically.
A useful sequence is not a fixed series of messages. It records the outcome, delivers what was promised and adapts when the prospect replies, books, declines or opts out.
Many sales sequences are designed as a calendar: call on day one, email on day two, message on day four and call again later. That structure ignores the most important input: what the prospect said.
A person who requested a proposal needs the proposal, not a generic reminder. Someone who asked for a call next Tuesday should receive that callback at the agreed time. An unsuitable contact or opt-out should leave the active sequence. A booked meeting needs confirmation and preparation rather than continued prospecting messages.
Use the framework below as an operating model, then adapt the timing, channel and content to the real conversation and your organisation's approved process.
Record the attempt and follow the approved retry rule. Avoid assuming silence is interest or adding every channel automatically.
Save the exact requested time, assign an owner and include enough context for the next conversation.
Send the specific material promptly through the agreed channel, then set a reasonable review action.
Route the prospect to the right person with needs, questions, objections and timing attached.
Stop prospecting activity, send confirmation and prepare the meeting owner for the discussion.
Close or suppress the record correctly and prevent unrelated automated messages from continuing.
Subject: Information from our conversation
Hi [Name], thanks for speaking with me. As requested, here is [specific material or link]. The relevant part for [need discussed] is [brief context]. I will [agreed next step] on [time/date].
Hi [Name], confirming our callback about [topic] on [day] at [time]. This is [name/company].
Hi [Name], your conversation with [person] is confirmed for [time/date]. We will focus on [agreed topic]. [Meeting link or location].
Templates should accurately reflect what happened. Remove fields and claims that are not necessary, and do not turn a requested message into a new promotional sequence.
FoxEra Calls connects calls, WhatsApp, SMS, email and CRM activity so the team can see the history and next action in one workflow. Explore the five-channel process.
Track requested actions completed on time, callback completion, overdue next steps, reply rates by outcome, qualified handovers, meeting attendance, opt-outs processed and records without owners. Sending more messages is not a success measure by itself.
The most useful question is whether each relevant prospect reached the correct next step with minimal delay and without unnecessary repetition.
A template or automation does not determine whether contact is lawful or appropriate. Organisations remain responsible for the audience, data source, lawful process, identification, channel use, message content, opt-outs, suppression and applicable obligations.
Follow the prospect's request, provide a practical stopping route and retain human ownership for exceptions and campaign decisions.
Use the timing agreed during the conversation. Send requested information promptly and use a specified callback time exactly.
No. The workflow should change according to the outcome, requested channel, qualification and opt-outs.
Outcome, requested action, channel, owner, due time, completion state and any stopping requirement.
After a meaningful reply, opt-out, unsuitable outcome, meeting booking or human handover.