Pre-purchase questions: how support turns them into orders
TL;DR
A shopper asking before buying is telling you what stands between them and checkout. Sort questions by intent, answer directly with evidence and a next step, be honest about reply times, and feed repeat questions back to product pages.
A shopper has your smart lock in the cart and opens chat: “Will this work with my door, and can it arrive before Friday?” Your team answers the next morning. By then the shopper has bought a competitor’s lock that listed its door thickness range on the product page.
Pre-purchase questions are the last objections between an interested shopper and an order. This guide covers how to sort them, what a converting answer contains, what to do when nobody is online, and how to measure the result.
Why pre-sale questions deserve their own queue
Most support processes are built around existing orders. Pre-sale chats have no order number, often no email address, and a shopper who can leave in one click. A 24-hour ticket target wastes that moment.
In its 2021 Shopify Inbox launch announcement, Shopify said 70% of Inbox conversations were with customers making a purchasing decision, and that customers who chatted with store owners through Inbox were 70% more likely to convert. A 2022 Shopify guide to live chat reports, from its analysis of Inbox usage, that businesses replying within five minutes were 69% more likely to get a sale. These figures describe Shopify Inbox merchants and show association, not proof that chat caused the sale: shoppers who start a chat may already be closer to buying. The practical point stands. Pre-sale chats are where intent is visible, and speed matters there more than in most queues.
Sort questions by what the shopper is trying to decide
The wording varies; the underlying decision usually falls into a handful of intents. Tag each pre-sale chat with one, and the right answer and owner follow.
Cart abandonment research points to the same themes. Among US online shoppers who abandoned for a reason other than “just browsing,” Baymard’s cart abandonment survey lists delivery that was too slow (20%), not trusting the site with card details (19%) and an unsatisfactory returns policy (13%). Each of those doubts can surface first as a chat question.
A framework: question, intent, answer ingredients
Use this table as the core of a pre-sale playbook. It tells an agent or a bot what a complete answer contains for each type of question.
| Typical question | Shopper’s real decision | Answer ingredients | Who should answer |
|---|---|---|---|
| “Will it work with my iPhone / router / door?” | Compatibility: will this fit my situation? | Yes, no or “it depends on X”; the spec that decides it; a link to the compatibility list or setup guide | Bot if a published list covers it; human for edge cases |
| “Can it arrive by Friday?” | Timing: will it arrive when I need it? | Cut-off time and shipping method; what is and is not guaranteed; link to shipping policy | Bot for standard answers; human when a date is critical, such as a gift or event |
| “What if it doesn’t work for me?” | Risk: what happens if I am wrong? | Return window and condition; who pays return shipping; warranty scope; link to both policies (what to state before checkout) | Bot, with policy text as the only source |
| “What’s the difference between the S and the Pro?” | Choice: which option is right for me? | One or two questions about their use; a clear recommendation with the reason | Human for high-price or technical products |
| “Are you a real company?” | Trust: is it safe to pay here? | Company name and contact details; payment and data handling facts; verifiable reviews or press, if they exist | Human, with a short, factual script |
Two rules apply to every row. Answer the question before explaining anything else, and end with one concrete next step: a product link, the right variant or the policy page.
What a converting answer contains
A useful pre-sale reply has four parts: a direct answer, the evidence behind it, the relevant policy link, and a next step.
For the smart lock, a weak reply says: “Our lock fits most doors! Let me know if you have other questions.” A strong reply says: “It fits doors 35 to 55 mm thick with a standard deadbolt. If you can measure your door, I’ll confirm. Orders placed before 2 pm ship the same day by ground service; delivery by Friday isn’t guaranteed from here, so I’d suggest express. Here is the product page with the fit guide.” The numbers are illustrative; every fact in a real reply must come from your own specifications and carrier arrangements.
Be careful with delivery promises. The US Federal Trade Commission’s Mail, Internet or Telephone Order Merchandise Rule requires sellers to have a reasonable basis for the shipping times they advertise, and to seek the buyer’s consent to a delay or offer a refund when they cannot ship as promised. A “definitely by Friday” to save a sale creates exactly the problem that rule addresses.
Do not reach for a discount by default. A code answers a price objection, but fit, timing and risk questions are not about price. Discounting them trims margin on orders you might have won anyway. Keep discount authority for defined cases, such as a price match you have decided to honor.
Response times and hours when nobody is online
Pre-sale chats need a faster target than post-purchase tickets, because the shopper is still on the page. Set it separately and staff for the hours your traffic arrives, in your customers’ time zones. The responsive support guide explains why a fast reply only counts when it moves the case forward.
Outside staffed hours, split the work by answer type:
- Clear-answer questions (shipping cut-offs, return window, published specs): a bot or FAQ can answer these well if it draws only on your policy and product content. Shopify’s help center describes an Inbox agent that answers questions about products, shipping, returns, sizing and store policies from your catalog, policies and published pages.
- High-consideration questions (technical fit, bundles, large orders, trust concerns): collect the details and hand off to a person. Our guide to when AI should hand a conversation to a human covers the triggers in more depth.
- Honest reply promise: tell the shopper when a person will reply, and in what channel. Shopify lets merchants set availability hours and a separate automatic first reply for chats that start outside them. Use that message to state a real reply time, not “we’ll be right with you.”
Feed recurring questions back to the product page
A question asked in chat is likely one other shoppers had and never asked. Once a week, check the ten most frequent pre-sale questions against the product page. If the answer is missing, buried or ambiguous, fix the page. Shopify’s own Inbox announcement makes the same point: understand the most common questions, then improve FAQs, quick replies and product descriptions.
Compatibility tables, a delivery estimate near the add-to-cart button and a plain-language returns summary are common places to start. For hardware, “will it work” questions often trace back to setup documentation that shoppers cannot see before purchase. The product manual guide covers how to make those instructions useful to buyers and support alike.
How to measure pre-sale support
Review a few measures weekly:
- Chat-to-order rate: the share of pre-sale chats followed by an order from the same shopper within a set window, such as seven days. Compare it across intents and product lines rather than chasing one overall figure.
- Time to first reply on pre-sale chats: reported separately from post-purchase tickets, and split by staffed and off hours.
- Top unanswered questions: questions the bot could not answer, or that took more than one reply to resolve. These are your content backlog.
- Discounts issued in chat: how many, why, and whether they were needed.
A worked example (hypothetical)
Consider a fictional store selling a video doorbell. In one month it records 400 pre-sale chats, and 60 of them are followed by an order within seven days: a chat-to-order rate of 15%. Tagging shows 120 are wiring compatibility questions, so the team adds a wiring checker to the product page. Next month compatibility chats fall to 50, and the remaining chats are harder. The chat-to-order rate may move either way; the better check is whether orders from that product page improved. All figures are invented for illustration.
Start with one week of tagged chats
You do not need new software to begin. Tag one week of pre-sale chats by intent, note the reply time and whether an order followed, and list the questions your team could not answer confidently. That list shows where the product page, policy wording or staffing hours need attention.
If you would like a second view, send us a week of anonymized pre-sale questions and your current coverage hours. We can discuss which questions a bot can safely handle and which need a trained person.