CUSTOMER SUPPORT
Rewrite Help Articles That Get Repeated Negative Feedback
Watches help-center article feedback for pages that accumulate "not helpful" votes, reads the failing article plus related tickets to find what readers actually needed.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- LogicFlag articles over the negative-vote threshold
- ActionFetch the flagged article body from ReadMeReadMe
- ActionPull recent tickets on the same topicZendesk
- ActionDraft an improved rewrite with a change summaryOpenAI
- OutputSave ReadMe draft and post diff to review channelSlack
What it does
A gap is not always a missing article, sometimes it is a bad one. This workflow monitors article feedback and flags any page that crosses a threshold of "not helpful" votes in a window. It then reads the failing article alongside recent tickets about the same topic to understand what readers were missing, drafts an improved rewrite in ReadMe, and routes it for editorial review with a diff summary.
When to use it
Use it when articles exist but are not landing, leaving customers to file tickets anyway. Instead of waiting for a manual content audit, this catches underperforming docs from the feedback signal and proposes a concrete fix grounded in the questions the article failed to answer.
How it works
- 1A daily schedule starts the run.
- 2Pull article feedback counts and flag pages over the negative-vote threshold.
- 3For each flagged page, fetch the current article body from ReadMe.
- 4Pull recent tickets tagged to the same topic for missing context.
- 5Use OpenAI to draft an improved rewrite plus a summary of what changed.
- 6Save the rewrite as a ReadMe draft and post the diff to the docs review channel.
Set it up
What you configure once, before turning it on.
- 1Connect ReadMeAPI docs, changelog, auth.
- 2Connect ZendeskTickets, queues, knowledge base.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.