Answer support tickets from Freshdesk history
A SaaS owner connected ChatGPT to Freshdesk and internal tools, then pulled back from full autonomy.
What they did
The agent could read past tickets and use internal tools to draft and send answers.
How it went
Picking the right answer, and knowing when not to answer, proved unreliable. It now drafts and a person sends.
Our read
Our analysis · Oct 28, 2026Not from the source. Our own assessment of the approach, which may date as the tools change.
Where it falls down
- The reported failure was knowing when not to answer, which is the hard part of support automation.
- Past tickets teach it what was said before, including the answers that were wrong.
- Draft-and-review saves less than it looks once a person reads every draft.
Worth trying next
- Let it answer only the ticket types where it scored well, and stay silent on the rest.
- Measure how much drafts are edited before sending, to see where it actually helps.
Try it by SolvedWith.ai
A starting prompt we built from this case. Not the original poster's wording.
I work in saas & technology and want to answer support tickets from Freshdesk history. Walk me through setting this up with ChatGPT, step by step. Before anything that sends messages as you, stop and ask me first.