Guest details, without the chasing
Send each guest a personal link — no login — where they see their own reservation and fill in contact details, loyalty numbers, and travel. What they enter lands back on your guest list, and you can see who has filled things in and who you are still waiting on.
When you turn guest pages on for an event, each guest gets a personal link — private, no login, one link per person even when a stay spans two weekends. The guest sees only their own reservation and fills in their contact details, loyalty numbers, and travel; everything lands back on your guest list as they save it.
“I email three hundred guests for their details and spend the next three weeks copying replies into a spreadsheet.”
Each guest enters their own details on their personal page — contact information, loyalty number, travel — and every answer lands on your guest list the moment they save it, not in your inbox waiting to be re-typed.
“Guests keep asking me which hotel they're in and when check-in opens.”
The guest's page carries a 'your hotel' card — the address with a maps link, the front-desk phone, and check-in and check-out times. You fill those in once on the hotel, and every guest sees them.
“Half the email addresses I was given are wrong, so half the links go nowhere.”
A guest can correct their own email address right on their page. Blocks confirms the new address with a code, updates the reservation, and reissues the link to the right inbox — no change requests routed through you.
“I don't want guests seeing each other's rooms — or a link floating around forever.”
Each personal link shows one guest their own reservation and nothing else. You can copy, turn off, or reissue any guest's link at any time, so a stale link never outlives its welcome.
How do guests fill in their own details for a room block?
Guest pages are a per-event choice: turn them on for an event, and each guest on the block can get a personal link — private, with no login or account to create. One link per person, not per stay, so a guest working back-to-back weekends gets a single link covering both. When a guest opens their page, they see their own reservation — hotel, room, and dates — with fields for their contact details, loyalty numbers, and travel. Whatever they enter flows straight back to your guest list; there is no export to run or reply to copy out of an email thread. Booking confirmation emails carry a View your reservation button, so a guest you have already confirmed lands on their page without you sending anything extra. The work of collecting details moves to the people who know the answers — and the answers arrive already attached to the right reservation.
What does a guest see on their personal page?
Their own reservation, and only that — the hotel, the room, the dates of their stay. Alongside it sits a 'your hotel' card with the practical answers guests usually email you for: the address with a tap-to-open maps link, the front-desk phone number, and check-in and check-out times. You fill those in once on the hotel and every guest on the block sees them. Below the card are the guest's own fields — contact details, hotel loyalty numbers so the stay credits the right account, and travel: flights, ground transport, and the rest of how they are getting there. If the email address you were given turns out to be wrong, the guest can fix it themselves — Blocks confirms the new address with a code before updating the reservation and refreshing their link. What a guest never sees is anyone else's room, name, or details.
How do I see who has responded and who still owes details?
Your guest list carries the state of every link: who has been sent one, who has opened their page and filled things in, and who you are still waiting on. Each guest gets per-link controls — copy the link to resend it through your own channel, turn it off if it should no longer work, or reissue a fresh one if it has gone stale. When the deadline is close and gaps remain, reminders to everyone outstanding go out in one click — Blocks-branded mail that sends only when you click. The chasing that used to mean re-reading an inbox thread per guest becomes a column you can scan: filled in, waiting, never sent. And because answers land as guests save them, the picture is current every time you look, not as of the last time you did the copying.
How is a guest's personal page different from the department portal?
They are two of the three private surfaces a room block runs on, and each sees only its own slice. The department portal is for department leads: they submit room requests and guest names for their team, watch what is still outstanding, and never see another department's rooms. The guest's personal page picks up where the department portal stops — once a guest is named on a reservation, their page lets them finish their own details: contact information, loyalty numbers, travel. The hotel portal is the third surface, where the hotel receives and returns the rooming list. The three work in sequence rather than overlapping: leads put names on the block, guests complete their own records, the hotel gets the finished list. You stay in the middle with the full picture — and nothing a guest or lead enters changes a reservation you have not approved changing.
Frequently asked questions
Send each guest a personal link — no login — where they see their own reservation and fill in contact details, loyalty numbers, and travel. What they enter lands back on your guest list, and you can see who has filled things in and who you are still waiting on.
What is a guest self-service page?
Do guests need an account or a login?
Can a guest fix a wrong email address themselves?
Does the guest's personal page replace the department portal?
Is guest self-service on for every event?
Have more questions? Check our glossary of terms or get in touch.
More ways Blocks helps
Related terms
Bring us your next room block.
We’ll show you how Blocks turns one hotel contract into the live plan your team can run.