# Clear the ticket queue. From your agent. Source: https://corespeed.io/integrations/zendesk Connect Zendesk to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent searches tickets, reads the comments on one, runs a view, and previews what a macro would change without saving it. It signs in with your own Zendesk account, and a public reply or internal note is a separate call that approvals can hold. ## Set up an agent Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)` It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Zendesk after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up ## Read the whole ticket. Answer the real question Have your agent find the ticket, read every comment, and check what your usual macro would change. You get a draft reply to review. You ask your agent: "Find the open Zendesk tickets about export timeouts. Read the latest one, preview our Known issue macro on it, and draft a reply. Do not post anything." It calls CoreSpeed: - `zendesk__search`: ok, 431 ms - `zendesk__list_ticket_comments`: ok, 388 ms - `zendesk__preview_macro`: ok, 512 ms It reads from: Zendesk. ### Ticket brief: Ticket #4821, ready to answer. Large exports time out for Diane’s team. Other accounts report it too, so it is a known issue, not a setup mistake. **What the macro would do** - Set the ticket to pending. - Add the export-bug tag. **Draft reply** - Thanks, Diane. We can reproduce the timeout on large exports and are fixing it. I’ll update this ticket when the fix ships. _Illustrative ticket and draft · Nothing posted to Zendesk_ All connectors: https://corespeed.io/docs/connectors ## Less tab-hopping. More answered tickets Requests you can make once Zendesk is connected. The data is fictional. ### Catch up on a ticket Ticket #4821 · the short version · Ticket summary - Customer asks: Why large exports time out - Already tried: Two retries, a smaller date range - The history, without the scroll ### Work a view Urgent, unassigned · A view, read in place - Oldest: Export times out - Needs a person: Refund for a double charge - Read only · Nothing reassigned ### Hold the reply for a person A public reply, waiting · CoreSpeed approvals - Tool: Add a public reply - Rule: Ask before replying to a customer - Ask Full example: https://corespeed.io/solutions/agent-approvals (Markdown: https://corespeed.io/solutions/agent-approvals.md) ## Keep your agent. Bring your work One CoreSpeed account, across compatible agents. 1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in. 2. **Connect Zendesk**: Authorize the account and the content you need. 3. **Start with one task**: Ask for a summary, a brief, or a draft. Review the answer. Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor ## Questions ### Can my agent reply to customers in Zendesk? Yes, with a separate call that adds a public reply or an internal note. Approvals can hold that call for a person first. ### Does it apply macros? It previews what a macro would change on a ticket without saving it. Changing the ticket is a separate update call. ### Which tickets can my agent see? Only what the connected Zendesk account can see, within the scopes you grant at sign-in. CoreSpeed does not bypass Zendesk roles. ### Do I have to switch agents? No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once. ### Can my agent access every account in our organization? No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private. ### Does this work without connecting an account? No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors Every tool and price: https://corespeed.io/catalog/zendesk ## Related pages - [Approval gates for AI agent tool actions](https://corespeed.io/solutions/agent-approvals): Set approval policies for writes through CoreSpeed. Review held tool actions while your team keeps using its preferred agents. - [Gorgias for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/gorgias): Bring your Gorgias helpdesk into your agent. Work a view, read the ticket, find the right macro, and draft a reply you review. - [Help Scout for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/helpscout): Bring Help Scout conversations, customers, and Docs into your agent. Find the pattern and the gap in your docs. Read-only. - [Intercom for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/intercom): Bring Intercom conversations and Help Center articles into your agent. Catch up, find the answer, and draft a reply you review. - [ServiceNow for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/servicenow): Bring ServiceNow incidents, changes, and knowledge into your agent. Triage the queue and draft a work note you review. ## Sources - Connectors: https://corespeed.io/docs/connectors - Zendesk: Tickets API: https://developer.zendesk.com/api-reference/ticketing/tickets/tickets/ - Zendesk: Ticket comments API: https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_comments/ - Zendesk: Search API: https://developer.zendesk.com/api-reference/ticketing/ticket-management/search/ Reviewed 2026-11-10. ## Links - Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md) - All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md) - Documentation: https://corespeed.io/docs - Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)