A guest books two hotels from the same group in the same month. At one, the assistant knows the parking arrangement, the late check-out policy and the dog charge. At the other, it answers vaguely and promises a call back that never comes. The guest concludes the brand is unreliable, not that one property maintains its website better.
Consistency is a brand promise, and for hotel groups it is largely a content problem.
Where inconsistency comes from
Properties are often acquired, each with its own website history. Policies differ for legitimate reasons, such as parking or accessibility, and for illegitimate ones, such as nobody having reviewed them since. Group-wide information like loyalty schemes or cancellation terms is duplicated and drifts out of sync.
What should be consistent
Tone of voice, how questions are escalated, how quickly guests are promised a response, group-wide policies such as loyalty, gift vouchers and corporate rates, and the categories of information every property publishes.
What should be property-specific
Parking, breakfast times, accessibility, pet policies, check-in and check-out times, facilities, restaurant opening, local recommendations and event spaces. Forcing these into a generic answer is what makes guests feel unheard.
The framework approach
Define a standard set of questions every property must answer on its pages. Then each property fills them in. The assistant answers from that property's content, in the group's voice, with the same escalation rules everywhere.
Rolling it out
Start with one property, refine the framework there, then replicate. Trying to launch across twenty properties at once produces twenty different implementations, which is the problem described in how to roll out a chatbot across a multi-property group.
Guest: Can I check in early at your Brighton property? Assistant: The Brighton hotel's page explains that early check-in is subject to availability and can be requested before arrival, with the fee shown if a room is held from the morning. Group-wide, your booking can be modified up to the time listed in the cancellation policy. Would you like me to pass an early check-in request to the Brighton team?
Escalation consistency
Guests should experience the same handover everywhere: a clear statement that a person will respond, and a realistic timeframe. Inconsistent escalation is more damaging than inconsistent detail.
Group and event enquiries
High-value enquiries must route to the right team fast at every property, as described in group and event enquiries hotels should answer first.
Independent character
Boutique and independent properties within a group worry about sounding corporate. The framework should specify structure, not personality, which is the balance covered in choosing a website assistant for a boutique hotel.
Other multi-site groups
Dealer groups face the identical problem across sites, as described in dealer groups and consistent answers across sites.
Answering across properties
SpideyChat for hotels and hotel groups lets each property answer from its own published pages while sharing a common voice and escalation path, so a guest gets the Brighton answer at Brighton and the same standard of service everywhere. Properties keep their character, and the group keeps its promise.
Maintaining it
Assign each property an owner for its content and review it quarterly. Answers are only as good as the pages behind them.
Getting started
Agree the framework, pilot at one property, then roll out with property-specific content. The guides to installing the widget and training your bot explain how.