Passer au contenu
On this page
Cycle de vie & automatisation

Create and send an SMS campaign

Prepare a concise, consent-safe SMS, test its destination, and monitor provider delivery.

Available when the workspace has the required customer data and channel setup; activation or sending requires publish permission.
Open this feature in Leado
Expected outcome

What you’ll achieve

  • A short, attributable SMS delivered through a configured provider only to eligible, consented recipients.
Pas à pas

Suivez le flux de travail

  1. 1

    Open Actions → Messages → SMS

    Confirm the active workspace and provider readiness, then select Create SMS. Use a provider and sender identity authorized for the intended destination countries.

  2. 2

    Choose the audience

    Select contacts with a valid phone number and SMS marketing consent. Apply suppressions, exclusions, country rules, and frequency controls before relying on the displayed estimate.

  3. 3

    Write for the channel

    Add the essential offer or update, brand identity where required, one clear destination, and required opt-out language. Watch character count, Unicode, and segment count because they affect readability and cost.

  4. 4

    Choose SMS or RCS preferred

    Use SMS for standard delivery. Where the selected Twilio or ClickSend setup reports RCS enabled, RCS preferred can use the approved RCS sender with provider SMS fallback. Verify destination-country support before relying on it.

  5. 5

    Add dynamic product context carefully

    The SMS editor supports variables such as `{{product_title}}`, `{{product_url}}`, and `{{discount_code}}`; it does not expose the visual recommendation-source picker used by email or Web Push. Ensure the selected audience or workflow supplies usable values and destinations.

  6. 6

    Save and review the native preview

    Check the phone preview, brand prefix, target URL, unsubscribe text, character encoding, and segment count. Leado does not provide a separate SMS test button; if a live test is required, use a deliberately created one-contact consented audience and treat it as an external send.

  7. 7

    Schedule or send after approval

    Verify local quiet hours, campaign timezone, recipient countries, and final segment count. Sending is an external action and requires publish permission.

  8. 8

    Monitor delivery and opt-outs

    Review queued, sent, delivered, failed, and opted-out results. Remove invalid numbers and ensure unsubscribe events update future audience eligibility.

Quality check

Verify your work

  • The selected provider, sender, and SMS or RCS-preferred state show ready
  • The preview and, when authorized, a controlled one-contact live send resolve variables and open the intended destination
  • Delivery failures and opt-outs update campaign reporting and contact eligibility
Troubleshooting

If something doesn’t look right

Send is disabled

Configure an SMS provider, save the draft, and confirm your publish permission.

A product variable is blank

Verify the audience or triggering event supplies the product title, URL, or discount value.

RCS preferred is disabled

Use a Twilio or ClickSend configuration with approved RCS enabled, or send standard SMS.

Cost is higher than expected

Remove unnecessary Unicode characters or shorten copy to reduce SMS segments.

Scope

Limitations and safeguards

Limit

Sender types, RCS availability and fallback, quiet hours, opt-out wording, delivery receipts, and two-way replies vary by provider and country.

Aidez-nous à améliorer

Ce guide a-t-il été utile ?