SaaS teams index the pricing page first, naturally, and wonder why the bot fumbles billing. The pricing page describes plans; it rarely describes mechanics. Visitors ask what happens when they add a seat mid-cycle, whether tax is included, how to get a PDF invoice for accounting, or if downgrade takes effect immediately. Those answers live in billing FAQ, Stripe emails, or nowhere.
Nowhere is where models get creative. Fluent billing answers without citations are liabilities — finance discovers them when credits get issued to undo a confident wrong proration explanation.
The gap list your pricing page hides
Pull fifty billing tickets. The topics repeat even when plans differ.
- Proration on upgrade, downgrade, and mid-cycle seat changes.
- Trial conversion — when card charges, how to cancel before.
- Invoices and receipts — VAT fields, company name, resend link.
- Failed payments — grace period, feature lock, dunning emails.
- Annual versus monthly — refunds, switches, contract terms.
- Tax — included or added, which countries, exemption process.
- Enterprise quotes versus self-serve — who to contact, SLAs.
Write a billing FAQ finance will sign
One “Billing & subscriptions” help section beats scattered Notion. Finance or ops reviews it quarterly. Each answer states effective behaviour (“downgrades apply at next renewal”), not vibes. Link to the pricing page for plan names; keep numbers about money on the billing FAQ.
If behaviour differs by plan tier, say so explicitly. Tables with plan × scenario reduce paraphrase error. Avoid “contact sales” as the only cell for questions self-serve customers ask weekly.
Include screenshots or deep links to the billing portal where actions happen — “Update payment method here” with the path described in words the bot can cite. Reducing portal hunting is often worth more than clever paraphrase.
Usage-based and metered billing
Metered products break FAQ templates built for seat-based SaaS. If overage bills automatically, say when and how credits apply. If usage resets monthly, say the timezone. Billing bots that guess meter semantics cause the invoices finance has to credit — and the tweets marketing has to ignore.
Seat math and add-on products
Pricing pages list plans; they rarely explain how seats stack when someone owns two products, or when a guest vs member counts toward a limit. If your product has seat semantics, write a paragraph support can quote verbatim. Bots that invent seat rules create sales calls that should have been a FAQ sentence.
What the bot should never guess
Custom enterprise contracts, tax exemption approvals, chargebacks, and refund exceptions belong in human queues, or forms with account context. Hard refusal beats improvising credit. Align with when a contact form should stay: billing disputes with attachments are form-shaped work.
Keep numbers in sync with the system of record
Docs drift from Stripe or Chargebee settings silently. When you change dunning, trial length, or currency support, update the FAQ in the same deploy, and recrawl. Playground-test: “What happens if my card fails?” should cite the paragraph that matches your live dunning config, not last year’s Notion export.
Measure billing automation honestly
Billing deflection without citation clicks is suspicious. Track how many billing chats end with opened invoice links, successful self-serve portal paths, or clean escalations with account ID. A “resolved” chat that invents proration creates work in finance, not savings in support.
“The pricing page closes deals. The billing FAQ keeps them.”
Trials, coupons, and legacy plans
Grandfathered pricing and expired coupons live in billing systems, not on marketing pages. If support still honours them, document the rules support uses — even if the doc is internal-first and crawl-excluded for the public bot. For public answers, state what new customers get and defer legacy exceptions to a form.
Finance teams forgive bots that escalate with account context. They do not forgive bots that state net terms incorrectly on month-end close week.
SaaS bots fail billing for boring reasons: the answers were never published, or they were published once in sales copy. Index billing operations on purpose, refuse what contracts individualise, and treat every money answer like it will be forwarded to accounting — because it will.
