Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Customer Experience, Retention & Loyalty › Service and Support

Answering Pre-Purchase Questions

How to answer people who are deciding whether to buy: who answers, the product knowledge agents need, honest answers, handover to sales and fixing the pages.
Guideintermediate10 min readUpdated

Why pre-purchase questions are a service job

A person who asks a question before buying has done something most visitors do not: they have told the business exactly what is stopping them. The touchpoints guide names the unanswered pre-sales question as one of the costs a support team can see once it is shown where its touchpoint sits in the journey. The support channels and self-service guide notes that chat on product and checkout pages can protect conversion (CVR) by answering a hesitation before it becomes an abandoned basket. The same applies to email, phone and messaging.

Yet pre-purchase questions often fall between teams. Support is organised around customers with orders and accounts; sales, where it exists, is organised around qualified leads. A question from someone with no order and no lead record can wait behind service problems or be answered by someone who does not know the product well. This guide sets out how to treat these questions deliberately, in any business, consumer or business-to-business. Qualifying leads and sales follow-up stay with the inbound lead handling playbook, and the service and support hub sets out the channels and standards the work sits within.

The jobs-to-be-done framework is a useful lens. A question such as "Is this loud?" is rarely about the product alone; it reveals the job the person is hiring it for, such as using it in a flat with thin walls. An agent who hears the job can answer the real question and, where the product does not fit, say so.

Where the questions arrive and who should answer

Pre-purchase questions arrive wherever a person can reach the business: chat on product and pricing pages, the contact form, the phone, messaging apps, social comments and direct messages, and sometimes the general support inbox. Start by finding out where they come from today. Tag contacts as pre-purchase for a few weeks, or read a sample of contacts from people with no order history, and note the channel, the product and the question.

Then decide who answers which kind of question:

  • Support agents answer factual questions about the product, delivery, returns, compatibility and how things work, in the channel the person chose.
  • Specialists or product experts, where the business has them, take questions that need deeper knowledge, such as technical fit or a complex configuration.
  • Sales takes questions about tailored pricing, finance, large or custom orders, contracts and business buyers' requirements, through lead routing that sends each enquiry to the right person.

Set a standard for how quickly pre-purchase questions are answered in each channel, from the business's own evidence of what its buyers expect. For enquiries that go to sales, Lead Response Time is the measure; the lead response time test shows how a business can find out whether faster follow-up matters for its own leads. Pre-purchase questions should not sit in the same queue as complaints without a way to tell them apart, because both lose when they compete for the same agents.

What agents need to know, and what they must not promise

Agents answering pre-purchase questions need product knowledge that support teams often lack: what each product does and does not do, how products compare with each other, sizes and specifications, delivery options and times, the returns policy, and the questions people commonly ask before buying. A short product sheet for each product or range, kept where agents work, is usually enough to start.

Accuracy matters as much as knowledge. The claims library tutorial records that in the UK the Advertising Standards Authority publishes the codes and rulings that apply to advertising claims, and the site's guides use those codes as the reference for whether a marketing claim was acceptable. An agent's answer to a buyer carries the same risk as the claim on the page: if it promises a result the product cannot deliver, the customer has been misled, and the complaint or return comes later. The expectation-disconfirmation model describes why: the buyer judges what arrives against the expectation the answer set. The practical rules are simple:

  • Use the approved wording. Product sheets should take their claims from the claims library, so agents say what the marketing has been cleared to say, in the same words.
  • Never add a promise the page does not make. If the page does not say the product will do something, the agent does not say it either. Where the honest answer is "it depends", say what it depends on.
  • Say when you do not know. A promise to find out and come back is better than a guess.
  • Do not pressure. Urgency, scarcity and "today only" lines belong to the page's own checks; the honest persuasion guide covers them, and agents should not add their own.

This is general direction, not legal advice; anything about claims or advertising rules should go through whoever handles compliance.

Answering well: a table by question type

Most pre-purchase questions fall into a few types, each with its own trap.

Question typeExampleA good answerThe trap
Fit and suitability"Will this work for a small room?"Ask about the situation, then answer for it; suggest a better-suited product if there is oneSaying yes to close the sale
Comparison"What is the difference between these two?"The real differences that matter for this person's jobReciting the specification sheet
Total cost"What will I pay in total?"The full price with delivery, fees and any ongoing costsLeaving out charges that appear at checkout
Delivery and timing"Will it arrive before the weekend?"The delivery options and what the business can commit toPromising a date the delivery promise does not support
Risk and returns"What if it does not suit me?"The returns or trial terms in plain words, from the policyParaphrasing the terms more generously than they are
Contract and cancellation"Can I cancel any time?"The terms as written, with a linkReassurance that is not in the terms
Payment and finance"Can I pay in instalments?"What is offered, and a handover to the right person for detailsAgents explaining finance they are not trained on
Business requirements"Can you invoice us and sign our supplier form?"What the business can do, then a handover to salesTreating a business buyer as a consumer question

Answers to recurring questions can be prepared as saved replies, with gaps for the agent to fill for the person's situation. The tutorial on building a library of saved replies covers how. Pre-purchase replies should end with a clear next step: a link to the right product, a way to buy, or the name of the person who will follow up.

Handover to sales and recording what was asked

