As of 13 August 2026, AI can write a customer login help page.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, no skill needed, and roughly 30 minutes until you can act on the result.

   How to actually do it

   1. Open the current login, password-reset and account-recovery flows for your product, and record the exact buttons, labels, URLs and messages a customer sees.
   2. Gather your approved support route, opening hours, account lockout rules, security guidance and the cases that must be handled by a person.
   3. Remove passwords, one-time codes, customer names, email addresses and other private data, then paste the remaining product information into the prompt.
   4. Paste the drafted page into your help-centre editor and replace every [NEEDS CONFIRMATION] marker using your approved product documentation.
   5. Use a test account to follow every numbered instruction from the login page, including the failed reset-email and locked-account routes, and correct any step that does not match the live product.
   6. Ask a support colleague who knows the escalation process to check the recovery advice, privacy wording and contact route before publishing the page.

   Prompt

   Write a customer-facing help page for people who cannot log in to [PRODUCT OR SERVICE]. Use only the information supplied below and do not invent steps, settings, error messages, timeframes, contact details or security rules. Do not ask customers to share passwords, one-time codes, full payment details or other confidential information. Explain the safest recovery route first, then cover these known cases: forgotten password, incorrect password, locked account, password-reset email not arriving, one-time code not arriving, changed email address or phone number, and an account that may have been compromised. Include a short introduction, numbered steps, plain-English explanations, a section for what to do if the steps fail, and the correct escalation route. Mark any missing information as [NEEDS CONFIRMATION] rather than guessing. Keep the tone calm and concise, use UK English, and write for a customer with no technical knowledge. After the draft, provide a verification checklist showing which source item supports each instruction.
   
   Product or service: [NAME]
   Login page: [URL]
   Confirmed login and recovery steps: [PASTE CURRENT STEPS]
   Known error messages and their confirmed meanings: [PASTE ERRORS]
   Account lockout rules: [PASTE RULES]
   Support route and opening hours: [PASTE DETAILS]
   Security and privacy rules: [PASTE RULES]
   Cases that require manual support: [PASTE CASES]
   Audience and tone: [PASTE GUIDANCE]

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.