Custom PMS fields have to be mapped individually
Besty does not automatically pull every field from your PMS. Standard reservation and listing data comes across, but custom fields have to be mapped explicitly.
The reason is that custom fields are unique to each account. Two Streamline customers can have entirely different sets of them, with different names, so there is no general rule that would bring them all in.
If you can see a field in your PMS but the variable does not populate in Besty, it has not been mapped yet.
Getting a field mapped
Send us the exact variable name as it appears in your PMS. For example:
reservations_unit.pool_access_informationreservation_additional.goodneighbortech_code
We will raise a ticket to pull it in, and it is usually available the same day. Once mapped, it behaves like any other template variable and can be inserted from Messaging Fields in the message editor.
Streamline: check "Show in Site API" first
If you are on Streamline, there is a setting on each custom field called Show in Site API.
If it is not enabled, the field is not exposed to the API at all, and we cannot pull it in no matter what we do on our side. Enable it in Streamline before sending the field name over, otherwise the mapping will appear to succeed and the variable will still come through empty.
The alternative: a Besty custom variable
If the value rarely changes, you may not need the PMS field at all. You can create your own variable in Besty and enter the value directly.
Go to the messaging fields section under Listings and create a custom field, for example a pool code or a gate code. These can be scoped to all listings, a listing set, or an individual listing, so each property can hold its own value behind the same variable name in your message templates.
This is the usual approach for codes that stay the same year-round. Use PMS mapping when the value is maintained in your PMS and changes there.
Do not reuse your PMS's own tag syntax
Variables written in your PMS's format, such as Streamline's {client.first_name}, will not reliably work in Besty. A few coincidentally match and most fail silently, leaving blanks in messages that looked correct when you wrote them.
Always insert variables from the Messaging Fields picker in the message editor rather than typing them by hand.
Still Having Trouble?
Reach out via chat or at support@getbesty.ai.