EXECUTIVE CASE STUDY • HOSPITALITY • CORPORATE GUESTS AND LOYALTY
How a business hotel keeps corporate guest profiles on its own server and automates the review loop
Corporate guests return — if the hotel remembers them correctly. That means holding preferences, company details and stay history somewhere reliable, and asking for a review at the right moment without a person remembering to do it. Hotel Palas Grand View runs both on a self-hosted CRM.
- Guest profiles stored on the hotel’s own server
- Review requests sent automatically
- Corporate accounts with stay history
The hotel’s challenge
Guest knowledge living in people rather than in a system
A returning corporate guest expects the hotel to know the company, the invoicing details and the preferences from last time. That knowledge sat with whoever was on shift, and reviews were requested when someone remembered.
Guest data is also personal data. Keeping it on a third-party platform raises a question the hotel would rather not have to answer, so the installation runs on the hotel’s own infrastructure.
Memory on shift
Preferences and company details were recalled by staff who had served the guest before, and review requests happened irregularly.
Profile on record
Each guest and corporate account carries its history and preferences, and the review request is triggered by the stay, not by memory.
Client testimony
“Looking after corporate business guests demands close attention. The platform gives us secure local storage of client profiles and automates the reviews module, raising loyalty to a high standard.”
Guest profiles, corporate accounts and an automated review loop
The installation holds guest and corporate accounts with stay history, preferences and invoicing details, on the hotel’s own server rather than a hosted platform.
The reviews module turns the follow-up into a process: after a stay, the request goes out automatically, and the responses attach to the guest record rather than to an inbox.
Modules in use
- Guest profiles — personal and corporate accounts with stay history and preferences.
- Reviews automation — review requests triggered by the stay, with responses stored on the record.
- Corporate accounts — company-level records for repeat business travel.
- Local data storage — the database on the hotel’s own infrastructure, access decided by role.
The modules are licensed separately, so an installation carries only what it uses.
See the pricingWhat changed in guest handling
A returning guest is recognised from the record rather than from a colleague’s memory, and review volume stopped depending on who was on duty. The guest data sits on the hotel’s own server, which answers the data-protection question before it is asked.
One-time licence
The platform and the active modules are paid once, not every month, for as long as the company uses them.
Unlimited users
People are added without a per-seat cost, so the licence never decides the size of the team.
Own infrastructure
The installation and the database sit on the company’s own server, so the data stays where the company put it.
Related case studies
Other companies running on Zarina CRM
Sixteen deployments across eleven industries, each with the company named and the workflow described, so you can find one close to your own.
STRATEGIC PARTNERSHIP • ENTERPRISE
Move your operation onto a platform you own
The editions, the modules and the one-time licence are the same ones used in this deployment. The installation sits on your server, the users are unlimited, and the licence is paid once.
- Installed on your own server
- Unlimited users
- One-time payment