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 outside 8 AM to 9 PM.
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 wait for 8 AM to 9 PM local time, up to 12 hours
Out of tokens? Runs pause and resume in order, nobody is skipped
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 8 AM to 9 PM local time and wait up to 12 hours. Running out of tokens pauses runs in order instead of skipping people. Before activation Trybe shows what will happen, that only new activity counts, the cost per run and your token balance, and test runs go only to you. Every skipped run says why in plain words.
Marketing steps skip anyone unsubscribed; important steps are reserved for essentials like a venue change or their ticket.
The daily cap, spacing rules, re-entry settings and quiet hours apply to every run, whatever the automation does.
Choose what cancels a waiting run: they bought, they checked in, the order was refunded, the team handled it.
Runs that didn't send say why in plain words: unsubscribed, a stop rule matched, already been through, hit the daily cap, event cancelled.
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.
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.
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.
No. Automated texts respect quiet hours, 8 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.
Runs pause instead of skipping people, and resume in order once you top up. Ready-made automations and internal messages are free, so they keep running.
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 tokens you have left.
Flows that run on their own when fans follow, buy, abandon a cart or have an event coming up
Ten triggers, seven actions, waits and if/otherwise branches: build the exact flow you have in mind
Text your community with a tracked link, the price shown in tokens before you press send
Free for organizers hosting on Trybe. No credit card, two-minute setup, works in English and French.