AI Blocks › Help your customers
Turn repeat customer questions into help pages people understand
Give it the questions you answer every week. Get checked help pages a stranger can follow.
Turn repeat customer questions into help pages people understand is a free AI workflow for the job "Help your customers". It guides your AI through several skills in order, passing each step's output to the next.
Free · No account · Made by AI Blocks · Level: beginner · Thinking: high
What it does
Every business has ten questions that make up most of its support. The answers exist, scattered across sent emails, a chat log and one person's head. New staff answer them differently. Customers who could have helped themselves write in instead, and the help page that does exist reads like a terms sheet. This workflow turns those questions into pages people can follow. It first gathers what your docs and tickets already say about each question, with gaps marked. It writes a help page per question: the steps, what the reader should see, and what to do if it fails. It checks the reading level of each page and rewrites any that read hard, following George Orwell's rules for plain English. Then it checks each page as a reader would, for a missing step or a wrong button name. You publish pages that answer the question the first time.
You give it
- The questions you answer every week, and how you answer them today
- Your current docs, FAQ or help pages (optional)
- Who the readers are and what they already know
- Brand brain (optional)
- Source text (optional)
- Codebase (optional)
You get
- What your records already say about each question, with gaps marked
- A help page per question, with steps, what the reader should see and what to do if it fails
- A reading-level check and a plain rewrite of any page that reads hard
- An accuracy check on every page, with the fixes applied
Use it when
- Ten questions make up most of your support inbox.
- Your help pages exist but customers write in anyway, because they could not follow them.
- You are training someone new and want the answers written down once, correctly.
Steps
- Customer question researcher: Ask a customer question. Get an answer found across your docs, past tickets and chats, with each source named.
- Solved-ticket help page writer: Give it a solved ticket. Get a help article with steps, what you should see, and a fix for next time.
- Text difficulty checker: Paste a text. Get its difficulty by length, meaning and reader task, with support ideas for struggling readers.
- Plain English editor: Paste a draft. Get it back in plain words, with each cut explained and a check that you would still say it.
- Documentation checker: Give it a README or doc. Get false claims, drift from the code and weak spots listed before you publish.
How to use it
- Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
- Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
- Paste the questions, how you answer them and any docs you have. It writes a page per question.
- Read the reading-level report and the plain rewrites. Confirm the button names and steps are right.
- Publish the checked pages and link them in your replies.