The product page says one thing. The FAQ says something slightly different. Then you message the shop, and someone gives you a third answer.
Which one are you supposed to believe?
Take a fairly ordinary question: “Does this come with the charging cable?”
The description says yes. An older image says the cable is sold separately. The person answering messages checks a saved reply and says it depends on the version.
At this point, buying a small electronic item has somehow become a research project.
When a shop starts thinking about automated customer replies, this is the sort of thing I’d want to look at first. Answering faster sounds useful. But if the information behind the answer is messy, a quicker response just gets the confusion to the customer sooner.
You don’t necessarily need a big technology project to sort it out. You do need to decide which information is current, where it lives, and who changes it when something stops being true.
Start with a question people actually ask
“Improve customer support” is a fairly difficult task to sit down and do on a Tuesday morning.
“Make sure everyone knows whether the cable is included” is much easier.
I’d start with a small handful of questions from actual customer conversations. The repetitive ones are useful because they give you something concrete to work with.
Things like:
- Does this include the accessories in the photo?
- Will this discount work on sale items?
- Can I collect an online order?
- Is this version compatible with the model I already own?
- How do I ask for an exchange?
Then try answering each question using only what a customer can find on the website.
You might discover that the answer is perfectly clear. You might find it hidden halfway down an unrelated page. Or you might find two answers that were both correct at different points in time.
That last situation is easy to create. Someone updates a product description but forgets the FAQ. A promotion ends, but the saved reply stays in the inbox. A new version replaces an old one without every reference being checked.
Nobody has to make a dramatic mistake. A few ordinary edits are enough.
A saved reply needs a little context
Saved replies are handy. Nobody wants to type the same explanation twenty times a day.
But a sentence copied without its conditions can become misleading.
“Yes, it’s included” might have been written for a specific bundle. “You can collect it tomorrow” might have depended on which location had stock. “That code works on everything” might have been true during one particular promotion.
Once the sentence sits in a shared folder, it can start to look like a general rule.
I’d want the person using it to be able to see what it applies to without digging through old messages.
For the cable example, the working note could be very plain:
“Current standard bundle: cable included. Replacement unit sold on its own: no cable. Check the selected option before answering.”
That isn’t especially elegant copy. It doesn’t need to be. It’s a useful internal explanation that helps someone give the customer a short, accurate reply.
The customer can then hear: “Yes, the standard bundle you selected includes the cable.”
Same friendly tone. Much less guessing.
Decide where the answer is kept
A shared document can work. So can information maintained in the store platform or another system the team already uses.
The important part is that people know where to look.
If one person checks a spreadsheet, another checks the website, and a third asks whoever happens to be nearby, the answer depends on who picks up the message.
That’s uncomfortable for staff as well as customers. Nobody enjoys giving a confident answer and finding out later that somebody else knew it had changed.
I’d keep the starting setup small. For each common question, record the current answer, the conditions that matter, and who can confirm it if something looks wrong.
A date can help, too, although “updated recently” isn’t a guarantee that the information is correct.
And having one agreed place for answers doesn’t mean every type of information belongs in a document. A general explanation about a product is different from live stock availability. One can stay useful for months; the other may change while the customer is typing.
The team needs to know that difference.
Give someone the job of keeping it current
“We should update that” is one of those sentences that can float around a business for weeks.
Everyone agrees. Nobody knows whether someone else has done it.
An answer needs an owner, even if that sounds a bit formal for a small shop. It can simply mean that one person checks product details and another looks after promotions.
The same person doesn’t have to write every reply. They’re just the person who can settle the question when information conflicts.
Suppose a bundle changes next month. There are now two accessories in the box instead of three.
Updating the product page is one task. Checking the comparison chart, FAQ and saved replies is another. If those are treated as unrelated jobs, something is likely to get missed.
A short list is usually enough to make the change manageable:
- Update the product information.
- Check the places that repeat it.
- Replace or remove old saved replies.
- Tell the people answering messages what changed.
- Try the customer question again.
That final step is easy to skip. It’s also the point where you find out whether the update actually reached the places people use.
Keep the customer’s answer short
Doing this properly doesn’t mean customers should receive a miniature policy document whenever they ask a question.
If someone asks whether the cable is included, they probably want a yes or no, followed by any detail that affects their purchase.
They don’t need the history of the bundle, the name of the person who checked it, or an explanation of how the shop manages product information.
The extra detail belongs behind the reply.
This is where I think a useful distinction gets lost. An internal answer needs enough context to prevent mistakes. A customer-facing answer needs enough context to help that particular person.
Those aren’t always the same amount of text.
For example, if the customer hasn’t said which version they’re considering, one question might be enough:
“Are you looking at the standard bundle or the replacement unit?”
That feels much more natural than sending both descriptions, every exception, and a request to read the full product page.
A helpful conversation should get simpler as it goes along.
Try the awkward questions before switching things on
A neat FAQ makes testing feel easy. Ask the exact question in the document, get the expected answer, and move on.
But customers rarely use the exact wording you prepared.
Someone might ask, “Do I need to buy anything else?” Another might send a screenshot with “Is all of this included?” A third might refer to an older version that’s still visible in a search result.
Those are the conversations I’d try before relying on automated replies.
If I were setting up Cubbo Engage, I’d use that same little collection of real questions instead of judging the setup on a few tidy demo messages.
The useful check is whether the answer stays accurate when the wording changes or an important detail is missing.
Sometimes the right response is a clarification. Sometimes it’s asking a person to check. A system that confidently picks one of two conflicting answers hasn’t resolved the conflict.
I’d also include at least one question the shop genuinely cannot answer from the information available. That tells you what happens at the edge of the setup, where a customer is most likely to need a little extra help.
Leave a way to flag something that looks wrong
Even after a good cleanup, information will change again.
A customer may notice an old image before anyone on the team does. A staff member may spot that a saved reply sounds wrong for a new product option.
They need somewhere easy to put that observation.
It could be a shared list with the question, the conflicting answer and the person who needs to check it. The format matters less than making sure the issue doesn’t disappear inside a private conversation.
For an unresolved question, the team should also know what they can safely say in the meantime. “I’m checking which accessories come with that version” is a reasonable reply. Guessing and hoping the parcel matches is a much harder mistake to undo.
Once the correction is made, go back to the original customer question.
Open the product page. Read the saved reply. Ask through the chat.
If all three now lead to the same useful answer, you’ve fixed something the customer can actually feel.