Send a Single SMS

Overview

Send SMS is for low-risk validation first, because one live message confirms line configuration and content rendering before you message a larger audience. By selecting one outbound line and one recipient, you can verify messaging behavior quickly and reuse proven settings in batch workflows.

How it works

• The flow ties message delivery to line-level messaging settings, so correct phone number configuration must exist before send is allowed. This dependency protects reliability by preventing sends from unconfigured lines.
• After the message is sent, thread visibility in SMS History provides immediate feedback on delivery behavior. That feedback loop helps you refine content before scaling.

Important fields

• Outbound line: Must have messaging pathway configured.
• Message body: Plain text sent to the recipient.

Tips

• Good to know: Do Not Call suppression applies to SMS as well as voice, so blocked numbers will not receive single-message sends.

Recipient

Recipient configuration is first because line selection and destination validity determine whether the message can be routed correctly.

Confirm the from/to numbers, then move to Message Goal.

• You choose the outbound line and destination number before content execution, so delivery identity is fixed early. Correct identity setup reduces failed sends and improves recipient trust.
• From Number: Outbound line with messaging pathway.
• Destination Number: Recipient phone number.
• Good to know: if messaging settings are missing on a line, sending issues usually trace back to configuration rather than message text.

Message Goal

Message Goal sets communication intent first, so pathway or task logic can generate content that matches the outcome you want.

Approve the previewed message, then review Launch Summary.

• Selecting source mode determines how message content is built, and the preview confirms final text before delivery. Previewing early prevents tone or variable mistakes from reaching recipients.
• Source Mode: Pathway or Task drives message content.
• Message Body: Plain text sent to the recipient.
• Good to know: validating pathway behavior in Chat & Test first shortens iteration cycles when refining SMS wording.

Launch Summary

Launch Summary protects message accuracy at the final step, so identity and content are checked together before send.

Send the SMS and verify the resulting thread in SMS History.

• The summary view consolidates destination, outbound line, and message details into one confirmation moment. That final check catches most preventable mistakes before the SMS is dispatched.
• Send Time: Immediate send for single SMS.
• Good to know: suppression errors at this stage usually indicate an intentional compliance block, not a platform failure.

Next step

Send an internal test SMS, verify thread output, then reuse the same setup in Batch SMS if needed.