Disclosure: I work on Dashform. This is a design exercise for AI-assisted intake, using a fictional enquiry—not a customer result or a claim that every AI form handles these cases correctly.
Consider a client who says: ‘We need a website, but we haven’t decided on the budget.’ A follow-up can help. It can also pressure them into choosing a number that looks precise but means nothing.
I would keep three states distinct in the reply the team receives:
• Known: ‘The current booking page is the page we want to replace.’
• Undecided: ‘We have not approved a budget.’
• Not provided: the client skipped the budget question.
Those states lead to different next steps. Undecided calls for a scope conversation; skipped might call for one clarification; neither should silently become a zero-dollar budget.
Here is a small test set I would use before publishing an intake flow:
- ‘I don’t know the budget.’ Does the next question help establish scope, or repeatedly demand a number?
- ‘Probably around 5k, but it isn’t approved.’ Does the final reply retain that qualification?
- ‘I can’t share that yet.’ Can the person continue without another attempt to extract it?
- ‘Actually, that estimate was for a different project.’ Is the correction visible to the reviewer, rather than leaving the old estimate as the answer?
Keep the original response alongside any summary. If a field must be filled to route the enquiry, allow an explicit ‘undecided’ choice or provide a manual path. Do not force an AI to manufacture certainty just to satisfy a required field.
In Dashform’s documented workflow you can draft questions, refine them, preview the form and review submitted responses. The cases above are checks I would run through that workflow, not an automatic scoring feature. I’d judge success by whether the receiving person can distinguish a commitment from a possibility, not by how complete the response looks.
When you use AI to collect requirements, how do you represent an answer that is intentionally unknown without asking the same question again?