Hotel Groups

Start with the collection.
Get to the right hotel.

Compare service activity and guest satisfaction across properties, then enter the hotel workspace that needs your attention. Each hotel maintains its own content and guest identity.

My Stay group dashboard showing three hotels, guest satisfaction, service workload, and guest activity

Actual My Stay screens · Demo property

Used by
Group & multi-property managers
Starting view
All hotels in the collection
Working detail
Individual hotel workspaces

01Portfolio comparison

Find the property that needs attention.

Follow service activity across properties and understand where attention is needed. Move into a hotel workspace with the correct operational context.

Compare in one reporting period
Portfolio summaries and hotel rows use the same selected period. Review open issues, outstanding requests, reservations and guest activity in context.
Go directly to the work
Select a property to open the relevant hotel workspace. The selected hotel stays explicit, with a route back to the collection.
The portfolio aligns hotels in a shared view with service workload and guest activity. View full screen
The portfolio aligns hotels in a shared view with service workload and guest activity.

02Property performance

Read the service behind the headline.

Look at guest satisfaction and service performance together. Give managers the detail to understand the experience each property is delivering.

Service and satisfaction together
Review request completion, issue resolution and guest satisfaction. Property-level views help explain which operation needs a closer look.
Follow the same thread
Move from the group comparison into local requests, reservations, guest feedback or content rather than starting the investigation again.
A hotel overview gives managers the property-level detail behind a portfolio comparison. View full screen
A hotel overview gives managers the property-level detail behind a portfolio comparison.

03Local content & identity

Let each property keep its character.

A shared platform does not require a uniform guest experience. Each hotel maintains its own brand, facilities, content, and local recommendations.

A local guest experience
Hotels maintain their own logos, colours, photography, facilities and recommendations. A resort’s programme can differ from a city hotel’s.
Visibility into publishing
Group content views show published and draft facilities, activities and events by hotel. Local teams manage the underlying content.
Each property maintains the facilities and experiences that appear in its guest app. View full screen
Each property maintains the facilities and experiences that appear in its guest app.

04Roles & access

Match access to responsibility.

Keep hotel data separate while giving authorised managers the oversight they need. Roles and property context define how people work across the collection.

Hotel data stays in context
Property-isolated data and role-based access define what authorised colleagues can see and manage.
Group oversight, local action
Managers can enter authorised hotel workspaces. Local teams continue using the operational tools for their own property.
Team roles define who works within each property’s operational context. View full screen
Team roles define who works within each property’s operational context.

In practice

Spot an exception. Open the right workspace.

The collection view gives direction; the property workspace gives the details to act.

The team’s side
The corresponding workspace gives staff the details to take it forward. View full screen
The corresponding workspace gives staff the details to take it forward.
  1. Compare your hotels

    Review service workload and satisfaction for the same reporting period.

  2. Choose the property

    Open the hotel that needs attention in the relevant operational context.

  3. Coordinate with the team

    Review the local work, let the responsible colleagues act and follow progress from the collection.

Your setup

Fit it to the way
your hotel works.

These are the decisions we work through together before rollout.

See the rollout steps
Your property structure
Map the hotels in your collection and the managers who need access to each one.
Local responsibilities
Identify who owns each hotel’s branding, publishing, guest services and daily operations.
Rollout scope
Agree the initial properties, service priorities and configuration needs. The proposal defines the rollout and any integration requirements.

Before you decide.

Practical answers about Hotel Groups.

Can individual hotels keep their own brand?

Yes. Each hotel can maintain its identity, imagery, services, facilities, and content while using the common platform.

How is hotel data separated?

The platform uses property-isolated data and role-based access. Authorised managers enter the relevant hotel context when working across properties.

Can we plan the rollout around our collection?

We map your properties, priorities, responsibilities, and configuration needs during discovery. The proposal defines scope and rollout for the group.

Where it connects.

Hotel Groups adds multi-property oversight to the same local tools. Hotel Operations supports day-to-day work, and Guest Engagement provides guest feedback and communication.

Hotel Operations

Request routing, team ownership and publishing.

Guest Engagement

Scheduled feedback, guest messages and offers.

Compare all products

Let’s make it work for your property.

Connect your collection, thoughtfully.

Explore Hotel Groups with a walkthrough of the workflows and configuration relevant to your hotel.

Book a personal demo