Customer support FAQ gap-mining workflow
Your FAQ answers what you assumed users would ask, not what they're actually asking — and the gap shows up as support load.
- Last week's support tickets or chat logs
- An LLM in clustering-only mode
- Your FAQ source
- Plain text editor
Steps
- Export last week's support questions with PII stripped (no names, no emails, no phone numbers, no IDs).
- Ask the LLM to cluster questions into themes and list the top 5 themes with example wording.
- Compare to existing FAQ. Flag themes with no current answer.
- Write the 3 highest-impact new FAQ entries yourself, not the LLM. Use exact user wording in the question.
- Publish, and add a 'last updated' date to each entry.
Example output
Theme 1: 'Can the bot pause replies during off-hours?' — 8 mentions, no FAQ entry. New FAQ: 'Yes, see the off-hours pause toggle in the host config.'
Fork and remix ideas
- Adapt for internal HR Q&A.
- Adapt for an academic course FAQ.
- Adapt for a community FAQ refreshed weekly.
Keep going.
These pair well with this workflow.
You're running an internal AI workshop and don't know what each attendee actually wants to build, so the session ends up generic.
WhatsApp community onboarding bot workflowEvery new community member asks the same 5 questions and you answer them at 11pm.
No-code lead qualification workflowInbound leads include great fits, casual browsers, and time-wasters — and you waste hours sorting them.
Have a better version of this workflow?
Send the audience, the problem, the steps, and what you'd never automate. We review every submission with a human before publishing.