Limits and allowances

Everything below is enforced by the product: reach the number and something is refused, paused or stopped. The last section lists figures you will see in the interface that OMAI does not enforce — Meta’s own limits and illustrative estimates — so you can tell the two apart.

What each plan allows

Starter stops at exactly its included amount. Growth and Pro keep answering past the included amount, up to half as much again — the fair-use band — and stop there. The billing page shows your own stopping point in the Answers before service pauses tile, and warns you on the way: a banner appears once you pass 80% of the included amount, and again at 100%. When answering stops, incoming messages still arrive and are stored, and each new conversation is handed to your team in the inbox. An organization with no subscription at all is allowed 1 team member, not 2.

Limits that pause the assistant

Files and the knowledge base

The upload form states the limit for the file type you have selected, and changes it when you change the type — so the figure on screen is the figure that is enforced, and a file over it is refused in the form rather than accepted and then rejected. One file at a time: dragging several onto the drop zone takes the first. A file name may be up to 255 characters, and the Title field up to 200. The number of sources you may keep is not capped; what is capped is their total size, against your plan’s knowledge storage. Documents you delete stop being used immediately and free their space.

Text length limits

How much a screen loads

Time windows

Rate limits you can actually hit

These count actions per organization in a rolling minute. Going over does not break anything — the action is refused with a “too many attempts” message and works again a minute later.

How long things are kept

Conversations, messages, contacts and knowledge sources are kept for the life of the account: nothing in the product deletes them on a schedule, and there is no setting that shortens it. You remove them by deleting the source, or by deleting the organization. Invoices and the fiscal documents behind them are kept for the statutory period, even after an account is closed.

Numbers that are not OMAI’s to enforce

You will meet these figures in the interface or in Meta’s tools. They are real, but they are not limits OMAI applies, so do not plan against them as if they were.

• Meta’s registration attempts. Meta allows a limited number of registration attempts per number in a rolling 72 hours. OMAI’s protection is to register a number once and never retry automatically; the guidance text tells you to wait for Meta’s window to reset.
• About 20 messages per second on a number that also runs on your phone. That is Meta’s throughput figure, shown in the guided check. OMAI does not measure or shape your sending rate.
• Up to about six months of recent chats imported when you connect a number that also runs on your phone. Meta decides what it sends and how far back it goes; the import is best effort.
• The per-send cost shown on the Templates page is an illustrative default for a template message, not a contracted price, and not what Meta will invoice you.
• Connected WhatsApp numbers per plan. Pro and Custom include more than one connected number; Starter and Growth are sold as single-number plans. The connect flow does not stop you at that line, so treat it as a plan term rather than a wall.
• Rate limits are counted by each web server separately, so the effective number can be a little higher than the table above, and counters reset when a server restarts.