The useful takeaway
A guided enquiry should help a customer describe the problem and help your team take the next step. Ask about their situation before asking them to choose your internal service category.
The customer has a problem. You have a dropdown.
A business owner wants fewer missed enquiries. Your form asks them to choose between CRM integration, workflow automation, custom application development and AI assistance. They do not know which one they need. That is why they are contacting you.
The same mismatch appears in many services. A customer knows the room is too cold, the equipment makes a noise or the team cannot see what is happening. They may not know the technical category or the right package name.
A guided enquiry can bridge that gap. Its job is to gather the information needed for a useful next step, without making the customer do the diagnosis you are qualified to help with.
Start with what the person can confidently answer
Replace specialist labels with questions about the customer’s situation. The right first question might be “What are you trying to improve?” or “What is happening when the problem occurs?”
Then show the next relevant question. A business enquiry about repeated data entry needs different context from a request for a new public website. A fitting service may need location and the type of work before detailed measurements.
Let people say they are unsure. A route to a person is part of a good guided experience, not a failure of the form.
| Instead of starting with | Ask something the customer can answer |
|---|---|
| Select a technical service. | What are you trying to achieve or fix? |
| Choose a product configuration. | Where and how will you use it? |
| Specify the integration architecture. | Which tools are involved, and what are you copying between them? |
| Tell us the solution. | What happens today, and what would you like to change? |
Picture a more useful first enquiry
Imagine a customer interested in improving how their business runs. They choose “We lose track of enquiries”. The form asks where enquiries arrive, who handles them and which step is hardest to keep on top of.
It does not ask for a complete software specification. It gathers enough context for the first conversation. The customer can review the summary before sending and correct anything that does not represent their request.
The resulting record gives the team a useful starting brief. A workflow can route it for review, but a suggested category should not pretend to be an agreed scope or a binding quote.
Every question needs to earn its place
A longer form is not automatically a better-qualified enquiry. Ask what the answer will change: the next question, routing, preparation for a conversation or the ability to assess fit.
If nobody uses the field, reconsider collecting it. If the answer is needed only after the project is agreed, it may belong later. Data minimisation is a useful principle here as well as a privacy requirement.
Make required and optional fields clear, label the controls and explain unfamiliar terms. W3C’s forms guidance covers ways to make forms more accessible and easier to understand.
- Use plain language and a clear label for each input.
- Give examples where the question is easy to misunderstand.
- Ask related questions in a sensible order.
- Preserve answers if the user has to correct an error.
- Offer a route for uncertainty or a request that does not fit the options.
Where rules help, and where AI might help
Known choices can often use ordinary conditional rules. If the customer selects one situation, ask the relevant follow-up. There is no need for AI to choose the next step when the rule is explicit.
AI may help organise a free-text request or prepare a summary for the team. Keep the original request visible, make uncertain details clear and review the result before making commitments.
A generated paragraph can sound more definite than the customer was. A good system should preserve uncertainty rather than turn “possibly next month” into an agreed date.
Connect the form to the action behind it
A more useful form still falls short if the information ends up in an unattended inbox. Decide where the record belongs, who reviews it and what should happen next.
For a connected website and dashboard, the submission can create one opportunity with the original answers, suggested route and next action. If storage fails, the customer needs an honest result and another way to contact you.
Only request documents or sensitive detail when they have a clear purpose and an appropriate route. A guided experience should reduce the effort needed to start the conversation, not become an obstacle course.
Test the unsure customer, not just the ideal one
Try someone who knows exactly what they want, someone who describes only symptoms and someone whose request sits outside the usual categories. Include a person using the form on a phone.
Can they understand the questions? Can they change an earlier answer without losing everything? Does the resulting record give the team enough context to respond?
Measure completion, the usefulness of the information and the follow-up questions the team still needs to ask. A form that collects more answers but discourages suitable customers has not necessarily improved the journey.
Start by rewriting your first question
Look at your current form. Does it begin with the customer’s situation or your internal service menu?
A practical first project might redesign the questions and connect the result to the right review queue. A guided tool, a clearer page or a simple form may each be appropriate.
EfiOps can review what customers need to express and what the business needs to know, then build the website and working system around that exchange.