Skip to main content

Selling

Ombe, Your Storefront Chat: Answer Shopper Questions

Ombe answers shoppers from your own entries, your own pages and your live catalogue, in their language, names its sources, learns from your team's replies, and brings you every question it cannot answer.

Overview

Ombe is the chat on your storefront. It answers shopper questions — shipping times, return windows, sizing, prices, whether something is in stock — and it only ever answers from facts that came from you. It never makes up an answer from outside knowledge.

Ombe is on every plan.

When it genuinely cannot answer, it does not simply apologise and forget. The question is recorded, you are alerted, and your answer goes back to the shopper and into the knowledge base, so the next shopper who asks it is answered in a second. When your team takes over a chat, Ombe learns from the reply too (see Ombe learns from your team below).

Go to Channels → Ombe chat to set it up, and Customers → Shopper chat to see the questions, the conversations and what Ombe has learned.

What it answers from

Your own entries. Click Add entry on the knowledge base page, give it a short title and the answer in plain text — "Do you ship to Canada?" / "Yes, 5–7 business days, $12 flat rate." Add as many as you like; edit or delete them any time. These are the entries that win arguments: they are what you said, in your words.

Your own pages. BestWebby can read your storefront pages (FAQ, shipping, returns) and turn them into entries automatically. They show up read-only — to change what they say, edit the page and recrawl. A hand-edit here would be overwritten on the next crawl.

Your help center. Every article you publish in your help center becomes an entry, linked to the article on your store. Edit the article and the entry changes with it; unpublish or delete it and the entry goes. Articles you published before this was added are picked up within a day.

Answers to product questions. When you answer a shopper's question about a product (Customers → Reviews, Questions), the answer becomes an entry too, so the next shopper who asks gets it straight away. Hiding the question removes it.

Your catalogue. Every published product becomes an entry on its own, built from what you already maintain: the description, category, product code, listed price, specifications, tags, how it is sold, and whether a partner fulfils it. You do not write these and you do not maintain them — they regenerate when you change a product, and an entry for a product you delete is retired.

Your live stock and prices. Product entries deliberately carry no stock count. A count saved into an entry is true for about as long as it takes someone to buy one, and the chat quoting a stale number with your shop's authority behind it is worse than it saying nothing. So when a shopper asks what something costs or whether it is in stock, those two figures are read from your catalogue at the moment they ask — the price this storefront actually charges in its own currency, and whether they can buy it right now. The price is the one the product page shows: your Pricing rules and a running Flash sale are applied exactly as the page and checkout apply them, so the chat never quotes a happy-hour item at its full price or a surge-priced item below what checkout charges. A product your shop would refuse to sell (hidden, unpublished, or not priced for that market) is never quoted.

Products in an answer

When an answer names one of your products, a card for it appears under the answer: its first photo, its name, the price the product page shows (in your store's currency, formatted for the shopper's language), and whether it can be bought now — in stock, only a few left, available on backorder, available to pre-order, or out of stock.

Every card has View, which opens the product page. A plain product that can be bought now also gets Add to cart, which puts one in the shopper's cart without leaving the chat. Anything with a choice to make goes to the product page instead: products with options (size, colour), personalisation fields, a minimum quantity or case pack, products sold by weight, gift cards, items that need measurements, and pre-orders. Add to cart never puts more in the cart than you have in stock, and checkout prices the cart again, as it always does.

Cards only appear for products the answer actually mentions, at most three, and only for products this storefront sells. If your shop cannot take payment yet, the cards show View only.

The cards and the words around the chat (its title, buttons and messages) follow the shopper's language, including French.

How Ombe answers

  • In the shopper's language. A question typed in French on an English store is answered in French, and the other way round. When a question is too short to tell ("XL?"), Ombe answers in the language the shopper is reading your store in.
  • With its sources. Under an answer, Where this answer comes from lists the entries the answer actually used, and only those: a question about shipping does not show your returns page because it happened to be nearby.
  • With thumbs. Every answer has This answer helped and This answer did not help. A shopper who says it did not help can add What was wrong? (optional), and the question goes into Unanswered in Customers → Shopper chat with the answer they were given, so you can see what was wrong and write a better one. One answer is filed once, however many times the shopper changes their mind.

Ombe learns from your team

When someone on your team joins a conversation and answers the shopper, that reply is usually the best answer you have. Ombe turns it into a draft for next time:

  1. Contact details, order numbers and other personal details are taken out first.
  2. Ombe rewrites what was left as a general question and answer. A reply that was only about one shopper's own order is skipped.
  3. The draft waits under Ombe is learning at the top of Customers → Shopper chat. Approve adds it to your knowledge base, Edit lets you change the question and answer first (Save and approve), and the cross rejects it. What was actually said shows the original exchange until you decide; after that the draft keeps only the general version.

