Collector scenarios best practices
Scenarios help our assistant to recommend the right collectors to users using smart intent matching. Writing good scenarios ensures users quickly reach the help or input form they need. Below are best practices to help you write efficient scenarios.
1. Avoid Filler Phrasing
Avoid using filler words like:
- ❌ “User wants to report a bug”
- ❌ “I want to report a bug”
Instead, get to the point with:
- ✅ “Reporting a bug”
This makes your scenarios cleaner and avoids matching unnecessary words when the user is asking for something else.
2. Focus on the Core Request
Avoid adding extra details or context that may distract from the main intent. Scenarios should be concise and targeted:
- ✅ “Can’t access account”
- ❌ “While trying to sign in after resetting my phone, I couldn’t access my account and now I’m stuck”
Get straight to what the user needs help with.
3. Keep Sentences Clear and Simple
Scenarios work best when they are short and express a single clear intent. Avoid complex or compound statements:
- ✅ “Forgot my password”
- ❌ “I forgot my password and now I’m also locked out and I don’t know what to do”
Each scenario should cover one issue only.
4. Be Specific When Purpose Is Clear
If a collector is designed for a specific problem, use distinct scenarios rather than broad ones. For example, with an account recovery collector, you can use multiple specific scenarios:
- ✅ “Lost account”
- ✅ “Forgot password”
- ✅ “Can’t log in”
Avoid grouping these into something too vague like:
- ❌ “Account issues”
This helps the assistant recommend the right collector with higher precision.
5. General Forms Can Use Broad Scenarios
If the form’s purpose is broader (e.g. a bug reporting form), using a general scenario can be helpful:
- ✅ “Having issues”
This allows the assistant to recommend the form in more varied contexts.
6. Avoid Redundant Scenarios
Thanks to our assistant’s smart intent matching, there’s no need to add multiple phrasings of the same idea. For instance:
- Adding both “Having an issue” and “Having a bug” is unnecessary.
- Stick with one clear phrasing; the assistant understands variations in wording.
This keeps your list of scenarios tidy and easy to manage.
7. Start Small and Iterate
You don’t need to predict every possible way a user might ask for help. Begin with a few strong, well-written scenarios, then monitor usage and expand where needed.
This approach avoids clutter and lets data guide your improvements.
By applying these practices, you ensure that your assistant is better equipped to understand users, guide them effectively, and offer relevant help with minimal friction.