Monthly budget per site and alerts: avoiding unpleasant surprises
Monthly cap per site, alert threshold, balance alert: how to set the blabla.bot safeguards so that a sudden traffic spike does not eat into your margin.
Costs and AI models5 min read
You sold a client a fixed monthly package for their AI assistant. Everything runs smoothly for three months. Then the client launches an ad campaign, their site gets ten times more visits, and the assistant answers ten times more questions. Your package price has not moved.
Paying for AI per use works well, provided you can cap that use wherever you sell a fixed price. That is the job of blabla.bot’s monthly budget per site and its alerts. This article explains how they work and how to set them.
Two levels of protection
blabla.bot works at two levels.
- The site: a monthly budget caps what a site can spend, and an alert warns you before the cap is reached.
- The agency account: a balance alert and an estimated runway warn you before your credits run out for every site.
They complement each other. The site budget protects the margin on one client; the balance alert protects service continuity across your whole portfolio.
The monthly budget per site
How it works
For each site you can set a monthly budget in euros. It is a hard cap. The spend it counts includes the assistant’s answers and the indexing of that site’s knowledge, over the calendar month.
When a new answer would push spend over the budget, that site’s assistant stops answering. It is “paused” until the start of the next month, or until you raise the budget. Your other sites keep working normally.
By default no budget is set: the site has no cap.
What the visitor sees
During the pause, a visitor writing to the assistant sees a neutral message: the service is temporarily unavailable, please try again later. They see neither the word “budget”, nor your agency’s name, nor the platform’s. The reason for the pause only appears in your console.
A detail worth knowing
Before each answer, blabla.bot reserves the maximum possible cost of that answer. So the pause kicks in slightly before the exact budget amount: an answer is refused as soon as its maximum cost no longer fits in what remains. That is what guarantees the cap is never exceeded.
Indexing, on the other hand, is not blocked by the site budget, since you trigger it yourself. Its cost does count toward the month’s spend.
The budget alert
A pause without warning would be a bad surprise for your client. That is why each site also has an alert threshold, expressed as a percentage of the budget. It is 80% by default, and you can change it.
When the month’s spend reaches that threshold, a banner appears in the console. You then have time to decide: raise the budget, warn the client, or accept the pause.
The alert is raised once per month and per budget amount. If you raise the budget, the alert re-arms for the new amount, and any pause is lifted.
Agency-level alerts
Estimated runway
At the top of the portfolio, the console shows your balance and an estimated runway in days, based on your average consumption over the last 7 days. A “Low credits” banner appears when the runway drops below 7 days.
Balance threshold
You can also set a balance amount below which an alert appears. None is set by default. The alert re-arms with every new top-up.
Alert email address
In the alert settings you can enter a single email address for balance and budget alerts. Left empty, alerts are shown in the console only.
Setting budgets: a four-step method
- Estimate the site’s normal consumption. For a new site, start from the expected number of conversations and the estimated cost per conversation of the chosen AI option. For a site that has been live for a month, use the 30-day billed cost shown in the portfolio.
- Add headroom. A budget equal to normal consumption would pause the site at the slightest spike. Headroom of 50% to 100% above normal consumption leaves room for variation.
- Check that the budget fits within your price. The budget is your maximum loss on that site for the month. It must stay well below what you bill the client.
- Agree with the client on what happens at the cap. Accepted pause, move to a higher package, or billed overage: put it in your offer.
An example
Here is a fictional example. A site handles about 600 conversations a month on GPT-6 Luna · Simple, estimated at €0.0042 per conversation with the catalogue prices checked on 13 November 2026. Normal consumption is therefore about €2.52 a month.
| Setting | Value chosen | Reason |
|---|---|---|
| Monthly budget | €5 | About twice normal consumption |
| Alert threshold | 80% (default) | Alert at around €4 of spend |
| Price billed to the client | your choice | Must stay well above €5 |
If traffic doubles, the site stays under budget. If it grows fivefold, you are warned at 80%, then the assistant pauses at the cap, and your loss is limited to €5 for the month.
Still to come
Some settings are not offered yet: a budget at client level (all their sites together), automatic balance top-up, or several recipients for alerts. We will refine these safeguards based on feedback from agencies.
In short
Set a monthly budget on every site sold as a package, keep the alert threshold at 80% unless you have a reason not to, and watch your balance runway. Those three settings are enough to avoid most unpleasant surprises.
To estimate a site’s normal consumption before setting its budget, use the calculator on the Pricing page.
Tags
- budget
- alerts
- costs
- agencies
On the site
Read next
Costs and AI models
Working out the profitability of an AI assistant you resell to clients
Credit costs, time spent, resale price: a simple method to check whether the AI assistant you resell to your clients actually makes money for your agency.
· 5 min read
Costs and AI models
Prepaid credits or subscription: why pay as you go
Fixed subscription or prepaid credits debited per use: how the blabla.bot model works, what it brings an agency, and the precautions it calls for in practice.
· 5 min read
Agencies and white label
Managing all your clients' sites from a single console
Clients, sites, agents, statuses, consumption and budgets: how the blabla.bot console organises a multi-client portfolio, plus a weekly follow-up routine.
· 5 min read