Give every price a complete record.
A document designed for people often relies on context: a heading supplies the currency, a footnote explains tax, or a salesperson knows which customer type qualifies. An AI agent needs those conditions attached to each price so it can verify the whole offer, not only the number.
For every product, service, plan or add-on, record:
- a stable name or internal identifier;
- the exact amount and currency;
- whether tax is included, excluded or not applicable;
- the unit, billing period and quantity included;
- customer, market or channel restrictions;
- what is included and specifically excluded;
- the effective date and, where relevant, expiry date; and
- the person authorised to approve an exception.
Keep internal cost, public price and promotional price in separate fields. Similar labels make it easy to retrieve the wrong number.
Separate facts from sales wording.
The price record should be factual and reusable. Put optional explanations—such as how the plan compares or who it suits—in a different approved content field. This allows the business to change the tone without changing the commercial terms.
Apply the same rule to links. A correct price sent with an old payment or checkout link is still an unsafe answer. Maintain one approved link source, define what happens when a link cannot be matched, and verify the deployed behaviour before describing it as a guardrail.
Make exceptions explicit.
Discounts, bundles and custom work should never be inferred from old conversations. Define allowed discount ranges, who qualifies, whether items can be combined and who must approve the final amount. If there is no rule for the requested combination, the agent should describe the known options and ask a person to decide the exception.
Avoid instructions such as “use your judgement” or “offer something reasonable”. Replace them with conditions that can be checked. If the business intentionally allows negotiation, define the floor, the permitted steps and the point where owner approval is required.
Block unknown and stale numbers.
A missing match is not permission to estimate. The safe action is to pause the price answer, alert the owner and tell the customer that the amount is being confirmed. Kai currently gives its owner Telegram controls to pause the agent or take over a single conversation. That recovery control does not replace a separately configured and tested price-validation step.
Version the price source. Keep a record of when each change became active and which published pages or templates depend on it. Existing quotes should retain the terms that were actually sent; new messages should use the current approved version. Assign one owner to retire expired promotions and review links at the same time.
Test combinations, not only single prices.
Build a test set with a normal plan, quantity change, expired offer, different currency, tax question, discount request, unsupported bundle and a customer quoting an old price. For each case, verify the source record, calculation, wording, link and whether human approval was required. Repeat these tests after every pricing change.
The Kai roles page is the current public source for Kai’s available plans and included volumes. For the wider operating controls, see current capabilities and the operating profile. Pair pricing rules with customer escalation rules and a tested brand voice guide.