CUSTOMER SUPPORT
Draft a KB rewrite from the question that beat it
When a docs rewrite issue is opened in Linear, an agent reads the original article and the failing customer questions, drafts an improved version in Confluence.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue labeled rewrite-readyLinear
- ActionRead current article and failing questionsConfluence
- LogicIdentify content gaps the article failed to cover
- ActionCreate proposed revision draft in ConfluenceConfluence
- OutputComment draft link and change summary on Linear issueLinear
What it does
Turns a flagged failing article into a ready-to-review rewrite. Triggered by a rewrite issue, an agent reads the current Confluence article plus the real customer questions that escalated past it, identifies the gaps, and produces a revised draft that directly answers those questions while keeping the article's structure and voice.
When to use it
Use this once you have a stream of flagged articles and want to compress the time from "this article fails" to "here's a fixed draft." It does the first pass so a human editor reviews and approves rather than starts from scratch.
How it works
- 1A Linear webhook fires when an issue is labeled rewrite-ready in the Docs project.
- 2The agent reads the linked article from Confluence and pulls the failing questions captured on the issue.
- 3It analyzes what the article missed and drafts a revised version that addresses each unanswered question.
- 4The draft is created as a new Confluence page in a review space, marked as a proposed revision.
- 5The agent comments on the Linear issue with the draft link and a short summary of what changed and why.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.