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: Catch a refund request with an evaluation agent

TL;DR: An evaluation agent returns the probability that a message is a refund request. A high probability waits for a person. A low probability lets the playbook continue.

Who this is for

Support teams that need a refund check before anyone drafts a reply or issues a credit.

What you'll need

  • Connectors: Your helpdesk, Slack.
  • Agent: An evaluation agent with one boolean question. See What is an evaluation agent?.
  • Trigger: Webhook when a customer message arrives.

A customer message goes to an evaluation agent, which returns a refund probability. A high probability asks a person. A low probability continues.

How to build it with Ask Ballet

  1. Open the Console on Home.
  2. Paste the prompt below.
  3. Review the proposed plan and confirm.
  4. Connect the helpdesk and Slack when prompted.
Build a playbook that triggers when a new customer message arrives.
Create an evaluation agent with one boolean question: is the sender asking for a refund.
Pass the subject and body. Do not send a prompt. Read the probability.
If the probability is high, wait for a person and post the message to Slack #refunds.
If it is low, continue. The evaluation agent must not issue a refund and must not draft the reply.

What the playbook does

  1. Webhook trigger — receives the message.
  2. Evaluation agent — returns the refund probability.
  3. Branch — a high probability waits for a person. A low probability continues.

Variations and tips

  • Pair this with ticket triage when you also need a queue and an urgency.
  • Do not treat the probability as a decision to refund. A person still decides.

Related articles

  • What is an evaluation agent?
  • Triage a support email with an evaluation agent