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: Check the work before a reply

TL;DR: An evaluation agent answers whether the work is done. Only a yes continues to the language agent that drafts the customer reply.

Who this is for

Support teams that want a check before a reply is drafted.

What you'll need

  • Connectors: Your helpdesk.
  • Agents: An evaluation agent for the done check, and a language agent for the reply. See What is an evaluation agent?.
  • Trigger: Manual, or a webhook after the ticket, policy, and proposed action are gathered.

Order, policy, and action go to an evaluation agent, which answers whether the work is done. Done continues to a drafted reply. Not done stops.

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.
Build a playbook that receives an order, a policy, and a proposed action.
Create an evaluation agent with one boolean question: are the order, the policy,
and the proposed action all present. Pass those three fields. Do not send a prompt.
Read the probability. If it is high, continue to a language agent that drafts the
customer reply. If it is low, stop and wait for a person. The evaluation agent
must not write the reply.

What the playbook does

  1. Input — receives the order, the policy, and the proposed action.
  2. Evaluation agent — returns whether the work is done.
  3. Branch — a high probability continues to the draft. A low probability stops.
  4. Language agent — drafts the reply only after the check passes.

Variations and tips

  • Use this as the gate in front of any reply, not as the reply itself.
  • Name the missing field in the language step only after the check says the record is complete.

Related articles

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