The agent said “I'll check with the team” when the answer was already in our data

The pain

Oct 13, 2026. A key customer, a UAE wholesale buyer, received our quote and wrote on WhatsApp: “tha delivery … for 3 units or for 1” (amount omitted). In other words: is that delivery price for three units or one?

The responder replied: passed to the team, we'll get back to you. The business owner saw it and asked why the agent didn't just answer. Why send it to the team? We have the quotes, we know which items, we know how many units are in the batch.

Then he set the rule: if the information is anywhere in our memory, our call prompts or the project, find it first, check that it fits the customer, and give it. Don't say “we'll get back to you.”

Why it happened

The review turned up three causes at once.

1. The facts weren't in context. The responder saw final prices but not the delivery rate, how many units are in a batch, or delivery cost per unit. It honestly didn't know.
2. A rule that was too broad. The owner handles this customer personally. A two-day-old rule said: any question with a price word gets one line, “passed on, we'll get back to you.” The delivery question fell under it.
3. A false alarm in the check. The mechanical outbound check treated delivery cost per unit as an “off-list price” and would have blocked the answer.

We covered why this hurts in Voice AI agent mistakes in B2B. This case is about how we fixed it.

What we did, step by step

1. Built logistics facts for the customer's destination. Delivery rate, how many units fit in a batch, delivery cost per unit, and what the delivery terms include. The WhatsApp responder, the voice agents' catalog tool and the call context all get these facts now.
2. Wrote down the answer order. Our data comes first: quote, logistics, price list, catalog. Then check whether it fits this customer. “I'll pass it to the team” only if nothing answers the question, along with a note on where we looked.
3. Defined which numbers are OK to share. Numbers from a quote the customer already has, plus logistics facts: yes. New prices, discounts, haggling, items not in the quote: still no. Those go to the sales rep (see the price-to-manager case).
4. Added a disclaimer. The owner asked for it: delivery costs move a lot, up or down. The disclaimer is one sentence, once per reply, and it's added mechanically, so the model can't forget it.
5. Allowed delivery cost per unit in the outbound check. Otherwise the correct answer would get blocked.
6. Facts for the owner's customers too. Fact-based answers now go to customers the owner handles personally. Price and haggling for them still go to the owner.
7. Updated the voice agent prompts. They used to say “never give a delivery figure.” Now delivery cost and units per batch are allowed, but only from the tool and with the rate's expiry date. Shipped Oct 13 at 10:40 Moscow time.
8. Audited the history. We went back 14 days: 14 “I'll pass it on / I'll check” replies in chat and 3 on calls, and all three calls were tests. In three cases, the answer was in our data. The rest really were about price and haggling, so they belonged with the sales rep.

The result

The new responder answers the same question like this: it's per unit. Delivery of a batch of 3 units costs X, so that's Y per unit, and the rate is valid until a given date. The outbound check passes it clean.

What was still open at the time of the fix:

• There's no auto-responder for email yet, so the rule covers WhatsApp and calls.
• The voice agents' knowledge base was updated later, in a separate rollout.
• Logistics facts only work while the delivery rate is valid. Once a rate expires, the agents don't get those facts until someone renews it.

How it works for Polyglot clients from day one

• The agent connects to your data: price list, quotes, logistics, catalog.
• The answer order is data first, then a “does this fit the customer” check, and only then a human.
• Every handoff includes a note on where the agent looked, so your rep doesn't start from scratch.
• Numbers with an expiry date are given with the date and a disclaimer.

Talk to us about a launch

FAQ

Isn't it risky to let the agent share numbers?

It only shares numbers the customer already has in their quote, plus logistics facts with an expiry date. New prices and haggling stay with your rep.

What if the rate is out of date?

Without a valid rate, the agent doesn't get the logistics fact. In that case it honestly passes the question to the team.

How do you know if the agent hands off too often?

We audit every “I'll check” reply over a period and see whether the answer was in the data. We do it once right after a fix and then on a regular schedule.