Handover. Agree which questions go to sales and how. The person should not have to repeat themselves: the handover carries their question, contact details and anything already answered, and the agent tells them who will follow up and roughly when. Where the business has a lead process, the handover enters it as an inbound lead, and the inbound lead handling playbook takes over from capture and routing to follow-up.

Recording. Record every pre-purchase question with its product, its type from the table above and its outcome where known: answered, handed to sales, bought, not bought. The record does three jobs. It shows which questions come up most, which is the list for the pages. It shows which products generate the most doubt. And it lets the business judge the effect of answering, by linking questions to later orders and comparing with similar visitors who did not ask, with care, because people who ask are often already closer to buying. Watch the Cart Abandonment Rate and returns for the same products too: a fall in abandonment after a page fix, or a rise in returns after an agent's answer, both say something. Remarks that people make at a counter or on the phone while they decide, which are not questions, fall outside this record, and the tutorial on recording what customers tell your staff writes them down in the customer's words.

The business's own records are the evidence here. No general figure tells a business how much answering pre-purchase questions is worth for its products and buyers; its own counts, read carefully, do. A controlled test of a new channel, such as chat on product pages, is a separate piece of work and needs to be designed for the business's own traffic. The product page chat test sets out that design, with visitors split between chat and the usual routes and returns read as a guardrail. Whether an automated assistant should take the first reply in that chat is a separate question, and the AI chat assistant test designs it with answer accuracy and handover time as guardrails.

Moving recurring answers onto the pages

The best pre-purchase answer is the one the person finds without asking. Each question that comes up repeatedly is a gap on a page. Take the most-asked questions from the record each month and put the answers where the question arises: on the product page, the pricing page, the delivery page or the checkout.

The product page optimisation guide sets out the questions a product page must answer in the order buyers ask them: identity, appearance and use, fit, total cost and timing, and confidence. The pricing pages guide says that answers about contracts, cancellation, limits and upgrades belong on the pricing page itself, close to the plans, and that the best source for them is the questions the business already receives. The pre-purchase record is that source. Where the most-asked question is which product suits a particular situation, the guide to product finder quizzes turns the same record into questions a shopper can answer on the site.

After moving an answer to a page, keep counting. Fewer questions of that type, with no fall in sales, is a sign the page now does the work. Questions that keep coming may mean the answer is hard to find or hard to believe, and agents' notes on how people phrase the question help rewrite it in their words.

A piano retailer answers buyers in chat and by phone (illustrative)

Illustrative example — not a real result

Wubrinox Pianos turns buyers' questions into answers

Wubrinox Pianos, an invented retailer of digital and acoustic pianos, has 4 support staff and 2 sales advisers. Tagging a month of chat and phone contacts, the team finds that 290 of 510 come from people with no order: most ask whether a digital piano is quiet enough for a flat, how two models differ, and whether delivery includes carrying the piano upstairs.

The team writes a one-page product sheet for each of 12 models, with claims taken from the claims library, such as the headphone socket and volume range, and no promises about how a piano will sound in a particular room. Agents answer fit, comparison and delivery questions; questions about lesson packages and finance go to a sales adviser, with the question and contact details passed on so the buyer is not asked again.

Every pre-purchase question is logged by model and type. After 2 months the 3 most asked questions, about volume, stairs and the difference between the two best-selling models, are answered on the product pages. Over the next 2 months pre-purchase chats about those questions fall from about 120 to 45 a month, and online orders for the two compared models hold steady, which the team reads as the pages now answering what chat used to.

Common mistakes

  • Leaving pre-purchase questions in the general queue. They wait behind service problems and lose the moment. Tag them and decide who answers.
  • Agents without product knowledge. A vague answer is a reason to buy elsewhere. Give agents a product sheet.
  • Overpromising. An answer that adds a claim the page does not make creates returns and complaints. Use the approved wording.
  • Handover that loses the question. A buyer passed to sales who has to start again may not bother.
  • Not recording what was asked. Without the record, the same questions return forever and nobody can tell whether answering them made a difference.
  • Never fixing the pages. A question asked every day is a page that does not answer it.
  • Judging agents only on sales. Honest answers sometimes lead to a different product or no sale; that protects the business from returns later.

Frequently asked questions

Should support agents or salespeople answer pre-purchase questions?

It depends on the question. Factual questions about the product, delivery, returns or how something works are usually answered best by support agents with good product knowledge, quickly and in the channel the person chose. Questions about tailored pricing, finance, large or custom orders, or a business buyer's requirements usually need a salesperson. The important part is deciding the split in advance and handing over smoothly, so the person does not have to ask twice.

How do you stop agents overselling when they answer pre-purchase questions?

Give them the same approved wording the marketing uses, ideally from a claims library, and a clear rule that they never promise anything the product page or the terms do not. Measure them on whether the answer was accurate and helpful, not only on whether the person bought. An honest answer that leads someone to a better-suited product, or to not buying, protects the business from returns and complaints later.

How do you know whether answering pre-purchase questions is worth the cost?

Use the business's own records. Tag pre-purchase contacts so they can be counted, link them to orders where the person later bought, and compare how often people who asked went on to buy with how often similar visitors who did not ask bought, bearing in mind that people who ask are often already more interested. Watch returns and complaints from those buyers too. A controlled test gives a firmer answer, but it needs to be designed for the business's own traffic.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Advertising Standards Authority — ASA

Related