hegl for customer operations
Answer more tickets without growing the queue team.
hegl is an AI agent platform for customer operations teams. It resolves tickets, refund and return requests and order changes that fit your policy, on top of the tools you already use, and routes the rest to a person with the context attached.
Onboard your agent
Claude Code
/plugin marketplace add Katch-AI/hegl-plugin /plugin install hegl
Codex
codex plugin marketplace add Katch-AI/hegl-plugin Then install hegl from /plugins. Codex asks you to authorize it in your browser on first use.
Quick start
Start with "list my Hegl organizations", then: /hegl:build [agent] Start building an agent, or pick up where the build stopped. /hegl:feedback [agent] See what people complained about and improve the agent on it. /hegl:fix-errors [agent] Find out why runs are failing and fix it. In Codex and OpenCode, ask in words, e.g. "fix the errors on my agent". Any other MCP client: add the MCP server https://app.hegl.ai/mcp
- Works inside the helpdesk and order systems you already run
- Tested on tickets your team already closed before it goes live
- Hands anything outside policy to a person, with the reason

Use cases
What customer teams run through hegl
Most tickets are a lookup and a policy call. Find the order, check what the policy allows, do it, tell the customer. hegl handles the ones that fit and brings a person the ones that do not.
Support ticket resolution
Questions that need the account looked up before anyone answers.
hegl pulls the account, answers what policy covers, and routes the rest with context.
Refund and cancellation decisions
Each request checked against the order, the policy and the customer’s history.
hegl applies your refund policy and escalates anything above its limit.
Returns and warranty claims
Claims with photos, receipts and serial numbers to check before approval.
hegl checks the claim against the order and warranty terms, and drafts the decision.
Complaint handling
Complaints that need a fair, consistent answer and a record of it.
hegl drafts the response from the account history. A person approves before it goes.
Order entry and validation
Orders arriving by email and PDF that have to be keyed in correctly.
hegl reads the order, enters it, and flags missing or conflicting details.
Booking and reservation changes
Date, quantity and address changes that each need a rules check.
hegl makes the change where policy allows and explains why where it does not.
Ticket triage and routing
A shared inbox that has to be sorted before it can be worked.
hegl tags, prioritises and routes each ticket to the team that owns it.
Account and billing changes
Plan changes, address updates and duplicate charges to look into.
hegl checks the account, makes the routine change, and logs what it did.
- Where is my order
- Damaged in transit
- Partial refunds
- Goodwill credits
- Subscription cancellations
- Exchange requests
- Duplicate charges
- Address changes
- Proof of purchase checks
- Escalation summaries
- Macro selection
- Policy exception notes
- Survey follow-up
- Fraud flags
Your systems
Nothing to rip out
hegl runs on top of your helpdesk, your order system and your inbox. Tickets stay where they are, and your team keeps working where it already works.
No migration.
Your tickets and orders stay in your systems. hegl works through the access you approve.
No engineers.
A support or operations lead describes the policy. We connect the systems with you on a call.
No tools replaced.
hegl works alongside the helpdesk and macros you already have.
The fit
Why this work fits
The policy covers most tickets. The edge cases cover the rest.
Refund windows, return conditions and goodwill limits are written down. What is not written down is how your best agent handles the case that almost fits. hegl learns that from their corrections.
Same lookup, every ticket.
Find the customer, find the order, check its status, check the policy. hegl does the lookup every time, so your team starts from the answer.
You already have the answer key.
Every closed ticket is a worked example with a known outcome. hegl is tested against them before it goes live and after every change.
When it is unsure
What happens when it is wrong
It asks.
When an item does not match what it has seen, it stops and asks the person who owns it. It does not guess.
It remembers.
Every answer becomes a permanent test. Accuracy goes up with use, not down.
It shows its work.
Every decision carries its inputs, its reasoning, and who overrode what. The audit trail is built in.
Proof
Support and refund handling at Enhancv
I built an automation that handles refund tickets in an afternoon without pulling engineers off the roadmap. What used to be handled by 1 FTE is now done in a couple of minutes.

80%+
of refund requests
auto-resolved
30h+
saved every month
for the team
Getting started
How you start
Describe the work.
Someone who does the work talks it through. hegl writes the spec.
Test on your history.
hegl runs against work your team already finished. You see where it agrees.
Go live on your call.
It runs alongside your team, escalating when unsure. You widen it when ready.
FAQ
Frequently Asked Questions
hegl is an AI agent platform that resolves support tickets, refund and return requests, order changes and complaints on top of the tools a team already uses. It looks up the account, applies the team’s policy, takes the action, and routes anything outside policy to a person with the context attached.
No. hegl works the ticket behind the scenes: it looks up the order, makes the decision your policy allows, takes the action in your systems and drafts the reply. Whether a person reviews the reply before it is sent is your call.
A person on your team. hegl applies the limits you set, and anything above them or outside them is routed for approval with the account history and a recommendation.
No. It works inside the helpdesk, order system and inbox you already use, through connections you approve. Nothing moves.
Before go-live, hegl runs on tickets your team already closed and you see where it agrees. After, every correction becomes a permanent test. We report a monitored error rate, not a promise of zero.
Data stays in your systems and hegl reads and writes only through the access you approve, with every action logged. hegl is GDPR compliant and SOC 2 Type II is in progress.
Security & compliance
Secure by design
- SOC 2Type IIIn progress
- HIPAACompliant
- CASAApproved
- GDPRCompliant
Other teams
The same loop, other work
- Chargeback and dispute evidence
- Supplier invoice and rebate matching
- Product compliance documentation
- Invoice processing and exception handling
- Expense report review
- Payment reconciliation
- Group booking contract review
- Commission reconciliation
- Damage and incident claims
