A communication ends with the effect it produces on the journey, not with scheduling the send. Before sending, organize the audience, message, timing, responses, and monitoring with the teams that will sustain that continuity.
Choose the right stage and audience
Describe what the message should help the person do: complete pending information, confirm a stage, or resume a conversation. Define who is included in the audience and who should be left out. The scope needs to account for the current situation to avoid asking for an action the person has already completed or sending duplicate messages through different campaigns.
Confirm with the people responsible that the audience, purpose, and channel may be used. Record the source of the list and when it was updated. If that authorization or update is unclear, resolve the pending issue before execution. This guide organizes the work; it does not replace the company's assessment of the applicable rules.
Review content, variables, and destination
Prepare a message with an understandable reason and a clear next action. Check the channel template, variables, links, and destination of each response. A correct name with an incorrect link still produces an incorrect communication. Also test missing data: it is better to stop a send that lacks necessary information than to fill in a variable based on an assumption.
Ask someone who knows the journey to review it. Read the message as if you had not participated in the project: is it clear who is speaking, why the person was contacted, and how to continue? Avoid including unnecessary sensitive information in the text itself. The review should cover the final content, with examples of the variables already filled in.
Plan the send and the operation that receives responses
Align the schedule with service capacity. A message can trigger questions, refusals, corrections, and requests the agent does not handle. Define who monitors this feedback, which queue receives each situation, and how a person takes over with context. Sending volume should account for the real capacity to continue, not just the channel's technical limit.
Determine how to pause the communication and who can make that decision. Handle failures, invalid recipients, and repeated attempts without assuming that every error requires resending. When there is a delay or missing confirmation, check the available status before repeating. Record the message version and the scope used so you can investigate what each person received.
Monitor the journey beyond the message
Distinguish the states reported by the infrastructure: scheduled, sending attempt, accepted by the channel, delivered, and responded to, according to the available records. Do not turn a lack of response into a delivery failure. Do not treat delivery as confirmation of reading, understanding, or task completion either; each of these points requires its own evidence.
Observe the outcome chosen at the start and unintended effects, such as repeat contact or an increase in unhandled requests. If the message was delivered and no one completed the stage, investigate the content, audience, and subsequent path. If many people responded but the team could not serve them, the adjustment may involve scheduling or operational capacity.
Illustrative example · no customer data
Remind someone of a pending item and allow the conversation to continue
Illustrative example: a team wants to remind people who have not yet sent a document. Before sending, it removes from the list anyone who has already completed the stage, reviews the link, and agrees on a response for those who cannot access the file. The agent can explain the pending item; situations outside the scope go to the team.
Monitoring distinguishes delivered messages, people who responded, and documents actually received. An “I'll send it” response does not close the pending item. If the link fails, the team pauses the send, corrects the destination, and decides which people need updated instructions, without automatically resending the entire campaign.
When the approach needs to change
If there is no delivery confirmation, record that limitation when interpreting the results. If the audience changes rapidly, update the scope close to execution. When the message does not allow a response in the same channel, offer a path to continue that is operational and that the team can monitor.
A point to watch: Considering the work complete once it is scheduled and forgetting the operation that receives the responses.
The worksheet is ready to move forward when…
- The audience, purpose, channel, and content have been reviewed by the people responsible.
- Responses, failures, and stopping have a defined operational path.
- The success measure tracks the process stage as well as the volume sent.
Use the guide to review a communication before scheduling it. The communications demonstration helps visualize the audience, message, and monitoring without sending a real message.
Your worksheet
Complete it with your team.
Record what you know and what still needs confirmation. Answers stay in memory and are not submitted.
References for further reading
- Twilio · tracking message status ↗
Explains status notifications and differences between channels. Read receipts depend on the channel, and notifications may arrive out of order. These records do not confirm that the person completed the task.