Automations, blasts & SMS tips (ClubSpeed)

SMS tips

ClubSpeed does not tell Patch whether a guest opted in to SMS. Patch manages SMS consent on its own.

Do

Make sure the contact has a mobile number and is opted in for SMS in Patch before you send.
Keep texts short; lead with your venue name and one clear action (book, top up, directions).
Use quiet hours. ClubSpeed data syncs about every 6 hours, so a “thanks for racing” can fire later than you expect.
Limit how often someone can get texts from the same journey (for example, once per week) with the Throttle block.
Treat email opt-out (including ClubSpeed “do not email”) separately from SMS rules in Patch.

Don’t

Assume “do not email” in ClubSpeed also means SMS opt-out (or opt-in).
Send SMS on every small contact update (like credit balance refreshes) without a threshold and cooldown.
Message guests who never synced because they had no email or phone.

Automations

Build for ClubSpeed timing

Prefer triggers tied to Orders, Check-ins (heats), Calendar, or Memberships when you can — they’re clearer than generic Contact Updated.
Add a short delay after Order Finished or Checkin Finished so late syncs still feel natural.
Match the trigger to the real moment: spent money vs raced vs booked a party. See Orders vs heats vs parties.

Before you turn an automation on

The trigger matches what you want to celebrate or follow up on.
You’ve filtered out staff if you use ClubSpeed’s employee flag.
Test contacts have email/phone and the right consent.
Exit rules stop people from looping forever.
Your team knows updates arrive on a schedule (~6 hours), not instantly.

Blasts

Use blasts for one-time news (holiday hours, special track days, new membership promos).
Use automations for ongoing journeys (welcome, win-back, expiry, post-race).

Useful ClubSpeed-powered audiences

Active members
Raced in the last X days
Spent in the last X days
Credit balance above $0
Upcoming or past party bookers

Always suppress unsubscribed contacts, and send yourself a test first.