Respond.io
AI-powered customer conversation management software.
Verdict
Common use cases
- Triage support tickets from multiple channels
- Log handoff notes for overnight shift
- Tag high-value leads during discovery calls
- Audit team response times by user
- Create contacts from inbound demo requests
Integration
- Vendor
- Respond.io
- Category
- other
- Auth
- API_KEY
- Tools
- 8
- Composio slug
respond_io
Tools
- Add internal comment to conversation
Tool to add a comment (internal note) to a contact's conversation. use after verifying the contact identifier.
- Add internal comment to conversation
Tool to add a comment (internal note) to a contact's conversation. use after verifying the contact identifier.
- Create Contact
Tool to create a new contact in the workspace. use when you need to add a contact by specifying an identifier; delay subsequent actions due to processing.
- Create Space Tag
Tool to create a new tag in the workspace. use when you need to label or categorize contacts or conversations after workspace setup.
- Get Message
Tool to retrieve a specific message. use when you need the details of a message sent to or received from a contact.
- List channels
Tool to retrieve a list of channels connected to the workspace. use when you need to enumerate all messaging channels with pagination support.
- List users
Tool to retrieve a list of users in the workspace. use when you need to fetch all workspace users for auditing or assignment.
- Update Space Tag
Tool to update an existing tag in the workspace. use when you need to modify a tag's name, description, color, or emoji after confirming it exists.
Setup
Setup guide
- 11. In Switchy, open the Space where you want to use Respond.io and click the integrations panel. 2. Search for Respond.io and select 'Connect'. 3. In a new tab, log into your Respond.io workspace, navigate to Settings > API, and generate a new API key with read and write permissions. 4. Copy the key and paste it into Switchy's connection dialog, then click 'Authorize'. 5. Back in your Space, type '@Respond.io list channels' and send; if the MCP returns your connected messaging channels, the integration is live. 6. To invoke any tool, start your message with '@Respond.io' followed by the action — for example, '@Respond.io add internal comment to conversation [conversation_id] noting customer prefers email follow-up'.
What teammates see: by default, memories from Respond.io are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Active Channels
@Respond.io list all channels in the workspace and show me their names and connection status.Open in a Space →
Add Handoff Note
@Respond.io add an internal comment to conversation 12345 noting the customer wants a callback tomorrow at 2pm EST.Open in a Space →
Create New Contact
@Respond.io create a contact with phone number +1234567890 and name Alex Chen for follow-up.Open in a Space →
Tag Urgent Conversations
@Respond.io create a tag called 'Urgent' with red color, then apply it to conversation 67890.Open in a Space →
Retrieve Message Details
@Respond.io get message abc123 and show me the sender, timestamp, and content.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@respond.io list all channels connected to our workspace and show which ones have the most activity this week
Based on the channel list retrieved from Respond.io, your workspace has 5 active channels: WhatsApp Business (ID: ch_wa_001), Facebook Messenger (ID: ch_fb_002), Telegram (ID: ch_tg_003), Instagram DM (ID: ch_ig_004), and LINE (ID: ch_line_005). The API returns channel metadata including connection status and identifiers, but does not include activity metrics. To analyze this week's activity, you would need to cross-reference conversation data separately. All channels show 'connected' status as of this query.
This example shows the MCP's ability to enumerate messaging channels, useful for auditing your omnichannel setup. Note that the list_channels tool returns configuration data only—conversation volume or engagement metrics require additional queries or external analytics. Requires read access to workspace channel settings.
@respond.io create a new contact for sarah.chen@example.com and add an internal note that she's a priority lead from the enterprise demo
Contact created successfully for sarah.chen@example.com (Contact ID: cnt_9x4k2). An internal comment has been added to her conversation thread: 'Priority lead from enterprise demo—follow up within 24 hours.' Note that Respond.io processes new contacts asynchronously, so there may be a brief delay before the contact appears in all workspace views or becomes available for message sending. The contact is now visible in your workspace and tagged for follow-up.
This example demonstrates the MCP's write capabilities for contact management and internal collaboration. The create-then-comment workflow is common for lead intake. Be aware that contact creation triggers background processing, so immediate follow-up actions (like sending a message) may need a short delay. Requires API key with contact:write and conversation:comment permissions.
@respond.io pull the last message from contact ID cnt_7h3m9 and draft a professional reply addressing their refund request
The most recent message from contact cnt_7h3m9 (received via WhatsApp at 2:47 PM today) reads: 'Hi, I still haven't received my refund for order #8834. It's been 10 days. Can someone help?' Based on this, here's a draft reply: 'Hi [Name], thank you for your patience. I've escalated your refund for order #8834 to our finance team. Refunds typically process within 7-10 business days, but I see yours is overdue. You should see the credit within 2 business days. I'll follow up personally to confirm. Apologies for the delay.' This response acknowledges the delay, provides a timeline, and commits to follow-up.
This example pairs the MCP's message retrieval with AI reasoning to draft context-aware responses. The get_message tool returns the raw message content and metadata, which the AI then uses to generate a reply. This workflow is powerful for customer support triage, but always review AI-drafted responses before sending—especially for sensitive issues like refunds. The MCP retrieves messages; it does not send them.
Use-case deep-dives
When Respond.io beats a shared Slack channel for customer triage
A 10-person SaaS team fields 40-60 customer messages daily across WhatsApp, Telegram, and web chat. The support lead wants AI to tag urgent issues and route them to the right engineer without copying threads into Slack. Respond.io's MCP wins here because it exposes conversation tagging, internal comments, and user assignment in one workspace. Switchy can read the last five messages, tag the conversation "billing-urgent", add an internal note summarizing the issue, and ping the finance engineer—all without leaving the AI session. The threshold: if your team uses more than three messaging channels or needs audit trails for compliance, this MCP justifies the API key setup. If you're still on email-only support, stick with Gmail's MCP and revisit when you add chat channels.
Using Respond.io to score inbound leads before the first call
A four-person sales team at a B2B agency gets 20-30 inbound leads weekly via Facebook Messenger and Instagram DMs. The founder wants AI to score each lead by extracting company size, budget signals, and urgency from the initial conversation, then tag high-intent prospects for immediate follow-up. Respond.io's MCP handles this because it lets Switchy create contacts, retrieve message history, and apply tags without manual CSV exports. The AI reads the conversation, creates a contact record with the lead's identifier, tags it "high-intent" or "nurture", and adds an internal comment with the score rationale. This works best for teams closing deals under $10k where speed matters more than CRM depth. If your sales cycle involves multi-touch attribution or Salesforce syncs, you'll need a heavier integration—but for fast qualification at small scale, this MCP closes the gap.
When to use Respond.io for post-purchase feedback loops
A six-person e-commerce brand collects customer feedback across WhatsApp, Telegram, and web chat after every order. The ops manager wants AI to scan conversations for product complaints, tag them by issue type (shipping, quality, sizing), and summarize trends weekly without hiring a VA. Respond.io's MCP fits because it centralizes messages from multiple channels and exposes tagging and retrieval tools. Switchy can list recent conversations, filter by keyword patterns, apply tags like "defect-reported", and compile a summary of the top three issues. The catch: if your feedback volume exceeds 200 conversations per week, the MCP's pagination and rate limits will slow down bulk analysis—at that scale, export to a data warehouse and query there. For sub-200 weekly conversations, this MCP turns feedback chaos into actionable tags in under five minutes per session.
Frequently asked
What does the Respond.io MCP let me do in Switchy?
It connects your Respond.io workspace so AI agents can read messages, create contacts, tag conversations, and add internal comments. You can automate customer support triage, log notes from Slack threads directly into Respond.io, or sync contact data across tools without switching tabs.
Do I need admin access to connect Respond.io?
You need an API key from your Respond.io workspace settings. Only workspace admins can generate API keys, so if you're not an admin you'll need to ask one to create the key and share it with you in Switchy's connection flow.
Can the MCP send outbound messages to customers?
No. The eight tools focus on reading messages, managing contacts, and adding internal comments or tags. If you need to send replies to customers, use Respond.io's UI or their separate messaging API—this MCP is built for logging and coordination, not outbound campaigns.
How is this different from using Respond.io's web app?
The MCP lets AI agents pull message history and contact data into Switchy workflows without manual copy-paste. You still use Respond.io's app for sending replies and configuring channels, but the MCP handles the repetitive lookup and tagging tasks that slow down support teams.
Who on my team should connect the Respond.io MCP?
Whoever owns customer support tooling or has admin rights in Respond.io. Once connected, any Switchy user in your workspace can invoke the tools in their AI chats—but the API key grants read access to all conversations, so treat it like a shared credential.