CUSTOMER SUPPORT
Send a Personalized CSAT Survey When a Ticket is Solved
When a Zendesk ticket moves to solved, generate a personalized one-question CSAT email with OpenAI and send it to the customer, skipping internal and spam tickets.
How it runs
The automated pipeline, trigger to output.
- TriggerZendesk ticket marked solvedZendesk
- LogicSkip internal, suppressed, and no-survey tickets
- ActionDraft personalized survey intro with OpenAIOpenAI
- ActionSend CSAT survey email via GmailGmail
- OutputLog survey dispatch as private Zendesk noteZendesk
What it does
Fires whenever a support ticket is marked solved, then sends the requester a short, tailored CSAT survey by email. OpenAI rewrites the survey intro to reference what the ticket was actually about, so the ask feels human instead of robotic. Internal, automated, and no-reply tickets are filtered out before any email goes out.
When to use it
Use this if your help desk's built-in survey is generic or never gets sent, and you want higher response rates from a message that acknowledges the specific issue the customer just had resolved.
How it works
- 1A Zendesk trigger fires when a ticket transitions to the solved status.
- 2A logic step drops tickets from internal domains, suppressed requesters, or tickets tagged no-survey.
- 3An OpenAI step drafts a friendly two-line survey intro referencing the ticket subject and resolution.
- 4An action sends the survey email via Gmail with a 1-5 rating link back to the colony.
- 5A final action writes the dispatch timestamp back onto the Zendesk ticket as a private comment.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect GmailRead, draft, send, label.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Tell Intercom users their reported bug shipped after a Vercel deploy
On a successful Vercel production deployment, match the release's resolved Sentry issues to Intercom conversations and message each affected user that their reported issue is…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.