Community
Promoter automations
Set a rule once. We send the right message at the right time — birthdays, anniversaries, post-event, more.
3 min read
What it is
An automation is a rule that auto-sends a message to your client list members when a trigger condition is met. Set it up once; it runs forever in the background.
Think 'Mailchimp drip campaigns' but for nightlife clientele — birthday wishes, post-event thank-yous, win-back nudges to inactive members, tier-promotion celebrations.
Triggers we support
**Birthday** — fires on a member's MM-DD. We pull from each client's profile birthday.
**Anniversary** — fires on the anniversary of joining your list. Template gets a {years} variable so you can write 'Happy 3 years on the list'.
**Inactive (N days)** — fires when a member hasn't visited for N days. Configure N in the rule's trigger config.
**Post-event** — fires N hours after one of your events ends. Sends to everyone who attended.
**New member** — fires the moment someone joins your list. Useful for welcome flows.
**Tier upgrade** — fires when you promote a member to a new tier. Celebrate the move.
**New event** — fires when you publish a new event. Notify the right tier instantly.
**Spend milestone** — fires when a member crosses a spend threshold. Reward the loyalty.
Channels
Push notification — instant, free, requires the member to have the app installed.
SMS — most reliable, costs money per message (we pass through Twilio rates).
Email — best for longer messages and offers with images.
In-app — appears in the member's notification center; lighter than push.
Dedup + idempotency
We never send the same rule to the same recipient twice within 23 hours. So if your daily cron runs again, or you accidentally toggle a rule on/off, no one gets spammed.
Every send is recorded in an audit log. If something doesn't fire, we can tell you exactly why (recipient missing email/phone, dedup hit, channel failure).
Templates + variables
Custom messages support {ownerName} (your handle), {years} (for anniversaries), {eventTitle} (for post-event), and {s} (the plural-s helper).
Leave the message blank to fall back to a sane default per trigger — useful when you're just dipping a toe in.
Was this helpful?
Tell us if it answered what you came for.