Skip to content
English
More support
Go to patchretention.com
  • There are no suggestions because the search field is empty.

Automations, blasts & SMS tips (Capitan)

Better email, SMS, automations, and blasts with Capitan data.

SMS

tips

When Capitan has marketing opt-in turned on for a member, Patch can seed email and SMS opt-in (it won’t override an explicit opt-out already in Patch). After that, Patch manages consent.

Do

  • Confirm mobile + SMS opt-in in Patch before journey go-live.
  • Keep texts short; lead with your gym name and one clear CTA.
  • Use quiet hours. Check-ins and payments arrive within minutes, but other data can take up to about 6 hours.
  • Cap frequency (for example, once per week per journey family).

Don’t

  • Assume every Capitan member is opted in for SMS.
  • Fire SMS on every Contact Updated without filters and cooldowns.
  • Message the wrong gym’s audience in a multi-location setup — build on the correct child account (or carefully scoped parent journeys).

Automations

Build for Capitan signals

  • Prefer Order Finished, Checkin Finished, Calendar Event, and Membership Started / Ended when you can.
  • Check-in and payment triggers fire fastest, so they suit time-sensitive journeys.
  • Membership and booking automations should allow for sync delay.
  • See Orders vs check-ins vs bookings.

Before you turn something on

  1. Trigger matches the real gym moment.
  2. Location / account scope is correct for multi-gym brands.
  3. Test contacts have consent and the right gym.
  4. Exit rules prevent loops.
  5. Your team knows what’s near real-time (check-ins, payments) vs delayed up to ~6 hours.

Blasts

Use blasts for one-time news (holiday hours, member sales, new class launches).
Use automations for ongoing journeys (welcome, win-back, post-check-in).

Useful Capitan-powered audiences

  • Active members (by plan)
  • Checked in within the last X days
  • Purchased within the last X days
  • Upcoming class bookings
  • Marketing opt-in from Capitan / Patch

Suppress unsubscribed contacts and send a test first.

Multi-location tips

  • Build automations only after Patch has finished connecting your gyms — see Connect your Capitan account.
  • Most Capitan automations should live on the venue (child) account that owns that gym’s data.
  • Copying an automation to another child account does not copy that gym’s Capitan setup; ask Patch if a new gym isn’t receiving data.