CUSTOMER SUPPORT
Open a Detractor Recovery Task in Linear for Every Bad Score
When a CSAT detractor response arrives in Zendesk, create a tracked recovery task in Linear assigned to the account owner, with the customer context and a follow-up due date.
How it runs
The automated pipeline, trigger to output.
- TriggerZendesk CSAT rating submittedZendesk
- LogicProceed only on detractor scores
- ActionAssemble ticket context and resolve ownerZendesk
- ActionCreate Linear recovery issue with due dateLinear
- OutputConfirm new issue in SlackSlack
What it does
Converts every detractor CSAT response into an accountable, trackable recovery task rather than a fleeting alert. It creates a Linear issue containing the ticket summary, the customer's verbatim complaint, and a 48-hour due date, assigns it to the right owner, and drops a short confirmation in Slack so the team knows it is captured.
When to use it
Use this when Slack alerts get lost and you need detractor follow-up to live in your actual work tracker with an owner and a deadline. It is the right fit for teams that measure recovery as a closeable task, not just a notification.
How it works
- 1A Zendesk webhook fires when a satisfaction rating is recorded.
- 2A logic step continues only for detractor scores and skips everything else.
- 3An action assembles ticket details and maps the account to its owner.
- 4An action creates a Linear issue titled with the customer name, body filled with context, and a due date 48 hours out.
- 5The final step posts a Slack note linking the new Linear issue to the recovery channel.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.