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

Support Ops recipes

TL;DR: Support Ops recipes automate the ticket lifecycle — triage and routing, AI-drafted answers and deflection, SLA escalations, and CSAT follow-up. They connect helpdesks like Freshdesk or Zendesk with Slack, PagerDuty, and your knowledge base so your team handles fewer routine tickets.

Who this is for

Support and customer experience teams who want to reduce manual ticket handling and protect SLAs.

Recipes in this department

  • Triage and route tickets — classify new tickets and route them to the right queue.
  • Triage a support email with an evaluation agent — an evaluation agent picks the queue, the urgency, and whether it is a refund.
  • Catch a refund request with an evaluation agent — a refund probability waits for a person or lets the playbook continue.
  • Check the work before a reply — an evaluation agent checks the record before a language agent drafts the reply.
  • Auto-answer and deflection — draft answers from your knowledge base and deflect common questions.
  • Escalations and SLA breaches — escalate at-risk tickets to on-call and Slack.
  • CSAT follow-up — send a survey after resolution and log the result.

Related articles

  • What is an evaluation agent?
  • How do first-party integrations (Cursor, Freshdesk) work?
  • What triggers can start a playbook?
  • How do I build a playbook with the Console?