How to Set Up Automated CSAT Surveys After Support Tickets

The cheapest early-warning system you can build for customer churn is also one of the most ignored: a CSAT survey wired to every closed support ticket. It costs nothing to deploy, takes about half a day to build, and surfaces unhappy customers weeks or months before they would otherwise show up in your churn report.

The logic is straightforward. A customer who just had a bad support experience is roughly 4x more likely to cancel within 90 days than a customer who had a good one. Catching that signal at ticket close — while the experience is still fresh, before the next renewal conversation, before the bad Twitter thread or the G2 review — is one of the highest-leverage automations a support team can run. Done right, a CSAT program also feeds your review and referral programs by routing your happiest customers to the asks that drive growth.

This post is the operator's guide to building that workflow. I will walk through the design choices first (scale type, send timing, channel) because those decisions determine response rate, and a 5% response rate is worthless data. Then I will walk through the build in Deelo's Helpdesk, Automation, SMS, and CRM apps. The same architecture works on any stack with a helpdesk that fires close events and an automation engine that can dispatch surveys.

Most retention programs are reactive. They watch usage and billing for signals that something is wrong, and by the time those signals fire, the customer has often already mentally cancelled. CSAT is different. It is a customer self-reporting that they are unhappy, in their own words, while they are still on the bill.

The data backs this up. Across most B2B SaaS and service businesses, customers who give a 1 or 2 on a 5-point CSAT scale churn within 12 months at roughly 3-5x the rate of customers who give a 4 or 5. The signal is loud, it is timely, and it is volunteered. The only thing standing between most teams and this data is the work of building the survey and the routing logic — work that compounds for years once it is in place.

Three scales dominate post-ticket CSAT surveys. Each has a tradeoff.

For SMB and mid-market support, pick thumbs up/down or 1-5. The simpler the question, the more responses you collect, the better your data. I recommend thumbs up/down for teams under 1,000 tickets per month and 1-5 for teams above that — the larger dataset can absorb the response-rate hit and rewards you with more granular trend data.

Every helpdesk vendor will tell you to send the survey instantly when the ticket closes. They are wrong, and here is why.

When the survey lands in the customer's inbox seconds after the agent closes the ticket, it feels like the agent personally just asked them to rate the agent. That biases the response upward (people are conflict-averse, especially toward people who just helped them) and undermines the honesty of the data. It also feels needy.

Send the survey 24 hours after close instead. The customer has had time to verify that the fix actually worked. The agent feels less present in the loop. The response feels like a genuine evaluation of the outcome, not a politeness rating of the conversation. Response rate drops by maybe 10-15% compared to instant send, but the data quality goes up enough that the tradeoff is worth it. For teams with high ticket volume, this also smooths the response curve across a day rather than spiking right after close.

Email is the default channel. It is free, has good deliverability, and lets you embed a richer survey if you want. Most teams should start there and stay there for the bulk of their tickets.

SMS makes sense for two situations. First, high-value customers (Enterprise, top-quartile MRR, VIP-flagged accounts) where you want the higher response rate (SMS CSAT often pulls 30-40% response vs. 15-25% for email) and the faster turnaround. Second, post-urgent-ticket follow-ups — if the ticket was an outage or a critical bug, an SMS the next day saying "is everything still working?" lands harder than an email.

In Deelo, this is a Conditional node in the Automation workflow: if the customer's VIP flag is true or the ticket type was P1, send via Deelo SMS; otherwise send via Deelo Marketing as an email.

Open Deelo Helpdesk and create a Survey template. For a thumbs up/down design, the survey has two screens. Screen one is a single question: "How would you rate the support you received on this issue?" with two big buttons. Screen two depends on which button they clicked. For thumbs up, ask "What did we do well?" with an optional text field. For thumbs down, ask "What could we have done better?" with an optional text field and an offer to escalate.

For a 1-5 design, screen one is the rating buttons. Screen two is conditional: for 1-2, ask "What went wrong?" and offer to escalate. For 3, ask "What would have made this a 4 or 5?" For 4-5, ask "Anything we should know?" and optionally surface the review-request link.

Keep the survey to two screens maximum. Three-screen surveys see a roughly 40% drop in completion rate compared to two-screen.

Open Deelo Automation and create the dispatch workflow. The trigger is the Helpdesk `ticket.closed` event. The first node is a Delay node set to 24 hours — this is the design choice from earlier, encoded.

After the delay, a Conditional node checks two things. First, does the customer have CSAT surveys turned on? (Some Enterprise customers ask not to be surveyed; respect that flag.) Second, has the ticket been re-opened during the delay window? If yes, abort the survey — the issue was not actually resolved and surveying now would look tone-deaf.

If both checks pass, route to the next Conditional node: VIP or P1 ticket goes to SMS via Deelo SMS; everyone else goes to email via Deelo Marketing. The survey link is a unique URL per ticket that includes the ticket ID, customer ID, and a one-time token. When the customer clicks through and submits, the response posts back to the Helpdesk Survey record with full context.

The whole point of CSAT is to catch unhappy customers in time to do something. That requires a second workflow that fires on survey submission and routes responses.

For a 1-5 scale: scores of 1 or 2 fire the alert workflow. For thumbs up/down: any thumbs down fires the alert workflow.

The 24-hour SLA on the recovery task is the most important piece. Most customers who give a low CSAT score and then get a personal phone call from a real human within a day stay. Most who get nothing churn within the quarter. The phone call is the intervention; the survey is just the trigger.

Happy customers are an underused asset. Most teams collect 4s and 5s, file them away, and never ask for anything. The third workflow fixes that — it routes high scores to a downstream automation that builds your review and referral pipeline.

For a 1-5 scale: scores of 5 (and optionally 4) fire the advocacy workflow. For thumbs up/down: any thumbs up fires it.

The workflow checks two things first. Has this customer been asked for a review in the last 90 days? If yes, skip — repeated asks fatigue people. Is the customer in a healthy account status (not failed payment, not in cancellation flow, not enterprise-special)? If yes to all gates, send a follow-up email a few days after the survey response with two soft asks: "Would you mind leaving a quick review on G2 or Capterra?" with a one-click link, and "Know anyone who might benefit from us?" with a referral link. Most teams that wire this up see a 3-5x increase in review velocity within 60 days, just from harvesting signal that was already there.

Once data is flowing, build four views in Deelo's reporting. These are the views that turn CSAT from a vanity metric into a tool that drives decisions.

Most teams that run this workflow for a quarter end up shipping product changes based on CSAT-by-ticket-type that they would never have prioritized otherwise. The data shifts product investment toward the issues that actually annoy customers, not the ones that are loudest internally.

Ship the simplest version of this workflow first. Thumbs up/down survey, 24-hour delay, email-only, low-score Slack alert. Skip the review-request workflow, skip the SMS channel, skip the per-agent reporting. You can have this live in half a day on Deelo, and you will start collecting signal the next week.

Layer on the rest in priority order: the manager alert and recovery task are highest leverage and should ship first. Then the high-score advocacy routing. Then the SMS channel for VIPs. Then the per-agent reporting. By the end of a quarter, you have a complete customer-satisfaction intelligence loop that costs nothing to run and pays out every renewal cycle from here forward. If you want help mapping your existing ticket categories onto the survey design and the alert routing, the Deelo AI Assistant can review your last 90 days of helpdesk data and recommend the right starting design.