An AI support assistant that reads the account before it writes
Open a ticket, ask for a draft. The assistant reads the conversation, the customer’s services and invoices, how similar tickets were solved and your help articles, then writes a reply in the customer’s language — and, when the answer is an upgrade or a refund, prepares it for you to approve. Nothing is sent and nothing changes until a person says so.
- The conversationEvery message on the ticket, with internal staff notes labelled as notes so they inform the draft without being quoted.
- The customer’s accountTheir services and account balance, and the ways they can pay — only what the staff member asking is allowed to see.
- Invoices and proformasAny document the ticket names by number: lines, VAT, discounts and every payment attempt with its failure message.
- Similar past ticketsHow problems like this one were solved before. Used for the fix, never for names or details, which belong to other customers.
- Help articlesYour own knowledge-base articles that match the question.
When the first read is not enough, it looks things up
With Claude or ChatGPT the assistant calls tools while it writes, and the draft comes back with the sources it used, so you can check a figure before you send it.
It prepares the upgrade or the refund. You decide.
When the right answer to a ticket is a change to the account, the draft arrives with the change ready: the quote, and a plain list of what will happen when you approve. Approving runs it through the same admin endpoints as your own buttons, one step at a time, and stops at the first step that fails — showing what already went through.
It refuses what it cannot plan safely, such as a partial refund on a gateway that only refunds whole payments. A team member without billing permissions gets no billing actions at all.
- UpgradeOrders the next plan on the service’s upgrade path, priced exactly as the upgrade page would price it.
- DowngradeMoves the service to a cheaper plan. Crediting the unused time is a separate step staff tick themselves.
- Option changeAdds or changes a configurable option, such as extra IPs or RAM, with the quote.
- Billing-cycle changeMonthly to annual or back, with the new price.
- RefundBack to the card or to the account balance — including one payment of an invoice that was paid twice.
Like an engineer typing a quick, helpful reply
In the customer’s language, opening with their first name, straight to the point. It answers every question they asked, in their order, and only states facts it found — prices exactly as the catalogue gives them, never a guessed date, limit or IP address.
Plain text with numbered steps, no “I hope this finds you well”, and no sign-off — your staff signature is added as usual.
Or tidy up the reply you wrote yourself
Write the answer your way and ask for a refine: grammar, tone and clarity in the same house style, with an optional instruction such as “shorter” or “more formal”. Drafts take an instruction too, so you can point the assistant at the answer you already have in mind.
What it will not do
What the model may see is decided before it sees anything — by permission checks and redaction in the platform, with the rules in the prompt as a second line, not the first.
- Send a reply. It writes a draft; a person sends it.
- Change an account on its own. A prepared upgrade or refund does nothing until staff approve it.
- Quote internal notes, name servers, suppliers or costs, or mention other customers.
- Confirm anything about an account to a sender who is not the verified customer.
- Ask for, confirm or send a password, a card number or a secret.
- Follow instructions written inside a ticket. Ticket text is the customer’s request, not a command.
Your key, your model, no AI surcharge
Claude and ChatGPT are built in. Paste your Anthropic or OpenAI API key in Settings, pick the model from the list your provider offers, and the assistant is on — on every tier, with no charge from FluxBilling. Your provider bills the usage to your key.
Any other provider can be connected as an AI-provider plugin in the visual plugin builder. A plugin provider gets everything gathered up front in one prompt; the tool-calling research above needs Claude or ChatGPT.
The same key drafts your blog posts
Give it a topic and it drafts a post for your storefront blog with proper headings, plus the excerpt, meta title, meta description and keywords. For a post you wrote yourself, it fills in just the SEO fields. Everything opens in the editor as a draft for you to publish.
The AI support assistant, answered
- What does the AI support assistant do?
- It drafts replies to support tickets after reading the ticket, the customer’s account, any invoice the ticket mentions, similar past tickets and your help articles. It can also prepare an upgrade, downgrade, option change, billing-cycle change or refund for a staff member to approve. Staff can ask it to refine a draft they wrote themselves.
- Does it answer customers on its own?
- No. Every draft lands in the reply box for a person to read, edit and send, and a prepared billing action only runs when a staff member approves it. There is no customer-facing chatbot.
- Which AI models does it use?
- Claude from Anthropic or ChatGPT from OpenAI, built in — you paste your own API key in Settings and pick the model from the list your provider offers. Any other provider can be connected as an AI-provider plugin in the visual plugin builder.
- What does it cost?
- FluxBilling does not charge for the assistant, and it is on every tier. Usage is billed by the AI provider to the key you supply.
- What data does the AI provider see?
- The ticket and the account facts the reply needs, gathered under the same permissions as the staff member asking — a team member without billing access gets a draft without billing data. It goes to the provider you chose, under your own agreement with them.
- Which languages does it reply in?
- The language of the customer’s latest message.
The records the assistant reads
- BillingInvoices, proformas, refunds and upgrades — the actions the assistant prepares.
- Reseller programWholesale prices and tiers the assistant can quote to your resellers.
- Visual plugin builderWhere a different AI provider is connected as a plugin.
- Built-in ticketing and retentionWhy support that sits next to billing keeps customers.
- Fewer tickets to begin withThe self-service portal that answers questions before they are asked.
- PricingThe assistant is on every tier, from Lite to Business.
Try it on your own data. Refund inside 14 days if it’s not the fit.
Pick a tier and provision a tenant in under two minutes — isolated K3s namespace, your own database, the full product. If FluxBilling isn’t the right fit inside 14 days, open a ticket and we’ll refund the subscription. No sales call, no qualification gate. Want to look around first? The live demo opens the admin and client panels with sample data, no signup.
- 01.< 1 minPick a tierLite from €4.95/mo. Upgrade later, no migration.
- 02.< 2 minProvision the tenantIsolated K3s namespace + your own PostgreSQL database. Full product, your data.
- 03.d0 — d14Refund inside 14 daysNot the fit? Open a ticket within 14 days and we refund the subscription. No questions, no qualification gate.