If your property uses Mews, the door PIN codes Mews generates for each guest can now flow straight into Bookboost. Bookboost reads these codes from Mews and stores them on the guest profile as access tokens, so you can include a guest's PIN in a pre-arrival message or show it in the digital reception automatically. For properties that were looking up codes in Operto by hand, this removes that step.
How it works
PIN codes sync from Mews. Bookboost fetches Resource Access Tokens directly from the Mews Connector API and maps them onto the guest profile as access tokens.
The PIN becomes a usable token. The door PIN code (held in Mews on the guest record) is surfaced as a token you can drop into guest communications and into the digital reception experience.
Old codes are cleaned up automatically. Each time the data resyncs, stale or duplicate codes of the same type for the same guest are removed, so the profile only carries the current code.
Where to find the token
When you build a message or a digital reception, add the PIN code by inserting the token. Go to Token > Mews and choose one of two options depending on what you want:
Resource Access Token — the access token of a specific guest to a reservation space. Token text:
{{mews.guest_resource_access_token}}Valid Resource Access Token — the access token of a specific guest to a reservation space, limited to within its validity timeframe. Token text:
{{mews.guest_resource_access_token}}
Pick Valid Resource Access Token when you only want the code to appear while it is inside its valid window; pick Resource Access Token for the code regardless of the validity timeframe.
Before you start
Your property is on the Mews PMS integration. This feature only works for properties using Mews.
Resource Access Tokens are enabled in your Mews configuration. The PIN code has to be available from Mews for Bookboost to sync it.
If you are not sure either of these is set up, contact support and we will check for you.
What you can do with it
Send door PIN codes in pre-arrival messages. Include the guest's code in the automated message they receive before they arrive, so they can go straight to their room.
Show access codes in the digital reception. Display the PIN as part of the guest's digital reception experience.
Retire manual Operto lookups. Properties already running Mews and Operto together no longer need to look codes up by hand.
What to expect
The code comes from Mews. Bookboost surfaces the PIN that Mews holds for the guest, so the code you send always matches what the lock expects.
It refreshes on resync. When guest data resyncs, the current code stays and any stale or duplicate codes are cleared out.
It works in messages and the digital reception. Once the code is on the profile, you can use it as a token in guest communications and in the digital reception flow.
Known limitations
Mews only. The feature is available for properties on the Mews PMS integration and not for other PMS integrations.
Depends on Mews returning the code. If the Mews Connector API does not return a valid Resource Access Token for a reservation, there is no code for Bookboost to sync.
What's next
We are looking at supporting more token types from Mews Resource Access Tokens, such as parking codes and locker codes, so more of a guest's access details can flow into Bookboost the same way.
Common questions
Do I need Operto for this?
No. The PIN codes come from Mews directly, so a separate Operto integration is not required. If you already use Mews and Operto together, you can stop looking codes up manually.
Which properties can use this?
Properties on the Mews PMS integration with Resource Access Tokens enabled in their Mews configuration. Contact support if you are unsure whether your property qualifies.
Which token should I use, Resource Access Token or Valid Resource Access Token?
Both are found under Token > Mews and both use the token text {{mews.guest_resource_access_token}}. Use Valid Resource Access Token if you only want the code shown while it is within its validity timeframe, and Resource Access Token if you want the code regardless of the validity window.
Where does the PIN code come from?
From Mews. Bookboost reads it through the Mews Connector API and stores it on the guest profile as an access token.
What happens to old codes?
On each resync, stale or duplicate codes of the same type for the same guest are removed automatically, so only the current code remains.
A guest's code did not come through. Why?
The most common reason is that Mews did not return a valid Resource Access Token for that reservation. Check that Resource Access Tokens are enabled in your Mews configuration, and contact support if the code still does not appear.
Getting help
Open Talk to Us in the left menu, or email support@bookboost.io.