Push Notifications

Overview

Push Notifications is the management center for your mobile app's push messages. It supports three kinds of notifications:

• Automated notifications — event-triggered messages such as session reminders, cancellation reschedules, and re-engagement series
• Webhook notifications — messages fired by a ClubReady automation webhook (e.g. booking scheduling pushes); the trigger comes from ClubReady, the message is managed in Blend
• Ad-hoc campaigns — one-time notifications sent to a targeted audience

Phase 1 (UI): All screens are fully functional with sample data. Delivery to real devices is part of the backend phase.

Dashboard

The landing page shows delivery performance at a glance:

• Notifications Sent Today
• Delivery Rate (average across all notifications)
• Open Rate (average across all notifications)
• Click-through Rate (average across all notifications)
• Active Automations
• Scheduled Campaigns

Use the search and filters to narrow metrics by Studio Name, ClubReady Studio ID, Division, Country (US/CAN), State/Province, and City.

Automated Notifications

Automations send a message automatically when something happens. They are organized in Drafts, Active (with a Turned ON / Turned OFF filter), and Archived tabs.

Each automation is configured in eight sections:

1. Message — One or more notifications, each with a title (60 character limit) and message (150 character limit) and live character counters. Add multiple messages when the automation fires a series at different times (e.g. session reminders at 24h and 2h before a booking, or re-engagement at 5/8/14 days). Insert personalization tokens (First name, Last name, Session start time, Session timeframe, Practitioner, Studio name) into any message.

2. Triggers — Choose from phase-1 triggers such as Most immediate future open booking, Booking cancelled, Become active member, Birthday, Membership Anniversary, Earns points in Perkville, Voucher expiring, and more. Each trigger has a timing setting (e.g. [X] hours before booking, yearly recurring on member date of birth). Multiple triggers can be combined with AND/OR logic.

3. Conditions — Restrict who receives the automation. Four conditions are enforced today: audience segment (active/inactive members, prospects), country (US/Canada), future open booking (true/false), and available session credits (true/false). The remaining options — studio, division, studio tier, Perkville status, completed-booking counts over a time window, and cancellation reason — can still be selected but are not yet applied, so don't rely on them to narrow an audience.

   Country is how you run an automation for one country only. US and Canada studios share one account, so turning an automation ON sends it to both countries. Add a Country condition to limit it to US or to Canada. To run different messages or timing per country, create two automations, each with its own Country condition, and enable or disable them independently.

4. Deep Link Destination — What opens when the notification is tapped. Values are the mobile app's exact screen identifiers (screens register themselves — the list is not hardcoded): Login, Register, Book a Session, Studio Finder, Membership, Add Sessions, Join FlexPoints, Redeem Reward, Refer a Friend, My Rewards, Session Survey, or an External URL.

5. Frequency — Once per booking, once per booking cancellation, once every [x] days/weeks, once a year, or once every event.

6. Notification Priority — High (time-sensitive transactional, can bypass promotional limits), Medium (respects quiet hours and daily limits), or Low (marketing, sent only if limits allow).

7. Suppression Rules (required) — Users exit the automation when criteria are met: booking scheduled, booking cancelled/completed/rescheduled, agreement purchased, [x] days from enrollment, on a specific date, or push disabled. At least one rule must be selected: without an exit criteria a user never leaves the automation. Saving or activating an automation with none selected is rejected with "Select at least one suppression rule".

8. Status — Turn each automation ON or OFF, and toggle Bypass quiet hours for transactional notifications (e.g. session reminders) that should be delivered even during quiet hours.

Delivery Rules

• Automations respect quiet hours (Monday–Saturday 8:00 PM – 9:00 AM, Sunday 8:00 PM – 12:00 PM) unless Bypass quiet hours is turned on.
• Notifications are sent based on the studio's time zone.

Webhook Notifications

Webhook notifications are triggered by a ClubReady automation webhook — ClubReady fires the event, and the message is managed in Blend. The trigger is hard-coded (registered by ClubReady) and cannot be changed here; everything else (message, timing note, conditions, deep link, priority, suppression, quiet-hours bypass, ON/OFF) is configurable.

The phase-1 webhook is Booking scheduling pushes (event: Booking scheduled), which fires on the member's most immediate future open booking, bypasses quiet hours, and taps through to the booking screen. Webhooks are organized in Active and Archived tabs.

Campaigns (Ad-hoc)

Campaigns are one-time notifications, organized in Drafts, Scheduled, Sent, and Archived tabs. Creating a campaign is a four-step wizard:

1. Audience — First pick a Customer Type (Member, Inactive, or Prospect — required). The customer type decides which recipients you can choose under Select Recipients:

   • Member → Active members
   • Inactive → Inactive members
   • Prospect → Prospect: All / Scheduled / Unscheduled / Missed Sale / No Show

   Checking a customer type pre-selects its default recipient. Unchecking it removes that type's recipients. Then narrow further by studios (all, specific, or multiple), divisions, studio tiers, country (US/CAN), referral types (corporate-level referral types only), membership types (by agreement ID, from the mobile app package mapping), and Flex Points status (Active/Pending). An estimated recipients summary updates as you select. A campaign can't be saved if a recipient doesn't match its customer type, or if a selected customer type has no recipient.

   Studios and Divisions stay in sync. Every studio belongs to one division, so checking a studio unchecks All divisions and ticks the division that studio belongs to; checking a division selects all of its studios (and unchecks All studios). Unchecking a division removes only its studios, so picks from other divisions are kept, and checking All studios or All divisions resets both panels to "all".

   US and Canada studios are managed together. Both countries appear in one studio list rather than in separate accounts, so Country (US/CAN) is how you target one or the other — selecting a country also narrows the Studios list to that country. Leave Country empty to reach both.

   The Studios, Divisions, and Membership Type lists each have a search box above them — type part of a studio name or ClubReady ID, a division, or a package name to narrow the list instead of scrolling through 400+ studios or hundreds of sales packages. Each list shows how many options are visible, how many you have selected, and a Clear selection link. Searching only filters what is displayed; anything you already checked stays selected.

2. Notification Content — Title (60 cc) and message (150 cc) with character counters, personalization tokens, and a live device preview.

3. Action — Deep link destination when the notification is tapped (same registered-screen list as automations, including External URL).

4. Delivery Options — Send Now or Schedule with a date and time. Scheduled campaigns are sent at the selected time in the studio's time zone.

Send Summary

Before anything is sent, a summary screen shows the Audience (e.g. 2,485 users), Message, Action, and Delivery, with Back and Send/Schedule buttons.

Notification History

Every notification ever sent, searchable and filterable by Studio, Division, ClubReady Studio ID, ClubReady User ID, and Email Address.

Columns: Notification, Audience, Date, Sent, Delivered, Opened, CTR.

Overall Notifications Settings

Admins can tune the global system rules:

Quiet hours are based on the studio's time zone. Transactional notifications (e.g. session reminders, booking scheduling pushes) can bypass quiet hours — this is chosen per notification via the Bypass quiet hours toggle on each automation or webhook.

Installation

1. Go to Apps in your tenant and install Push Notifications.
2. Configure the sender name, quiet-hours behavior, and studio time-zone delivery in the app configuration.
3. Open the app from the sidebar — Dashboard, Automated Notifications, Webhook Notifications, Campaigns, Notification History, and Settings are available immediately.