When two people answer the same customer differently
When two people answer the same customer differently, the customer does not hear two colleagues with two opinions. They hear one business that does not know its own facts. Sales QA, the practice of reviewing Instagram, Facebook, and WhatsApp conversations after they happen, finds these threads in the pile that looks healthy: fast, friendly, fully answered, and dead.
Nothing was slow. Nothing went unanswered. This is the opposite of the better known failure, where a thread everyone can see is one nobody picks up: that is the handoff problem, and it has its own fix. Here everybody answered. Promptly. Twice.
What does a customer do when they get two different answers?
They go quiet. A customer holding two prices, two dates, or two refund policies has a job they did not ask for: working out which of you to believe. They cannot, and the cheapest way out is to stop replying.
Composed example. Rosa Delgado asks a four person moving company on Instagram about the deposit on Monday, then again on Thursday, ready to commit.
| What Rosa read, in order | What she could reasonably conclude | What was actually true |
|---|---|---|
| Monday: the deposit holds your date and comes back if you cancel a week out. | She can change her mind within reason. | Jonah Reyes repeated an exception the owner had granted twice, in his hearing. |
| Thursday: the deposit is not refundable once a van is held. | A condition appeared the moment she said yes. | Priya Raman quoted the written terms, which are current and correct. |
| Nothing more from Rosa. | The terms depend on who is typing. | Neither was careless, and the only person asked to reconcile them was her. |
Why is this a trust failure with a logistics cause?
Because the damage is not the wrong answer, it is what the customer concludes from holding two. One wrong answer plus a correction still closes. Two live answers tell her nobody here is keeping track, and that spreads to the price, the timeline, and whatever you said was included.
Which is why it survives teams who are lovely to customers: warmth is not the variable. You will also rarely hear about it, because nobody writes in to say they left over a contradiction. And there is no honest number: nothing this blog will cite measures how often teams contradict each other.
Why is answering two ways almost never carelessness?
Because people answer from what they are holding in their head, and the facts answered two ways are the ones that live nowhere else. Not your standard prices, those are on the website. The exceptions.
A yes given once, by somebody entitled to give it, gets remembered as the rule. And some facts move faster than anyone can write them down: two people can answer availability correctly nine minutes apart and still contradict each other.
Which facts get answered two ways, and where do they live now?
Nearly always the same handful: money, dates, and promises. Here is the home each one has today, which in half the cases is nobody's.
| The fact | Where it lives now | A ten second check |
|---|---|---|
| What is genuinely free this week | The calendar, if whoever replies opens it | Open it, and offer a slot as open now rather than as held |
| A price or discount somebody agreed to once | The memory of whoever agreed to it | A short list of the live exceptions, each with an end date |
| Whether the deposit is refundable | Everybody's recollection of one conversation | The sentence itself, written once and copied verbatim |
| What this customer was already promised | Further up the same thread | Scroll up before answering anyone who has written before |
Two of those are habits, not documents: open the calendar, scroll up. Ten seconds is the real specification, because a fact that takes two minutes to look up gets answered from memory instead.
Why will a process document not fix this?
Because nobody reads a document in the middle of a thread with a customer waiting. What survives a busy Tuesday is narrower: take the few facts your team genuinely answers differently and give those one home anybody can check in ten seconds. Not a wiki, not training, not a product to buy. A pinned message in the chat you already use, or one page in the notes app everyone has. You do not need to buy anything.
- One screen, one place, facts only. Prices, terms, lead times, the live exceptions, each with its date. No advice, no scripts, and no second copy.
- One person edits it, and the edit is the announcement. A price that changed only in a conversation has not changed.
- Everything else goes back to the thread. If a fact is not on the list, reading the conversation is part of replying.
Write each fact in the words you want sent, then stop. Resist writing the other forty.
Perfect consistency is not the goal. Two people describing your service in different words is part of why a customer messages a person at all. The target is the few facts where a second answer loses somebody who was ready to pay.
How do you find which facts your team answers two ways?
Search last month's threads for the customer's confusion rather than for your own answers. Most teams cannot name the facts they contradict themselves on. Their customers already flagged them.
- Search the phrases confusion arrives in. Someone said, I was told, I thought it was, so which is it. Every hit is a thread where the customer did your reconciling for you.
- Put your own answers to one question side by side and count the versions your side sent. Two is normal. Four is a finding.
Then mind the wording, because a contradiction finding names two people by definition. We answered the deposit question four ways last month is a finding. Jonah told her wrong is a verdict, and also false: he repeated something the owner had genuinely agreed to, twice. There is a fuller set of rules for wording a finding.
What do you say to the customer who already has both answers?
Name the difference, give the answer that stands, and end with something she can accept today, in one message from one person.
You have had two different answers from us on the deposit, and that is ours to sort out, not yours. The written terms are the ones that stand: the deposit holds your date and is not refundable. Because you were told otherwise on Monday, we will refund it in full if you cancel within the week. Saturday the 18th is still yours, shall I confirm it?
Note what is missing: who was wrong, how your terms came to live in two places, and the word sorry four times. Where two answers differ on money, honor the better one once and say you are doing it. Decide that before you type: let me check and come back to you becomes a third answer the moment you go quiet.
Three repairs leave her holding the contradiction. Answering only her newest question teaches her she misread something. Sending the right answer as though the first had never been given teaches her that answers depend on when you ask. And making your teammate wrong in front of her, sorry, whoever told you that is new, costs you twice: she trusts nothing that is not in writing, and your teammate stops answering without checking.
What Reploom does here, and what it does not
Reploom is AI Sales QA for social conversations. It reviews Instagram, Facebook, and WhatsApp messages, comments, and mentions after they happen and reports repeated gaps as named patterns with the conversations as evidence. It does not draft, send, suggest, queue, or approve replies, and it is not an inbox or a chatbot.
Be plain about the limits here. Reploom does not compare answers across threads, does not detect contradictions, does not keep a source of truth for your prices or availability, and does not flag when two of you disagree. None of its patterns is two people said different things: a contradiction thread lands in whichever pattern caught it, if one did, and nothing on the card says the answers disagreed. A person reading the thread is what spots the difference. On WhatsApp, monitoring starts at connection, so a review reaches only as far back as available history.
In the example Sales QA report on the homepage, a sample week shows 420 conversations checked, 96 potential buyers, and 7 sales opportunities stalled. Example data from one account, not research. A thread that died between two answers sits inside a count like that with no label of its own.
Pick one fact this week, the deposit or what is free on your busiest day, count the versions your own side sent last month, and write the current one down with its date. Book a Demo to see which of your conversations stopped after an answer.