For hotels, resorts, venues and transportation operators, a health check shows whether guest data, property access and group sales records are ready for the next busy season.
In hospitality and transportation, a health check focuses on guest and customer data arriving from many properties or locations, the sales teams booking groups, events and charters, and the service staff handling complaints and changes. We review how guest identities are matched, whether payment card details have crept into notes or cases, how property managers and franchise or partner users are limited to their own locations, and how booking and loyalty integrations behave. The findings are ranked by guest and payment risk first, followed by sales pipeline accuracy and technical debt left behind by past property openings or acquisitions.
Hospitality and transportation organizations are unusually distributed. Each hotel, venue, terminal or depot may have its own staff, systems and habits, and ownership structures often mix managed, franchised and partner locations. Staff turnover is high and seasonal, so user accounts accumulate quickly. Guests share card numbers and personal details over the phone and by email, and those details end up in whatever text box is nearest. Group and event sales run on long lead times with frequent date and room block changes. A useful review has to look at each location's footprint, not just the central configuration, because the risks tend to hide in local variation.
We search case comments, email messages, task descriptions and custom text fields for patterns resembling payment card numbers, and review whether attachments such as authorization forms are stored in Salesforce. Where exposure exists, we note how it got there and which process needs to change. The goal is to keep card data out of the org entirely, rather than trying to protect it once it arrives.
Sales managers, front office leads and franchise partners should normally see their own locations and shared regional accounts. We test that with sample users, review role hierarchies and territory rules, and check whether a departed employee at one property still has access. Reports and dashboards shared across the portfolio are examined to confirm they do not reveal guest details beyond what regional leaders need.
Group blocks, meetings, weddings and charter bookings move through tentative, definite and cancelled states, with dates and room counts changing along the way. We check whether stages, required fields and lost reasons are used consistently across properties, whether forecasted revenue reflects current blocks and whether duplicate accounts for the same planner or third-party intermediary are distorting production reports. Cutoff and attrition dates are sampled as well.
One guest can appear through reservations, loyalty enrollment, complaints and marketing lists under different emails or spellings. We measure duplication, review matching and merge rules and look at how loyalty status and preferences are stored. That tells you how reliable a single guest view is today and what would need to change before building personalization or AI-driven service on top of it.
We start with the central sales and marketing systems owner, then add a revenue or distribution lead and a few property-level users from different location types. Access is read-only and interviews are scheduled around peak travel periods and major events. Card data findings are shared immediately with your security team rather than held for the final report. The complete report groups results by central configuration and by location, so regional leaders can see which properties or depots need the most attention.
We check which guest and stay fields sync, how often, and whether the integration creates a new record for returning guests instead of matching existing ones.
Where group and event details live in a separate system, we confirm that bookings, status and revenue reach Salesforce accurately enough for pipeline reporting.
We review how loyalty status arrives and confirm that payment tokens, not card numbers, are the only card-related values stored in or passed through Salesforce.
Most hospitality organizations want Salesforce outside PCI DSS scope. That depends on processes as much as settings, since agents type card numbers into cases when there is no better option. The review identifies where that happens so security teams can close the gap with process changes and tooling.
Seasonal and temporary staff need access quickly and lose it just as quickly. Check whether provisioning is tied to your HR or identity system, whether shared logins are in use at front desks and whether frozen or inactive users still hold paid licenses.
Personalized offers and AI-generated guest responses depend on knowing who the guest is. If one traveler exists as several records with conflicting preferences, the experience will feel random. Resolve identity matching, consent flags and preference storage before connecting any personalization or agent tooling to guest records.
The review documents where they are and how widespread the problem is, then recommends a remediation path agreed with your security team. That usually means masking or deleting affected values under a controlled process, adding validation or detection to stop new entries and giving agents a secure way to take payments. Cleanup itself happens afterward, once the approach is approved.
Not necessarily, but franchise agreements usually limit what the brand and each owner can see. We compare actual visibility against those limits, looking at guest records, group accounts and reports. Where franchise users can reach another owner's pipeline or guests, we recommend specific sharing changes and flag the issue for your legal and franchise teams to review.
Yes. Charter, transit, rail and fleet operators face similar issues: distributed locations, shift-based staff, customer complaints tied to specific trips and integrations with booking or dispatch systems. We adapt the sampling to those processes and add a look at how trips, routes and vehicles are represented, since those models often grow without much design. Driver and crew access is reviewed as well.
It tells you whether the agent will have the right information and nothing more. We check knowledge articles for property-specific accuracy, test what guest data a low-privilege user can reach and look at how bookings and loyalty details are linked. The findings become a readiness list, so your first pilot does not stall on data problems.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.