Gym Email Templates

Navigate to Content → Gym → Email Templates to manage the master library of member-facing email templates used by gym automation flows.

Purpose

Gym Email Templates are member-facing emails (sent to gym members by the gym). They are distinct from Platform Email Templates (sent to gym owners/leads by Bliply). Each template is linked to one or more automation flow nodes.

Current Templates (17)

Template	Linked Automation Flow
New Lead Follow-Up	New Lead Follow-Up
New Trial Membership Welcome	New Trial Membership Welcome
Trial Expiry Conversion	Trial Expiry Conversion
Trial Final Nudge	Trial Expiry Conversion (step 2)
Post-First-Class Follow-Up	Post-First-Class Follow-Up
Inactivity Check-In	Inactivity Check-In
Failed Payment Recovery	Failed Payment Recovery
Failed Payment Escalation	Failed Payment Recovery (step 2)
Membership Expiry - 14 Day Reminder	Membership Expiry Reminder
Membership Expiry - 7 Day Reminder	Membership Expiry Reminder
Membership Expiry - 3 Day Reminder	Membership Expiry Reminder
At-Risk Member Follow-Up	At-Risk Member Re-engagement
At-Risk Member Re-engagement	At-Risk Member Re-engagement (step 2)
Birthday Message	Birthday Message
Milestone Celebration	Milestone Celebrations
Referral Thank You	Referral Thank You
Membership Upgrade Prompt	Membership Upgrade Prompt

Distribution Model

Master templates are pushed to gyms via the Push All mechanism. When pushed:

Templates are upserted into each gym's local gym_email_templates repository
A platform_template_snapshot (JSONB) is stored with the original platform content
Existing local customisations are not overwritten
Gyms can Revert to Default — this requires typing the word "REVERT" to confirm, which restores the platform snapshot version

Late-Binding Resolution

Automation nodes reference email templates by name (not by ID). At send time, the system resolves the template from the gym's local repository. This means:

If a gym customises a template, their version is used automatically
If a gym deletes a local template, the automation node will fail to resolve — this is by design to prevent unintended sends
Template names must match exactly between automation config and the email template record

Template Format

All templates use the block-based email builder format with:

Standardised hero headers — Platform hero image with gym logo overlay
Locked footers — Unsubscribe link, gym address, and contact details via merge tags
Merge field support — {{first_name}}, {{gym_name}}, {{gym_email}}, {{join_link}}, etc.
Light-mode consistent rendering — Templates are designed for light backgrounds