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.

Ask a hotel group's ops team what it actually takes to get a new local phone number live in Spain, and the answer is rarely about phones. It is about paperwork. A Spanish local number is not simply assigned. It is registered, province by province, against a real company identity and a real proof of address in that specific province, because Spanish telecom regulation treats a local number as evidence of a local presence, not a courtesy extension of a national one. For a group opening its third property in the country, or its fortieth, that becomes a job someone on the team quietly inherits: chase the documents, submit them to a carrier, wait, resubmit when something is rejected, repeat for the next province.
Most platforms leave exactly that job in your hands. GuestMaker doesn't.
The regulatory reality does not disappear, and it shouldn't. A local number tied to a real address in Baleares still requires proof of a real address in Baleares. What GuestMaker removes is everything that isn't legally necessary to repeat.
Submit your company's identity documents and a province's address proof once, and once that submission clears review, two things become true. First, claiming a second number within that same approved province stops being a paperwork exercise entirely. It becomes a single action, "claim another number," and the platform requests the new number directly rather than asking you to fill out a form it already has the answers to. Second, when you expand into a new province, the address proof for that new place is unavoidably fresh (a different province means a different local presence, and there is no shortcut around that), but the company identity you already proved once does not need to be re-uploaded and re-reviewed from scratch. The system recognizes an already-approved identity and skips straight past the document that would otherwise ask you to attach your incorporation certificate for the fifth time this year.
That distinction, between what has to be province-specific and what genuinely doesn't, is the whole design. A group running properties across Madrid, Baleares, and half a dozen other provinces isn't filling out the same form over and over with different postcodes. It's proving something once per real requirement, and reusing everything else, the same logic that lets a new property inherit its settings from the group instead of rebuilding them from scratch.
The button itself changed too, in a small way that says something bigger. It used to say "Reserve this number," which implied you were picking from a visible list of available numbers, holding one, and confirming it. That isn't what happens. A carrier assigns the actual number from its pool the moment you submit the claim. There was nothing to reserve, and nothing to browse. The button now says "Claim a phone number," because that's the true shape of the action, and status updates arrive on their own: a live check on demand when you want to know right now, a background sync running every fifteen minutes so nothing sits stale for hours, and a real webhook that reports a verdict the moment the carrier reaches one.
And a property is rarely a one-number problem. A resort with English-, German-, and French-speaking source markets doesn't want a single line that defaults to English and hopes for the best. GuestMaker lets one property hold several numbers at once, each wired to answer as that property, each ready to greet a caller in the language that number is meant for. Which process provisions each number depends on where it's based, since Spain's province-and-identity claim flow described above, or the standard flow used for numbers in other countries, but none of that shows up on the guest's end; they just hear a line that already sounds like it was built for them. The same idea holds inside a single property too, where a spa or restaurant can sound like itself, not just the front desk.
For groups operating well beyond Spain, this sits inside a wider footprint. Number provisioning spans a large set of countries, and Spain is the one where GuestMaker has done the work of turning a genuinely manual, government-adjacent process into something a hotel operations team can do themselves in an afternoon, not something they email a carrier about and wait on. If you want the fuller picture of how one number connects to one AI agent that actually knows the property and the guest, we've written about that architecture separately.
The second idea is a different shape entirely, and worth separating cleanly from the first, because it's easy to collapse "AI answers your phone" and "AI joins your voice call" into the same story. They aren't.
A guest browsing a hotel's website and chatting with its AI assistant can, mid-conversation, choose to talk instead of type. Not by being handed a phone number to dial. Not by opening a new tab or a separate app. A call option appears right inside the same widget they're already using, and choosing it starts a live voice conversation without the guest ever leaving the page.
What makes this worth explaining on its own is what travels with the guest when they make that switch. Everything the chat already knew comes along: their name and contact details if they've already shared them, the language they've been typing in, and their identity as a known contact if this is a returning visitor rather than a stranger. That identity is checked server-side against the hotel's own guest records before anything is trusted with it, so a returning guest's context can never leak across properties or tenants. The voice agent that picks up isn't starting cold. It can look up what this guest has asked before, across channels, the same guest memory that lets the guest record remember a conversation whether it happened by chat, WhatsApp, or a call last month. A returning visitor who chatted last week and calls today gets greeted by name, not asked to introduce themselves again.
The handoff runs in the direction the guest is already moving, and it also runs back. When the call ends, nothing forces the guest to start over. They can place another call, pick the chat conversation back up exactly where the voice call interrupted it, or start fresh if that's what they'd rather do. The call becomes one more turn in a single ongoing conversation with the property, not a separate, disconnected channel that happens to also involve an AI.
It's also careful about when it shows up at all. If a hotel's call center is outside its configured hours, not yet set up, or simply switched off, the option to call just doesn't appear. No greyed-out button, no apology message promising a callback. A guest never gets offered something the property can't actually deliver in that moment, which matters more than it sounds: a broken promise from an AI reads worse than no promise at all.
A hotel's phone line has always meant two separate things at once: the number a guest dials from outside, and the conversation a guest is already having that could become a call. Most platforms solve neither well. The first gets treated as an IT ticket a hotel group files and waits on, province by province, paperwork by paperwork. The second usually doesn't exist as a concept at all, because chat and voice are built and sold as two unrelated products that happen to share a logo.
GuestMaker treats both as the same underlying commitment: that whichever way a guest wants to reach a property, in whatever language they reach it in, the AI on the other end already knows who they are and where the conversation left off. A local number in the right province, answering in the right language, backed by an identity the property never had to re-explain. A voice call that starts from a chat message instead of a dial tone, carrying the whole conversation with it. Neither is the interesting part on its own. Together, they're what it actually means to give every property a phone line, rather than a phone number.
See how the full voice agent platform fits together, or get in touch to talk about what it takes to bring your group's properties onto it.
Twenty minutes, your real properties, no generic demo environment.