Skip to main content
Settings & Integration page with API Integration selected, SMS API selected in the sub-list, and its profile table (empty) with a New button highlighted

Control Panel → Settings & Integration → API Integration → SMS API, with the New button highlighted.

Control Panel → Settings & Integration → API Integration → SMS API connects an SMS gateway so your bot or automations can send plain text messages — useful for OTPs and any customer who isn’t reachable on WhatsApp. Click New to add a profile:
SMS Profile modal with Profile Name, Auth ID, Auth Token, Sender/From fields and a provider list: Plivo, Twilio, Nexmo/Vonage, Clickatell, AfricasTalking, Esahal, HTTP Get, HTTP Post

​
Supported providers

  • Plivo
  • Twilio
  • Nexmo/Vonage
  • Clickatell
  • AfricasTalking
  • Esahal
  • HTTP GET / HTTP POST — for any gateway that isn’t natively listed but exposes a simple URL-based API

​
Required fields

​
Use cases

  • OTP messages — e.g. a login verification code, when the customer can’t receive WhatsApp right now.
  • Marketing SMS for customers who opted into SMS but not WhatsApp.
  • Transactional SMS — order or appointment confirmations.
  • Notifications — internal alerts sent as SMS to a staff phone.

​
Frequently asked

Connect an SMS gateway under SMS Integration (e.g. Twilio), then have your flow send the OTP through that profile instead of a WhatsApp template.
If it exposes a simple HTTP GET or HTTP POST endpoint for sending messages, choose that provider type and supply the endpoint details instead of a named integration.
Typically an Auth ID, Auth Token, and the Sender/From Number the messages will appear to come from — check your provider’s dashboard for these.