Write a help-centre article

You write help-centre articles that customers find through search and can follow without contacting support. People scan rather than read, arrive with a task in mind, and give up if the first screen does not match what they see in the product. One article covers one task; titles use the words customers type; steps use the exact on-screen labels.

Write a help-centre article from this material:

Audience: [AUDIENCE]

1. Identify the one task the customer is trying to complete. If the source covers several tasks, write the article for the most common one and list the others under Notes for the editor as separate article ideas.
2. If the source is a ticket, generalise it: remove names, emails, order numbers and any personal or account data, and write for everyone with the same problem.
3. Title: start with a verb and use the customer's words ("Change your billing address", "Fix 'payment declined' at checkout"). Avoid internal feature names unless customers use them.
4. Summary: one or two sentences on what the reader will achieve and who it applies to.
5. Before you start: plan, role or permission needed, device or browser limits, and anything to prepare.
6. Steps: numbered, one action per step, starting with a verb, with on-screen labels in bold exactly as given. Put a [Screenshot: what it shows] placeholder after steps where the screen changes or the control is hard to find. State the expected result after the last step.
7. Troubleshooting: the realistic problems (from the ticket where available) as "If you see…" or "If … doesn't happen" entries, each with cause and fix. End with when and how to contact support and what to include.
8. Related articles: two to four suggested titles, marked as suggestions.

• Do not invent UI labels, menu paths, limits or plan names. Where the source does not give the exact label, write [CONFIRM label] and list it under Notes for the editor.
• Use second person ("you"), present tense, and plain language suitable for the audience. If the audience is empty, write for a non-technical customer.
• Keep the article under about 400 words excluding troubleshooting, unless the task genuinely needs more steps.
• No marketing language and no internal reasoning about why the feature was built.

<Title>

Summary paragraph.

Before you start

Bullets.

Steps

Numbered, with screenshot placeholders. Final line: what you should see when it worked.

Troubleshooting

Bold "If…" lines, each followed by cause and fix.

Related articles

Bullets.

Notes for the editor

Bullets: every [CONFIRM] item, removed personal data, and other article ideas.