What did your rep promise the customer on WhatsApp?

A customer asks for a better price, and your rep, wanting the sale, types “I can do 15% off if you confirm today.” It is a reasonable thing to say in the moment, and it is also a commitment your business now owns. It was made in the WhatsApp Business app on a company phone, and it is written down nowhere else you can see.

Most of the time the promise is kept. This post is about the other times: how to find a promise later, how to catch it while it is due, and why the same record protects your reps as often as your margin.

The promises that cost money

Not every promise is a problem. The ones worth your attention have a price attached, and they share a pattern: made quickly, in writing, to close a sale, and found weeks later by someone who was not in the chat.

Each one is cheap when it is typed and expensive when it surfaces. The argument afterwards, between a customer who remembers a number and a rep who does not, usually costs more than the promise did.

Why your CRM rarely has them

A CRM records what a rep decides to log, after the conversation. The deal moves to “verbal yes”, while the 15% that got it there and the free fitting stay in the chat. That is not reps hiding anything: at the end of a long day, the details that cost money feel too small to type twice.

A tool that syncs chats into the CRM helps only with what it syncs, and anyone with CRM permissions can edit its records: does syncing WhatsApp to your CRM create a record covers why. The reliable copy of a promise is the message itself, on the company phone that sent it.

How to find a promise after the fact

A customer writes in to say your rep offered 15% off, or a deal file does not add up. Either way you need the message, and the phone is a poor place to look: an edited price shows only its new figure, and a deleted one reads “This message was deleted”.

If each company-owned number is linked to WAOversight, every message on it is captured as it is delivered, into an archive nobody can edit. A single search runs across every linked number, and you can narrow it to a rep, a date range, the messages the rep sent, or only those deleted or edited. It reads the text a message was first sent with, not just what it says now, so a price edited down or an offer deleted for everyone still turns up with its times.

The messages your team deleted shows how each one appears in the conversation, with the original in place. Every search is written to the access log before any result appears, and if that row cannot be written, the results are not shown. Your workspace owner and any auditor they appoint can read the log, and nobody can edit it.

What that looks like

Here is a thread from our demonstration workspace, Hudson Cotton Co., with sample figures rather than a customer’s. Laura orders an $89 dress and asks for a discount, and at 14:32 Chris offers 30% off, $62.30, then deletes it 4 minutes later. At 14:37 he sends “Would $84 work?” and edits it twice, to $79, which Laura accepts.

Chris’s phone now shows 1 deleted message and 1 price marked edited. The archive shows all 3 prices in order with their times, and a search for $84 finds the edited message though it now reads $79. If Laura later says she was promised $62.30, you can see that it was offered, when, and that it was withdrawn before she agreed to $79.

If Chris leaves, the thread stays with the company number, and when a rep leaves the promises they made in writing are part of what you can see they left open.

How to catch a promise before the customer chases it

Finding a promise while it is still due is better than finding it after the complaint, because then the fix is a call rather than a refund. There are 3 ways to be told.

Nora reads the thread

Nora, the AI that watches your queue, reads a customer’s thread when something may need you, including when a rep’s message sounds like a promise. It lists the promise with the rep’s words quoted, marks it due soon, then overdue if the date passes with nothing in the thread to show it was kept. When a later message shows it was kept, Nora closes the item and records why.

In the demonstration workspace, Chris’s “Shipping in 2 days” is a line in the queue marked due Friday, with his message quoted above the reason. Marcus’s “Let me check with the warehouse and get back to you today” is marked overdue, because Monday passed and nothing followed.

Nora reads customer threads only: the ones your CRM matches, and any contact you mark as a customer. Nothing is read until the workspace owner switches it on, and every reading is written to the access log first. It does not listen to calls, so a promise kept by phone or in person can show as overdue until someone resolves it.

A deadline rule for routine promises

Some promises are routine: a figure after a price question, a brochure after “I will send”. A deadline rule turns one into a clock: you say what starts it, what should follow and how long it may take, and the rule reports how often it was met on time. SLA tracking shows the rules teams write.

A threshold for discounts

A detection rule flags any discount above a threshold you choose, as soon as the message is captured, so you hear about it on the day it was offered rather than at the end of the month. Set it at the discount you would have wanted a phone call about.

None of the 3 sends anything. Each puts a line in your queue, and the WhatsApp daily sales report lists what is open each morning without quoting a message.

The record works in both directions

A customer says your rep promised free delivery, and the rep says they never did. Without the thread you have 2 memories and a customer ready to leave, and the cheapest way out is to give in. With it, you read what was said with the time beside it, and if the line is not there, the rep was right and you can say so.

That only works because nobody can tidy the record. The archive is append-only, so neither a rep nor a manager can change what it kept, and every look a manager takes is logged. What a deleted message actually costs you makes the same point about deletions.

Your team is told before any number is linked: which numbers, what is kept and who can look. The link is visible on each phone under Linked devices. Here is the page we wrote for your reps.

What to do this week

1. Tell the team, then link the company numbers. Capture starts at the link, and linking is one QR scan per number from the company phone, about a minute each.
2. Choose the promises you want to hear about: a discount threshold and 2 or 3 deadline rules.
3. Read open promises as a list of customers. An overdue promise is a customer who needs a call today, not a rep who needs a meeting.

What this does not do

Little history before the link. Capture starts when a number is linked, so history from before that day is limited, and a promise edited or deleted before it is gone for good.

No personal phones or personal numbers. It covers the company-owned numbers you link and nothing else.

Nothing sent to customers. WAOversight never messages a customer, so a promise is always kept by the rep, from the phone.

No messages in your CRM or your inbox. It does not put messages into your CRM, and no email quotes one. Reading a message means signing in, and the read is logged.

No verdict on intent. A promise in the record is a fact about what was said, not a judgement on why. Nora rates conversations, never people.

Not a shared inbox. If you want reps replying from 1 screen together, that is a different tool, and the comparison of a shared inbox or a management view sets out which one you need.

FAQ

How do I find out what discount my rep offered a customer on WhatsApp?

Search the conversation. On the WhatsApp Business app that means scrolling the company phone, which shows an edited offer only as its new text and a deleted one not at all. With each company-owned number linked to WAOversight, a single search covers every number and finds the original wording with its times, though history from before the link is limited.

Can I see a price my rep edited after sending it?

Not on the phone, which shows only the new text, marked edited, and WhatsApp allows an edit for 15 minutes after sending. On a linked number, the archive keeps the current text and every earlier version, and search finds the original wording.

Can AI tell me which promises are overdue?

Yes, if the workspace owner switches on Nora. It reads customer threads when a rep’s message sounds like a promise, quotes it, marks the promise due soon or overdue, and closes it once the thread shows it was kept. A promise kept by phone or in person can show as overdue until someone resolves it.

Does WAOversight put promises into our CRM?

No. The promise stays in the archive, where nobody can edit it, and reading it means signing in, which writes a row to the access log.

Will my reps know their promises are on the record?

They should, because you tell them before a number is linked, and the link shows on the phone under Linked devices. The record protects them too: when a customer claims a discount that was never offered, the thread shows what was actually said.