The Buyer Who Almost Did Not Buy
A few years back I watched a small retailer nearly lose a sale in the most ordinary way. A customer landed on a product page late in the evening with one simple question about fit and delivery timing. The site had a contact form and a polite promise to reply within one business day. One business day. The customer did not need an answer tomorrow. She needed it while her card was still on the desk.
That story sticks with me because nothing went wrong technically. The form worked. The inbox worked. The process worked exactly as designed, and the design was too slow for how people actually buy. Live chat fixes the design. When I help businesses set up Odoo on their website, the chat window is not decoration. It is the front door, staffed, with the lights on, for the exact moment a buyer is deciding.
The lesson is simple: people do not chat to make conversation. They chat because something small is blocking a purchase, and removing that one small thing, right now, is worth real money.
Speed Matters, but Honesty Matters More
Everybody knows fast replies help. What gets less attention is that honest replies help more, because a chat that strings a buyer along is worse than no chat at all. If your team is at lunch, in the warehouse, or done for the day, the chat should say so plainly and offer the next best thing: leave a message, send an email, or get a callback at a real time you will actually honor.
In my experience, buyers forgive waiting when you tell them the truth up front. "We reply within the hour during business hours" builds more trust than a window that pops up cheerfully and then sits silent for forty minutes. That silence feels like a broken promise, and broken promises are how browsers become former visitors.
So set your availability honestly. Publish the hours the chat is truly staffed. Route chats to people who are actually at their desks, not to a shared login nobody checks. A smaller promise kept every time beats a big promise kept most of the time, in chat and everywhere else in business.
Canned Answers That Do Not Sound Canned
Let me defend the humble saved reply, because used well, it is how a small team answers fast without answering sloppy. Your buyers ask the same dozen questions constantly: shipping timing, returns, sizing, setup, compatibility, and what happens after they order. Writing those answers once, carefully, means every customer gets your best answer in seconds instead of a rushed version typed one-handed.
The trick is to write them like you talk. Read each saved reply out loud before you save it. If it sounds like a policy manual wearing a headset, rewrite it. Keep the sentences short, use the words your customers use, and leave a natural place to personalize the first line with their name or their specific product. A saved reply should be a strong starting point, not a script your team hides behind.
In my experience, the best teams review these replies every few months, because products change, policies change, and yesterday's perfect answer quietly becomes wrong. Ten minutes of review keeps your fastest answers from becoming your most embarrassing ones.
Hand It to a Human Before It Gets Weird
Chat handles the easy questions beautifully, and then real life shows up: a complicated order, an unhappy customer, a question with money and feelings tangled together. That is the moment good setups shine, because the handoff to a human is fast, warm, and loses nothing along the way.
Train your team to spot the handoff moment early. If a conversation needs a phone call, say so like a person: offer your number, offer to call them, and send a short summary so they never have to repeat their story to the next human. Repeating their story is the part customers hate most, and it is completely avoidable with thirty seconds of care.
Also decide who owns chats when things get busy. In my experience, unowned chats are answered chats' slower, sadder cousins. One named person per shift, a clear backup, and a simple rule for what happens after hours will carry a small team further than any fancy configuration buried in a settings screen.
Frequently Asked Questions
How fast do we need to reply on live chat?
Faster is better, but honest is best. If your team can reply within a minute or two during staffed hours, you are in great shape, because the buyer is still on the page and still deciding. If you cannot staff it that tightly, say what you can do and do it every time. A truthful expected wait builds trust, while a silent window quietly teaches buyers to shop somewhere else.
Who should staff Odoo Livechat in a small business?
Start with the people who already answer the phone and the inbox well, because chat is the same skill in a faster costume. In my experience, one named owner per shift plus a clear backup beats a vague everyone-watches-it approach. Rotate the duty so nobody burns out, keep product knowledge within reach, and make sure the person chatting can actually solve problems or reach someone who can.
What questions should we prepare saved replies for?
Begin with the questions your team already hears every week: delivery timing, returns and exchanges, basic product fit, setup help, and what happens right after an order is placed. Write each answer the way you would say it out loud to a neighbor. Review the list every few months, fix anything that has drifted, and add new replies whenever the same fresh question shows up twice.
What should chat say when nobody is available?
Say so plainly, warmly, and with a next step. A good offline message thanks the visitor, states when the team returns, and offers a way to leave a question with a promise you will keep about when the reply comes. Then keep that promise like it is a delivery date. In my experience, buyers remember a kept follow-up promise longer than they remember the wait itself.
