AutoHost handles guest verification: ID collection, background checks, and screening before arrival. Connecting it to Bookboost means each guest gets their own check-in link inside a message you already send, rather than a separate email from another system.
There is nothing to switch on. You build the link yourself, using a token.
Building the check-in link
AutoHost gives you a base URL for your guest portal, along the lines of checkin.myawesomehotel.com. If you do not know yours, ask AutoHost for it.
Add the reservation ID token to the end of that URL:
checkin.myawesomehotel.com/{{connector.connector_reservation_id}}
Use that as the destination of a button or link in your campaign. When the message sends, Bookboost replaces the token with that guest's reservation ID, so everyone receives their own portal link.
What it is for
Automating ID collection and guest screening before arrival.
Taking verification work off the front desk.
Meeting security and compliance requirements without a manual step per guest.
Sending the check-in link inside a pre-arrival message the guest is already expecting.
What this does not do
The link is built by hand. There is no AutoHost picker in the editor. If the base URL is wrong or the token is mistyped, the guest gets a broken link and nothing warns you.
No data comes back. Bookboost sends guests to AutoHost. Verification results, ID checks, and screening outcomes stay in AutoHost.
It needs a connector reservation ID. The token resolves from your PMS connector, so a guest without one gets an incomplete link.
What to do next
Send yourself a test on a real reservation and click the link before putting it in a live campaign. A token that has not resolved is obvious in the URL.
Getting help
Open Help at the bottom of the left menu and choose Talk to Us, or email support@bookboost.io.