Limits & Deduplication
Understand how messaging limits and deduplication keep your automations effective without over-messaging.
Monthly message limit
Your restaurant has a limit of 5,000 SMS and 5,000 emails per month. Each channel is tracked separately, and both campaigns and automations count toward the same per-channel total.
Example: If you've sent 3,000 campaign SMS this month, automations can send up to 2,000 more SMS. Your email quota is independent — you'd still have the full 5,000 emails available.
Fire-once deduplication
Each automation fires at most once per customer. Once a customer receives a message from an automation, they will not receive it again — even if they still match the conditions. This prevents repeated messaging.
State reset
A customer becomes eligible again only if they place a new order after the automation last fired. This is the "state reset" — the customer's new activity requalifies them for evaluation.
Example: A "lapsed 60 days" automation fires for John on March 1. John orders on March 15. 60 days later (May 14), the automation can fire again because John has a new order after the last send.
Multiple automations
If a customer matches conditions for different automations, each one fires independently. Automation deduplication is per-automation — one automation triggering does not prevent others from firing.
Campaigns don't affect automation cooldowns
The campaign frequency cap (7 days between campaign sends) is separate from automation deduplication. Receiving a campaign does not delay or block automations, and vice versa.