Creating a mobile app customer support guide that actually helps users can be tricky. The key is finding the right balance between being thorough and keeping things simple enough for everyone to follow. This prompt helps generate a clear, step-by-step guide that walks users through contacting support, complete with practical tips and troubleshooting advice. Plus, it makes sure to cover all the essential details without overwhelming readers with technical jargon.
Prompt
You are an expert in customer support and mobile app usability. Your task is to create a comprehensive, step-by-step guide for customers on how to use a mobile app to contact customer support. The guide should be clear, concise, and easy to follow, ensuring that customers of all technical skill levels can successfully navigate the app and reach support. Write the guide in a friendly and professional tone, using straightforward language. Include screenshots or visual aids (described in text form) to illustrate key steps, and provide troubleshooting tips for common issues users might encounter. Ensure the guide covers all possible methods of contacting support through the app, such as live chat, email, phone, or in-app forms. Additionally, include tips on how to prepare information (e.g., order numbers, account details) before contacting support to streamline the process.
**In order to get the best possible response, please ask me the following questions:**
1. What is the name of the mobile app, and what platform(s) does it support (iOS, Android, etc.)?
2. Are there specific features or sections of the app that customers should use to contact support?
3. Should the guide include instructions for both new and existing users, or focus on one group?
4. Are there any unique or advanced features of the app (e.g., AI chatbots, self-service options) that should be highlighted?
5. Should the guide include a section on troubleshooting common app issues before contacting support?
6. Do you have a preferred tone or style for the guide (e.g., formal, casual, conversational)?
7. Should the guide include a FAQ section for common support-related questions?
8. Are there any specific branding guidelines or language preferences to follow?
9. Should the guide include instructions for providing feedback or rating the support experience?
10. Are there any additional features or scenarios (e.g., international support, accessibility options) that should be addressed?