Connect Claude and ChatGPT to Your Billing Platform

How much of your week goes on pulling numbers out of your billing system? A report here, an export there, a spreadsheet to answer one question in a Friday meeting. It adds up.

We are about to remove most of that work. SAFE is gaining a built-in MCP server, which means the AI assistant you already use, such as Claude or ChatGPT, can connect straight to your live billing data. You ask a question in plain English. It answers from the real figures.

Key Takeaways

• SAFE will include a first-party MCP server, so Claude and ChatGPT can connect directly to your billing data
• You can ask for revenue, collections, aged debt, growth, and individual customer records in plain English
• Write access is off by default, and the assistant confirms significant actions with you first
• Every connection uses your own login, your own permissions, and two-factor approval
• Launching soon: contact us for early access

Key terms in this article

What does MCP mean?

MCP (Model Context Protocol) is an open standard that lets AI assistants connect to other software in a controlled way. SAFE’s MCP server gives assistants a structured, permission-checked route into your billing data, rather than screen-scraping or spreadsheet exports.

What is an AI assistant?

An AI (artificial intelligence) assistant is a chat-based tool, such as Claude or ChatGPT, that understands plain-English requests and can use connected systems to answer them. For a telecoms reseller, that means asking billing questions and getting answers from live data.

What does OAuth mean?

OAuth (open authorisation) is the standard way modern web apps grant each other access without sharing passwords. SAFE’s AI connections use OAuth 2.1, so your assistant receives a short-lived token and your login details never leave the platform.

What does KPI mean?

KPI (key performance indicator) is a headline measure of how the business is doing, such as monthly invoiced revenue or failed Direct Debit collections. SAFE’s assistant connection can report KPIs grouped by month, quarter, dealer, or payment method.

What Does the AI Assistant Connection Do?

It turns questions into answers. Instead of building a report, you type what you want to know:

• “What did we invoice each month this year, broken down by dealer?”
• “How much did we collect by Direct Debit last month, and how much failed?”
• “Show me aged debt in 30, 60 and 90 day buckets.”
• “What were my ten largest invoices last month?”
• “How many customers did we add this quarter, and how many did we lose?”

The assistant queries the same live data your billing runs use. No exports, no stale copies, no waiting until someone has time to build the report.

It goes beyond headline figures too. Describe a customer by name, account number, postcode, or phone number, and the assistant finds them. From there it can pull their invoices, payments, numbers, and services. That is handy when a customer is on the phone and you need their story in front of you now.

Can It Actually Do Things, or Just Report?

Both, and you choose which. Read access and write access are separate permissions, and write access is off by default.

If you do grant write access, the assistant works through the platform’s own vetted workflows rather than editing raw data. It can:

• Email an invoice to a customer, with a covering note you approve
• Generate a secure payment link for outstanding invoices
• Suspend or reinstate billing on a number
• Raise a refund through the official refund workflow

For significant steps, such as write-offs, refunds, and account changes, the assistant is required to confirm with you before it acts. You stay in charge; it does the legwork.

How Is This Different From the API?

The REST API is for developers. It is the right tool when you want two systems talking to each other on a schedule, such as syncing invoices to your accounting package.

The MCP connection is for people. There is no code, no endpoints, and nothing to build. You connect your assistant once, then ask questions as they occur to you. Both routes run on the same permission model underneath, so nothing is exposed through MCP that the API would refuse.

The Model Context Protocol itself is an open standard, now supported by the major AI assistants. That is why one SAFE feature covers Claude, ChatGPT, and whatever comes next, rather than needing a separate plugin for each.

Is It Safe to Let an AI Near Billing Data?

We treat an AI connection with the same seriousness as an API key, because it carries similar power. The security model is built in from the start:

• Your login, your rules. Each person approves their own connection with their normal login plus a two-factor code. The assistant can never see or do more than the person behind it.
• You choose what it can do. Reporting KPIs, reading records, and making changes are three separate permissions. Tick only what you want. Changes stay off unless you say otherwise.
• Modern sign-in. Connections use OAuth 2.1 with short-lived tokens. There are no API keys to paste into a chat window, lose, or leak.
• A full audit trail. Every query and action is logged and marked as assistant activity. You can always see what was asked and what was done.
• Off switches at every level. Anyone can revoke their own connection at any time. An admin can turn off read or write access for the whole platform in one step.

We think this matters more than the novelty. Anyone can bolt a chatbot onto a product. Doing it so that a billing team can trust it is the real work, and it is where we have spent our time.

When Can I Use It?

Soon. The feature is in final testing now, covering both the Claude and ChatGPT connection paths.

If you would like to be among the first, register your interest and we will be in touch as early access opens. There is nothing to install: once it is enabled for your platform, connecting takes a few minutes from your assistant’s connector settings.

For the full picture of what the connection can do, see the AI Assistants integration page. If you are weighing it against a code-based integration, the API access page covers that route.

Your billing data already holds the answers. Now you will be able to just ask.