Detected country: US
logo
Sign InBook a Demo
GuideRecipesDeveloper

Playbook Recipes

  • Data Ops recipes
    • Recipe: Data sync and ETL to a warehouse
    • Recipe: Scheduled reports and readouts
  • Engineering Ops recipes
    • Recipe: AI code review on pull requests with Cursor
    • Recipe: Incident response and on-call paging
    • Recipe: Triage new errors into tracked issues
  • Finance Ops recipes
    • Recipe: Invoice and expense processing
    • Recipe: Reconcile payments and payouts
  • Introduction
  • Marketing Ops recipes
    • Recipe: Campaign performance report
    • Recipe: Competitor monitoring digest
    • Recipe: Content and marketing operations
    • Recipe: Generate a content brief
  • RevOps recipes
    • Recipe: Automate new customer onboarding
    • Recipe: Enrich new leads automatically
    • Recipe: Route a deal review with an evaluation agent
    • Recipe: Score and route a lead with an evaluation agent
    • Recipe: Score, route, and follow up on leads
  • Support Ops recipes
    • Recipe: Auto-answer and deflect common tickets
    • Recipe: Catch a refund request with an evaluation agent
    • Recipe: Check the work before a reply
    • Recipe: CSAT follow-up after ticket resolution
    • Recipe: Escalate SLA breaches and priority tickets
    • Recipe: Triage a support email with an evaluation agent
    • Recipe: Triage and route support tickets
Loading…
logo

Powered by

Recipe: Triage a support email with an evaluation agent

TL;DR: When a support email arrives, an evaluation agent picks the queue, scores urgency, and estimates whether it is a refund. A later step routes the ticket. The evaluation agent does not write the reply.

Who this is for

Support teams that sort incoming email before anyone drafts a reply.

What you'll need

  • Connectors: Your helpdesk or shared inbox, Slack.
  • Agent: An evaluation agent with questions for queue, refund, and urgency. See What is an evaluation agent?.
  • Trigger: Webhook when a new email or ticket is created.

A support email goes to an evaluation agent, which returns a queue, a refund probability, and an urgency. The next step routes the ticket.

How to build it with Ask Ballet

  1. Open the Console on Home.
  2. Paste the prompt below and adjust the queue names and Slack channel.
  3. Review the proposed plan, confirm, and let Ballet build it.
  4. Connect the helpdesk and Slack when prompted.
Build a playbook that triggers when a new support email arrives.
Create an evaluation agent to classify it. The agent does not write the reply.
Questions: queue as a choice of billing, access, or other; refund as a boolean
for whether the sender wants a refund; urgency as a score of low, normal, or high.
Pass the subject and body. Do not send a prompt. Read the queue choice, the refund
probability, and the urgency score, and do not change a low confidence into another label.
Then route the ticket to the matching queue and post a summary to Slack #support-triage.
If the refund probability is high, wait for a person before anyone replies.

What the playbook does

  1. Webhook trigger — receives the new email.
  2. Evaluation agent — returns the queue, the refund probability, and the urgency.
  3. Route — sets the queue from the choice.
  4. Notify — posts the summary to Slack. A high refund probability waits for a person.

Variations and tips

  • Add a product area as another choice if more than one team shares the inbox.
  • Keep the customer reply as a later language step. Do not ask the evaluation agent to draft it.

Related articles

  • What is an evaluation agent?
  • Triage and route tickets
  • Catch a refund request