Your arrival instructions reached the person who booked. Not the person who arrived.

When someone books on behalf of others, arrival instructions often stop at the booker — not at whoever shows up at the door. That's where check-in chaos starts.

One a.m. Three guests at the wrong entrance. Confused. Tired. The person who had organized the stay — a colleague who booked for them — hadn't forwarded the arrival instructions and wasn't picking up the phone.

This isn't rare. Corporate bookings where an assistant books and the manager travels. Group trips where one person organizes and five arrive. Gift stays where one partner surprises the other with nothing more than an address. In every case, the platform account belongs to someone who isn't at the door at midnight.

The instructions reached the right inbox. They just reached the wrong person.

Booker–guest split is more common than it looks

For most short-term stays, the booker and the guest are the same. But a meaningful share of bookings works differently: corporate travel, group trips, gifts, third-party management.

In each case, the person holding the platform notification and the confirmation email is not the one standing outside your door with luggage and a dying phone battery.

What the standard flow assumes

The standard flow assumes a direct line between booker and guest. The platform sends instructions to the registered account. The host sends the pre-arrival message to that same account. Everything lands in one inbox.

It works perfectly when the traveler is the booker. It breaks, sometimes badly, when they aren't.

Three ways the chain breaks — same root cause

The unreachable intermediary. The booker has everything but isn't available when guests arrive. The forwarding gap. The booker meant to pass things along, but didn't. The third-party summary that misses what matters. The booker read the instructions, summarized them — and skipped the one detail that mattered.

All three share the same root cause: the host sent information to one person, assuming it would reach another. That assumption holds when they're the same person. When they aren't, it's a chain with a weak link in the middle.

Reaching the person who actually arrives

The fix isn't sending more information to the booker. It's building a flow that can reach the people who will actually be there — independent of whether the booker forwards anything.

How it works in StayFast

The key idea: the Stay Hub is not built around the person who booked. It's built around the stay.

The booker can be the guest, but they can also be a company, an assistant, a tour operator, a family member or a group lead. That's why the Stay Hub link needs to be able to reach the people who will actually live the stay, not just the booking holder.

If several people on the same booking need the information, they can open the same Stay Hub on their own devices, within reasonable limits. They don't need to create an account, and they don't need to be the person who booked. The property keeps working on the stay: dates, unit, useful information, requests and the phase of the trip.

To make this flow easier to manage, the host can also list Stay Hub Recipients: people to remember to share the stay link with, beyond the booking contact. It could be a colleague, a family member, a tour leader or a guest in the group.

These recipients don't become guest accounts and don't automatically identify whoever is using the Stay Hub. They serve the host as an operational reminder: the stay link needs to reach whoever will actually use it. From there, the host can copy the link or a ready-made message and send it through their preferred channel.

Names also need care: the name on the booking may only be the contact person. That's why, inside the Stay Hub, the main reference is the stay. The booker's name can appear as a booking reference, but it's not treated as a certain identity for whoever is reading.

Arrival instructions, rules, local tips, requests and — where appropriate and safe — stay-specific information are all available without going through the booker's account.

From there, the host can collect contacts for the people who will actually arrive and share the Stay Hub link with them through whichever channel fits best.

Where to start

• Ask for and note the right contacts early. Whenever a booking looks like a booker–guest split, ask right away who will actually arrive. In StayFast you can list these recipients next to the stay, so the Stay Hub link isn't tied to the booking contact alone.
• Build stay information that works even for someone who hasn't read anything in advance.
• Have a stay link that doesn't depend on the platform account.

Conclusion

Information sent to the booking account reaches the booker. Information delivered to the person who arrives reaches the person who arrives. Both are useful. Only one is reliable at one a.m.