The Exception That Should Become a Better Form Question
Updated: 7 days ago

The request says “Please update access by Friday.” The person opening the ticket still has to ask, “For which workspace?” The AI assistant can draft that follow-up. The next request will come in with the same missing detail.
Change the intake question when the same missing answer repeatedly blocks a decision, the requester can reasonably answer it, and your team can show what it will do with the answer. Let the request go through to a person when the requester genuinely doesn’t know.
Eleven follow-ups, three different problems
Imagine a small design firm reviewing 24 fictional access tickets from the last two weeks. Eleven needed a follow-up. Six omitted the target workspace, three needed a manager’s approval, and two involved conflicting access records. The support lead counts tickets, with one primary reason per ticket, so one long email thread can’t dominate the tally.
She changes the form for the six missing workspace names. She keeps the manager approval step and the conflicting records in the human queue. Another dropdown can’t resolve either problem.
Rewrite the moment that gets stuck
Old question: “Anything else we should know?” The workspace name is optional and buried in a text box.
New question: “Which workspace should we check?” In the internal form, staff can pick a workspace they can already see or choose “I’m not sure.” If they are unsure, a short hint asks for the project name if known. Don’t display an organization-wide directory to help someone answer an intake question.
Routing rule: A selected workspace goes to the coordinator for that workspace. An unknown workspace goes to the general queue with the original request. Assignment changes; access still requires separate approval. The GOV.UK question-page guidance offers a question protocol for deciding why each answer is needed. W3C’s form instructions explain how to make required fields, formats and help available to people using assistive technology.
A field change you can review on one screen
Repeated blocker: The coordinator can’t identify the workspace.
Evidence: Six of 24 fictional tickets; review a real sample before changing your form.
Proposed question: Which workspace should we check?
Safe fallback: Let the requester choose “I’m not sure.” Route that answer to a person without guessing.
Owner and review: The coordinator checks routing, follow-ups and abandonment before keeping the change.
This card keeps the request, answer and decision together. If nobody can name the decision that changes, drop the proposed field. An AI assistant can group redacted examples and suggest wording. Have the process owner check the evidence and approve any form or routing change.
Let people try the slow path
Try the new question with someone who knows the workspace and someone who doesn’t. Have them submit test requests by keyboard and on a phone. Check with a screen reader that it announces the selector label and the hint when it appears. Verify that the known and unknown requests reach the right queues. If a selected workspace becomes unavailable before submission, send the original request to a person and tell the requester what happened. A form answer never grants access. Then compare equal pilot windows for requests needing workspace follow-up, incorrect routing and form completions. Note any changes in volume or request mix before drawing a conclusion.
If you have several recurring reasons for review, use the exception queue guide to give each one an owner and a decision. The prompt change management guide shows how to test a related assistant change without editing the production version first.
Once the form routes the request to the right person, use a clear finish line for the AI draft so the reviewer knows which record would settle it.
Intake form FAQs
Should I make the new question required?
Require an answer only when the workflow needs one and the requester has a usable way to answer. If uncertainty is normal, allow “I’m not sure” and make that path useful.
Can AI choose the workspace from the project name?
It can suggest a match from records it’s allowed to read. If several matches are plausible, let a coordinator decide. Keep access approval separate from the match.
What if a question cuts follow-ups but more people abandon the form?
Review both outcomes. The change may be moving work to the requester. Improve the wording or options, then run another small test before expanding it.
Bring one question your team keeps answering twice
Take a redacted request, the follow-up your team sends and the decision waiting on the answer. Ask Bell Consulting Solutions to review the workflow, or start with the AI process optimization guide.





Comments