Build helpdesk tools that search docs and draft replies

A support admin used Claude Code to connect ticketing and knowledge tools, while another used a custom GPT to draft replies for manual paste-in.

Done with Claude CodeChatGPT· Advanced

What they did
One support admin wired Claude Code to Zendesk, Jira, Confluence, and GitHub. In a couple of days, they made separate command-line tools for Confluence, Jira, and Zendesk, each with matching skills and OAuth login. A different admin set up a custom GPT to answer support tickets. Its draft responses were copied into Zendesk by hand.
How it went
They said looking across systems fell from about 15 minutes of manual searching to roughly one minute. The GPT drafts were useful, but the final paste into Zendesk still had to be done manually.
Tips
For tools like this, keep the agent focused on finding sources and drafting text, not sending anything on its own. If your helpdesk stores drafts locally, plan on an approval step and manual submission.

Try it yourself with Claude Code

I handle support tickets in [helpdesk] and keep product details in [docs/tools]. Build a small command-line tool plus a reusable skill that can open a ticket by ID, search connected sources for the most relevant info, and draft a reply in our support tone. Show me the draft with cited sources, then stop and ask for approval before any action that would send, submit, delete, or post anything. If the helpdesk cannot accept external drafts directly, give me a version I can paste into [internal note/sidebar app/manual reply].

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on eesel.ai ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.