CUSTOMER SUPPORT
Convert Failed Help-Center Searches into a Ranked Article Backlog
Reads logged help-center search queries that returned no results, clusters the recurring misses.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionQuery Postgres for yesterday's zero-result searchesPostgres
- ActionCluster queries and count occurrencesOpenAI
- LogicDrop clusters below frequency threshold
- ActionDraft an article outline per clusterOpenAI
- OutputCreate a Linear issue per cluster, priority by hit countLinear
What it does
Customers type questions into your help-center search bar and sometimes get nothing back. This workflow reads those zero-result queries from a Postgres analytics table, clusters the ones that repeat, and creates a Linear issue for each cluster. Every issue carries the raw queries, a hit count, and an OpenAI-drafted article outline so a writer can start immediately. Higher-frequency gaps get higher priority.
When to use it
Use it when your help center has search but no feedback loop. Zero-result searches are the cleanest possible demand signal for missing docs, and this turns them into a backlog the docs team can burn down in order of real customer need.
How it works
- 1A daily schedule starts the run.
- 2Query the Postgres search-log table for yesterday's zero-result queries.
- 3Cluster near-duplicate queries and count occurrences per cluster with OpenAI.
- 4Filter out clusters below a frequency threshold.
- 5Draft a short article outline for each remaining cluster.
- 6Create one Linear issue per cluster with priority set from hit count.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.