Push Notification & SMS Workflows on Salesforce
Connect in-app notices, mobile push where supported, SMS messages, reminders, and alerts to the booking and operational workflows your team manages in Salesforce.
Use different notification channels for different operating needs.
Booking Ninjas can connect communication workflows to Salesforce and operational records so suitable alerts, reminders, notices, or messages can be triggered by bookings, payments, requests, events, memberships, and other configured activity.
In-app messaging can be configured inside supported Booking Ninjas experiences. SMS can be handled through Communication Hub. Mobile push notifications depend on the mobile application, device permissions, push provider, and integration used in the implementation.
Show In-App and Mobile Notifications Where Supported
Use notification rules around the user experience instead of assuming every message belongs in email.
In-App Notices
Show configured guidance, reminders, or announcements inside supported Booking Ninjas experiences.
Mobile Push
Use mobile push where the required application, device permissions, provider, and integration are available.
Workflow Triggers
Use supported operational events and record conditions to start configured notification workflows.
Audience Rules
Use suitable customer, member, user, location, role, or workflow data to determine who should receive a message.
Add SMS for Outbound Reminders and Updates
Use Communication Hub when operational workflows need broader outbound SMS communication.
Transactional Updates
Send suitable booking, payment, request, event, or other workflow messages when SMS is configured for that operating process.
Reminders
Schedule configured reminders before appointments, bookings, events, classes, deadlines, or other supported activities.
Preferences
Use available opt-in, opt-out, or communication-preference data when configuring SMS workflows.
Delivery Context
Review available delivery or provider information where the messaging service makes that data available.
Manage Notification Rules in a Structured Workflow
Control who communicates, which workflow triggers a message, and when internal review is required.
Message Ownership
Assign responsibility for selected notification templates and workflows.
Approval Steps
Add internal review or approval where a message should not be released automatically.
Scheduling
Use configured dates, times, or workflow conditions for selected notifications.
Reporting
Use the notification and provider data captured by the implementation for operational reporting.
Coordinate Communication Across Supported Channels
Different channels can serve different purposes without requiring every message to be duplicated everywhere.
- Use in-app messaging for contextual guidance while a user is already inside a supported experience.
- Use SMS for suitable outbound reminders or transactional updates.
- Use email for confirmations, documents, detailed information, and other configured communication.
- Use WhatsApp through Communication Hub where that channel is part of the configured workflow.
- Use mobile push only where supported application and push infrastructure are available.
- Keep communication history close to the related Salesforce records where provider data is available.
Keep Preferences and Governance Connected
Use available consent, preference, permissions, and workflow information when configuring communication.
Communication Preferences
Store configured channel preferences with the appropriate customer or user record.
Consent Data
Use available consent or opt-in information when defining outbound communication rules.
Administrative Access
Use Salesforce permissions around the records and administration involved in messaging workflows.
Message History
Keep available communication activity for operational review and reporting.
Review the Notification Data Available in Your Setup
Reporting depends on the channel, provider, and interaction data captured by the implementation.
- Notification type
- Configured audience
- Workflow trigger
- SMS delivery data where available
- In-app interaction data where captured
- Push-provider data where integrated
- Communication preferences
- Salesforce reports and dashboards
Optional AI-Assisted Messaging Analysis
AI can assist with drafting and historical analysis when separately scoped. It does not guarantee engagement, delivery, or the best channel or send time.
Draft Assistance
Generate draft notification copy from suitable business context for human review.
Activity Summaries
Summarise available notification and communication activity for internal review.
Historical Patterns
Review suitable historical communication data for recurring engagement patterns.
Follow-Up Support
Help staff organise communication records that may need additional human follow-up.
Connect Notification Workflows to the Rest of Booking Ninjas
Use communication alongside the booking, customer, billing, portal, and operational workflows that create the message context.
Notification Workflows Connect Communication to Operations — They Do Not Replace Every Messaging Platform
Booking Ninjas can coordinate in-app notices, SMS, email, WhatsApp, workflow triggers, audience rules, preferences, and communication reporting where the required modules and services are configured. Mobile push requires supported application and push-notification infrastructure. Specialist mobile engagement, marketing automation, notification delivery, customer engagement, or messaging platforms can remain in place where broader capabilities are required. Delivery, reach, engagement, and compliance outcomes are not guaranteed.
Available on Salesforce AppExchange
Booking Ninjas is available on Salesforce AppExchange.
Push Notification & SMS Pricing
SMS, email, and WhatsApp use Communication Hub. Mobile push and in-app notification workflows are scoped around the experience and infrastructure required.
Email, SMS & WhatsApp
£100/monthper organisation
- Up to 5,000 emails
- Up to 500 SMS messages
- Up to 500 WhatsApp messages
- Configured communication workflows
- Customer and operational context
Configured for Your Experience
Implementation-basedThere is no separate fixed public mobile push or in-app notification add-on price listed here.
- Notification rules and triggers
- Audience configuration
- In-app message placement
- Mobile push integration where required
- Preference and permission logic
- Testing and rollout
Booking Ninjas Core
for 1–50 Active Bookable Units when communication is connected to Booking Ninjas booking and reservation workflows
- Booking Engine and Reservation System
- Availability Management and Rate Controller
- Billing and Invoicing
- Request and Contact Management
- Standard reports and dashboards
- Basic transactional communication
Separate Messaging Tools vs Connected Notification Workflows
Both approaches can work. The main difference is how closely communication is tied to operational records and workflow context.
| Capability | Separate Messaging Platform | Connected Operational Setup |
|---|---|---|
| Message triggers | Operational data may need to be synchronised into the messaging platform | Configured Salesforce and Booking Ninjas events can provide workflow context |
| In-app messaging | Specialist engagement platforms may provide broad in-app tooling | Selected notices can be configured inside supported Booking Ninjas experiences |
| SMS | Handled through a dedicated messaging provider or platform | Communication Hub can support configured SMS workflows |
| Mobile push | Often provided through specialist mobile engagement infrastructure | Can be integrated where the required mobile app and push infrastructure exist |
| Preferences | Preference data may be maintained in the messaging platform | Available communication preferences can remain close to Salesforce records |
| Reporting | Messaging and operational reporting may remain separate | Available communication data can be reviewed with Salesforce reporting |
Frequently Asked Questions
Connect Notifications to the Work That Triggers Them
Show us which alerts and reminders you send, who should receive them, and which booking or operational events should trigger each message.