Daily sending limits on messaging integrations Guide
Why Praxivara applies daily caps to WhatsApp messages and outbound calls, and what to do when a send is held back.
Last updated July 16, 2026
On this page
To protect your account and keep your messaging reputation healthy, Praxivara applies daily limits to outbound messaging on channels like WhatsApp and voice calls. This article explains what those limits cover, why a send is sometimes held back, and what you can do to keep things flowing.
Why sending limits exist
Messaging and calling channels are powerful, which is exactly why they benefit from guardrails. A daily cap on outbound WhatsApp messages and outbound calls helps you avoid accidental over-sending, protects the sender reputation tied to your connected number, and keeps a runaway automation from reaching more people than you intended.
These limits apply to messages and calls the assistant or your agents send on your behalf through a connected messaging integration. They are a safety ceiling, not a target — most everyday workflows never come close to them.
Note: Limits are counted per day and reset on their own. If you reach a cap, sending on that channel resumes automatically on the next cycle without any action from you.
What the limits cover
- Outbound WhatsApp messages — messages your assistant or agents send to recipients through your connected WhatsApp channel.
- Outbound calls — calls placed on your behalf through a connected voice or phone integration.
Inbound activity — messages and calls people send to you — is handled separately and is not affected by these outbound caps.
Why a send might be refused
If the assistant or an agent tells you a message or call couldn't be sent, the most common reasons are:
- The daily limit for that channel has been reached. Sending pauses until the next cycle, then resumes on its own.
- The integration needs attention. The connection may have been disconnected, or it may need to be reconnected from the Integrations page.
- The specific action isn't enabled. Each connection has an allowlist of actions the assistant is permitted to perform. If sending isn't turned on, enable it under the connection's Manage actions.
- The recipient or content was rejected by the provider. Some channels have their own rules about who you can message and what a first message may contain.
What to do when you hit a limit
- Confirm the channel is the cause. The assistant will usually tell you when a send was held back because of a daily limit rather than a connection problem.
- Wait for the reset. Because limits are counted per day and reset automatically, queued or repeat sends can go out on the next cycle.
- Prioritize what matters. If you're close to a cap, focus the day's sends on the most important recipients rather than large bulk runs.
- Spread larger campaigns out. If you regularly need to reach many people, pace the work across days or across more than one connected channel.
Keeping automated messaging healthy
A few habits help your agents run smoothly and stay well within the caps:
- Scope your actions deliberately. When you connect a messaging app, enable only the sending actions you actually want the assistant to use.
- Design agents to send with intent. Have agents message specific, relevant recipients rather than broad lists, which keeps volume low and engagement high.
- Watch your channel's own rules. WhatsApp and voice providers maintain their own standards for outbound messaging; following them protects both delivery and your sender reputation.
- Consider your plan. If your workflows consistently need more outbound headroom, higher plans are built for greater messaging volume.
Tip: If sends are being refused and it isn't a daily limit, open the Integrations page and check that the channel still shows as connected and that the sending action is enabled under Manage actions. Reconnecting the app resolves most delivery issues.
Getting help
If a channel keeps refusing sends and none of the steps above apply, note the channel, the recipient, and the message the assistant showed you, then reach out to support. That detail helps us pinpoint whether the cause is a daily limit, the connection, or the provider on the other end.