SMS lists
Bring short reminders and timely updates to your phone-number lists. Connect 019SMS, preview the exact message and use the same publishing and review workflow as your other content.
From list to publication
An SMS publishing channel connects an authorized sender with its own recipient list. Prepare a focused message, check the final composition and schedule it through the publishing workflow. Review delivery by recipient instead of treating a queued message as a completed result.
Use a configured 019SMS connection with the required service available in your deployment. The selected sender must match the authorized connection. International sending also depends on the connection’s international setting.
Add recipients individually, paste numbers or review a CSV import. Phone numbers are normalized for delivery, with duplicates and invalid entries identified before import. Each publishing channel supports up to 1,000 recipients.
Draft a concise update in the publishing editor, using AI assistance where useful. The preview shows the sender, example recipient, exact final text and any shortening. Apply configured content approvals and scheduling before the message enters delivery.
An illustrative example
Your new guide is ready. Instead of putting a whole announcement into an SMS, tell the recipient what changed and where to go next. The example below is a content preview, not an automated message or a live send.
Your guide is ready. Open your workspace to read it.
If unsubscribe is enabled, its URL and separator must fit inside the same message budget. Recheck the final preview rather than assuming the draft and delivered text will be identical.
Illustrative content only. No email or SMS is sent from this website.
Your list. Your publishing controls.
Set up the list, message and delivery options for the work you intend to run.
The complete outgoing SMS is limited to 70 UTF-16 units, including any unsubscribe URL. Some characters, including emoji, use more than one unit. The preview shows the exact shortened text. This workflow does not send multipart SMS, MMS or attachments.
Unsubscribe is optional and off by default. It needs the configured public HTTPS address and enough space in the message. A confirmed opt-out suppresses the recipient for that channel, and a later import does not reactivate it.
Delivery status can distinguish accepted, delivered, failed, uncertain, pending and suppressed recipients. Where an attempt is uncertain, the system reconciles provider evidence instead of blindly sending it again. A scheduled publication is not a delivery guarantee.
Inbound SMS support requires a separately active Support channel with a receiving number. That configuration can route incoming messages into Tickets. Creating an outbound SMS list does not enable support intake by itself.
Practical details
Know how the list, sender and delivery fit together.
The connection-backed list workflow uses 019SMS. It requires the configured provider service, authorized sender and enabled deployment. The broader SMS / MMS catalog icon does not imply that every SMS provider or MMS format is supported.
Yes. Mailing targets use the existing publishing workflow, including scheduled publication and configured content approvals. Review the final sender, recipient list and message preview before the scheduled action.
The limit is 70 UTF-16 units for the entire outgoing text, including any opt-out URL. That is not always 70 visible characters: emoji and combined characters can consume more units. Use the exact composition preview to check the result.
No. This SMS list workflow produces short plain-text messages. Attachments, MMS and multipart SMS are not included. Consider an email mailing list when your update needs more explanation or supported attachments.
When sending begins, the operation freezes its recipients and content. Current suppression is checked again before a pending recipient delivery is claimed, so later opt-outs can still exclude recipients who have not yet been claimed. A message already accepted by the provider cannot be recalled by editing the list.
Build the surrounding workflow
Bring content creation, list publishing and customer support together with the right configuration.
PUT IT INTO PRACTICE
Follow the setup, understand the controls and find the next step.
Configure an authorized 019SMS sender, import phone recipients, preview the 70-unit message and inspect delivery results.
Understand Telegram Bot/User and WhatsApp support capture, Facebook and Instagram publishing, activation boundaries and provider-specific reply limits.
Create a post, check channel variants, choose review and scheduling, and read publication results in EleonEcho.
Your next chapter, with AI
Bring your publishing, marketing and support work into Echo.