Nothing a draft says reaches a shopper until someone approves it, unless you tick Publish takeover answers automatically for a store. With it on, a draft Ombe rewrote with no personal details left is added straight away, and any other draft still waits for you. Only someone who can edit the storefront can change that setting; anyone who can answer shopper chats can approve drafts. Ombe drafts from up to 200 team replies per store a day; replies after that are kept in the conversation, just not drafted.

Ombe is learning also shows this week's answer rate (how many questions Ombe answered against how many it passed to your team), how many shoppers said an answer helped or did not, how many drafts are waiting, and the questions it could not answer most often, with Answer them in Unanswered.

Turn it on

Flip the switch at the top of the knowledge base page. If you have no entries at all, turning it on is confirmed first: with nothing to answer from, every question would come straight to you.

When it cannot answer

This is the part that makes the chat get better instead of just forwarding work.

  1. The question is recorded. One row per question, however it is worded. "Do you ship to Alberta?", "Can you ship to Alberta, and how long does it take?" and "Do you deliver to Alberta?" are one thing for you to answer, with a count of how many people asked and the other wordings listed underneath, so you can see if one of them is really asking something extra.

Two questions are only merged when they mean the same thing, and three rules stop that going wrong: the match has to be a strong one, a question and its negative are never merged (“is this dishwasher safe” and “is this not dishwasher safe” want opposite answers), and a one-word question like “price?” is left on its own rather than being swallowed by every other question about price.

  1. The shopper is offered a reply address. Only at this point, never as a form up front. If they leave one, your answer can reach them after they have closed the tab.
  2. You are alerted — in your dashboard, by email, and on your phone if you have turned on browser notifications (Settings → Notifications → Push). Each question alerts once. A shop that takes a dozen in a minute gets one alert saying a dozen, not a dozen alerts.
  3. You answer it in Customers → Shopper chat. One answer, typed once, does four things: it goes to every shopper who asked and left an address, it appears in their chat window if they are still on the page, it is saved against the question, and — unless you untick the box — it becomes a knowledge base entry under the shopper's own wording, so the chat answers it itself from then on.

If you answer a question and shoppers still get deflected on it, the question re-opens and alerts you again. That is deliberate: it means the entry you wrote is not matching how people ask, and it is worth knowing.

Taking over a conversation

In Customers → Shopper chat → Conversations you can read any conversation and join it. While you are there the chat stays silent — it will not answer over you. Your replies appear in the shopper's widget within a few seconds.

Presence is live, not a switch: if you close the tab or walk away, the chat starts answering again after about a minute and a half rather than leaving shoppers talking to an empty room.

When a shopper is waiting for a person

A conversation is waiting for you when the chat could not answer the shopper, or when they clicked Talk to a person in the chat window (it shows once they have written something). The moment a conversation starts waiting you get the notification A shopper is waiting in chat: in your dashboard and, if you turned on browser notifications, on your phone. Email is off for this one by default, because by the time an email is read the shopper has usually gone; switch it on under Settings → Notifications if you want it. The notification opens the conversation in Customers → Shopper chat. One waiting conversation is one alert, however many questions the shopper asks while they wait.

Working a conversation

  • Canned responses. The button beside the reply box lists the canned responses you keep in the Inbox. Pick one to put it in your reply, then edit and send. Canned responses are written in Customers → Inbox, so they show here on plans that include the Inbox.
  • Make a ticket. For a conversation that needs follow-up after the shopper has left, Make a ticket copies the whole chat into a ticket in Customers → Inbox, where it can be assigned, prioritised and answered by email. A chat makes one ticket; pressing it again shows In the Inbox. A reply from the ticket goes to the email address the shopper left; without one, the reply is saved and the Inbox says it could not be sent.
  • Customer record. If the shopper left an email address that matches one of your customers, the conversation shows that customer with Link to this customer. The address a shopper types into a chat is not verified, so the link is made only when you click it (or when you make the chat into a ticket). A linked chat and its ticket appear with that customer, move with them if you merge customers, and are removed if you erase them.
  • Email transcript. Sends the shopper the whole conversation from your own email domain, when they left an address. Shoppers can ask for it themselves with Email me this conversation in the chat window: it goes only from your own domain, at most twice a day for one conversation, and never to an address that bounced or complained. Without your own email domain, it is not sent and the screen says so.

Good to know

  • This is a different knowledge base from the one behind BestWebby's own help chat (the help button at the bottom of every dashboard screen). That one answers "how do I use BestWebby" from BestWebby's manual and FAQs; your storefront's Ombe answers "tell me about this store". The help chat has thumbs too: when you say an answer did not help, or it cannot answer, your question goes to BestWebby's team with contact details and order numbers taken out, and the answer they write is then given to every store that asks.
  • Answering a shopper by email sends from your domain, so it reads as your shop replying. If you have not set up email on your own domain yet, the answer is still saved and still added to the knowledge base, and the screen tells you plainly that the shopper could not be emailed.
  • Anyone with the support roles (owner, admin, manager, staff, accountant) can answer questions and join conversations.
  • Crawled entries are replaced wholesale on each crawl. For an answer that must never change even if a page does, write it as a manual entry.