CUSTOMER SUPPORT

Prioritize KB Gaps by Low-CSAT Tickets

Mines tickets that received a negative satisfaction rating and had no article to point.

CategoryCustomer Support
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionFetch low-CSAT ticketsZendeskZendesk
  • LogicKeep tickets with no article
  • ActionGroup and score by pain (OpenAI)OpenAI
  • ActionCreate ranked Linear backlogLinearLinear
  • OutputPost top gaps summary to SlackSlack

What it does

Not all documentation gaps hurt equally. This workflow focuses on tickets where the customer left a bad CSAT rating and the agent had no article to share — the gaps that actively damage your support experience. It groups those tickets into topics and builds a backlog ordered by frustration, not just volume.

When to use it

Use it when leadership asks where to invest documentation effort for the biggest CSAT lift, or when you want the writing queue driven by customer pain rather than raw ticket counts.

How it works

  1. 1A weekly schedule triggers the run.
  2. 2Fetch Zendesk tickets from the past week that carry a negative satisfaction rating.
  3. 3A logic step keeps only those with no help article attached during resolution.
  4. 4An OpenAI step groups them into gap topics and scores each by CSAT impact.
  5. 5Create a ranked set of Linear issues, highest-pain topic first, each with sample tickets.
  6. 6Post a summary of the top gaps to Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZendeskTickets, queues, knowledge base.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.