Guardrails & consent
Automations only work if fans trust them. Trybe caps automated messages per person per day, stops marketing messages for anyone unsubscribed, requires a stop rule on every wait, and holds texts due before 9 AM or after 9 PM.
See the Automations page →What you get
Daily cap on automated messages per person, across all automations
Unsubscribing stops marketing messages from every automation
Every wait needs a stop rule: they bought, checked in, were refunded
Texts go out from 9 AM to 9 PM local time; a held text waits up to 12 hours
When credits run out, runs pause and resume in order, and nobody is skipped
Guardrails & consent in detail
Guardrails are the rules Trybe enforces on every automation, for organizers and promoters. A daily cap means no one receives more than a set number of automated messages per day across all your automations, and a spacing rule can skip a send when the person already heard from you in the last few hours, campaigns included. Unsubscribing stops marketing messages from every automation at once; only steps marked important, reserved for essentials such as a venue change, a cancellation or the ticket itself, reach everyone who bought.
Every wait must carry a stop rule (they bought, they checked in, the order was refunded, the team handled it), checked the moment it happens. A cancelled event stops its runs. Texts respect 9 AM to 9 PM in the recipient's time zone and wait up to 12 hours. Running out of credits pauses runs in order instead of skipping people, and nothing is charged. Before activation Trybe shows what will happen, that only new activity counts, the cost per run and your credit balance, and test runs go only to you. Every skipped run says why in plain words.
How it works
Consent comes first
Marketing steps skip anyone unsubscribed; important steps are reserved for essentials like a venue change or their ticket.
Limits are enforced
The daily cap, spacing rules, re-entry settings and quiet hours apply to every run, whatever the automation does.
Waits carry stop rules
Choose what cancels a waiting run: they bought, they checked in, the order was refunded, the team handled it.
Every skip is explained
Runs that didn't send say why in plain words: unsubscribed, a stop rule matched, already been through, hit the daily cap, event cancelled.
Questions organizers ask
How does Trybe prevent automations from over-messaging fans?
A daily cap limits automated messages per person across all your automations, and each automation can add a spacing rule that skips a send when the person already heard from you recently, campaigns included. Re-entry rules also decide how often the same person can go through.
What happens when someone unsubscribes?
Marketing messages stop for that person in every automation, immediately. Only steps marked important, meant for essentials such as a venue change, a cancellation or their ticket, still reach everyone who bought.
Why does every wait need a stop rule?
Because things change while the run waits: someone buys, checks in, gets refunded or your team handles the request. The stop rule is checked the moment it happens and cancels the run, so the message never goes out.
Are automated texts sent at night?
No. Automated texts respect quiet hours, 9 AM to 9 PM in the recipient's local time, and a held text waits up to 12 hours before going out. The run shows when the text will leave in the meantime.
What if I run out of credits in the middle of an automation?
Runs pause instead of skipping people, nothing is charged, and they resume in order once you add credits. The abandoned checkout reminder and emails to you or your team are free, so they keep running.
Will activating an automation message my existing contacts?
No. Activation counts only from now on; your existing records are never swept up. Before you switch on, Trybe shows what will happen, the cost per run, that opt-outs are honoured and how many credits you have left.
Related features
Automations
Flows that run on their own when fans follow, buy, abandon a cart or have an event coming up
Triggers & actions
Twelve triggers, seven actions, waits and if/otherwise branches: build the exact flow you have in mind
SMS campaigns
Text your community a tracked link, and see the cost in credits before you press send