sinch-api-messages-send-choice

Send choice and quick-reply button messages via the Sinch Conversation API.

6|2|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/sinch/sinch-plugins --skill sinch-api-messages-send-choice-sinch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sinch-api-messages-send-choice
Source: https://github.com/sinch/sinch-plugins/tree/main/plugins/sinch-antigravity-plugin/skills/sinch-api-messages-send-choice
Command: npx skills add https://github.com/sinch/sinch-plugins --skill sinch-api-messages-send-choice-sinch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sending interactive messages with tappable buttons or quick replies through the Sinch Conversation API requires constructing a specific choice_message payload with postback data, which is error-prone when done manually. ## Core Features & Use Cases - Choice Message Delivery: Send a text message accompanied by selectable choice buttons to a recipient over RCS, WhatsApp, or SMS channels. - Automatic Postback Generation: Each choice label gets a postback_data slug so user taps are reported back to your webhook. - MCP and REST Fallback: Uses the Sinch MCP tool when available, otherwise calls the Conversation API directly with OAuth2 credentials. - Use Case: A support team sends "How can we help?" with Sales, Support, and Feedback buttons so customers can route themselves with one tap. ## Quick Start Ask the assistant to send a choice message to a phone number with your message text and a comma-separated list of button labels, for example send a choice message to +14155551234 saying "Confirm order?" with choices Yes and No.

Frequently Asked Questions about sinch-api-messages-send-choice

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send a quick-reply button message with the Sinch Conversation API?

Provide the recipient phone number in E.164 format, the main message text, and a comma-separated list of choice labels. The skill builds a choice_message payload with postback_data for each label and posts it to the messages:send endpoint.

Which channels support choice messages in Sinch?

Choice messages are supported on RCS and WhatsApp and other interactive channels, with RCS as the default because it supports the most buttons. SMS has limited interactivity, so choice count and layout vary by channel.

What credentials are required to send Sinch choice messages?

You need CONVERSATION_PROJECT_ID, CONVERSATION_KEY_ID, CONVERSATION_KEY_SECRET, CONVERSATION_REGION, and CONVERSATION_APP_ID environment variables. If the Sinch MCP server is configured, its send-choice-message tool is used instead of direct credentials.

What happens when a user taps a choice button?

The postback_data generated for that choice, typically a slug of the label, is sent to your configured webhook. Your application can then process the selection and continue the conversation.

Why does my Sinch choice message fail to send?

Common causes are missing CONVERSATION_* environment variables, a recipient number not in E.164 format, or an empty choices list. The skill reports "Sinch API is not configured" when credentials are absent.