Pre-Sales Support: Answer Product Questions Before Checkout
Help shoppers make informed choices with a pre-sales support workflow for product questions, clear comparisons, useful source information and human review.

Pre-sales support helps a customer understand a product before buying it. A useful reply identifies what they need to know, answers from checked product information, and explains any uncertainty before offering a relevant next step.
For a small online business, that work can happen in website chat, WhatsApp, Instagram or Facebook Messenger. “Will this fit?” and “What is the difference between these two?” are support questions even when no order exists yet. This guide shows how to prepare the answers without turning every enquiry into a sales pitch.
What should pre-sales support do?
The immediate goal is to help someone make an informed decision. That may mean recommending an appropriate option, explaining a limitation or confirming that you cannot verify the requested fit.
Keep three outcomes distinct:
- A useful answer: the customer receives relevant, supported information.
- A next step: they open a product page, request human help or agree to follow-up.
- A purchase: an order is actually completed.
These are different events. A product link is not a sale, and a captured email does not prove that the customer’s question was answered. Track them separately in your own review process.
1. Organise questions around the buying decision
Review recent pre-purchase messages and group them by what the customer was trying to establish. Use the actual wording rather than replacing every question with a broad topic such as “product enquiry”.
| Decision | Example question | Information needed |
|---|---|---|
| Fit | Will my laptop fit in this bag? | Usable compartment measurements and relevant limitations. |
| Difference | How does this version differ from the other one? | A comparison of the specific features that matter. |
| Contents | Does the set include the accessories? | An explicit list of included and separately sold items. |
| Use | Can I use it outdoors? | Approved use conditions and any restrictions. |
| Purchase conditions | What delivery options can I choose? | The relevant current delivery information or checking process. |
Start with the questions your business actually receives. A stationery shop and a furniture retailer need different detail. Do not assume a general answer about a collection applies to every product variant.
2. Build a small product-answer worksheet
For each common question, keep the following information in the source your team maintains:
- Product and variant: the exact item the answer covers.
- Approved answer: a short factual explanation.
- Source: the relevant product record, specification or maintained policy.
- Conditions: exceptions, measurements or usage limits that change the answer.
- Unknowns: what needs a person or a current check.
- Destination: the most relevant page or human contact route.
- Owner and review trigger: who updates it when the product or policy changes.
This is a suggested preparation worksheet, not an automatic Zorachat feature. It is useful because a short marketing description may not contain enough detail to answer a specific customer question.
Separate stable facts from information that can change quickly. A material specification may remain valid for a product version; stock by variant or a delivery estimate may require a current check. An item appearing in a catalog does not by itself confirm that it can arrive on a particular date.
3. Answer before asking the customer to qualify themselves
If the customer asks whether a set contains four or six items, give the confirmed quantity. There is no need to request their email, budget and purchase date first.
When clarification is needed, ask the question that changes the answer. “Which model are you using?” may be relevant to a compatibility enquiry. “How many employees do you have?” is unlikely to help someone choose a notebook.
Use the details already supplied. If the person has named the product and size, do not send a generic “Which item are you interested in?” A useful clarification moves the decision forward; it should not restart the conversation.
For more adaptable wording, see the customer service response templates. Check every template against the specific item before using it.
4. Compare options against a stated need
Consider a fictional retailer selling two bags. Its approved product information says:
- Bag A has an internal laptop compartment measuring 32 × 23 × 2 cm.
- Bag B has an internal laptop compartment measuring 35 × 25 × 3 cm.
- The customer says their laptop measures 33 × 24 × 2.5 cm.
A weak recommendation says, “Both are great, but Bag B is our premium option.” It does not explain the fit.
A more useful reply is:
“Based on the measurements you shared, Bag A’s compartment is smaller than your laptop. Bag B’s listed compartment is larger in each dimension, so it is the option to examine further. Please also check the opening and any case you use; these measurements alone do not guarantee a fit. Here is Bag B’s details page: [link].”
These products and dimensions are illustrative, not actual Zorachat products or customer results. The reasoning matters: compare relevant facts, name the limitation and link to the exact option. If the dimensions are missing, do not infer fit from a product photo or a label such as “large”.
5. Involve a person when the evidence runs out
Custom orders, conflicting specifications, requested exceptions and unsupported compatibility claims need more than confident wording. Explain what still requires checking and use the real route to the team.
For a handoff, preserve the product, the customer’s requirement, the information already given and the unresolved question. A teammate should be able to continue the investigation rather than ask the customer to describe everything again.
If the enquiry concerns custom work rather than a standard product, use the guide to handling quote requests to collect a useful brief. Do not present an unapproved custom price or appointment as confirmed.
6. Put repeated answers where shoppers can find them
If several people ask what is included in a set, improve the product page as well as the chat reply. Keep item-specific facts with the item; use a general FAQ for information that genuinely applies across the business.
Shopify’s FAQ guide describes FAQs as a place to find common product and policy answers and recommends using them when a question needs more context. You can apply that content principle regardless of which website platform you use.
After an update, check the page, the information given to your assistant and any saved replies your team uses. A corrected answer in one place is not enough if another source still contains the old version.
7. Use AI to support the conversation, then test it
Zorachat can learn business and product information, answer product questions and point customers towards relevant product details. Its human takeover lets your team join conversations that need judgment across website chat, WhatsApp, Instagram and Facebook Messenger.
Give the assistant the facts behind the recommendation, not just persuasive descriptions. Test two similar products, a missing specification, an unavailable answer and a customer who explicitly requests a person. Check whether it asks useful clarifications and avoids unsupported promises.
For the channel-specific setup, read how to use one catalog across WhatsApp, Instagram and Facebook. This article’s worksheet and review method remain team practices, not a promise of automated stock checks or guaranteed recommendations.
Review whether the customer got useful help
Sample conversations regularly. Record which questions were answered, which required human checking and which exposed missing product information. Where you can verify an order outcome, record it separately rather than treating every recommendation as revenue.
A successful pre-sales conversation can also end with an honest “this option does not meet that requirement”. Useful support helps someone understand the choice, including when your product is not the right fit.
Build your Zorachat assistant around the product questions your customers already ask, then improve the source information as you review the conversations.


