A sales enquiry goes quiet after you send a quote. Someone on the team blames the price. Someone else wants a better website. Before changing either, talk to the person behind that enquiry. What were they trying to do, what happened after they contacted you, and what did they do instead?
These customer interview questions are for an operating service business with a specific decision to make. You’ll follow one fictional enquiry from an initial assumption to a practical next check. At the end, a six-part worksheet helps you keep the customer’s account, supporting evidence and your interpretation separate.
In this guide
Choose the decision before the questions
“We want to understand our customers” leaves too much room for a conversation that goes nowhere. Try a narrower starting point: “Some enquiries stop after we explain the service. We need to decide what to investigate before changing our offer.” Now you know which part of the experience matters.
Write down three separate things. The signal is what happened: an enquiry stopped. The possible explanation is your interpretation: perhaps the price was too high. The evidence is something you can return to, such as the customer’s message or the recorded sequence of the enquiry. No reply after a quote does not, by itself, tell you that the quote was too expensive.
If you haven’t chosen a stage to investigate, start with finding the constraint before spending more on advertising. That guide helps you choose where to look. Here, the task is to collect better evidence about one part of the customer experience.
Speak to people who experienced the relevant stage
For an enquiry that stopped, a happy repeat customer is not your only useful contact. Someone who recently bought, someone who did not proceed, and the colleague who handled the enquiry can describe different parts of the process. Keep those perspectives separate. A team member’s explanation is not a substitute for the customer’s account.
Record each person’s role. The person using a service may not approve the budget. HBS’s Customer Discovery Basics distinguishes buyers from users and cautions against relying on interviews alone.
A simple invitation is enough: “We’d like to understand what happened with your recent enquiry. This isn’t a sales call. Would you be comfortable talking us through the experience?” Agree on a time, explain how the notes will be used, and ask before recording. If recording is unwelcome, take notes with the person’s agreement. You don’t need confidential company documents or colleagues’ personal details to begin.
Customer interview questions: follow one recent event
Ask the person to take you through a particular occasion. The GOV.UK guide to in-depth interviews recommends open, neutral questions and specific examples. Use the following prompts as a route through the conversation, rather than a questionnaire you must finish.
- The trigger: “What happened that made you look for this service?” Bring a general answer back to the recent occasion you agreed to discuss.
- The sequence: “What did you do between that moment and getting in touch with us?” Note the order of events.
- The alternatives: “What other options did you actually explore?” Doing the work in-house or postponing it may have been real alternatives.
- The stopping point: “After you received the details, what did you do next?” If something was missing, ask what they needed to continue.
- The people involved: “Who else needed to make a decision or do something?” Ask about responsibilities rather than names.
- The outcome: “What eventually happened to the work?” They may have chosen another supplier, found a workaround or left it unfinished.
- Your understanding: “Have I understood this correctly…?” Give a short summary and invite corrections.
“Was our website confusing?” introduces your explanation before the customer has described theirs. “What information were you looking for on that page?” gives them more room. If they’re willing to show you the page and what they tried, you can compare their account with something observable.
Leave room for answers you didn’t expect. If they say the work became unnecessary, explore what changed rather than steering them back to price. Likewise, “I’d probably buy that” is not an order. HBS frames discovery as learning about the customer, rather than pitching or asking them to endorse your opinion.
A worked example: a product photography enquiry
This is a fictional teaching example, not an Erfan Bashiri client project or a reported business result. A product photography studio notices that some enquiries stop after it sends its terms. The owner is considering a discount. The team first reviews one recent enquiry.
The conversation opens up a different explanation
The salesperson asks what the shop owner needed the photographs for. New products were due to go on the website. Asked what happened after receiving the terms, the shop owner explains: “I realised I’d have to send the products to the studio. For some items, I only had one in stock. I didn’t know how long they’d be unavailable to sell.”
The salesperson doesn’t jump straight to a solution. They ask what the shop owner did to find out. The reply: “I asked when the products would come back. I remember being told it depended on the workload.” The shop owner took some photographs on a phone and postponed the rest.
When asked what part price played, the shop owner says: “It mattered, but first I needed to know which products would be away, and for how long.” Price stays on the list of possible barriers. What changes is the team’s assumption that a discount is the obvious first move.
The message supports only part of the account
In this fictional scenario, the team reviews the relevant messages with permission. There is a question about when the products will be returned, followed by an answer without a usable timeframe. This supports the account of an unanswered practical concern. It does not establish that the customer would have bought if the answer had been clearer.
A useful note reads: “For this enquiry, the return timing was unclear. The customer says it mattered to their decision.” “Our customers don’t buy because turnaround is unclear” goes beyond what this one case shows.
The team makes a smaller, testable change
Before offering a general discount, the team prepares a collection and return plan for the next relevant enquiry. It states which items would be sent, when they could be returned, and what could affect those dates. The person responsible for the studio schedule checks what is feasible before sales makes a promise.
The team then records whether the prospective customer understood the plan, which questions remained, and what happened to the enquiry. A purchase would be an outcome worth recording, but one purchase would not prove that the new explanation caused it. The next customer may have a different budget, deadline or product range.
- Initial assumption
Perhaps the price stopped this enquiry.
- Customer’s account
I did not know when my products would be returned.
- Checkable record
The message asks about return timing; the reply gives no clear window.
- Still unknown
Would a clear schedule have led to a purchase? We do not know.
- Next check
Explain a feasible collection and return plan; record what remains unclear.
One case does not establish why all customers behave this way. Keep each step tied to its own account or record.
Use a six-part evidence note
Use a separate note for each enquiry. Copy these six headings into your own document. Each has a completed example so you can see how much to write. This is a practical working sheet, not a diagnostic score or a validated research instrument.
- Initial assumption. The owner thinks this enquiry stopped because the price was too high.
- Account or evidence. The customer says the return timing was unclear. The message history contains a question about return timing and no specific answer. Keep the customer’s recollection and the message record as separate entries.
- Another explanation. The work may have become less urgent, the budget may have been insufficient, or shipping the products may have been impractical. None has yet been ruled out.
- What we don’t know. Would this person have bought with a clear schedule? Do other enquiries contain the same unanswered question?
- Next check. Review recent enquiries at the same stage. For a suitable new enquiry, prepare a feasible collection and return plan and record remaining questions. This does not isolate the effect on sales.
- Owner and deadline. The studio lead checks the available dates by the end of the next working day. Sales records the customer’s understanding and next action during the following conversation.
When evidence is missing, write “not checked yet”. Don’t replace a blank with a plausible story. The GOV.UK guide to analysing research separates observations, findings and actions. The six headings above apply that distinction to this enquiry; they are not an official GOV.UK template.
Prepare your own interview note
Use these six fields for one specific enquiry. The completed example above shows the level of detail; write your own observations here.
Which enquiry and which decision? Label the team’s initial explanation as an assumption.
Separate what the person said from what the record shows. Include the source and date.
What other explanation could fit the same evidence?
Which question still lacks evidence? Write “not checked yet” where appropriate.
Choose a limited check. What will you examine, and which evidence would help?
Who will do what, by when, and when will you review it?
This tool does not send your text to the site or save it in browser storage. Download it before leaving. Leave out customer names and confidential information.
Choose what to check next
Match the next check to the uncertainty. If someone says a form failed, try to reproduce the relevant steps and device conditions. If they say nobody replied, examine the timing and content of the messages you are authorised to access. If they no longer needed the service, ask what happened to the task instead. More interviews are not automatically the answer to every gap.
Compare like situations. A small shop buying a few photographs and a company commissioning a large catalogue may face different constraints. Group notes by stage and type of need before combining them. Keep cases that contradict the team’s favourite explanation; they may show that you are dealing with more than one problem.
There isn’t a fixed interview count that makes every business decision safe. A few conversations may clarify your next question without showing how common the problem is. “Most customers…” needs evidence about the wider group and how people were selected. Keep the size of the decision proportionate: clarifying an ambiguous answer is different from changing every service price.
Prepare your customer interview questions and evidence note
Pick one recent enquiry. Write down the decision you have paused, invite the person to discuss that specific experience, and complete the evidence note afterwards. A useful result might be a small change, a focused investigation or a clear reason to hold off deciding.
If you plan to continue the investigation with a consultant, bring the note, the enquiry timeline and any relevant material you have permission to share. The guide to preparing for a business consultation explains how to make that conversation more concrete.