[Article title]
Briefly answer the customer’s question.
Explain:
- what this workflow or feature is
- when someone would use it
- what they’ll accomplish
Avoid marketing language, implementation details, and unnecessary UI narration.
Who can use [Feature Name]
State only the information the reader needs:
- required role
- required plan (if applicable)
- required permissions
- important prerequisites
If another workflow must be completed first, link to it using a relative link.
If unavailable on mobile, state:
This feature is not available on mobile.
How to [Complete Primary Task]
Keep the steps focused.
Describe only the actions necessary to complete the task.
Do not document every click if it doesn’t help the reader.
If web and mobile differ, separate the instructions.
If they’re identical, combine them.
What happens after you [Complete Task]
Explain what changes after completing the workflow.
Focus on consequences the customer may not expect.
Examples:
- billing changes
- notifications
- approvals
- ownership changes
- synchronization
- downstream effects
Don’t restate what the task already accomplished.
Related Articles
FAQ
[Natural customer question]
Clear answer.
[Another natural follow-up question]
Clear answer.
