# SMS

<Aside type="tip">
To start working with the SMS channel, connect your SMS provider in **Settings → Configure Platforms → SMS**. [Learn how](/product/first-steps/start-with-your-project/configure-platforms/sms-configuration/) Otherwise, sending SMS will not be available.
</Aside>

**SMS** element indicates a point to communicate with a customer via SMS.

<Aside type="caution" icon="setting" title="Developer assistance needed">
To send SMS using Customer Journey Builder, first ask your developer team to associate customer phone numbers with **UserId** using the [/registerDevice](/developer/api-reference/device-api#registerdevice) method. The phone number must be specified in the "hwid" parameter.
</Aside>

To send SMS to users within the journey, add the **SMS** element to the canvas next to any element. Choose a preset or enter the text of the SMS manually.

<img src="/shared-30.webp" alt="SMS element on journey canvas with preset and text options"/>

<Aside type="note">
If you want to use an [SMS preset](/product/content/sms-presets), create it in the **Content** → **SMS presets** section. You can also use [Dynamic Content](/product/personalization/dynamic-content/) in the message text. [Learn more](/product/content/sms-presets)
</Aside>

## Set message type

Choose **Marketing message** or **Transactional message**:

* **Marketing message**: For campaigns and promos. All rules and limits apply. Respects: Opt-outs, Frequency capping, and Silence period. Excludes: the [global control group](/product/audience-data-and-segmentation/global-control-group/).
* **Transactional message**: For operational or service messages. Rules and limits don't apply. Bypasses: Opt-outs, Frequency capping, and Silence period. Sent to: the [global control group](/product/audience-data-and-segmentation/global-control-group/).

<img src="/messaging-channels-sms-4.webp" alt="SMS element message type selection with Marketing message and Transactional message options"/>

[Learn how message type affects delivery](/product/messaging-channels/marketing-vs-transactional/).

## Overwrite personalization

When you select a preset, you can overwrite how the message is personalized:

* **Personalise message with event attributes:** Enable this option to use event attributes or API-based entry placeholders instead of device tags as value sources in message content and presets. [Learn more](/product/customer-journey/journey-elements/dynamic-content-and-liquid-templates-in-journeys)
* **Overwrite Liquid placeholders:** Enable this option to use values from the selected Event in Liquid personalization. Liquid tags that match event attribute names will use values from the event. [Learn more](/product/customer-journey/journey-elements/dynamic-content-and-liquid-templates-in-journeys)
* **Use Vouchers:** Enable this option to use vouchers in message content. [Learn more](/product/content/vouchers/)

<img src="/messaging-channels-sms-5.webp" alt="SMS element overwrite personalization options showing event attributes, Liquid placeholders, and vouchers toggles"/>


## Configure message delivery settings  
### Set frequency capping

<Aside type="note">
Frequency capping options are available only when **Marketing message** is selected. When you choose **Transactional message**, frequency capping doesn't apply and these options are disabled.
</Aside>

Use [**Frequency capping**](/product/messaging-channels/global-frequency-capping/#enable-global-frequency-capping) to control how often users receive SMS messages, helping prevent message fatigue and opt-outs.

You can choose one of the following options:

* **Use global frequency capping settings**
  Apply the project-wide SMS limits set in your [Global frequency capping settings](/product/messaging-channels/global-frequency-capping/#enable-global-frequency-capping).
  *Example:* If the global limit is 3 SMS messages in 9 days, any additional messages will be skipped.

* **Ignore global frequency capping**
  Send the SMS regardless of how many messages the user has already received. Use with caution to avoid over-messaging and compliance issues.

* **Use custom frequency capping**
  Set a custom SMS limit specifically for this message step. If the user has reached the limit, they will skip this message and move to the next step in the journey.
  [Learn more](/product/messaging-channels/global-frequency-capping/#customize-capping-for-specific-messages)
### Set send rate limits 

The **Send rate** setting controls how quickly messages are delivered to your audience. Adjusting the send rate helps you manage delivery speed, prevent backend overload, and improve overall deliverability.

Choose one of the following options:

* **Use global send rate settings**  
  Applies the send rate limits configured in your project’s message delivery settings. If no limits are set, all messages will be sent immediately. Use this option when you want delivery speed to follow your project’s default rules. [Learn more about global send rate limits](/product/messaging-channels/global-frequency-capping/#set-send-rate-limits) 

![Use global send rate settings](/send-rate-in-journey-elements-1.webp)

* **Send messages without send rate**  
  Sends messages as fast as possible, ignoring any global send rate limits. Use with caution to avoid overloading your backend or creating delivery spikes.

![Send messages without send rate](/send-rate-in-journey-elements-2.webp)

* **Use custom send rate**  
  Overrides the global send rate for this message only. Allows you to specify the number of messages sent per minute, giving you full control over delivery speed. Messages will be sent at the custom rate you define in the message element.

![Use custom send rate](/send-rate-in-journey-elements-3.webp)

## Flow options

Enable the **Split flow depending on whether this message is delivered or not** toggle to split the journey based on whether the SMS is delivered.

Then, set the delivery waiting time.

If the SMS is delivered within the specified time period, the `"delivered"` branch will be activated. Maximum 7 days.

<img src="/shared-57.webp" alt="Split flow depending on whether the SMS is delivered"/>