A digital guidebook for every guest
TravelPal gives every guest a digital guidebook: a private web page for that one stay, branded as your company and created automatically when the booking syncs in from your property management system. There is no app and no login; the link itself is the guest's key, and it is sent where the guest already reads.
4:00 PM
11:00 AM
Styled after the live guest guidebook.
The stay as a ticket: nights, countdown, and check-in and check-out times
The stay renders as a ticket: the number of nights, a countdown, and oversized check-in and check-out dates with the reservation's own planned times, read live from your own system. Around it sit the address, a styled map with your own pin, and one-tap directions. A button adds the stay to the guest's phone calendar.
How the guidebook link reaches the guest
You never mint a link, and a guest never hunts for one. Every confirmed booking gets its own, and it travels the channel that booking came from.
Sent where they already read
Airbnb guests get their link in their Airbnb thread; everyone else gets it by email. Every send goes out through your own connected account, never around it, so your team's inbox shows exactly what each guest was told.
Sent on your schedule, in the property's timezone
Two automated messages exist: an intro shortly after booking and a pre-arrival reminder timed from a lead you choose, computed in the property's own timezone and held to daytime hours. Nothing messages a real guest until you turn sending on.
Inside your own message templates
TravelPal writes an id onto the reservation as a custom field, so the message automations you already run in the system you already use can carry each guest's live link inside your own words.
A QR card in the unit
A printed QR card gives guests a second way in: they type the email or phone they booked with and get their own stay link back. Only active, confirmed stays at your company can match; a finished stay, and every other company's guests, are invisible.
A link that expires after checkout
A cancellation revokes the link immediately, and it expires shortly after checkout, so a forwarded or leaked link is worthless within days. Expired and canceled links get honest, distinct messages, not an error page.
Private, and never indexed
Guidebook pages are never indexed by search engines, because a stay link is a private credential. The page shows branding and display facts only: door codes, the house manual, and your team's contact data never render on it.
The way back to a human is channel aware: Airbnb and Booking.com guests get a link back to their own booking thread, and direct guests get a message box that reaches your team with the guest's stay attached.
What the guidebook sells: four bookable extras
The guidebook sells early check-in, late checkout, an extra mid-stay cleaning, and a damage waiver, each at the prices you configured.
Arrive earlier, stay later. Early check-in and late checkout render as a ladder of tappable time chips, each a real clock time with its exact price, computed from the reservation's live planned time so a guest is never quoted a time they will not get.
Mid-stay cleaning, on a real slot. The guest picks a day and an exact hour, because a specific time is what your crew is dispatched on. Checkout day is excluded, since that clean is the turnover.
The damage waiver. A one-time, non-refundable charge covering accidental damage, offered instead of the refundable security deposit. It covers the whole stay, so it asks for no date.
One rate card with the chat. The page prices through the same quote engine as the AI in chat, so the guidebook and the concierge can never quote two different numbers. Prices are read live on every load.
Availability is real, not decorative: the same checks the chat sales path runs decide what the page may offer, and an extra that is not available for the dates is simply absent. The hours your cleaning crew needs for a turnover are never sold; the chat side of the same engine is covered in how upsells work.
How guests pay in the guidebook
Before a guest commits, the card tells them what happens next, and which payment route applies is decided per stay on the server, never guessed from the booking channel.
Stripe checkout in the browser
Your Stripe account, never TravelPal's
Reservation updates automatically
A card link that settles itself
The guest gets a Stripe checkout for the exact item and amount, pays in the browser, and is returned to their own stay page. When the payment lands, the reservation updates itself in the system you already run, with nobody at a keyboard.
Your Stripe account, not ours
The money goes to your company's own Stripe account, never TravelPal's. The revenue is yours.
How Airbnb guests pay is your choice
You choose how Airbnb guests pay, per surface: keep it inside Airbnb's own flow, use card links, or mix the two. The full story is on collecting payment from Airbnb guests.
Never a broken link
If no payment route can be built for a stay, the guest is told plainly that your team will follow up with how to pay. A deadline shown to a guest is one the sales engine itself enforces, and a refused purchase is never rendered as bought.
Concierge services and Viator experiences in the guidebook
Below the extras, the guidebook carries your own service catalog, and the AI concierge chat opens the destination.
Your services, as photographic tiles. Your catalog renders as image tiles that open into real inventory: name, photo, features, and a price or "on request". Items you disable never reach a guest.
Ask the team, not a buy button. These are things a person confirms, so the button says ask, not book. The request reaches your team with the guest's pick named, and nothing is charged from the guidebook itself.
A hold, not a charge. When a booking request is made through the concierge chat, the guest's card is held, not charged. Money moves only when your team confirms, and an untouched hold releases itself.
Tours and experiences through Viator. Guests can discover and book local tours and experiences from Viator, with photos, star ratings, review counts, and from-prices. Booking completes on Viator's own site.
Everything the guidebook sells is a paid guest service or a stay change during the stay; it does not take booking payments. How Airbnb guests in particular pay for services is covered in how Airbnb guests pay for upsells.
Guidebook FAQ
Do guests need to download an app?
No. The guidebook is a private web page for that one stay, opened from a link. There is no app, no login, and no password: the link itself is the guest's key, and guidebook pages are never indexed by search engines.
How do guests get the link?
Where they already read. Airbnb guests get it in their Airbnb thread and everyone else by email, and every send goes out through your own property management system, so your own inbox shows what each guest was told. You can also drop each guest's link into the message automations you already run there, or put a QR card in the unit.
What happens to the link after checkout?
It dies on its own. A cancellation revokes it immediately and it expires shortly after checkout, so a forwarded or leaked link is worthless within days. An expired link gets an honest message, not an error page.
Who gets the money when a guest buys something?
You do. Card payments go to your own Stripe account, never TravelPal's, and the reservation updates in your own booking system automatically once the payment lands. TravelPal charges a flat $25 per unit per month and takes no commission on upsells.
Updated