Why You'd Use This
Control how often each contact can enter and trigger an automation using the Frequency per Contact setting. This helps you avoid overwhelming clients with repeat communications and ensures your automations behave as expected.
🔍 What It Does
This setting limits how frequently an individual contact can trigger an automation. It helps prevent duplicate or excessive messaging to the same person, especially in scenarios where the automation could otherwise be triggered frequently.
Once a contact triggers the automation, they will not be eligible to re-enter it again until the specified frequency window has passed.
📋 Setting Options
Choose from the following options to control how often a contact can trigger an automation:
✅ One-time Only
The automation will only run once per contact.
Ideal for one-time messages like welcome emails or single-use offers.
✅ Annual
Runs once every 12 months for the same contact.
Great for birthdays, anniversaries, or yearly check-ins.
✅ Custom
Set a specific number of days between automation runs.
Example: Setting 30 days means the same contact can only enter the automation once every 30 days.
✅ Custom (for testing only)
Allows short windows like 1 hour between runs for testing purposes.
Intended for use in staging or development environments only.
Be sure to disable this after testing to prevent unintended live use.
⚙️ How It Works
When a contact qualifies for an automation, the system checks how long since the prior automation last ran for them.
If it falls outside the defined frequency window, they’ll be surfaced by the automation again.
If not, the automation will skip them until the time passes.
💡 Practical Use Cases
Use frequency limits to keep your automations relevant and non-intrusive:
New Client Welcome Series (One-time Only)
Prevent clients from receiving the same welcome automation more than once.
Upsell Reminders (Every 30 Days)
Send upgrade offers to clients who meet conditions, but no more than once a month.
Birthday Campaign (Annual)
Celebrate client birthdays every year no need to re-enroll them manually.
Testing Flow (Every 1 Hour)
Test your automation in a dev environment by setting a short interval, then switch to a longer interval before going live.
Important Note
The frequency setting is not available for pre-built automations.