Find which request does not fit the selector
Look for enquiries where the selected category conflicts with the description. Ask staff whether customers use the wrong option because their task is missing, the label is unfamiliar or the form requires a choice too early. A selector should help routing. It should not become a miniature internal service catalogue that only technicians can interpret.
Use supported services in customer language
W3C form-label guidance emphasizes understandable control purpose. Apply that to both the selector label and its choices. The operational owner supplies the current service list, and customer questions supply familiar wording. Avoid adding search phrases as service options when the business cannot deliver those tasks.
Source checks: W3C WAI: Labeling Controls · W3C WAI: Form Instructions
Test an ordinary and an uncertain job
Choose a small set of distinct useful options. Where a customer reasonably cannot distinguish repair from replacement, let them describe the issue under 'not sure'. Staff can decide the technical category later. Check that the chosen answer is saved, included in the review view and used correctly by any routing rule.
- Compare category selections with recent request descriptions to find recurring mismatches.
- Confirm current services and remove obsolete or unsupported options.
- Rewrite specialist labels using familiar customer tasks while preserving useful distinctions.
- Add a bounded uncertain option with a short description field where needed.
- Submit marked tests and verify staff see the selected answer and relevant description.
Avoid a catch-all that gives staff no context
Do not make 'Other' the destination for everything without explaining what information is useful. Do not create numerous near-identical choices that require trade expertise. A corrected label may still feed an old routing rule, so inspect the receiving workflow. Avoid silently changing stored historical category meanings when updating current choices.
Review misclassified requests
Track requests needing recategorization and the reason: missing choice, unclear wording or genuine uncertainty. Ask staff whether the revised selection provides enough context for the first response. This is an intake-quality check. A lower misclassification count does not independently establish an increase in qualified demand.
Maintain the selector with the service owner
Keep the selector's current options with the person responsible for service scope. Review it whenever services change and confirm any automated routing still matches. Staff should know how to handle the uncertain route respectfully. Preserve historical records with their original meaning rather than rewriting past selections to resemble the new form.
Worked example: an illustrative customer journey
For example, a door-service form offers only 'installation' and 'maintenance'. A customer with a damaged panel does not know which to choose, although staff handle repairs. The owner adds a verified repair option and a 'not sure—describe the issue' route.
TEST-CHOICE-2801 uses the uncertain route and reaches staff with its description intact. A second test selects repair and follows the correct internal route. These tests demonstrate useful intake choices, not that every damaged door can be repaired.
A selector should help the first response
Known supported task
Choose a clear service option
Technical uncertainty
Describe the issue under 'not sure'
Unsupported task
Read the service-scope explanation
Staff review
See the choice and description together
Your practical checklist
- Compare selected categories with actual message descriptions.
- Verify every option represents a currently supported service.
- Use customer task language rather than unexplained trade terms.
- Provide a useful uncertain path where classification is hard.
- Test saved answers and associated staff-routing rules.
- Preserve original meanings in historical enquiry records.
Your next action
Identify one recurring mismatch between selected service and request description, then revise the relevant option.
Questions about this task
Should I add every possible service variation?
Only distinctions that help the first decision. Too many near-identical choices can make classification harder.
Is 'not sure' a low-quality lead?
Not necessarily. Customers may describe a real problem without knowing the technical service category.
Can the service page preselect an option?
A useful preselection can reflect the page the visitor came from, but keep it visible and editable. Test what staff receive if the customer changes it. Do not silently force the original category when their message describes a different supported task.
Sources and editorial notes
Prepared with AI-assisted research. Official sources are linked below; worked examples and checklists are Getting Found Local recommendations, not measured client outcomes.
Sources checked October 13, 2026. Platform interfaces and local resources may change; follow the current instructions on the linked official page.
How we research, illustrate, and update these guides · Suggest a correction