Canadian Cancer Society required a lodge-management system built around people whose accommodation journey does not behave like a normal hotel stay.
Canadian Cancer Society provides lodge accommodation for people who need to travel away from home for cancer treatment, with support designed for patients and caregivers during their stay.
Booking Ninjas worked through a detailed solution design for extending the organisation's Salesforce environment with reservations, lodge inventory, payments, operational workflows, and reporting.
The challenge: the person mattered beyond one reservation
A conventional lodging system often centres the operation around a room reservation.
Canadian Cancer Society needed a broader model.
A guest could return for another stay. A caregiver could be connected to the accommodation. Beds and rooms needed availability. Payments could come from different sources. Operational restrictions and history also needed to remain visible over time.
- Guest and caregiver profiles
- Returning guests
- Rooms and beds
- Availability and waitlists
- Check-in and checkout
- Payments and third-party billing
- Operational status
- Management reporting
The formal requirements also reached into areas such as communications, bilingual operation, security, custom fields, dashboards, and integrations.
The direction: extend Salesforce instead of creating another guest database
Canadian Cancer Society already had a Salesforce environment.
Booking Ninjas proposed adding the lodge and reservation layer around that foundation instead of introducing another isolated application with another copy of the people the organisation already knew.
That is important when accommodation is only one part of a much wider relationship with the organisation.
Booking Ninjas' current Reservation Management works directly with Salesforce data, workflows, security, automation, and reporting rather than requiring a separate reservation database.
Learn more about the wider concept in What Is a Salesforce Org? .
A returning guest shows why the connected model matters
The clearest workflow is a person returning for another lodge stay.
Start from the existing guest or client profile instead of rebuilding basic information.
Add the new reservation while keeping it connected to the person's previous history.
Use the appropriate room or bed based on availability and applicable operating rules.
Keep the relevant payment or third-party billing information connected to the stay.
Manage arrival, departure, status, and reporting without separating the stay from the person.
How the solution direction fit the lodge operation
| Lodge need | Booking Ninjas direction | What it could make easier |
|---|---|---|
| Keep guest history | Salesforce Customer Record | A returning person could remain connected to previous and future stays instead of being treated as a new isolated reservation each time. |
| Manage lodge stays | Reservation Management | Reservations, changes, status, rules, and operational information could stay in one structured workflow. |
| Control room and bed availability | Availability Management | Accommodation availability could follow actual inventory, occupancy, restrictions, and reservation activity. |
| Handle excess demand | Waitlist Management | Demand that could not immediately be accommodated could remain structured instead of disappearing into informal follow-up. |
| Manage arrival and departure | Check-In & Check-Out | The lodge could track where a stay sits in its lifecycle and keep status connected to the reservation. |
| Handle different payment sources | Payment + Billing Workflows | Payments and third-party billing could remain associated with the correct person and stay. |
| Give management usable data | Salesforce Reports + Dashboards | Operational and management questions could be answered from the same underlying lodge and guest records. |
The person could stay at the center of the system
A room is temporary.
The relationship with the person may continue before and after that room assignment.
This matters particularly for an organisation serving people who may return for treatment-related stays or interact with other support services over time.
A Salesforce-based customer record gives the lodge another way to organise that history: the reservation belongs to the person rather than becoming the person's entire identity inside the system.
The Booking Ninjas Knowledge Center explains this model in What Is a Customer Record? .
Room and bed availability needed more than an occupied-or-empty flag
Specialised accommodation can involve restrictions, assignment rules, different bed configurations, pending stays, waitlists, and operational status.
That means availability needs to reflect more than whether a room appears empty on a calendar.
Booking Ninjas' current Availability Management connects availability directly with Salesforce workflows, restrictions, capacity, inventory, and reporting. :contentReference[oaicite:2]{index=2}
For Canadian Cancer Society, the design direction was to make accommodation availability part of the same wider lodge environment as the reservation and person.
The payment relationship could also follow the stay
Not every accommodation payment has to come directly from the person occupying the room.
Canadian Cancer Society's requirements included third-party payment scenarios alongside the normal billing workflow.
That creates another reason to keep the person, stay, invoice or charge, and payer relationship connected rather than treating payment as an unrelated transaction.
Operations could share the same lodge picture
Accommodation operations continue after a reservation is created.
Staff need to know who is arriving, who has checked in, what accommodation is occupied, what is becoming available, and what needs attention before another person can use it.
The Canadian Cancer Society requirements also considered housekeeping-related status, communications, operational restrictions, and management reporting.
A connected Salesforce model gives those workflows a common record structure instead of asking each team to maintain its own version of what is happening.
What the engagement demonstrated
The available material does not prove that Booking Ninjas became Canadian Cancer Society's production lodge-management platform, so this story should not claim a completed rollout or quantified results.
The meaningful result was translating the organisation's requirements into a structured Salesforce-native solution direction.
Guest history and future stays could be organised around one continuing profile rather than separate reservation identities.
Rooms, beds, reservations, availability, restrictions, and waitlists could be considered as parts of the same accommodation model.
The design could account for situations where the person staying and the party responsible for payment were not necessarily the same.
Arrival, departure, status, accommodation, and other lodge activity could use the same operating foundation.
Dashboards and reports could use the same Salesforce records supporting lodge activity instead of depending on another reporting database.
The solution could be shaped around patient and caregiver accommodation rather than assuming a leisure-hospitality workflow.
The system should adapt to the lodge, not turn the lodge into a hotel
Canadian Cancer Society's accommodation exists for a specific purpose.
Its guests, rules, payment relationships, support environment, reporting needs, and multi-location operation are shaped around that purpose.
Booking Ninjas can use Salesforce as the foundation and then configure reservation rules, fields, workflows, permissions, dashboards, and integrations around the organisation.
That is the broader lesson: an organisation can use professional reservation technology without having to operate like the industry template the software was originally designed around.
Why the use case fits Booking Ninjas today
Booking Ninjas now explicitly supports complex booking environments across multiple locations, facilities, resources, programs, and stakeholders. :contentReference[oaicite:3]{index=3}
Reservation Management can provide the core stay record. Availability Management can control rooms, beds, capacity, and restrictions. Waitlist Management can structure excess demand. Check-in and checkout can track the stay lifecycle. Salesforce records, workflows, and reporting can connect the wider operation.
That makes the Canadian Cancer Society engagement a useful example of where Booking Ninjas is strongest: when booking is only one part of a more complicated operational relationship.
Learn more about the connected lodge model
See how several bookings and other approved activity can stay connected around the same person or organisation.
What Is a Customer Record? →See how inventory, capacity, restrictions, and booking activity determine whether accommodation can actually be assigned.
How Availability Is Managed →See how reservations, changes, operational rules, availability, and reporting stay connected directly inside Salesforce.
Explore Reservation Management →About this story: Canadian Cancer Society engaged Booking Ninjas around a detailed lodge-management solution covering client profiles, reservations, rooms and beds, availability, waitlists, payments, operational workflows, reporting, security, bilingual requirements, custom fields, and integrations. The available material supports detailed solution design and implementation planning, but does not establish a completed production rollout or measured post-launch results.
Your accommodation program does not have to behave like a hotel.
See how Booking Ninjas can connect people, stays, rooms, beds, payments, availability, operations, and reporting around the way your organisation actually provides accommodation.
.jpeg)
.jpg)
.png)
