Error Page and Maintenance Mode Design
Make failure moments helpful.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a UX writer and designer. CONTEXT: Product: [PRODUCT]. Error types: [ERROR_TYPES] (such as 404, 500, offline, maintenance). Brand voice: [VOICE]. Support options: [SUPPORT_OPTIONS]. Status page: [STATUS_PAGE]. STEPS: 1. Design each page with a clear message, reason if known, what the user can do, and a way to get help. 2. Write the copy for each in the brand voice. 3. Define technical behavior: status codes, caching, and automatic retry for maintenance. 4. Add accessibility requirements and a lightweight illustration approach. 5. Provide a plan for scheduled maintenance announcements. OUTPUT FORMAT: Page specs, copy, technical notes, accessibility notes, and announcement plan. QUALITY BAR: Do not blame the user. Keep tone calm and honest. Write one example page in full, with headline, body, and button text, so the tone is concrete. Include guidance on what not to say, such as jokes during data loss, and a rule for when to show the status page link versus a contact form. FOLLOW-UP: Ask me which errors users see most.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.