-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
6d2cdee
commit 92b5c6f
Showing
3 changed files
with
19 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
- start your research for the customer behavior, what they are asking about what are the biggest pain points. | ||
- categorize your research | ||
- look for common themes and start categorizing them accordingly. | ||
- consider creating a separate FAQ article for each category to make it easier for customers to find information. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
- here is what is the structure of an FAQ article should look like | ||
- title, Use the format [subject] FAQs. | ||
- example return police FAQs | ||
- intro | ||
- briefly describe what the FAQs are about so they know they've found what there were looking for. | ||
- question with answer | ||
- pay attention to the words your customer use to describe your product or service. write your FAQs using the same words as they use instead of your company internal terminology | ||
- related article | ||
- this part is optional but recommended if you have one or more article that are related to the same topic. list them at the bottom of your FAQs article to make them easily accessible for your readers. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters