Work helpdesk tickets with Claude Code and custom GPTs
Rama Adi. Task: Rama Adi Katelin Teen Last edited October 14, 2026 You can point Claude at your support queue this afternoon, and it will be useful inside ten minutes. Add your helpdesk's remote MCP server as a custom connector, and Claude reads tickets, drafts replies, summarises threads, spots patterns across your backlog, and answers questions your reporting tab cannot. What it will not do is work the queue unattended. Some vendors, Gorgias among them, do expose a send tool, so Claude can fire off a reply when a person asks it to. What none of them gives you is a rota-free agent picking up tickets by itself. I checked every first-party surface Anthropic ships and every route the major helpdesks publish, and all five of them are built for a human in the loop. There is exactly one exception worth knowing about, and almost nobody knows about it: Zendesk quietly shipped its own Claude connector that runs inside Zendesk's action flows on your Anthropic API key. The reason people go looking for this is money. Raw model tokens on a typical ticket cost between $0.005 and $0.02, against $1.50 to $2.00 per automated resolution on Zendesk. That gap is real, and it is also not the whole bill, because the model was never the expensive part. If you want the drafting half, follow the steps below. If you want tickets actually closed, that is a different tool, and eesel does it inside the helpdesk you already run, from $299 a month for 500 tickets. The five routes, and what each one is for The most common mistake I see is treating "use Claude for customer support" as one decision. It is five, and they suit different teams, and which ones are even open to you depends on the customer support software you already run. Here is the whole map before the how. The honest summary of that table: routes one and two are excellent and I would set one up today. Route three is the most interesting and least known. Route four is a real project. Route five is technically possible and Anthropic's own safety guidance tells you not to. Pick your helpdesk below and the widget gives you the exact route, endpoint and gate for it. Which Claude route does your helpdesk actually have? Verified against vendor documentation in August 2026. Before you start: three things that will bite you None of these is difficult. All three are easy to walk straight into, and the third one in particular will look like a broken connector rather than a network rule, so clear them first. Your plan is probably fine. Custom connectors using remote MCP work on Free, Pro, Max, Team and Enterprise, and the custom connectors article states the only numeric cap is that Free users get one custom connector. If you are on Free and you want both your helpdesk and your docs tool, that is the wall you will hit. On Team or Enterprise, you are not the one who adds it. Only Owners can add a connector to a Team or Enterprise organisation, per the same article. Members then individually authenticate against it afterwards, which is the right design because Claude inherits each person's permissions from the connected service. If you are a support lead on a company plan, your first step is a message to whoever owns the workspace, not a settings page. The network gotcha nobody expects. This one is worth reading twice, because it silently breaks self-hosted setups: "When you add a custom connector, Claude connects to your remote MCP server from Anthropic's cloud infrastructure, rather than from your local device. This is true across every Claude client, including claude.ai, Claude Desktop, Cowork, and the mobile apps." Which means a server behind your VPN or corporate firewall will not connect, even though you can reach it perfectly from your own laptop. The fix is allowlisting Anthropic's published IP ranges. If your helpdesk is cloud-hosted this never comes up, and if you run anything on-prem it is the first thing to check. Route 1: add your helpdesk as a custom connector This is the one to do first. It takes about ten minutes and it is where most of the value lives. Find your helpdesk's MCP endpoint. Front publishes mcp.frontapp.com/mcp, Gorgias publishes mcp.gorgias.com/mcp, HubSpot publishes mcp.hubspot.com. For Zoho Desk you generate your own URL in Zoho's MCP console, and note that Zoho's URL embeds its own API key, so treat it exactly like a password.; tools: Claude Code, ChatGPT. Human role: The original post does not say how a person stayed involved.; limitations: Prerequisites include a supported helpdesk (e.g., Front, Gorgias) and appropriate Claude plan (Free capped at 1 connector). Network constraints require allowlisting Anthropic's IP ranges for self-hosted servers. Human approval is mandatory for sending replies, and sensitive data handling must comply with vendor safety guidelines..
Tools
Published on Agent Work Atlas:
Overview
Rama Adi
Workflow
Rama Adi Katelin Teen Last edited October 14, 2026 You can point Claude at your support queue this afternoon, and it will be useful inside ten minutes. Add your helpdesk's remote MCP server as a custom connector, and Claude reads tickets, drafts replies, summarises threads, spots patterns across your backlog, and answers questions your reporting tab cannot. What it will not do is work the queue unattended. Some vendors, Gorgias among them, do expose a send tool, so Claude can fire off a reply when a person asks it to. What none of them gives you is a rota-free agent picking up tickets by itself. I checked every first-party surface Anthropic ships and every route the major helpdesks publish, and all five of them are built for a human in the loop. There is exactly one exception worth knowing about, and almost nobody knows about it: Zendesk quietly shipped its own Claude connector that runs inside Zendesk's action flows on your Anthropic API key. The reason people go looking for this is money. Raw model tokens on a typical ticket cost between $0.005 and $0.02, against $1.50 to $2.00 per automated resolution on Zendesk. That gap is real, and it is also not the whole bill, because the model was never the expensive part. If you want the drafting half, follow the steps below. If you want tickets actually closed, that is a different tool, and eesel does it inside the helpdesk you already run, from $299 a month for 500 tickets. The five routes, and what each one is for The most common mistake I see is treating "use Claude for customer support" as one decision. It is five, and they suit different teams, and which ones are even open to you depends on the customer support software you already run. Here is the whole map before the how. The honest summary of that table: routes one and two are excellent and I would set one up today. Route three is the most interesting and least known. Route four is a real project. Route five is technically possible and Anthropic's own safety guidance tells you not to. Pick your helpdesk below and the widget gives you the exact route, endpoint and gate for it. Which Claude route does your helpdesk actually have? Verified against vendor documentation in August 2026. Before you start: three things that will bite you None of these is difficult. All three are easy to walk straight into, and the third one in particular will look like a broken connector rather than a network rule, so clear them first. Your plan is probably fine. Custom connectors using remote MCP work on Free, Pro, Max, Team and Enterprise, and the custom connectors article states the only numeric cap is that Free users get one custom connector. If you are on Free and you want both your helpdesk and your docs tool, that is the wall you will hit. On Team or Enterprise, you are not the one who adds it. Only Owners can add a connector to a Team or Enterprise organisation, per the same article. Members then individually authenticate against it afterwards, which is the right design because Claude inherits each person's permissions from the connected service. If you are a support lead on a company plan, your first step is a message to whoever owns the workspace, not a settings page. The network gotcha nobody expects. This one is worth reading twice, because it silently breaks self-hosted setups: "When you add a custom connector, Claude connects to your remote MCP server from Anthropic's cloud infrastructure, rather than from your local device. This is true across every Claude client, including claude.ai, Claude Desktop, Cowork, and the mobile apps." Which means a server behind your VPN or corporate firewall will not connect, even though you can reach it perfectly from your own laptop. The fix is allowlisting Anthropic's published IP ranges. If your helpdesk is cloud-hosted this never comes up, and if you run anything on-prem it is the first thing to check. Route 1: add your helpdesk as a custom connector This is the one to do first. It takes about ten minutes and it is where most of the value lives. Find your helpdesk's MCP endpoint. Front publishes mcp.frontapp.com/mcp, Gorgias publishes mcp.gorgias.com/mcp, HubSpot publishes mcp.hubspot.com. For Zoho Desk you generate your own URL in Zoho's MCP console, and note that Zoho's URL embeds its own API key, so treat it exactly like a password.
Reported result
Actual outcomes are not reported in the source. The text notes that while drafting is useful, unattended ticket resolution is not supported by standard connectors. A proposed measurable acceptance check is verifying that Claude can summarize open tickets by root cause within 10 minutes of setup, with zero unauthorized sends.
Human role
The original post does not say how a person stayed involved.
Limitations
Prerequisites include a supported helpdesk (e.g., Front, Gorgias) and appropriate Claude plan (Free capped at 1 connector). Network constraints require allowlisting Anthropic's IP ranges for self-hosted servers. Human approval is mandatory for sending replies, and sensitive data handling must comply with vendor safety guidelines.
Try it
Act as a support lead. I want to set up Claude to assist with my helpdesk tickets. First, identify my helpdesk vendor [replaceable: e.g., Gorgias, Front] and find its remote MCP server URL. Add this URL as a custom connector in Claude. Authenticate using OAuth. Once connected, ask Claude to: 'Summarize the last 5 open tickets regarding billing issues and draft a polite reply for each.' Do not send any replies. Present the drafts to me for review. If the drafts are accurate, I will manually send them. If the connector fails to load, check if my server is behind a firewall and ensure Anthropic's IP ranges are allowlisted. Confirm the setup works by successfully retrieving ticket data before attempting any drafting.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.