RecipeAgents / Recipes / Support
Support recipeFind the questions your FAQ doesn't answer
Once a week, collect the questions customers asked and list the ones your FAQ doesn't cover yet.
| Input | Last week's support conversations (export), FAQ text |
| Tools | Helpdesk export, Make, an AI step, Notion or Google Docs |
| Time | Setup about 45 minutes. Running it is just reading one doc a week. |
Download it
- n8n workflow (.json)Import in n8n: Workflows → Import from file. Then connect your credentials.
- Zapier blueprint (.md)Step-by-step rebuild guide. Zapier has no public import format, so this isn't one-click.
- Open the Zap editorCreate a new Zap and follow the blueprint.
The n8n file has three nodes (trigger, AI step, output) plus a read-me note. We check that its JSON structure is valid, but we haven't run every file in a live n8n instance, so test it with sample data before you switch it on.
Steps
- Weekly schedule: export the subjects and first messages.
- AI step compares them with the FAQ.
- Write a list of uncovered questions, with how often each came up, to a doc.
The prompt
Here are customer questions from this week and our FAQ. List questions NOT answered by the FAQ, grouped by theme, with a count per theme. Don't list questions the FAQ already answers. Questions: {{qs}} FAQ: {{faq}}Sample run
Example input (written for illustration)
(40 subject lines + the FAQ)
Example output (shows the format, not a real log)
Billing dates (6): 'when am I charged?' … Team seats (3): 'can I add a colleague?' …
SPONSOR SLOT · AVAILABLEFeature your product here
Where it breaks
- Counts are approximate. Models count loosely. Treat the numbers as rough rankings.
- Anything customer-facing or money-related. Keep a human approval step until you've watched a few dozen runs and trust it.
Tool names and pricing change often, so check each tool's current docs before you build. Times on this page are estimates, not measurements.