SMS
Mercleo Events can send announcements by SMS via Twilio. Your workspace uses the platform Twilio account by default — per-workspace credentials are not yet self-configurable.
Updated May 26, 2026
Mercleo Events delivers announcements by SMS through Twilio. Credentials are resolved at the organization level: if your workspace has tenant-specific Twilio credentials configured on the back end, those are used; otherwise Mercleo's platform Twilio account handles delivery.
There is no UI to configure your own Twilio credentials today. All workspaces share the Mercleo platform Twilio account. Per-workspace 10DLC self-serve onboarding is planned as a future release.
Where SMS works
SMS is available on announcements only. Email campaigns do not support SMS — the channel selector in the campaign editor offers email only.
When you create or edit an announcement, a channel selector lets you choose email, SMS, or both. Selecting both does not send to every recipient twice — see the gotcha below.
When you select both email and SMS, attendees who have SMS consent receive the announcement by SMS only — not by both. Email is sent only to attendees who are ineligible for SMS (no consent, no verified phone, etc.).
How attendees opt in
SMS consent is stored on each attendee's identity record. There are two separate consent flags: SMS marketing consent and SMS transactional consent.
Attendees grant consent during the registration flow. You control which consent language appears by editing your Marketing Consent settings (under your event settings). A verified phone number is also required — an attendee who consented but never verified their phone will not receive SMS.
Quiet hours
TCPA guidelines restrict marketing SMS to between 8 am and 9 pm in the recipient's local time. If your local time is outside that window when you send an announcement with the SMS channel selected, Mercleo displays a warning.
The warning is advisory — you can override it and send immediately. You are responsible for compliance with applicable messaging regulations.
Testing SMS
Each announcement form includes a Send test option when SMS is the selected channel. Enter a phone number in E.164 format (e.g., +16135550123) and the current title and body are sent immediately to that number.
Test sends bypass all consent checks and do not create a recipient record. They are for verifying message content only — use them before sending to your full attendee list.
When SMS is skipped
An attendee is skipped for SMS delivery when any of the following apply:
- No SMS consent on their identity record.
- No verified phone number on their identity record.
- No E.164-formatted phone number stored on their record.
- They registered before the attendee identity system was introduced — those records have SMS transactional consent defaulting to false and are skipped.
- Twilio credentials are unavailable for your workspace — the send is short-circuited with "SMS is not configured for this workspace".