What happens when the token reservoir is empty?

On ABYS, each account has a token reservoir for the month. This reservoir powers all your agents, whether you have one, two, or five. When it empties, the agents stop. This is neither a malfunction nor a bug: it's an intended mechanism, with alerts and solutions. Understanding how this works allows you to anticipate and never be caught off guard.

IHow does the token tank work?

The tank is capped according to your plan. With the "Once a week" plan at €19 excl. VAT per month, you have 100,000 tokens. With "Every day" at €59 excl. VAT, you move up to 400,000 tokens. Higher plans offer 1.5 million then 5 million tokens. Each task completed by an agent consumes part of this stock. A follow-up email might cost a few hundred tokens, a longer report several thousand.

The essential point: all your agents share the same tank. An agent drafting quotes and another following up on unpaid invoices draw from the same pool. If one consumes a lot, less remains for the others. This pooling simplifies management, but requires monitoring overall consumption.

IIThe first signal: the 80% alert

When your tank reaches four-fifths of its capacity, ABYS sends you an email. This message tells you how many tokens remain and invites you to monitor what happens next. This is the time to assess whether your consumption rate will last until the end of the month or not. For an "Every day" account with 400,000 tokens, the alert arrives when 80,000 remain.

IIIWhat happens when the token quota is exceeded?

When the tank reaches zero, all agents on the account stop automatically. They don't disappear: they pause. You receive a notification explaining the situation. The agents can no longer read incoming emails, draft, or send anything. They wait, like a car at a standstill for lack of fuel.

This stoppage is immediate but not abrupt. Tasks in progress are completed if tokens are sufficient. If an agent was drafting an email and the tank empties, the email doesn't go out halfway: either it is completed and sent, or it is put on hold. No incomplete message is sent to your contacts.

IVNumerical example: three agents on an "Every day" account

Let's take an account at 59 euros excl. VAT per month, which is 400,000 tokens. Three agents are working: one for quotes, one for payment reminders, one for answering frequently asked questions. Each agent consumes an average of 4,000 tokens per day. With three agents, that's 12,000 tokens daily. Over a 30-day month, total consumption reaches 360,000 tokens. This leaves a margin of 40,000 tokens.

But if one of the agents handles a complex file, with long documents to analyze, their consumption can double over a few days. Suddenly, the account reaches 80% as early as the 20th of the month. The alert arrives. If nothing changes, the tank empties around the 25th, and all three agents stop together.

VThe two solutions when the reservoir is empty

There is no one-time token recharge without changing your plan. The system is designed to be simple: one plan, one tank, one pace. If you need more, you upgrade to the next tier. If the following month is quieter, you can downgrade.

VIHow to anticipate to never run out?

A craftsperson using a single agent for quotes will consume far less than a firm running four agents in parallel. The right plan is one that matches your actual usage, not your ambitions on day one. Starting with "Once a week" and scaling up later is often wiser than aiming too high from the start.

VIIWhat the stoppage does not change

When your agents stop, your data remains intact. The documents you provided, the configured tasks, the conversation histories: everything is preserved. The stoppage is a pause, not a deletion. As soon as the tank refills, each agent resumes exactly where it left off, with the same configuration.