Turn Feature Notes into a Step-by-Step Help Center How-To Guide

Paste rough notes about a product feature and get a customer-ready how-to guide with one action per step, bold UI labels, expected results and a troubleshooting section.

You getTitle starting with "How to", one sentence on what the guide helps the user do and "Before you start" bullet list

Prompt

Prompt
You are a technical writer who builds help center articles for a software support team.

I will paste my notes about a product feature right after this prompt. They may be internal notes, a Slack thread, release notes or a rough draft. Turn them into a step-by-step how-to guide that a customer can follow without contacting support.

Rules:
1. One action per numbered step. If a step joins two actions with "and" or "then", split it into two steps.
2. Write every on-screen label (buttons, menus, tabs, fields) in bold, spelled exactly as it appears in my notes. Do not rename or guess labels.
3. After any step that saves, submits or changes the screen, add a line starting with "Result:" that says what the user should see.
4. Use short sentences, second person ("you") and plain words. Remove internal jargon, code names and ticket numbers.
5. Put prerequisites (plan, permissions, settings) before step 1, not inside the steps.

Output format:
- Title starting with "How to"
- One sentence on what the guide helps the user do
- "Before you start" bullet list
- Numbered steps
- "If this didn't work": 3-5 likely problems, each with cause and fix, based only on my notes
- "Still stuck?": one line on contacting support

End with a short list of any labels, steps or permissions my notes left unclear, so I can confirm them before publishing.

Example output

Example for: a support lead at an invoicing app pasting release notes for a new automatic payment reminders feature.

How to Set Up Automatic Payment Reminders

This guide shows you how to send clients automatic email reminders before and after an invoice is due.

Before you start

  • You need the Growth or Pro plan.
  • You must be an Owner or Admin on the account.
  • Your business email must be verified under Settings > Email.

Steps

  1. Click Settings in the left menu.
  2. Select the Reminders tab.
  3. Turn on the Automatic reminders toggle.

    • Result: Three reminder slots appear below the toggle.
  4. In the Before due date field, choose how many days ahead to send the first reminder.
  5. In the On due date row, tick the checkbox to send a reminder on the day the invoice is due.
  6. In the After due date field, choose how many days late to send a follow-up.
  7. Click Edit message to change the email text.
  8. Click Save template.

    • Result: A green "Template saved" banner appears at the top of the page.
  9. Click Save changes at the bottom of the Reminders page.

    • Result: The Automatic reminders toggle shows "On", and new invoices show a bell icon in the Invoices list.

If this didn't work

ProblemLikely causeFix
The Reminders tab is missingYou are on the Starter plan or are not an AdminUpgrade your plan or ask an Owner to change your role
Clients are not getting remindersYour business email is not verifiedGo to Settings > Email and click Resend verification
Old invoices have no bell iconReminders only apply to invoices created after you turn them onOpen the invoice and click Add reminders
A client got a reminder after payingThe payment was recorded after the reminder was sentRecord payments the same day; reminders check status at 8:00 a.m. in your time zone

Still stuck?

Contact our support team from Help > Contact us and include the invoice number.


Please confirm before publishing:

  • The notes say both "Save changes" and "Save settings". I used Save changes; check the live screen.
  • The notes do not say whether Admins on the Growth plan can edit message templates.
  • The 8:00 a.m. send time came from one Slack message; confirm it is final.
Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • One action per step stops customers from missing a click buried in a long sentence, a common cause of repeat tickets.
  • Required "Result:" lines let users check they are on track, so they catch errors at the step where they happen.
  • Banning guessed labels and listing unclear items at the end keeps the article accurate to the real interface.

Use when a feature ships and you need a help article fast. Have your release notes, Slack thread or rough draft ready to paste into ChatGPT, Claude or Gemini right after the prompt.

Common edits

  • Ask for screenshot placeholders described in plain text after each Result line so your designer knows what to capture.
  • Add a rule to output the guide in your help desk's format, such as Zendesk or Intercom article HTML.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Customer Support