Schedule a template message

POST 
/v1/desks/:desk_id/conversations/:session_id/scheduled-messages

Schedule a message for future delivery (30 seconds to 14 days ahead) in an open conversation. The payload follows the conversation's channel, resolved from its integration: WhatsApp takes a template, while SMS and RCS take a plain-text { text } body. Email and voice conversations are not supported. At the scheduled time the message is delivered in the original conversation, or skipped silently when it was cancelled, the conversation is no longer open, or the session has expired — it never opens a new conversation. Any reply from the contact cancels all pending scheduled messages for the conversation. WhatsApp template body placeholders must be positional ({{1}}..{{n}}).

Permissions - desks.read and conversations.write. API keys - not supported; requires user (JWT) authentication.

Request

Responses

201

The message was scheduled successfully

400

BadRequest

Response Headers

X-Request-Id
Unique identifier for the API request, useful for debugging and tracking.
Example: abc123xyz789

401

Unauthorized

Response Headers

X-Request-Id
Unique identifier for the API request, useful for debugging and tracking.
Example: abc123xyz789

403

Forbidden - scheduled messages require user authentication, not API keys

404

The specified resource was not found

Response Headers

X-Request-Id
Unique identifier for the API request, useful for debugging and tracking.
Example: abc123xyz789

409

The conversation is not open

429

The per-session scheduled-message limit (3) has been reached

500

Internal Server Error

Response Headers

X-Request-Id
Unique identifier for the API request, useful for debugging and tracking.
Example: abc123xyz789