Frequency caps
Limit Review Request Frequency Per Customer
Once a business runs several automations, one customer can qualify for three of them in a fortnight: an order, a support ticket closed, a renewal. Each email makes sense alone; together they feel like pestering. From Pro, two settings stop that: a cap on how often one person hears from an automation, and a review request step that skips anyone asked recently. This page is the team routine for using both everywhere.
- An inventory of every automation that emails customers
- Two layers: the cap and the asked recently skip
- The gaps no setting covers, such as other tools
The problem, solved
How customers end up over asked, and what limits it
Three automations, one customer, one week
Each automation was built by a different person for a different trigger, and none knows about the others.
With StoryProof: From Pro, each automation can cap how often one person hears from you. Set the cap on every one that emails customers.
The same person qualifies again and again
Repeat buyers and frequent support contacts trip the same trigger over and over.
With StoryProof: Make the request a review request step that skips anyone asked recently, as well as anyone who already reviewed.
Reminders stack on top of new asks
A customer still inside one follow-up sequence enters another.
With StoryProof: The ready-made follow-ups stop as soon as the customer leaves a testimonial and skip anyone who unsubscribed, which narrows the overlap.
Some customers asked us to stop
A polite “not now” reply should not lead to another request next month.
With StoryProof: An automation can tag the contact, move it to a Smart List or unsubscribe it, so the reply is respected.
We cannot prove the limit works
A complaint arrives, and nobody can say what that person was sent.
With StoryProof: Logs show every enrolment and every step that ran, with the reason a run ended, for 30 days.
Flip the switch to see how StoryProof handles each one.
Rollout checklist
Put a limit on every automation that emails customers
One owner works through this with whoever built each automation. It takes an afternoon the first time.
Ticks are kept in your browser only.
In StoryProof
Order of work
- You will need
- StoryProof on Pro or above
- Customers kept as contacts, so limits apply to a person
- 1
Keep customers as contacts
Contacts and Smart Lists are on every plan, so each person is one record that limits can attach to.
- 2
Set the cap on each automation
In each automation’s quiet hours and limits, cap how often one person hears from it.
- 3
Switch requests to the skipping step
Use a review request step that skips anyone who has already reviewed or was asked recently.
- 4
Test with your own contact and publish
Nothing runs until published. A test sends for real, so run it on yourself and read the log.
What happens next: Make “cap and skip set” part of the sign-off for any new automation.
Before you start
What these settings will not catch
Other tools’ emails
Asks sent from your CRM, email platform or by hand are outside StoryProof’s automations and are not counted.
Cap scope to confirm
StoryProof says an automation can cap how often one person hears from you. Check in the settings whether that counts across automations.
“Recently” is defined in the app
This page does not state how long “asked recently” covers. Read it in the step’s settings and compare it with your policy.
Logs are short
Run history is kept for 30 days, so a complaint about something older cannot be traced there.
FAQ
Questions people ask
Short answers to what usually comes up next.
What is the difference between the cap and the skip?
The cap limits how often one person hears from an automation. The skip is part of a review request step and passes over people already asked recently or who already reviewed.
How often should one customer be asked?
That is a policy decision. The how often to ask page lays out a cycle; this page is about enforcing whatever you choose.
Do unsubscribed customers still get requests?
The ready-made follow-ups skip anyone who unsubscribed, and an automation can unsubscribe a contact who asks to stop.
Who should own the limits?
One person who keeps the inventory and checks new automations. Without an owner, the next automation built in a hurry will lack the cap.
Still have a question? Ask the StoryProof team or book a demo.
Ask often enough, never too often
Cap each automation and skip customers asked recently, so every request still feels personal.
Last updated 2026-11-18.