Template: Troubleshooting Article
Sample header 1
Break down troubleshooting into short, numbered steps like below. Some other best practices:
- Each header should deal with a specific troubleshooting issue or symptom.
- Do not end headers with a question mark ("?") in troubleshooting articles.
- Use actual H1 or H2 header format for headers, like above.
- Do not use additional nested headers.
- If possible, limit text before the numbered steps.
Each header, along with any text below it, will be served as a single snippet in chat.
Sample header 2
There may be multiple headers per article, each dealing with a different symptom or issue (e.g. one header for resolving an issue in iOS, and another for Android).
- Sample numbered steps for header 2
- Sample numbered steps for header 2
Each of these headers and their text will be served as separate snippets in chat.
Updated 11 months ago