Send to an SMS recipient list

Prepare the connection and sender

The connection-backed SMS list workflow uses 019SMS. It requires the configured provider runtime, an authorized connection and the approved sender. A general SMS/MMS catalog entry does not imply support for every SMS service, image messages or live provider certification. Ask your administrator to confirm that the runtime and required deployment updates are available.

Connection validation checks authorization through the provider's test endpoint; it does not send a message. Changing sender settings invalidates authorization, so complete that step again before publishing. Create a Publishing channel for the list and confirm your list-management and publishing permissions. Track recipient permission to receive messages through your established audience process.

Build the recipient list

1. Open Mailing recipients on the SMS Publishing channel.
2. Add a phone number and optional name, or open the import area.
3. Paste numbers one per line or preview a CSV with address and name columns; phone headers are accepted.
4. Correct invalid rows and review duplicates, then apply the import.
5. Check which recipients are enabled before composing the publication.

Numbers use a canonical international identity; Israeli local forms are accepted. Sending internationally requires the connection's international setting. Each channel supports up to 1,000 nonremoved recipients. Import does not synchronize Contacts and does not reactivate disabled, removed or unsubscribed entries. If a preview becomes stale, reload and preview again rather than assuming another user's list changes were included.

Write for the actual SMS limit

Compose a short plain-text message and use a channel variant when the same post also targets email or social destinations. Every outgoing SMS in this workflow is limited to 70 UTF-16 units. That is not always 70 visible characters: some emoji and combined characters use more than one unit.

The composer shortens text at grapheme boundaries and reserves space for an unsubscribe URL and separator when enabled. If the required suffix cannot fit, validation fails. Use the exact preview to inspect the sender, an example recipient, final text and truncation notice. The workflow does not produce multipart SMS, MMS or attachments. For a longer explanation or supported files, consider an email mailing list.

Configure opt-out and publication time

Unsubscribe is optional and disabled by default. It requires a configured public HTTPS origin and enough room for the complete link inside the message budget. Opening the link displays a confirmation; confirmation suppresses the recipient only on that channel. Provider blacklists remain effective as well.

After checking the final text and recipient list, complete the configured post approval and choose a valid publication schedule. A scheduled time is not a promise of immediate handset delivery. Do not use a draft's full text as evidence of what will be sent; the preview reflects the composition limit and any enabled unsubscribe suffix.

Inspect results before sending again

When sending starts, the operation freezes its recipient list, sender, settings and rendered content. Later edits do not change that operation. Current suppression is checked before each pending delivery is claimed, but editing the list cannot recall a message that the provider has accepted.

Read accepted, delivered, failed, ambiguous, pending and suppressed results separately. An interrupted provider call can leave an uncertain outcome that must be reconciled with provider reports. It does not become safe to retry merely because time has passed. Only known retryable failures qualify for the explicit retry path. Inbound SMS replies require a separately active Support channel with its receiving number configured; an outbound list does not turn on ticket intake. Follow troubleshooting when delivery remains uncertain.