CUSTOMER SUPPORT
Bug-report intake form gate that scores repro before creating a ticket
Receives bug submissions from a public web form via webhook, scores them for reproduction completeness in real time.
How it runs
The automated pipeline, trigger to output.
- TriggerBug-report form posts to webhookHTTP webhook
- ActionScore repro completeness (LLM)OpenAI
- LogicBranch: score below threshold?
- ActionRespond with rejection + missing fieldsHTTP webhook
- OutputCreate repro-verified Zendesk ticketZendesk
What it does
This workflow sits in front of ticket creation. A bug-report web form posts to a webhook; the workflow scores the submission against the repro rubric and responds synchronously. Incomplete submissions are rejected with a precise list of what to add, so an underspecified bug never becomes a ticket. Complete ones are turned into a Zendesk ticket that lands on the queue already verified.
When to use it
Use it when you control the intake form and want to stop low-quality bug reports at the door rather than cleaning them up after they become tickets.
How it works
- 1The bug-report form submits payload to the webhook trigger.
- 2An LLM scores repro completeness and returns the missing fields and score.
- 3A branch checks the score against the threshold.
- 4If below threshold, the webhook responds with a rejection payload listing exactly which fields the user must add and no ticket is created.
- 5If at or above threshold, a Zendesk ticket is created pre-tagged `repro-verified` with the structured fields, and the webhook returns the ticket ID to the form.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ZendeskTickets, queues, knowledge base.
- 3Connect OpenAIModels, embeddings, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Tell Intercom users their reported bug shipped after a Vercel deploy
On a successful Vercel production deployment, match the release's resolved Sentry issues to Intercom conversations and message each affected user that their reported issue is…
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.