One Message Quota Across Messenger, Instagram, WhatsApp, Telegram, Web

A shared message quota means you buy one pool of messages and spend it across every channel your bot runs on, rather than paying a separate fee for each platform. aiSTAFF works this way: one subscription, one quota, used by Messenger, Instagram, WhatsApp, Telegram, the website widget, and the API together.

TL;DR: aiSTAFF charges one subscription with one shared message quota across all channels and the API. Adding a channel spreads your existing volume instead of multiplying the bill, and the bot count is one plan-gated pool too.

This sounds like a billing detail, but it changes how you plan a rollout. With most stacks, every channel is its own line item, so going from one channel to three triples the cost before a single extra customer arrives. With a shared quota, you size the plan to your real conversation volume once, and where those conversations happen stops mattering to the invoice. To get this set up under one plan rather than four, our pricing page lays out the tiers, and our team scopes the plan to your actual traffic.

This article covers how the shared quota works, why per-channel pricing punishes growth, how the bot-count pool fits in, and how to size a plan for a Georgian SMB.

How the shared quota works

Your plan defines a monthly message allowance. Every reply the bot sends draws from that one allowance, no matter which channel produced it. A WhatsApp answer, an Instagram DM reply, a Telegram message, and a website widget response all count against the same number. When you near the limit, you see it in one place, and you size up once for everything.

This is the opposite of the common model, where you would hold four subscriptions and four separate counters, with one channel hitting its cap while another sits half-used. With a single pool, an unusually busy week on Instagram borrows from the headroom your quiet Telegram channel was not using. The capacity flows to where the demand is.

The public Bot API draws from the same pool. If you wire the bot into a custom app or an internal tool, those messages count against the same plan, so you are never juggling a separate developer bill on the side. The Bot API guide covers how that connection works.

Why per-channel pricing punishes growth

Per-channel pricing has a quiet trap: it taxes the exact move you want your business to make. Expanding from Messenger to also cover WhatsApp and Instagram is good for sales, but under a per-platform fee, it raises your fixed cost before any of those channels has proven it pays. Owners hesitate, delay the expansion, and lose the leads they would have caught.

A shared quota removes that hesitation. Turning on a new channel costs nothing extra by itself; it gives your existing message pool another place to be spent. If your customers move from Instagram to WhatsApp over a season, your bill does not care. You react to where people are without re-budgeting every time.

There is a consistency benefit here too, tied to the single Brain behind all the channels. Because one Brain serves every surface, adding a channel does not mean building or paying for a second bot. The one Brain, five channels article explains how the shared core makes the shared quota possible in the first place.

The bot-count pool

Quota is about messages; bot count is about how many distinct bots you run. aiSTAFF treats bot count as one pool across all platforms, gated by your plan, rather than a per-platform allowance. So if your plan allows, say, a handful of bots, you decide how to allocate them, whether that is one bot on five channels or a few bots for different business units.

For most single-location Georgian SMBs, one bot on every channel is the whole setup, and the pool never becomes a constraint. The flexibility matters more for an operator running two brands or a clinic group with separate locations, where you might want a distinct bot per site while still living under one subscription and one quota.

The point is that both knobs, messages and bots, live in one place. You are not reconciling a WhatsApp bot limit against an Instagram bot limit. You see the pool, you allocate from it, and the platform enforces the plan ceiling.

Sizing a plan for a Georgian SMB

Sizing starts with one number: roughly how many customer messages do you handle in a month across all your channels combined? Not per app, combined. That total is what a shared quota is built around, and it is usually easier to estimate than four separate per-channel figures.

A small store fielding a few dozen conversations a day lands in a modest tier. A busier operation with evening Instagram surges and steady WhatsApp traffic sizes up. Because the quota is shared, you do not need to predict the split between channels, which is the part owners always guess wrong. You only need the rough total, and you can move up a tier mid-life if traffic grows, with the change applying next cycle.

The activity heatmap helps you read this. Once the bot is live, it shows when your messages arrive across the week, so your next plan decision is based on your real curve instead of a guess. The activity heatmap article shows how to read that pattern, and tuning the bot to sound right on every channel is covered in making the chatbot speak fluent Georgian.

For the broader picture of how billing, trial, and grace periods work across the platform, the aiSTAFF platform guide is the place to start, and the business chatbot guide sets the cost context for Georgia.

Related reading

• aiSTAFF platform guide
• Per-channel tone control
• Chatbot memory tiers explained
• Spin up a Telegram store assistant
• Put an AI agent on WhatsApp Business

FAQ

Is the message quota shared across all channels?

Yes. One subscription carries one monthly message allowance, and Messenger, Instagram, WhatsApp, Telegram, the website widget, and the API all draw from it. There is no per-platform counter to manage.

Does adding a channel cost extra?

Turning on a new channel does not add a separate fee. It gives your existing message pool another surface to be used on, so your volume spreads rather than your bill multiplying.

How is bot count handled?

Bot count is one pool across all platforms, gated by your plan. You allocate bots from that pool however suits your business, whether that is one bot on five channels or several bots across locations.

How do I know which plan size I need?

Estimate your total monthly message volume across all channels combined, not per app. That single number sizes the plan, and you can move up a tier later, with the change applying on the next billing cycle.