Help articles and responses.
FOR HELP ARTICLES
"Write a help article answering [question]. Reader is not technical. Numbered steps. Say what they will see after each step. Include what to do if it does not work."
WHAT GOOD SUPPORT CONTENT HAS
The answer first Numbered steps What the reader sees at each stage What to do when it fails Who to contact
WHERE THE TOPICS COME FROM
Your actual support tickets. The questions people ask repeatedly.
That is the best content source any business has.
FOR CANNED RESPONSES
Draft them with AI, then edit heavily.
Personalise before sending. A response that is obviously templated reads as dismissive.
WHAT TO VERIFY
Every step, by following it Every menu name and button label Anything version-specific
WHAT NOT TO DO
Publish generated instructions for your own product without testing them.
The model does not know your interface and will confidently describe buttons that do not exist.
THE HIGH-VALUE USE
Turning the same answer you have typed fifty times into an article you link to.
