Ask what changes the answer.

The customer’s intended use, technical constraints and required outcome matter more than a long form.

Keep the open questions visible.

Incomplete information is a reason for the next question. A useful brief distinguishes known requirements from details still to resolve.

Make the next response specific.

Pass the context to a person who can evaluate the fit. The goal is a relevant recommendation or a practical next step.

A requirement before a recommendation

A customer asks for a product recommendation without describing the application. A useful first conversation discovers what they are trying to achieve. It does not collect every possible field: it asks about the factors that change the product fit.

Starting question
We need equipment for a new production line.
First clarification
What will it process, and which output requirement matters?
Priorities
Capacity, variation, available space or operating conditions
Useful next step
A brief that supports a relevant product discussion

Illustrative business scenario