Where to find this: Services → Integrations tab
Automated notifications keep you and your customers informed about important events via email and SMS. This guide explains the notifications sent and how to manage them.
Overview
Automated notifications help you:
- Confirm bookings and remind customers of appointments
- Keep customers updated on subscription changes
- Recover failed payments automatically
- Request reviews after completed bookings
- Alert you to important account events
Important: Notification templates are professionally designed and cannot be customized. They automatically include your business branding and relevant details.
Types of Notifications
Email Notifications (Included in All Plans)
Email is the primary notification channel. To use custom domain emails, connect SendGrid in Services → Integrations tab.
SMS Notifications (Plan-Based Feature)
SMS notifications are optional and have monthly limits:
- Base Plan: Not included
- Standard Plan: 50 SMS/month
- Pro Plan: 200 SMS/month
To enable SMS, set up a Twilio account in Services → Integrations tab.
Booking Notifications
These notifications are automatically sent for booking lifecycle events.
Booking Confirmation
Sent when: Customer completes a booking
Recipient: Customer
Channel: Email
Content:
- Booking date and time
- Service name
- The season the booking belongs to, with the dates that season runs. It appears only when the booking is tied to a purchase that belongs to one of your seasons (see Setting Up Your Seasons); bookings with no purchase behind them — trials, complimentary places, sessions taken straight from a plan allowance — never show it.
- Location and address
- Duration
- Cancellation policy link
Purpose: Confirms the booking was successful and provides all details.
The dates shown are the season's own dates as you set them, not the dates of the sessions that customer happens to be booked into — so someone who joins halfway through still sees the season they've joined. If the season can't be looked up for any reason, the line is simply left out; the confirmation itself still sends.
Booking Reminder
Sent when: 24 hours before appointment
Recipient: Customer
Channel: Email and/or SMS (if enabled)
Content:
- Booking date and time (tomorrow/today)
- Service name
- Location
- "See you soon!" message
Purpose: Reduces no-shows by reminding customers the day before.
If SMS is enabled and the customer has a phone number on file, they receive both email and SMS reminders. Otherwise, email only.
Booking Cancellation
Sent when: Booking is cancelled (by customer or business owner)
Recipient: Customer
Channel: Email
Content:
- Cancelled booking details
- Cancellation reason (if provided)
- Refund/credit information (if applicable)
- Link to rebook
Purpose: Confirms cancellation and explains next steps.
Booking Reschedule
Sent when: Booking date/time is changed
Recipient: Customer
Channel: Email
Content:
- Old booking date/time
- New booking date/time
- Service and location (unchanged)
Purpose: Confirms the rescheduling and provides updated details.
Review Request
Sent when: 24 hours after a completed booking
Recipient: Customer
Channel: Email
Content:
- Thank you message
- Request for feedback
- Link to leave a review
- Simple rating system
Purpose: Collects customer testimonials for your business.
Note: Review requests are only sent if the Reviews feature is enabled.
Subscription Notifications
Automated emails for subscription lifecycle events.
Trial Started
Sent when: Customer starts a free trial
Recipient: Customer
Channel: Email
Content:
- Welcome message
- Trial duration (e.g., 14 days)
- What's included in the plan
- Trial expiration date
- How to cancel if not interested
Purpose: Welcomes trial users and sets expectations.
Trial Ending Soon
Sent when: 3 days before trial expires
Recipient: Customer
Channel: Email
Content:
- Trial ending reminder
- Expiration date
- Benefits of subscribing
- How to add payment method
- How to cancel
Purpose: Encourages conversion while respecting customer choice.
Trial Expired
Sent when: Trial period ends without payment method
Recipient: Customer
Channel: Email
Content:
- Trial has concluded
- Access restrictions (if applicable)
- Option to subscribe
- Special offer (optional)
Purpose: Re-engages trial users who didn't convert.
Subscription Upgraded
Sent when: Customer upgrades to a higher plan
Recipient: Customer
Channel: Email
Content:
- New plan details
- New features unlocked
- New pricing
- Prorated charge explanation
- Next billing date
Purpose: Confirms upgrade and explains billing.
Invoice Paid
Sent when: Monthly/annual subscription payment succeeds
Recipient: Customer
Channel: Email
Content:
- Payment confirmation
- Amount charged
- Invoice number
- Payment method used (last 4 digits)
- Next billing date
- Download invoice link
Purpose: Receipt for successful payment.
Subscription Cancelled
Sent when: Customer cancels subscription
Recipient: Customer
Channel: Email
Content:
- Cancellation confirmation
- Access until end of period
- What happens after period ends
- Feedback request (optional)
- Option to reactivate
Purpose: Confirms cancellation and explains what to expect.
Subscription Paused
Sent when: Subscription is temporarily paused
Recipient: Customer
Channel: Email
Content:
- Pause confirmation
- Duration of pause
- When billing resumes
- How to unpause early
Purpose: Confirms pause status.
Note: Pausing feature may not be available on all plans.
Subscription Resumed
Sent when: Paused subscription is reactivated
Recipient: Customer
Channel: Email
Content:
- Subscription reactivated
- Next billing date
- Features restored
Purpose: Confirms reactivation.
Payment Failure Notifications (Dunning System)
The automated dunning system handles failed payments for both your platform subscription and your customers' subscriptions. Different actions occur depending on which subscription type fails.
Two Types of Subscriptions
Platform Subscriptions (You):
- Your subscription to use the platform
- Failed payments affect your site's availability
- Dunning emails sent to you (the business owner)
Customer Subscriptions (Your Customers):
- Your customers' subscriptions to your services
- Failed payments affect their booking access
- Dunning emails sent to your customers
- Your site remains available
The dunning system sends escalating reminder emails for both types. However, site suspension only applies to platform subscriptions. Customer subscription failures affect only that customer's access to your services.
Platform Subscription Dunning
When your platform subscription payment fails:
Initial Payment Failure (Day 0)
Sent when: Your platform subscription payment fails
Recipient: You (account owner)
Channel: Email
Content:
- Payment unsuccessful notice
- Common reasons (expired card, insufficient funds)
- Link to update payment method
- Reminder that your account is still active
Purpose: Immediate notification with solution.
Site Status: Active (normal operation)
Day 3: Reminder
Sent when: 3 days after initial failure
Recipient: You (account owner)
Channel: Email
Urgency: Reminder
Content:
- Payment reminder
- Update payment method link
- Still have full access to your platform
- Support contact
Purpose: Gentle reminder with help offer.
Site Status: Active (normal operation)
Day 7: Urgent Notice
Sent when: 7 days after initial failure
Recipient: You (account owner)
Channel: Email
Urgency: Urgent
Content:
- Urgent payment required
- Your business account entering grace period soon
- Update payment within 7 days to avoid site suspension
- Clear call-to-action
Purpose: Escalates urgency, warns of impending restrictions.
Site Status: Active (approaching grace period)
Grace Period (Days 8-14)
Site Status: Grace period. Your site stays fully live and customers can still book — the only change is a stronger warning on your Purchased Services screen. Nothing is shown to your site visitors.
Day 14: Final Notice
Sent when: 14 days after initial failure
Recipient: You (account owner)
Channel: Email
Urgency: Final Notice
Content:
- Your platform subscription will be cancelled in 24 hours
- Your customer-facing site will be suspended
- Last chance to update payment
- Support escalation
Purpose: Final warning before cancellation.
Site Status: Still in the grace period — your site is live for one more day. Suspension happens the next day.
Day 15: Subscription Cancelled
Sent when: 15 days after initial failure
Recipient: You (account owner)
Channel: Email
Urgency: Service Suspended
Content:
- Your platform subscription has been cancelled
- Your service suspended
- How to restore your account
- Data retention policy (usually 90 days)
Purpose: Notifies of cancellation and restoration process.
Site Status: Inactive (fully disabled, customers cannot access your site)
Customer Subscription Dunning
When your customer's subscription payment fails:
Initial Payment Failure (Day 0)
Sent when: Customer's subscription payment fails
Recipient: Your customer
Channel: Email
Content:
- Payment unsuccessful notice
- Common reasons (expired card, insufficient funds)
- Link to update payment method
- Reminder that they still have access
Purpose: Immediate notification to customer.
Their Access: Still active (can continue booking)
Day 3: Reminder
Sent when: 3 days after customer's payment failure
Recipient: Your customer
Channel: Email
Urgency: Reminder
Content:
- Payment reminder
- Update payment method link
- Support contact
Purpose: Gentle reminder.
Their Access: Still active
Day 7: Urgent Notice
Sent when: 7 days after customer's payment failure
Recipient: Your customer
Channel: Email
Urgency: Urgent
Content:
- Urgent payment required
- Account restrictions coming soon
- Update payment within 7 days
Purpose: Escalates urgency.
Their Access: Still active but warned
Day 14: Final Notice
Sent when: 14 days after customer's payment failure
Recipient: Your customer
Channel: Email
Urgency: Final Notice
Content:
- Subscription will be cancelled in 24 hours
- Booking access will be removed
- Last chance to update payment
Purpose: Final warning.
Their Access: Last day of access
Day 15: Subscription Cancelled
Sent when: 15 days after customer's payment failure
Recipient: Your customer
Channel: Email
Urgency: Service Suspended
Content:
- Subscription has been cancelled
- Booking access removed
- How to resubscribe
Purpose: Confirms cancellation.
Their Access: Subscription cancelled, cannot book services included in the plan
Both platform and customer subscriptions follow the same 15-day dunning cycle with escalating reminders (Day 3, 7, 14, 15). However:
- Platform subscription failures → Your site status degrades (active → grace period → suspended → inactive)
- Customer subscription failures → Only that customer loses access to their subscription benefits; your site stays active
Payment Refunded
Sent when: A payment is refunded
Recipient: Customer
Channel: Email
Content:
- Refund confirmation
- Amount refunded
- Original payment date
- Refund reason (if provided)
- Refund method (original payment method)
- Processing time (5-10 business days)
Purpose: Confirms refund and sets expectations.
One-Off Purchase Notifications
For single-purchase services (non-subscription). Which of the three confirmations below a customer gets depends on what they bought — credits to spend, a place already booked, or a whole basket.
Purchase Confirmation
Sent when: Customer buys a one-off service that grants credits
Recipient: Customer
Channel: Email
Content:
- Purchase confirmation
- Service name and price
- Credits added to account
- How to use credits
- Booking instructions
- The once-per-account joining fee, named separately, if it was charged on the same payment
Purpose: Confirms purchase and explains next steps.
Note: Session packs, camps, season subscriptions and claimed waitlist places do not get this email — nothing needs booking and nothing expires, so they get the enrolment confirmation below instead.
Enrolment Confirmation
Sent when: Customer buys a session pack, a camp, a season subscription, or claims a place from the waitlist
Recipient: Customer
Channel: Email
Subject: "You're enrolled — [product name]"
Content:
- How many sessions are booked (and, if some are still being confirmed, "N of M sessions are booked so far")
- First and last session dates, in the venue's own local time
- Where the sessions run
- What was paid — or, for a season subscription, the ongoing billing line
- The once-per-account joining fee, named separately, if it was charged on the same payment
- "Your place is held for every session above — no booking needed."
Purpose: Confirms the places are booked, without credit wording that would tell the customer to go and book something.
Note: Sent once per enrolment — a repeated payment notification never produces a second copy.
Order Confirmation (basket)
Sent when: A customer pays for a basket containing at least one session, membership, credit pack or fee
Recipient: Customer
Channel: Email
Subject: "Your order is confirmed — [your business name]"
Content:
- Every line with its own amount, and a next step in its own words: sessions booked, membership active, credits added, family registration recorded, or a shop order following separately
- One total (labelled as the amount paid today where a subscription is included, with the ongoing charge spelled out)
- Delivery, where a shipping charge applied
- Any line that couldn't be fulfilled, named and marked refunded
Purpose: One receipt for the whole basket instead of one email per item. See How the Basket and Checkout Work.
Note: A basket of shop items only does not get this email — it goes through the store's own checkout, and the buyer receives the usual store order confirmation ("Order confirmed — [your business name] #1234") instead.
Credit Expiring Reminder
Sent when: Credits are about to expire (if expiration policy set)
Recipient: Customer
Channel: Email
Content:
- Credits expiring soon notice
- Expiration date
- How to use credits
- Link to book
Purpose: Encourages use of credits before they expire.
Purchase Refund
Sent when: One-off purchase is refunded
Recipient: Customer
Channel: Email
Content:
- Refund confirmation
- Service name
- Amount refunded
- Credits removed from account
Purpose: Confirms refund transaction.
Administrative Notifications
Sent to business owners (not customers).
Payment Failed Admin Alert
Sent when: Platform subscription payment fails
Recipient: Account owner/admin
Channel: Email
Content:
- Your subscription payment failed
- Action required
- Impact on your business
- Update payment link
Purpose: Ensures business owner is aware of payment issues.
Quota Usage Alert
Sent when: Usage approaches plan limits
Recipient: Account owner/admin
Channel: Email
Sent at: 75%, 90%, 95% of quota
Content:
- Feature approaching limit
- Current usage vs. limit
- Recommendation to upgrade
- Link to plans
Purpose: Prevents hitting limits unexpectedly.
Season Enrolment Alert
Sent when: The overnight run couldn't book one or more season subscribers into their sessions
Recipient: Account owner/admin
Channel: Email
Subject: "Action needed: 2 season enrolment issues — [site name]"
Content:
- A line per problem — usually naming the customer and what went wrong, sometimes a calendar-level issue such as no next season to roll into
- What to do: fix the cause, then wait for tonight's automatic retry or use the Season enrolments quick action and press Re-enrol now
- How many other enrolments booked successfully in the same run
Purpose: Makes sure paying subscribers don't quietly go unbooked. It re-sends each day until everything is resolved, and stops on its own once it is. See Checking Season Enrolments.
Contact Form Notification
Sent when: Someone submits a contact form on your website
Recipient: Account owner/admin
Channel: Email
Content:
- Contact form submission
- Sender name and email
- Message content
- Submission timestamp
Purpose: Ensures you don't miss customer inquiries.
Enabling SMS Notifications
SMS notifications are optional and require setup.
Requirements
- Standard or Pro plan (Base plan doesn't include SMS)
- Twilio account (sign up at twilio.com)
- Verified phone number
Setup Steps
- Go to Services → Integrations tab
- Click Connect Twilio
- Enter your Twilio credentials:
- Account SID
- Auth Token
- Phone Number
- Click Save
- Send a test SMS to verify
SMS Limits by Plan
- Standard: 50 SMS/month
- Pro: 200 SMS/month
Exceeding your limit disables SMS for the rest of the billing month. Email reminders continue to work.
SMS Content
SMS reminders are short messages:
- "Reminder: Your [service] appointment is tomorrow at [time] at [location]. See you soon! - [Your Business]"
Cannot be customized.
Managing Notifications
Enabling/Disabling Notifications
Most notifications are always enabled to ensure customers stay informed. You cannot disable:
- Booking confirmations
- Subscription payment receipts
- Payment failure notices
Optional notifications you can disable:
- Booking reminders (reduce no-shows, recommended to keep enabled)
- Review requests (disable if not using Reviews feature)
Viewing Notification History
Track sent notifications:
- Go to Services → Integrations tab
- View sent email and SMS logs
- Filter by date range or type
- See delivery status (sent, failed, pending)
Email Deliverability
To ensure emails reach customers:
Use Custom Domain Email
- Set up a custom email domain (e.g., notifications@yourbusiness.com)
- Emails from custom domains have higher deliverability than generic domains
- See Email Domain Setup
SendGrid Verification
- Verify your sender email address
- Complete domain authentication
- Monitor sender reputation
SMS Deliverability
To ensure SMS messages are delivered:
- Use a Twilio phone number (not your personal number)
- Verify phone numbers comply with local regulations
- Monitor SMS delivery status in your dashboard
Notification Timing
Common Questions
Q: Can I customize email templates?
A: No, templates are fixed to ensure professional, consistent communication. They automatically include your business name and branding colors.
Q: Can customers opt out of notifications?
A: Customers cannot opt out of transactional emails (bookings, payments) but may unsubscribe from marketing emails (if you send them separately).
Q: What if a customer doesn't have an email address?
A: Email is required for bookings and subscriptions. The system will not allow bookings without a valid email.
Q: What if SMS fails to send?
A: Email reminders will still be sent. SMS failures are logged in your notification history.
Q: Do I get notified when a customer books?
A: Bookings sync to your Google Calendar immediately. You'll see them in your calendar app with notifications based on your calendar settings.
Q: Can I add custom messages to notifications?
A: No, but notifications automatically include relevant details like your business name, location, service descriptions, and cancellation policies.
Q: Are there additional costs for email notifications?
A: Email notifications are included in all plans at no extra cost. SMS notifications count toward your monthly SMS limit.
Q: What happens if I exceed my SMS limit?
A: SMS reminders stop sending for the rest of the billing month. Email reminders continue. Upgrade to a higher plan for more SMS.
Q: Can I resend a failed notification?
A: Failed notifications are automatically retried. If they continue to fail, contact support.
Best Practices
Monitor Delivery
Check notification logs weekly:
- Identify failed deliveries
- Update invalid email addresses
- Verify SMS are within monthly limits
Keep Customer Info Updated
Encourage customers to:
- Provide a valid email address
- Verify phone numbers (for SMS)
- Update contact info if it changes
Test Notifications
Periodically test:
- Book a test appointment to receive booking emails
- Send test SMS from integration settings
- Verify emails don't land in spam
Plan for Busy Seasons
If you approach SMS limits during busy months:
- Upgrade temporarily to Pro plan
- Prioritize SMS for high-value bookings
- Rely on email for lower-priority reminders
Troubleshooting
Emails Not Delivered
Check:
- Customer email address is valid
- Emails not in spam folder
- Domain authentication is set up correctly
- SendGrid account is active
Solution: Contact support if emails consistently fail.
SMS Not Delivered
Check:
- Twilio credentials are correct
- Phone number is valid and not landline