Customer Portal on Salesforce
Give customers a self-service place to view the Booking Ninjas information and actions you choose to expose, including bookings, invoices, payments, documents, account details, and requests.
Add self-service without separating customers from your operations.
Customer Portal is a Booking Ninjas Portal configuration for external self-service. It can surface selected bookings, account details, requests, invoices, payments, documents, services, and other records according to the modules and permissions in your setup.
The portal is the customer-facing layer. The Booking Ninjas modules behind it continue to manage the operational workflow.
Give Customers the Actions They Actually Need
Choose the records and workflows that belong in the customer experience.
Account & Profile
Let customers view or update permitted account and profile information.
Bookings
Show selected reservation information and booking actions where configured.
Billing & Payments
Surface selected invoices, balances, payment history, and payment actions.
Requests & Documents
Let customers submit supported requests and access selected documents.
Keep Portal Activity Connected to Staff Workflows
Customer actions can stay connected to the same records your team already manages in Booking Ninjas.
Customer Takes Action
A customer views information, updates a permitted record, submits a request, or uses another configured portal action.
Booking Ninjas Updates
The action connects to the relevant Booking Ninjas and Salesforce records behind the portal.
Staff Follow-Up
Configured requests, approvals, tasks, or other workflows can route the work to the appropriate team.
Customer Sees Status
The portal can expose approved status information as the underlying workflow changes.
Control What External Users Can See and Do
Access depends on the portal configuration, Salesforce permissions, and the records intended for external users.
- Configure external-user access for the portal experience.
- Control access to selected records, fields, documents, and actions.
- Show different information to different customer or account types where required.
- Support multiple properties, locations, accounts, or programs when the data model allows it.
- Keep relevant portal submissions connected to internal records and workflows.
- Scope Salesforce external-user licensing separately where required.
The Portal Is the Access Layer
The operational capabilities behind the portal come from the Booking Ninjas modules in your setup.
Customer Self-Service
External access, dashboard views, requests, documents, and other permitted customer actions.
Bookings & Billing
Booking Engine, Reservation System, availability, billing, invoicing, requests, contacts, and related Core workflows.
Memberships, Classes & Events
Add Membership, Class App, Event Management, or other extensions when those workflows belong in the portal.
Broader Messaging
Use Communication Hub separately when broader email, SMS, or WhatsApp communication is required.
Where Customer Portals Can Fit
Useful wherever customers, members, students, residents, or guests need ongoing self-service access.
Available on Salesforce AppExchange
Booking Ninjas is available on Salesforce AppExchange.
Customer Portal Pricing
Portal is a separate recurring extension.
Core Package
for 1–50 Active Bookable Units
- Booking Engine and Reservation System
- Availability and Rate Controller
- Billing and Invoicing
- Request and Contact Management
- Standard reports and dashboards
Customer Portal
per portal
- Customer self-service access
- Configurable dashboard
- Role-based portal access
- Selected requests and documents
- Connected Salesforce records
Core + One Portal
for 1–50 Active Bookable Units, before implementation and separately required services
- Core operating capabilities
- One Customer Portal
- Additional extensions optional
- Implementation quoted separately
- Third-party fees separate where applicable
Separate Self-Service vs Connected Customer Portal
The difference is whether customer activity stays connected to the operational records behind it.
| Capability | Separate Portal / Manual Process | Booking Ninjas |
|---|---|---|
| Customer self-service | May depend on another system or staff | Available through the Portal extension |
| Booking context | May require syncing or manual updates | Can connect to Booking Ninjas booking workflows |
| Requests | Often handled through email or forms | Can enter configured operational workflows |
| Billing | May require a separate billing portal | Can surface configured Booking Ninjas billing information |
| Permissions | Controlled in the external platform | Configured around the Salesforce environment |
| Reporting | Portal activity may stay separate | Available activity can stay connected to Salesforce reporting |
Frequently Asked Questions
Give Customers One Place to Get Things Done
Show us what customers need to access, what they should be able to do, and how your team handles the work behind it.