Helpdesk for AI agents
HelpDesk is a ticketing system for organizing and managing customer support inquiries in one queue. Support teams use it to keep customer requests organized in one shared queue. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Helpdesk.
List open tickets
List current tickets assigned to a team to prioritize the day's support queue.
Check available canned responses
List canned responses to find one that fits a common customer question.
Review agent workload
List agents and their assigned tickets, read-only, to help balance the support queue.
14 Helpdesk actions, graded by risk.
Every Helpdesk action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
14Look things up. Allowed by default.
- helpdesk.list_rulesList Rules
- helpdesk.list_teamsList Teams
- helpdesk.list_viewsList Views
- helpdesk.list_agentsList Agents
- helpdesk.list_ticketsList Tickets
- helpdesk.list_licensesList Licenses
- helpdesk.list_webhooksList Webhooks
- helpdesk.list_custom_fieldsList Custom Fields
- helpdesk.list_email_domainsList Email Domains
- helpdesk.list_subscriptionsList Subscriptions
- helpdesk.list_trusted_emailsList Trusted Emails
- helpdesk.list_reply_addressesList Reply Addresses
- helpdesk.list_canned_responsesList Canned Responses
- helpdesk.view_agentView Agent
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Helpdesk in three steps.
- 01Your users connect HelpdeskThey add their Helpdesk api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Helpdesk through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('helpdesk', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Helpdesk connects.
Users add their Helpdesk api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Helpdesk connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Helpdesk from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Helpdesk and Arc0, answered.
Can I use Helpdesk with Claude, ChatGPT or Cursor?
Yes. Connect Helpdesk to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Helpdesk actions you allow.
How do users connect Helpdesk?
Users add their Helpdesk api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Helpdesk actions can my agent take?
14 in total: 14 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Helpdesk?
Yes. Allow read actions and deny writes in the Helpdesk policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Helpdesk too?
Yes. The same Helpdesk connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Helpdesk into your agent.
Your users connect Helpdesk once, under your brand. Your agent gets 14 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan