Supportbee
SupportBee is a web-based email support tool that helps businesses organize their customer support emails efficiently.
Verdict
Common use cases
- Triage new tickets during morning standup
- Archive resolved tickets in bulk
- Create canned responses as reusable snippets
- Assign tickets to teammates by customer domain
- Pull ticket history before customer calls
Integration
- Vendor
- Supportbee
- Category
- other
- Auth
- API_KEY
- Tools
- 33
- Composio slug
supportbee
Tools
- Archive SupportBee Ticket
Tool to archive a supportbee ticket by its id. use when you want to move resolved tickets to the archive.
- Assign Ticket to Team
Tool to assign a ticket to a team. use after confirming ticket and team ids are valid.
- Create Rule
Tool to create a new routing or automation rule in supportbee. use after defining rule conditions and actions.
- Create Snippet
Tool to create a reusable snippet for ticket responses. use when you need to store and reuse response templates.
- Create SupportBee Ticket
Tool to create a new support ticket. use when you need to open a ticket with subject, requester email, and content.
- Create SupportBee User
Tool to create a new user in supportbee. use when you need to provision an agent or admin via api.
- Create Ticket Reply
Tool to post a reply to a ticket. use after retrieving ticket details to respond to customers.
- Delete Snippetdestructive
Tool to delete a snippet by its id. use when you need to permanently remove an unwanted snippet.
- Delete SupportBee Ticketdestructive
Tool to permanently delete a trashed ticket. use when you need to remove a ticket from trash permanently.
- Fetch Emails
Tool to retrieve all forwarding email addresses for the company. use when you need to view or manage forwarding emails.
- Fetch Snippets
Tool to fetch all saved snippets. use when you need to list available snippets for the company.
- Fetch SupportBee Labels
Tool to retrieve all custom labels. use when you need to list labels for ticket categorization.
- Fetch SupportBee Team by ID
Tool to fetch a supportbee team by its id. use when you need to retrieve details of a specific team after confirming its id is valid.
- Fetch SupportBee Teams
Tool to retrieve all teams in the company. use when you need to list teams for organizing tickets by team.
- Get Avg First Response Time Report
Tool to retrieve average first response time data points. use when analyzing first-response performance metrics within a given period.
- Get Replies Count Report
Tool to get replies count data points over time. use when analyzing agent reply performance over a date range.
- Get Tickets Count Report
Tool to get ticket count data points over time. use when you need the total number of tickets for a given date range.
- List Ticket Comments
Tool to list all comments for a ticket. use after confirming the ticket id to retrieve its conversation history.
- List Ticket Replies
Tool to list all replies for a specific ticket. use after confirming the ticket id is valid.
- List Tickets
Tool to list tickets. use when you need a paginated view of tickets with optional filters.
- Mark SupportBee Ticket as Answered
Tool to mark a ticket as answered. use after sending response to update ticket status.
- Mark SupportBee Ticket as Spam
Tool to mark a supportbee ticket as spam. use when you need to flag unwanted or malicious ticket submissions after obtaining the ticket id.
- Mark SupportBee Ticket as Unanswered
Tool to mark a ticket as unanswered. use after confirming the ticket was previously marked as answered to revert its status.
- Search SupportBee Tickets
Tool to search supportbee tickets. use when you need to find tickets by query with pagination.
- Show SupportBee User or Customer Group
Tool to retrieve a user or customer group by id. use when you need details for a specific user or group after confirming the id.
- Show Ticket Reply
Tool to fetch a specific reply for a supportbee ticket. use when you need details of a single reply by ticket and reply ids.
- Trash SupportBee Ticket
Tool to trash a supportbee ticket by its id. use when you need to remove a ticket into the trash folder.
- Unarchive SupportBee Ticket
Tool to unarchive a supportbee ticket by its id. use when you need to restore an archived ticket back to active status.
- Unassign Ticket from Team
Tool to un-assign a ticket from its assigned team. use when you need to remove the current team ownership before reassigning or closing the ticket.
- Unassign User From Ticket
Tool to unassign the user from a ticket. use when you need to remove the assigned user before reassigning or closing a ticket.
- Unmark SupportBee Ticket as Spam
Tool to unmark a supportbee ticket as spam. use when a ticket was incorrectly flagged as spam.
- Untrash SupportBee Ticket
Tool to untrash (restore) a supportbee ticket by its id. use when you need to move a trashed ticket back to active status.
- Update SupportBee User
Update supportbee user
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Search for SupportBee and click Connect. 3. Log into your SupportBee account, go to Settings > API Token, and copy your API key. 4. Paste the key into Switchy's connection dialog and click Authorize. 5. Switchy confirms the connection and lists available tools. 6. Open any Space, type '@SupportBee list tickets assigned to me' and send — if you see ticket data, the integration works. 7. To invoke tools, @mention SupportBee in any message and describe the task in plain English; the AI routes your request to the correct tool. 8. For recurring workflows, save prompts as Space templates so teammates can reuse them without memorizing syntax.
What teammates see: by default, memories from Supportbee 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
Triage Unassigned Tickets
@SupportBee show me all unassigned tickets from the last 24 hours, then suggest which team member should handle each one based on the subject line and current ticket counts per person.Open in a Space →
Archive Resolved Tickets
@SupportBee find all tickets marked as resolved in the last 7 days and archive them. Show me the count before and after.Open in a Space →
Create Response Snippet
@SupportBee create a snippet titled 'Password Reset Instructions' with this text: 'Click the Forgot Password link on the login page, enter your email, and follow the link we send you. Reply if you need further help.'Open in a Space →
Route by Domain
@SupportBee create a rule that assigns any ticket from an email ending in @enterprise-client.com to the Enterprise Support team automatically.Open in a Space →
Reply to Ticket
@SupportBee pull ticket #4521, read the last two replies, then post a response confirming we've escalated the issue to engineering and will update them by end of day.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@supportbee show me all unassigned tickets from the last 48 hours and summarize the most common issues
Found 14 unassigned tickets from the past 48 hours. The most common issues are: (1) Password reset requests (5 tickets) — customers unable to receive reset emails, likely due to spam filtering. (2) Billing questions (4 tickets) — confusion about pro-rated charges after plan changes. (3) Integration errors (3 tickets) — Slack webhook failures after recent API update. (4) General inquiries (2 tickets). The password reset pattern suggests we should update our email deliverability docs or add a troubleshooting snippet.
This example demonstrates read-only ticket retrieval combined with AI synthesis. Requires API key with ticket read permissions. The summary is illustrative — actual ticket content and patterns will vary by your support queue. SupportBee's API returns paginated results; large volumes may require multiple calls.
@supportbee create a ticket from customer jane@example.com with subject 'Refund request for invoice #4521' and assign it to the billing team
Ticket #8834 created successfully with subject 'Refund request for invoice #4521' and requester jane@example.com. Assigned to team 'Billing' (team ID: 1203). The ticket is now visible in your SupportBee dashboard under the Billing team's queue. No reply has been posted yet — the ticket awaits agent response.
This example shows ticket creation with immediate team assignment, a common workflow for routing incoming requests. Requires API key with ticket creation and assignment permissions. Team IDs must exist in your SupportBee account — the MCP cannot create teams. Side-effect: the customer receives a ticket confirmation email unless your SupportBee settings disable it.
@supportbee draft a reply for ticket #8756 using our refund policy snippet, then post it and archive the ticket
Retrieved snippet 'Refund Policy - Standard' (ID: 442) with template text. Draft reply: 'Hi [Customer Name], thanks for reaching out. Our refund policy allows full refunds within 30 days of purchase for annual plans. I've initiated your refund to the original payment method — please allow 5-7 business days for processing. Let me know if you have questions.' Reply posted to ticket #8756. Ticket archived successfully and moved out of active queue.
This example chains three operations: snippet retrieval, reply posting, and archival — a typical resolution workflow. Requires API key with reply and archive permissions. The snippet text is illustrative; your actual snippets must be created in SupportBee first. Archiving is irreversible via API, so confirm resolution before running this type of prompt.
Use-case deep-dives
When Supportbee MCP beats manual ticket assignment at small scale
A 3-person support team at a 50-customer SaaS company gets 20-30 tickets daily across billing, onboarding, and bug reports. The Supportbee MCP wins here because the agent can ask the AI to bulk-assign tickets by keyword, create routing rules on the fly, and archive resolved threads without opening the web UI. The 33-tool scope covers the full triage workflow: create tickets from Slack mentions, assign by team, post replies using stored snippets, and archive when done. The threshold: if your team runs more than 5 concurrent routing rules or needs multi-language snippet variants, the MCP's rule-creation tool gets clunky and you'll want the web dashboard. For straightforward daily triage where speed matters more than policy complexity, this MCP cuts the context-switch tax by half.
Using Supportbee MCP to extract and templatize support patterns
A solo customer success manager at a 12-month-old startup notices the same 8 questions appearing in 60% of tickets. The Supportbee MCP is the right call for this scenario because the agent can scan recent ticket replies, identify repeated language, and create snippets in one session without manual copy-paste. The create-snippet and create-reply tools let the CSM prototype response templates while still in the conversation, then test them on live tickets immediately. The trade-off: if your knowledge base needs conditional logic or multi-step macros, the MCP's snippet tool is too basic and you'll outgrow it in 3 months. For the initial knowledge-capture phase where you're moving from ad-hoc replies to reusable templates, this MCP compresses a 2-week project into 90 minutes.
When Supportbee MCP handles incident ticket generation at deploy time
A 6-person product team ships a feature Friday afternoon and discovers a rendering bug affecting 40 users by Monday morning. The Supportbee MCP is borderline useful here: the create-ticket tool can bulk-generate tickets from a CSV of affected accounts, but the 33-tool scope doesn't include bulk-update or ticket-merge, so the team still needs the web UI to consolidate duplicates. The win is speed: the AI can create 40 tickets with personalized subject lines and requester emails in under 2 minutes, versus 20 minutes of manual data entry. The threshold: if you need to attach screenshots or link tickets to a parent incident, the MCP can't help and you're back in the dashboard. For high-volume ticket creation where the content is templated and the metadata is clean, this MCP saves the first hour of incident response.
Frequently asked
What does the Supportbee MCP let me do in Switchy?
It connects your Supportbee helpdesk so AI agents can create tickets, post replies, archive resolved issues, assign tickets to teams, and manage snippets. You can automate triage workflows, draft customer responses, or build rules without opening the Supportbee web app. All 33 tools run through your API key, so agents act as you.
Do I need admin access to connect Supportbee?
You need a Supportbee API key, which any agent or admin can generate from their profile settings. The key inherits your account permissions, so if you can't create users or rules in the web UI, the MCP won't be able to either. Admin keys unlock all 33 tools; agent keys are limited to ticket operations.
Can the MCP send replies as different team members?
No. Replies post under the account that owns the API key. If you want responses attributed to specific agents, connect separate Switchy workspaces with each agent's key, or use Supportbee's native assignment tools and reply manually. The MCP can assign tickets to teams, but the reply author stays fixed.
Why use this instead of Supportbee's web interface?
The MCP lets AI agents handle repetitive ticket tasks—tagging, archiving, drafting replies from snippets—without you context-switching into Supportbee. It's faster for bulk operations and workflow automation. For complex customer conversations or reviewing ticket history with attachments, the web UI is still better.
Does connecting Supportbee count against my Switchy plan limits?
The connection itself is free. Tool calls consume your workspace's monthly action quota—each ticket created, reply posted, or rule updated counts as one action. If you automate high-volume triage, monitor your usage dashboard. Supportbee's own pricing and agent seat limits apply separately.