TICKET MANAGEMENT
Real-time dedupe gate that blocks duplicate tickets before assignment
A webhook intercepts every ticket at creation, checks it against an in-memory canonical index in Postgres.
How it runs
The automated pipeline, trigger to output.
- TriggerTicket-created webhookHTTP webhook
- ActionEmbed ticket textHugging Face
- ActionQuery canonical vector indexPostgres
- LogicNew vs duplicate at threshold
- ActionRegister canonical or link duplicateZendesk
- OutputAcknowledge requester / pass to routingZendesk
What it does
Acts as a gate in front of your routing logic. Before a ticket is ever assigned to an agent, the webhook embeds it and checks a fast Postgres vector index of open canonical tickets. New issues pass through; duplicates are stopped, linked to their canonical thread, and the requester gets an immediate acknowledgment so they aren't ignored.
When to use it
When duplicate volume is high enough that you want to prevent assignment, not clean up after it. Best for teams with a webhook-driven intake already in place.
How it works
- 1A ticket-created webhook delivers the new ticket payload.
- 2The text is embedded with Hugging Face.
- 3The canonical vector index in Postgres is queried for the nearest match.
- 4A branch splits new tickets from duplicates at the threshold.
- 5New tickets are registered as canonical in Postgres and passed downstream to routing.
- 6Duplicates are linked in Zendesk and the requester receives an acknowledgment reply.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect ZendeskTickets, queues, knowledge base.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Ticket Management workflows
Intercom Known-Issue Auto-Responder
When a new Intercom conversation matches a known active incident, it attaches the conversation to that incident's parent ticket and sends the customer the current status reply.
Weekly reopen-by-agent coaching digest
Aggregates each agent's solved-then-reopened tickets for the week, identifies the most common reopen reason per agent, and emails a private coaching digest to the support manager.
Deduplicate Discord bug reports against existing Linear issues
Before creating anything, searches Linear for issues matching a new Discord bug report; if a duplicate exists it comments and links the report there, otherwise it opens a fresh…
Enrich Discord bug reports with Sentry errors before filing in Linear
Takes a Discord bug report, has an LLM pull out likely error signatures, searches Sentry for matching events.
Front-to-Linear Recurring Bug Linker
When a Front ticket is tagged as a bug, it searches Linear for an existing matching issue and either links the ticket to that parent issue or opens a new tracked one.
Front Duplicate Conversation Clusterer
When a new Front conversation arrives, it semantically compares the report against open conversations.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.