A bill spike, explained on Telegram before the call center opens
A utility customer asks why their bill jumped. Kav answers with the exact usage numbers from the billing system — never a figure the model made up.
"Why is my bill higher this month?" is one of the most predictable calls a utility's support line takes, and one of the hardest to answer well in a hurry — it needs two months of usage side by side, not an apology and a promise to look into it.
The same mechanism, a different organization
This is the same engine that answers a municipal property-tax balance, bound instead to a utility's own billing system and running on Telegram with an inline keyboard instead of website buttons. Nothing about the underlying capability, rule or render logic changed — only the connector and the channel did.
What the customer sees
Asked why this month is higher, the assistant answers with both months' totals and both months' usage in kilowatt-hours side by side — the actual comparison a person would have to look up manually, delivered immediately. The model chose to show a comparison rather than one number; it did not calculate or invent either figure. Both came from the billing system through a typed template, the same discipline that keeps a municipal resident's tax balance accurate to the agora.
Why the channel doesn't matter here
Telegram's inline keyboard replaces the website's buttons, but the two follow-up actions — a payment plan, or a day-by-day usage breakdown — are the same capabilities a website conversation would offer. A utility isn't maintaining two different support experiences for two different channels; it configured the capability once.
What this saves, concretely
A support agent doesn't have to open a billing dashboard to answer a question this specific. The customer gets an answer with real numbers attached before they've finished typing the question a second time to a human.