SMS campaigns on WebEngage are sent through SMS Service Providers (SSPs) of your choice. While you will use WebEngage to create the SMS campaign, the actual delivery of the message happens through a service provider like Twilio, Plivo etc.

WebEngage provides ready-to-use integrations with a number of SMS Service Providers (SSPs).

You can configure and add any of these SSPs to your project by clicking on Integration > Channels menu on the top-right and then navigating to the SMS section.

In the SMS section, you will see the various SSPs you can configure and add to your project. If you have already added some SSPs to your project, you will see this list as well. In the screenshot below, you can see two Twilio accounts already added to the project. You can also see various logos that represent the SSPs you can add to your project.

In the following sections, we will go through the details of how you can configure and add the various SSPs available on WebEngage to your project.


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.