A hotel's spa or restaurant can carry its own agent name, voice, hours, and rules in GuestMaker, inherited from the property by default until one field is deliberately changed.
Call a hotel's spa to ask about a couples massage, and you expect someone who actually works at the spa. You do not expect a switchboard voice that recites the lobby brochure, or worse, a pitch for every other property the parent company happens to own, before it gets around to answering your question. Call the golf course to ask what time the pro shop opens and you want an answer about the golf course, in a voice that sounds like it belongs there, not a copy of whoever answers reception at 2am.
That mismatch is common enough in hotel voice AI that GuestMaker built around avoiding it. One Number, One Brain covered the first half of the fix: a venue like a spa, a restaurant, or a golf course can get its own phone line, and a call to that line is answered by an agent that knows exactly which place picked up, drawing on that venue's own knowledge rather than the hotel's whole catalog blended together. That solves who answers and what they know. It does not, on its own, solve how they sound.
Once a venue has its own line, a handful of further questions follow immediately. What does the agent call itself when it introduces itself? What voice does it speak in? When is the venue actually open, since a spa that closes at 8pm and a front desk that never closes cannot share one honest answer to "are you open right now"? And what does a caller hear in the first two seconds, before any of that comes up? How a venue gets that number in the first place, claiming one line per property rather than sharing one switchboard, is a separate piece of the puzzle. This one picks up once the line already exists and is ringing.
GuestMaker treats all four, agent name, voice, business hours, and greeting, as properties that belong to the venue itself, separate from the hotel it sits inside. A restaurant can introduce itself by its own name instead of the hotel's. A spa can run in a calmer, quieter voice than the pool bar fifty meters away. A golf course can keep hours that track daylight rather than a 24-hour reception desk. None of that has to look, sound, or behave like the property around it unless someone decides otherwise.
None of this demands new setup work. A venue's configuration lives right alongside its hotel's, structured the same way and resolved the same way: check the venue first, fall back to the property if the venue has not set anything, fall back again to the group default if neither has an opinion. A venue that has never been touched behaves exactly like its property, down to the byte. That is deliberate. A group running a dozen restaurants across four hotels should not have to make a dozen decisions about voice and hours before any of them can take a single call. Most venues never will need to. They will simply answer as a slightly more specific version of their hotel, and that is a perfectly good default. That same fallback chain is what lets a new property join the phone tree correctly from its very first call, one level up from hotel to venue.
What changes is one field at a time, only where somebody has a reason to change it. Give the spa a different voice than the property default. Rename a restaurant's agent to the restaurant's own name. Trim a golf course's hours to actual daylight. Each override is independent of the others, so a group can hand-tune the one venue that genuinely needs to sound different and leave every other venue running quietly on inherited settings, at zero ongoing configuration cost. Two venues at the same hotel are also resolved and cached separately from one another, so setting the restaurant's voice never risks bleeding into the spa's line just because the two share a building and an address.
A caller's first impression of a venue is its greeting, and a generic one does real damage. The failure mode is easy to end up in by accident: a group writes one polished opening line for its voice agent early on, that line names the whole company, and nobody revisits it venue by venue as new lines get added. The result is a caller who dialed a single restaurant hearing a rundown of how many hotels the group owns before anyone asks how they can help.
GuestMaker checks whether the greeting configured for a hotel or venue actually names the place the call reached. When it does not, meaning nobody has written a specific one and the fallback is still the group's general opening line, the agent builds its own greeting from the venue's resolved name instead of reciting the wider pitch. A caller who reached the restaurant hears that restaurant welcome them by name. If a tenant has already written a real, specific greeting for that venue, that exact greeting is used, unchanged. The system only steps in for the gap nobody has filled; it never overwrites a real answer with an invented one.
Business hours had a version of the same gap, but only at the edge case of a venue with no single owning hotel, a golf club or spa run at the group level rather than attached to any one property. That kind of venue previously had no reader for its own time zone at all, so it fell back to an arbitrary hotel's clock and could be told it was closed during its own actual opening hours. Time zone now resolves for a group-level venue on its own terms, so "are you open right now" gets answered against that venue's own hours rather than a hotel's picked at random.
Voice and hours are not the only thing a venue can hold apart from its property. The rules that shape how the agent behaves, the guidance a tenant writes to define tone, policy, and boundaries, follow the same layered logic: group, then hotel, then venue. A rule written for one specific venue outranks the general rule written for the hotel it sits inside, but only on that venue's own line.
That distinction earns its keep at exactly the venues that are, in practice, run to a different standard than the property around them. A spa that operates more like an independent wellness clinic than a resort amenity, with its own cancellation and rebooking language. A fine-dining restaurant that holds a stricter reservation policy than the hotel's front desk ever applies to a room booking. A late-night lounge with its own age and conduct expectations that would be out of place applied to the whole hotel. Each of those can carry its own guidance, followed exactly on that specific line, without touching, softening, or overriding the hotel's general policy anywhere else.
It works in one direction only, by design. A rule scoped to a particular venue fires only when a caller has actually reached that venue's own line. It does not spill onto the hotel's main number, and it does not cross over to a different venue at the same property, even one under the same roof. The restaurant's cancellation policy never starts quietly governing the spa next door. Broader rules, written at the hotel or group level, still reach every call beneath them exactly as before; a venue only ever adds something more specific on top, it never removes a protection the wider group already put in place. That one-way boundary, where a general rule reaches down but a specific one never reaches sideways or up, is the same discipline behind how GuestMaker keeps AI safe with real guests more broadly. Scope is a boundary, not a suggestion.
The overall shape is worth saying plainly, because it is easy to undersell: nothing here asks a hotel group to do new work up front. Every venue starts identical to its property in name, voice, hours, and behavior, so adding a venue costs nothing operationally until the day someone decides it should sound, or act, differently. At that point it is one field, changed once, and every call to that venue's line reflects it from the next ring onward.
A guest calling a hotel's front desk should hear the hotel. A guest calling its spa should hear the spa, in the spa's voice, on the spa's hours, held to whatever standard that spa actually runs on. GuestMaker's voice agent makes that the default rather than a bespoke project reserved for the one location important enough to demand it.
Thirty minutes, your real properties, no generic demo environment.
How GuestMaker's voice agent inherits settings from group to hotel to venue, so a new property answers calls correctly on day one, no rebuild required.
Most hotel phone lines go unanswered, are picked up blind, or recite a script. GuestMaker's voice agent gives every property and venue a real memory instead.
Spain makes a hotel group register a local phone number province by province. Most platforms leave that paperwork to you. GuestMaker turns it into a claim button, and lets a website chat become a live call without a dial tone.
