Before adding a WhatsApp button to an online store, there's one thing worth thinking about: what happens when someone actually sends a message?
Adding the button is easy. The work starts when you're packing an order, someone asks about sizing, and another customer wants to change their delivery address while you're finding the answer.
None of those questions sounds like a big job on its own. Together, they can take up most of a morning.
If you run a small store, everything can end up on the same phone. Supplier messages, people who have already bought something, and people who just want to check a price. You can spend hours replying without feeling as though you've finished anything.
I'd find it hard to keep that up every day. When you're handling products, orders and the website as well, being permanently available is a lot to ask.
Before trying to reply faster, I'd look at what people are asking and why. A few fairly ordinary changes might remove some of the work.
If everyone asks the same thing, check the product page
I'd start by reading through the last few days of conversations. No elaborate report. Just a quick note of the questions that keep coming up.
You might find that most of them are about:
- Dispatch times: when an order will actually leave, rather than how long shipping takes afterward.
- Sizes and measurements: which version will fit or how much space something takes up.
- What is included: whether the accessories in the photo come in the box.
- Exchanges: what happens if the customer chooses the wrong size.
Then go back to the store and try to find those answers on your phone.
It's easy to think something is clear when you know exactly where you put it. A customer may be seeing the page for the first time, in a hurry, on a small screen. If the measurements are buried under five paragraphs, asking you can feel like the easier option.
Photos can leave similar gaps. A backpack might look great against a white background without showing how much fits inside.
A photo of the compartments, or a short explanation of their dimensions, may save you from writing the same answer again tomorrow.
You'll still get questions. But people should not have to start a conversation just to find information you could have put on the page.
You don't need to write every answer from scratch
Some replies are worth keeping handy, especially when they contain details you don't want to remember off the top of your head.
The trouble starts when the same saved reply gets used for questions that only sound similar.
If someone asks whether they can exchange a size, sending your entire purchase policy may leave them just as confused. They probably need to know whether that particular item can be exchanged and what they need to do next.
A saved answer can give you a starting point. You still need to read the question and adjust it.
I'd keep a simple shared document with:
- Measurements and differences between products that people often confuse.
- Packing, dispatch and shipping information.
- Return and exchange conditions.
- Questions that need checking before anyone gives a definite answer.
That last point matters. Some questions can be answered immediately. Others mean checking an order or asking someone else.
If you don't know whether a parcel will arrive before Friday, check before promising it will. A quick answer on Monday can turn into several uncomfortable messages on Thursday.
Someone also needs to keep the document current. A saved reply about a product that has changed can create more work than it saves.
This information will help while you're replying yourself. It will also be useful if you later decide to automate some of the routine questions.
A quick reply can still leave the customer stuck
Imagine you're buying a backpack for a 16-inch laptop.
You ask whether it will fit and get: “Hi, thanks for getting in touch. You can find all our models in the catalog.”
The reply arrived straight away. You still don't know whether your laptop fits.
That is the kind of exchange I'd look for when reviewing customer messages. An automatic greeting can confirm that a message has arrived. After that, someone or something needs to deal with the actual question.
I'd also check how much information you ask for before helping. Someone asking about a measurement probably doesn't need to give you their full name, email address and order number.
From inside the business, that might look like an organized process. From the other side, it can feel like a lot of effort for a small question.
Read the whole conversation and count how many messages it took to reach a useful answer. That can tell you quite a bit.
Try automating a few specific questions first
If customer messages are taking up too much of your day, looking for help makes sense.
I'd start with a few common questions where the information is already clear. That gives you something manageable to review instead of trying to check every possible situation at once.
If you're looking at options such as Cubbo Engage, I'd test them with the questions your store actually receives, including the half-written ones and the typos.
People don't always use the full product name.
“Do you have that in black?”
“Which one is the big one?”
“I want another like the one I ordered last time.”
Sometimes there's a photo. Sometimes they mean something they saw on social media and assume you know which item they are talking about.
Watch what happens next. Does the system ask for clarification? Is it answering about the right product? Does it recognize when information is missing?
I'd also try a question for which there's no answer in the store information. I'd rather see it left for someone to check than receive a confident explanation that turns out to be wrong.
You don't need to cover the entire catalog on day one. Start small enough that you can read the conversations and fix problems as you find them.
Make it easy to reach a person
Some conversations need more than a prepared answer.
An order arrived incomplete. The wrong item was sent. Someone has spent several messages explaining a problem and is getting frustrated.
Before leaving any system running, I'd check four things:
- A customer can ask to speak to a person.
- Someone on the team gets notified when that happens.
- That person can see what has already been discussed.
- The unresolved conversation stays visible when new messages arrive.
Keeping the context sounds like a small detail until you have to explain the same problem for the third time.
If you've already sent a photo and provided your order number, you expect the next person to be able to see them. Asking for everything again makes the conversation longer for both sides.
And if you're the only person handling support, you still need a way to separate finished conversations from the ones you need to sit down and review.
Set hours you can actually keep
I'd avoid saying “we will be with you right away” if there are parts of the day when nobody can check the phone.
It sounds friendly, but it creates an expectation you might not be able to meet.
A short message can explain your support hours and when someone will look at the question. Some routine questions might be answered automatically outside those hours. Anything that needs a person will have to wait, and it helps to say so.
There's no need for a long explanation. The customer wants to know that their message arrived and what happens next.
Having set hours can help you organize your own work too. You can make time to review messages instead of stopping every task as soon as a notification appears.
There will still be difficult days and urgent problems. But you should be able to put the phone down without wondering whether every unanswered message needs you immediately.
Read a few chats even when things seem to be working
Once the setup is running, I'd keep reading conversations now and then.
Look especially at exchanges where someone repeats a question, asks for clarification or stops replying just after receiving an answer.
A conversation ending doesn't tell you much on its own. The customer may have found what they needed. They may also have given up.
You won't always know which happened, but you can spot recurring problems:
- A shipping answer keeps being misunderstood.
- Two similar products keep getting mixed up.
- Customers are asked for details they have already provided.
- Conversations passed to the team sit unanswered for too long.
Fix the part you can see. Rewrite an unclear answer. Add the missing product measurement. Check who receives the notification when a customer needs help.
You don't have to rebuild everything each week. Sometimes one small correction makes the next conversation much easier.
Before calling the setup finished, I'd do one last check on my phone: open the store, choose a product and ask something that needs a follow-up question.
Stay with the conversation until the end. It's a useful way to see whether the WhatsApp button is helping someone shop or simply moving every unanswered question onto your phone.