---
title: "Support Ops recipes"
description: "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."
canonical_url: "https://docs.ballet.dev/articles/support-ops-recipes-Dyh0Jbf8ME"
md_url: "https://docs.ballet.dev/articles/support-ops-recipes-Dyh0Jbf8ME.md"
---
# 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](/articles/recipe-triage-and-route-support-tickets-M40UGJ9TVv) — classify new tickets and route them to the right queue.
- [Auto-answer and deflection](/articles/recipe-auto-answer-and-deflect-common-tickets-NcwOm4doJP) — draft answers from your knowledge base and deflect common questions.
- [Escalations and SLA breaches](/articles/recipe-escalate-sla-breaches-and-priority-tickets-7RFVotelRJ) — escalate at-risk tickets to on-call and Slack.
- [CSAT follow-up](/articles/recipe-csat-follow-up-after-ticket-resolution-xuee53bGA4) — send a survey after resolution and log the result.

## Related articles

- [How do first-party integrations (Cursor, Freshdesk) work?](/articles/how-do-first-party-integrations-cursor-freshdesk-work-ufEctQFe4A)
- [What triggers can start a playbook?](/articles/what-triggers-can-start-a-playbook-manual-schedule-webhook-P4mdwPZDGg)
- [How do I build a playbook with the Console?](/articles/how-do-i-build-a-playbook-with-the-console-ask-ballet-oHptRP9mI4)