Skip to the content
searchboar.

Customers and buying decisions

Customer question: meaning and practical examples

A customer question is a request for information that arises while someone explores, chooses, buys or uses an offer. Its wording can reveal what the person needs to understand, but does not by itself prove the reason behind the question.

At a glance

  • Preserve the actual wording and the situation in which it arose.
  • One question can require different answers for different customers.
  • Use questions to identify useful explanations, not to invent demand.
On this page
A customer asks a shopkeeper a question across a counter beside a helpful article.
Conceptual illustration: a customer asks a shopkeeper a question across a counter beside a helpful article.

What counts as a customer question?

Questions can appear in conversations, quote requests, support messages or website searches. “Can I collect it on Saturday?” is as useful as a polished research question if it exposes a real information gap. Record the situation alongside the wording so later editors understand what the person was trying to do.

User-needs research starts from the person's task, not just the wording of a proposed answer. Understanding user needs

How is it different from a search query?

A search query is what someone enters into a search service. A customer question is broader and may never be typed into a search box. A telephone question about stair access can reveal useful content even when a keyword tool reports little search volume.

Do not automatically equate repeated inquiries with a large market. A small number of customers may ask repeatedly because an existing explanation is unclear.

Example: renting equipment for a weekend

Imagine a local equipment-rental business receiving “Does a weekend mean two days?” Customers are uncertain whether Friday collection and Monday return are included.

A useful explanation states the actual collection and return conditions, illustrates a typical booking and identifies exceptions. It does not replace the question with a general history of equipment rental. This fictional example shows how a short question can require a precise operational answer.

Which questions belong together?

Group questions when the underlying customer need and answer are substantially the same. Keep them separate when conditions change the decision. “Will it fit in my car?” and “Do you deliver?” concern transport, but they need different facts.

A FAQ page can collect short answers. A complex comparison or preparation task may deserve its own explanation, linked from the relevant short answer.

What should the editor check?

Confirm the answer with the person responsible for the offer. Distinguish a general explanation from a specific commitment about stock, timing or eligibility. State uncertainty when details depend on the customer's circumstances.

After publication, check whether readers can find the answer where they need it. More content is not automatically better if the decisive information remains hidden or inconsistent across pages.

Sources

  1. GOV.UK Service Manual: Learning about users and their needs