Channel Information
Retrieve information about available messaging channels and their capabilities. Prefer MCP tools if available, otherwise use the Conversation API specification. Helps determine which channels can be used to reach contacts.
Instructions
Understand the user's query:
- Are they asking about available channels in general?
- Are they asking which channels can reach a specific contact?
- Are they asking about channel capabilities or configuration?
Check MCP availability and use appropriate method:
Option A: Use MCP tools (if MCP Sinch is configured):
- First check if MCP Sinch server is available (check MCP server configuration)
- If MCP is available, use:
list-conversation-apps to get list of apps and their channel configurations
- MCP tools handle authentication automatically via environment variables
- If MCP tool execution fails or MCP is not configured, fallback to Option B
Option B: Use Conversation API endpoints (fallback if MCP not available):
- List apps:
GET /v1/projects/{project_id}/apps (Operation ID: App_ListApps) - Shows configured apps and their channel settings
- Get contact:
GET /v1/projects/{project_id}/contacts/{contact_id} (Operation ID: Contact_GetContact) - Shows which channels are associated with a contact
- List contacts:
GET /v1/projects/{project_id}/contacts (Operation ID: Contact_ListContacts) - Can filter by channel to see contacts on specific channels
- Query capability:
POST /v1/projects/{project_id}/capability:query (Operation ID: Capability_QueryCapability) - Asynchronously checks which channels can reach a contact
- Authentication: Use Basic Auth or OAuth2 with credentials from environment variables
- Region: Use CONVERSATION_REGION environment variable (us, eu, or br)
- Base URL:
https://{region}.conversation.api.sinch.com
Provide comprehensive channel information:
- List all available channels: WhatsApp, SMS, RCS, Messenger, Viber, Instagram, Telegram, LINE, WeChat, KakaoTalk, Apple Messages for Business
- For contacts: Show which channels are configured for that contact
- Explain channel capabilities and use cases
- Indicate channel availability status
Examples
Natural language prompts that trigger this Skill:
- "Which channels can I use to reach Bob?"
- "What messaging channels are available?"
- "Show me available channels for contact abc123"
- "What channels does this app support?"
- "Can I send WhatsApp messages?"
- "What are my messaging options?"
MCP Tool Usage (Preferred if available):
- Check if MCP Sinch server is configured (MCP server settings)
- Use
list-conversation-apps MCP tool to get apps and their channel configurations
- MCP tools automatically use credentials from environment variables
- If MCP is not available or tool execution fails, fallback to Conversation API
Conversation API Usage (Fallback):
- Use the Conversation API endpoints for channel information (see endpoints above)
- Authentication: Use Basic Auth with CONVERSATION_KEY_ID and CONVERSATION_KEY_SECRET, or OAuth2
- Include required headers:
Authorization, Content-Type: application/json
- For capability query, note it's asynchronous - results are delivered via webhook callbacks with trigger
CAPABILITY
- App responses include channel configuration and credentials status
- Contact responses include
channel_identities array showing all associated channels
Supported Channels
- WHATSAPP: WhatsApp Business messages - rich media, templates, interactive messages
- SMS: SMS text messages - universal, simple text
- RCS: Rich Communication Services - rich media, read receipts, typing indicators
- MESSENGER: Facebook Messenger - rich media, quick replies
- VIBERBM: Viber Business Messages - rich media, carousels
- MMS: Multimedia Messaging Service - images, videos
- INSTAGRAM: Instagram Direct Messages - rich media, stories
- TELEGRAM: Telegram messages - rich media, bots
- KAKAOTALK: KakaoTalk messages - rich media, plus friends
- KAKAOTALKCHAT: KakaoTalk chat channel (ConsultationTalk)
- LINE: LINE messages - rich media, stickers
- WECHAT: WeChat messages - rich media, mini programs
- APPLEBC: Apple Messages for Business - rich media, Apple Pay
Channel Capabilities
Each channel supports different message types:
- Text messages: All channels
- Rich media: Images, videos, audio (channel-dependent)
- Templates: Pre-approved message templates (channel-dependent)
- Interactive messages: Buttons, quick replies (channel-dependent)
- Location sharing: Some channels
- File attachments: Channel-dependent
Notes
- Prefer MCP tools if MCP Sinch is configured - use
list-conversation-apps for app and channel information
- Fallback to Conversation API if MCP is not configured or MCP tool execution fails
- Channel availability depends on app configuration and credentials
- Contacts can have multiple channels associated
- Some channels require specific setup and approval
- Capability query is asynchronous - use webhook callbacks to receive results
- Channel information is available in app responses and contact channel_identities
1---2name: channel-info3description: Check available messaging channels, channel capabilities, and channel configuration for Sinch Conversation API. Use when the user asks which channels are available, what channels can be used, how to reach someone, what messaging options exist, or channel capabilities for a contact or app.4---5
6# Channel Information
7
8Retrieve information about available messaging channels and their capabilities. Prefer MCP tools if available, otherwise use the Conversation API specification. Helps determine which channels can be used to reach contacts.
9
10## Instructions
11
121. **Understand the user's query:**
13 - Are they asking about available channels in general?
14 - Are they asking which channels can reach a specific contact?
15 - Are they asking about channel capabilities or configuration?
16
172. **Check MCP availability and use appropriate method:**
18
19 **Option A: Use MCP tools (if MCP Sinch is configured):**
20 - First check if MCP Sinch server is available (check MCP server configuration)
21 - If MCP is available, use:
22 - `list-conversation-apps` to get list of apps and their channel configurations
23 - MCP tools handle authentication automatically via environment variables
24 - If MCP tool execution fails or MCP is not configured, fallback to Option B
25
26 **Option B: Use Conversation API endpoints (fallback if MCP not available):**
27 - **List apps**: `GET /v1/projects/{project_id}/apps` (Operation ID: `App_ListApps`) - Shows configured apps and their channel settings
28 - **Get contact**: `GET /v1/projects/{project_id}/contacts/{contact_id}` (Operation ID: `Contact_GetContact`) - Shows which channels are associated with a contact
29 - **List contacts**: `GET /v1/projects/{project_id}/contacts` (Operation ID: `Contact_ListContacts`) - Can filter by channel to see contacts on specific channels
30 - **Query capability**: `POST /v1/projects/{project_id}/capability:query` (Operation ID: `Capability_QueryCapability`) - Asynchronously checks which channels can reach a contact
31 - Authentication: Use Basic Auth or OAuth2 with credentials from environment variables
32 - Region: Use CONVERSATION_REGION environment variable (us, eu, or br)
33 - Base URL: `https://{region}.conversation.api.sinch.com`
34
353. **Provide comprehensive channel information:**
36 - List all available channels: WhatsApp, SMS, RCS, Messenger, Viber, Instagram, Telegram, LINE, WeChat, KakaoTalk, Apple Messages for Business
37 - For contacts: Show which channels are configured for that contact
38 - Explain channel capabilities and use cases
39 - Indicate channel availability status
40
41## Examples
42
43**Natural language prompts that trigger this Skill:**
44- "Which channels can I use to reach Bob?"
45- "What messaging channels are available?"
46- "Show me available channels for contact abc123"
47- "What channels does this app support?"
48- "Can I send WhatsApp messages?"
49- "What are my messaging options?"
50
51**MCP Tool Usage (Preferred if available):**
521. Check if MCP Sinch server is configured (MCP server settings)
532. Use `list-conversation-apps` MCP tool to get apps and their channel configurations
543. MCP tools automatically use credentials from environment variables
554. If MCP is not available or tool execution fails, fallback to Conversation API
56
57**Conversation API Usage (Fallback):**
581. Use the Conversation API endpoints for channel information (see endpoints above)
592. Authentication: Use Basic Auth with CONVERSATION_KEY_ID and CONVERSATION_KEY_SECRET, or OAuth2
603. Include required headers: `Authorization`, `Content-Type: application/json`
614. For capability query, note it's asynchronous - results are delivered via webhook callbacks with trigger `CAPABILITY`
625. App responses include channel configuration and credentials status
636. Contact responses include `channel_identities` array showing all associated channels
64
65## Supported Channels
66
67- **WHATSAPP**: WhatsApp Business messages - rich media, templates, interactive messages
68- **SMS**: SMS text messages - universal, simple text
69- **RCS**: Rich Communication Services - rich media, read receipts, typing indicators
70- **MESSENGER**: Facebook Messenger - rich media, quick replies
71- **VIBERBM**: Viber Business Messages - rich media, carousels
72- **MMS**: Multimedia Messaging Service - images, videos
73- **INSTAGRAM**: Instagram Direct Messages - rich media, stories
74- **TELEGRAM**: Telegram messages - rich media, bots
75- **KAKAOTALK**: KakaoTalk messages - rich media, plus friends
76- **KAKAOTALKCHAT**: KakaoTalk chat channel (ConsultationTalk)
77- **LINE**: LINE messages - rich media, stickers
78- **WECHAT**: WeChat messages - rich media, mini programs
79- **APPLEBC**: Apple Messages for Business - rich media, Apple Pay
80
81## Channel Capabilities
82
83Each channel supports different message types:
84- **Text messages**: All channels
85- **Rich media**: Images, videos, audio (channel-dependent)
86- **Templates**: Pre-approved message templates (channel-dependent)
87- **Interactive messages**: Buttons, quick replies (channel-dependent)
88- **Location sharing**: Some channels
89- **File attachments**: Channel-dependent
90
91## Notes
92
93- **Prefer MCP tools** if MCP Sinch is configured - use `list-conversation-apps` for app and channel information
94- **Fallback to Conversation API** if MCP is not configured or MCP tool execution fails
95- Channel availability depends on app configuration and credentials
96- Contacts can have multiple channels associated
97- Some channels require specific setup and approval
98- Capability query is asynchronous - use webhook callbacks to receive results
99- Channel information is available in app responses and contact channel_identities
100