What should an ecommerce support chatbot answer on its own?
By Omer Dahan
An ecommerce support chatbot should answer from business-approved information, not fill gaps with plausible details. Customer-specific requests, refunds and policy exceptions need separately scoped permissions and handling rules. A request for a person needs a clear route to the team rather than another loop of automated answers.
Key takeaways
- Start with answers supported by approved public information.
- Explaining a returns policy is not authorizing a refund.
- Define who receives unresolved requests and what the customer sees.
- Test boundaries before expanding to more channels.
What should an ecommerce support chatbot answer on its own?
There is no universal safe-answer list. The decision depends on the source, the sensitivity of the request and the action involved. Classify requests by the response the business permits instead of expecting an assistant to decide its own authority.
| Request | What to scope | When to stop |
|---|---|---|
| Opening hours and contact details | Answer from approved public information | Information is missing or contradictory |
| Shipping and returns policy | Explain the published policy | The customer asks for a promise about their order |
| Product information | Answer from approved product details | A specification is missing or an unsupported guarantee is needed |
| Status of a particular order | Separately scope identification and authorized access | There is no authorized source for the order data |
| Refund, order change or exception | A separate action path with permissions and review | The action and its boundaries have not been approved |
This is a proposed scoping framework, not a feature list for my existing client installation. The actual implementation is described here: Retail support assistant implementation
Why the distinction matters
“What is your returns policy?” and “Will you accept my return after the deadline?” sound similar. They are different requests. The first asks for information; the second asks for a decision about a particular customer.
A fast answer is not a good result if it creates an obligation the store never approved. Review whether the issue was resolved, whether the answer needed correction and whether a person received the case when required. Conversations answered are not the same as problems solved.
How should a handover to a person work?
Define what ends automated handling: an explicit request for a person, missing approved information, conflicting sources or an action outside the agreed scope. Then name the destination and the person responsible for receiving the request.
Agree on what the customer sees, what context the team needs and what happens outside staffed hours. Do not tell a customer that someone is handling the issue unless the process supports that statement. Do not keep asking the customer to rephrase a request that already qualifies for escalation.
Handover is not a feature to assume. Test the route in the actual channel and with the team that will receive the request. A visible contact button does not by itself establish that the underlying process works.
Which cases should you test before launch?
The following are proposed acceptance cases, not measured client results:
- A routine question with an unambiguous approved answer.
- A question whose key detail is missing from the information source.
- A request for someone else’s order information.
- A request for an exception to the returns policy.
- An explicit request to speak to a person.
- A request arriving when no team member is available.
- Equivalent Hebrew and English questions, if both languages are in scope.
- Messages from one customer in different channels, to check how the agreed process handles them.
For each case, write the allowed answer, the promises the assistant must not make and the owner of the next action. Do not change the expected outcome merely because the assistant gave a convincing answer. A failed boundary test is a reason to revise the implementation.
What should the implementation proposal contain?
Ask for a written scope: included channels, authorized answer sources, prohibited actions and ownership of policy updates. Specify how expired connections and unanswered questions are handled. Those responsibilities matter after the first demonstration.
Agencies bringing in a specialist should also define client communication and approvals. Who confirms the source information? Who approves a change? Who receives an incident? A demo on one store platform does not establish a ready-made integration with another platform.
Keep software usage, implementation work and maintenance separate in the proposal. This guide does not offer a standard price, a support response commitment or a promise of reduced staffing. Those terms require a scoped agreement.
Frequently asked questions
Can we start without order-data access?
Yes. An initial scope can be limited to approved public information. In that setup, the assistant must not present a general answer as a check of a particular order.
Can the assistant promise a delivery date?
Only when an authorized source and the relevant permission support that commitment. A general shipping policy does not prove a particular order will arrive on a particular day.
What if approved information conflicts?
Stop relying on the disputed answer and ask the information owner to approve the wording. Better phrasing cannot resolve contradictory policy.
Must all channels launch at once?
No. Start with a defined channel and scope. Each additional channel needs its access, message handling and support process assessed.
Do correct test answers guarantee an error-free system?
No. You still need an update owner, checks after changes and a failure-handling process. Passing a test set does not guarantee that every future request will be handled correctly.
Is there a real installation to review?
Omer Dahan built an n8n-based support assistant for a Konimbo retailer, answering customer questions across the website, Instagram, Facebook, WhatsApp and TikTok. A live demonstration is available. The acceptance framework above is a recommendation for scoping; it is not a claim that every mechanism described is already present in that installation.
Before choosing an implementation partner
Ask what happens when the assistant cannot answer—not only what happens when the demonstration goes well. Include a request the system should refuse to handle. That tests the boundary without requiring private customer data.
Related guides: Prepare store information Automation project cost factors
Discuss the fit or request a live demo: Discuss the fit or request a demo Do not include credentials, order records or customer details in the initial enquiry.