CUSTOMER SUPPORT
Low-CSAT Tickets to Drafted Help Articles
When a Zendesk ticket receives a bad satisfaction rating, an agent reviews whether the issue lacks help-center coverage and, if so, drafts a full new article in Notion and opens…
How it runs
The automated pipeline, trigger to output.
- TriggerBad CSAT rating received on ticketZendesk
- ActionFetch full ticket conversationZendesk
- LogicJudge if a missing article caused the ticket
- ActionDraft new help article as Notion pageNotion
- OutputOpen Linear task to review and publishLinear
What it does
Turns every poor satisfaction rating into a chance to close a documentation gap. On each bad CSAT response, an agent reads the ticket thread, decides whether the customer's problem was caused by missing or unclear self-serve content, and if so writes a complete draft article and queues it for review.
When to use it
Use it when negative CSAT is often driven by customers who could not find an answer themselves. It converts complaints into a publishing pipeline rather than just a dashboard metric.
How it works
- 1A bad CSAT rating on a Zendesk ticket triggers the workflow.
- 2The agent pulls the full ticket conversation for context.
- 3It judges whether a help article would have prevented the ticket; non-content issues are skipped.
- 4For real gaps, the agent drafts a structured article (title, problem, steps, related links) as a Notion page.
- 5It opens a Linear issue linking the draft and the source ticket for an editor to review and publish.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 4Connect LinearIssues, projects, cycles, triage.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.