Unpaid invoice lookup
Usually asked by a CS rep mid-conversation.
How much does this customer still owe us? Do they have any open invoices?
Your billing record already holds what your team needs: renewal dates, churn signals, unpaid balances, ARR by cohort. Point an AI client at it through the MCP server and query it directly. Finance, CS, RevOps, and product all ask, no dashboard required.
The data that decides what to do is already on the record: every invoice's payments and terms, every subscription's plan and add-ons, every cancellation's reason. The signal was always there. What was missing was a fast way to ask for it.
Connect an AI client through the Model Context Protocol and that history becomes queryable in plain English. One question reads the records, runs the math, and ranks the answer.
No SQL. No export. No analyst in the loop.
Each prompt on this page is a starting point. Connect Chargebee through MCP and the same questions build something you can operate from. A live finance copilot, a risk-ranked collections brief, a nine-quarter ARR cube, a churn model fitted to your own book.
| Quarter | ARR | QoQ | NRR |
|---|---|---|---|
| Q1 2024 | $248.1M | — | 106.2% |
| Q2 2024 | $271.4M | +9.4% | 108.1% |
| Q3 2024 | $293.7M | +8.2% | 110.4% |
| Q4 2024 | $322.0M | +9.6% | 112.3% |
| Q1 2025 | $362.4M | +12.5% | 114.1% |
| Q2 2025 | $398.7M | +10.0% | 115.8% |
One prompt. One table. Every customer’s ARR over time.
A health score learned from your own churn, not a generic rule.
One question. A collections call list ordered by risk, not size.
One question. A complete board packet (ARR, NRR, churn, and cohorts) pulled from live data.
Each recipe below is a natural-language prompt you can paste into Claude, Cursor, ChatGPT, Codex, Claude Code, or Notion AI with the Chargebee MCP server connected. Grouped by pain area, with the team that usually asks and the question in plain language.
Usually asked by a CS rep mid-conversation.
How much does this customer still owe us? Do they have any open invoices?
Usually asked by whoever owns Collections.
Show me all payment failures in the last 60 days. Group by failure type and flag repeat offenders.
Usually asked by the team working dunning.
Which accounts are currently in dunning? Which are most likely to recover vs. likely lost?
Usually asked by Finance watching cash flow.
How long does this customer take to pay each invoice?
Usually asked by whoever is saving failed payments.
Which customers have a failed payment but are still technically active, so I can intervene before they auto-cancel?
Usually asked by a RevOps lead building a save list.
Pull all subscriptions marked non-renewing in the last 30 days. Rank them by ARR at risk.
Usually asked by a CFO digging into churn.
How much of our churn was preventable, triggered by payment failure, vs. customers who chose to leave?
Usually asked by RevOps before QBRs.
Which enterprise customers renewing in the next 90 days have billing problems?
Usually asked by a CFO testing a hunch.
Do 2+ payment failures predict churn? Show me the chain.
Usually asked by Sales planning win-backs.
Which churned customers in the last 6 months had the highest LTV?
Usually asked by Finance chasing missed credits.
Which annual-plan customers downgraded mid-cycle but never received a prorated credit note?
Usually asked by Finance closing the books.
Show me all credit notes issued in Q1 and Q2. Group by reason. Flag anything above $5,000 and flag customers who received more than one.
Usually asked by Finance sizing discount exposure.
Which customers are on heavy discounts? What does revenue look like if those coupons expire?
Usually asked by CS spotting upsell moments.
Which customers' promotional pricing ends in the next 60 days?
Usually asked by a CFO sizing risk.
What percentage of our MRR is in annual contracts vs. exposed to monthly churn?
Usually asked by Finance prepping the board.
Is our add-on revenue dangerously concentrated in a small number of customers?
Usually asked by a Support rep on a ticket.
A customer is disputing the tax on their invoice. Can you pull the details so I can respond?
Usually asked by a CS rep prepping a renewal.
Give me the full picture on Pulseboard: plan, add-ons, last payment, any failures, credits outstanding.
Usually asked by Support on a feature access request.
A support ticket is asking for access to a feature. Is the customer already entitled to it on their subscription?
Usually asked by a CS rep before a call.
I'm about to call this customer. What is their full billing history and net LTV?
Usually asked by a CS rep before emailing.
Before I email this customer, what has already happened on their account this week?
Usually asked by CS watching for abuse.
Which customers keep pausing during low-usage months to effectively get free time?
Usually asked by Finance and Product reviewing a launch.
We launched two new plans 90 days ago. How many customers are on each? What's the revenue and churn rate per plan?
Usually asked by a Growth PM watching trials.
Show me all trials that started in April. How many converted? How many dropped off?
Usually asked by Product and RevOps.
Which plans are natural upsell vehicles? Which are dead ends for add-on revenue?
Usually asked by a Product manager.
How many subscription changes happened in the last 90 days and what drove them?
Revenue Analytics. One prompt. One table. Every customer’s ARR over time.
Customer Health. A health score learned from your own churn, not a generic rule.
Collections Intelligence. One question. A collections call list ordered by risk, not size.
Finance Intelligence. One question. A complete board packet (ARR, NRR, churn, and cohorts) pulled from live data.
Reads every object in your Chargebee account live (subscriptions, invoices, payments, usage, and events) in response to a plain-English question.
Answer from your docs, API specs, and how-tos, grounded in Chargebee's own product knowledge.
Stand up the product catalog and billing setup conversationally, guided, not manual.
Lives inside your Chargebee dashboard. Ask billing questions, surface churn signals, and run revenue lookups without opening another tool.
Log in to Chargebee Billing. Go to Settings → Agentic AI → MCP Servers. Select the server you need and open its configuration page.
Under Access & Authentication → MCP Access, find your server URL. The format depends on your data center:
Replace data_lookup_agent with knowledge_base_agent or
onboarding_agent depending on which server you connect.
For the Data Access and Onboarding servers, choose how your AI client authenticates:
The Knowledge Base server needs no authentication. It accesses public information only.
Use the configuration snippets from your server's Access & Authentication tab. Examples:
For API Key auth, add your key to the env block or Authorization header as shown in the
Chargebee dashboard.
Connect the Chargebee MCP server to Claude, Cursor, ChatGPT, or Codex, and run your revenue operations.