Send an outbound SMS/RCS
Send an outbound SMS or RCS message and open a reply-enabled conversation session.
POST
Send an outbound SMS/RCS
Sends an outbound message to the specified user number and opens a new conversation session. The endpoint handles both SMS and RCS on the same route: for SMS, send to a plain E.164 number; for RCS, prefix the recipient number with
This can lead to a conversation like:
rcs: and pass a Twilio Messaging Service SID for your RCS sender in messaging_service_sid. If the recipient’s device or carrier doesn’t support RCS, delivery automatically falls back to SMS. The message behaves like a greeting, so it is fully part of the conversation context that the agent can access. If the user replies, the agent handles the conversation as a normal SMS or RCS session.
Request
Headers
string
required
Your PolyAI API key, provisioned in the API keys tab under your account section in Agent Studio.
string
required
Connector ID for the target project. Contact your PolyAI representative.
string
required
Must be
application/json.Body
string
The plain-text message to send to the user. Delivered as RCS when the recipient supports it, or as SMS otherwise.
string
required
Recipient phone number in E.164 format (e.g.
+14155551234). For RCS, prefix the number with rcs: (e.g. rcs:+14155551234).string
Sender phone number in E.164 format. Must be one of the numbers provisioned for your project. If omitted, the API picks one automatically from the numbers available for the connector token’s environment. Not used for RCS — RCS senders are selected via
messaging_service_sid.string
Required for RCS. The Twilio Messaging Service SID for your RCS sender.
Response
The
202 response has an empty body.
Example
SMS
RCS
Outbound RCS uses the same endpoint. Prefixuser_number with rcs: and pass the Twilio Messaging Service SID for your RCS sender in messaging_service_sid. If the recipient’s device doesn’t support RCS, the message automatically falls back to SMS — no extra handling needed.
cURL
Error response format
All error responses return a JSON object:Notes
- SMS vs RCS delivery — SMS is sent to a plain E.164
user_number. RCS requires anrcs:prefix onuser_numberand amessaging_service_sid. If the recipient can’t receive RCS, delivery automatically falls back to SMS. - Agent number selection — by default the API picks from the numbers provisioned for your project for the environment linked to the connector token. Pass
agent_numberto override; it must be one of the provisioned numbers or the request is rejected with a400. - Rate limits are applied per project. If you hit a
429, back off and retry. - Inactivity timeout — if the conversation is engaged (the user has replied), after 24 hours of inactivity a warning message is sent. If the user replies within 10 minutes, the conversation stays open and a new 24-hour inactivity timer starts. Otherwise the session terminates.
- Number availability — not every country supports SMS or RCS. Check Number availability & compliance for country-by-country details, throughput limits, and regulatory links before sending to a new region.
Last modified on August 19, 2026
Send an outbound SMS/RCS

