I walked the journey myself.
Billing and subscription was one of the top twenty drivers of a company-wide contact-reduction goal, with hundreds of thousands of contacts a year, and charge lookup was one of the highest-volume questions inside it. So I tested the real path a customer takes: chat, voice, in-product search, and Google. A $228 subscription could become $288 and no surface would say why. The supportability teams confirmed what the journey suggested: customers called for the explanation, some of those calls ended in downgrades or cancellations, and many transferred internally when a discount or refund needed a higher tier.
You can view the subscriptions charged to your account in your account settings. Go to Settings, select Billing and Subscription, and open your account history to see your subscription charges.
If you still need help, you can browse articles in our support center.
The experts already had the answer. On the phone.
I pulled phone and live-chat transcripts to learn how experts actually solved the problem: what they checked, what they explained, and what next step they offered. The transcripts were design material, not validation. The best answers the assistant could give were already being spoken on the phone, and the customer's own words told me the topic wasn't one question at all.
One billing topic is four customer questions.
The trained intent could hear "billing." The customers were asking four different things, and each deserved a different response:
The target answer needed billing APIs that were months away. The MVP didn't wait: classify the question better, stop sending customers to articles, and offer the existing lookup tool inside the assistant. The routing is a hybrid of the eras, and it's the same shape my cancellation classifier proved out: the intent platform catches the topic, a language model reads the nuance.
NLU → billing intent · the platform's intent model catches the topicLLM → question type · price increase, double charge, unknown charge, or how muchroute → response · the right answer, or the charge lookup tool offered in the channelA phased PRD, because APIs take time.
Full personalization needed billing APIs, and API onboarding is lengthy. I scoped the roadmap so the team shipped a better experience immediately and absorbed account data phase by phase, instead of waiting for the dependency to land.
Use the existing lookup tool, rewrite the offer, keep the customer in-channel.
Price increase, duplicate, unknown charge, and how-much routes.
Plan, add-ons, promo dates, charges, permissions.
Show the math; offer a safe next action when one exists.
Same question, kept in the channel.
A charge you weren't expecting is never fun. Let's find out what's behind that $288.00. The charge lookup tool shows you every charge on your statement and exactly what each one covers.
Grab your statement, enter the amount and the date, and see what makes up that $288.00, item by item.
Customers accepting the self-help the voice assistant offers to send by text or email.
Self-help resolution on billing questions in the chat assistant.
Billing questions resolved in chat without a human expert.
Billing and subscription's place among the company's contact-reduction drivers: hundreds of thousands of contacts a year.
The prototype that pointed past the platform.
The MVP kept customers in the channel. The target state answers them: read the plan, explain what changed, and offer a safe next action when one exists. I built that target as a working prototype on mock data, and this is its run, unedited in shape.
Two things changed it. You added 2 team members at $6 each, and your 6-month welcome rate finished this cycle, which had been taking $48 off your bill. Together those bring your monthly total from $228 to $288. Everything else is the same plan you already had.
The welcome rate that just ended was the largest part of this change, so I checked whether it could continue. You may qualify to extend it, and I can request that for you now.
Done. So about $240 a month while the discount holds. The extra $12 is your two new team members, and I'll email you before the rate returns in October.
The roadblock was live data, and by then the successor agentic platform had made the old platform's ending visible. The right move wasn't to fight for buy-in; we banked the MVP gains and moved the billing experience forward. The prototype's heart, account-aware charge explanation, became a working read-only agent skill with its own eval: the billing skill. Ship the useful slice, phase the product around the API reality, and know when to stop investing in a platform.