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: CSAT follow-up after ticket resolution

TL;DR: When a ticket is resolved, this playbook waits a set delay, sends a short CSAT survey to the customer, and logs the response back to the ticket and a tracking sheet or warehouse. Trigger is a helpdesk webhook on resolution; outputs are a survey send and a recorded score.

Who this is for

Support teams measuring customer satisfaction without manual survey sends.

What you'll need

  • Connectors: Freshdesk or Zendesk, an email/survey tool (or HTTP survey API), optional Google Sheets/warehouse.
  • Secrets: Helpdesk API key, survey/email API key.
  • Trigger: Webhook on ticket resolved/closed.

How to build it with Ask Ballet

  1. Open the Console on Home.
  2. Paste the prompt below; set the delay and survey link.
  3. Review the plan and confirm.
  4. Connect the helpdesk and survey/email tool, then register the webhook.
Build a playbook that triggers when a Freshdesk ticket is marked resolved. Wait two
hours, then send the customer a one-question CSAT survey by email with a link that
captures a 1-5 rating. When the rating is submitted via webhook, record the score on
the ticket as a note and append a row (ticket id, customer, agent, score, date) to our
CSAT tracking sheet. Alert #support-quality in Slack for any score of 1 or 2.

What the playbook does

  1. Webhook trigger — fires when a ticket is resolved.
  2. Code step (delay/schedule) — waits the configured delay before sending.
  3. HTTP step (send survey) — emails the survey with a unique link.
  4. Webhook step (capture) — receives the submitted rating.
  5. HTTP step (log) — writes the score to the ticket and tracking sheet, and alerts Slack on low scores.

Variations and tips

  • Skip surveys for auto-answered or spam tickets by checking ticket tags.
  • Send via your existing survey tool if you already have CSAT templates.
  • Roll up scores weekly with the Scheduled reports recipe.

Related articles

  • Triage and route support tickets
  • Auto-answer and deflection
  • Scheduled reports and readouts
  • What triggers can start a playbook?