The Guesty Reservation Information context gives your AloAi Agent access to real-time reservation data during a guest conversation. The agent can share lock codes, WiFi passwords, property details, and stay dates without any manual lookup.
This feature is in Beta and requires the Guesty integration to be active on your account.
Before you start
Make sure you have:
The Guesty integration connected in Aloware
Admin access to configure AloAi Agents
Your account on the authorized Beta list (if you're unsure, contact support)
How it works
When a guest contacts the agent, Aloware looks up their caller phone number in Guesty to find the associated guest record and active reservations. No reservation ID is required from the guest; the lookup is automatic.
The lookup chain is: Caller phone number → Guesty contact (guestId) → active reservations with status confirmed or checked_in.
If multiple active reservations are found, up to 3 are returned and the agent will ask the guest to confirm which property they are calling about.
Step 1: Enable Guesty Reservation Context on your agent
In the Aloware sidebar, go to AloAi Agents and open the agent you want to configure.
Click the Context tab.
Find Guesty Reservation Information and switch the toggle ON.
Optionally, also enable Contact Information if you want the agent to personalize responses using the guest's name, email, or phone.
Update the agent's instructions to control how it shares the data.
Example: "Only share the lock code after the guest confirms their reservation number."
Save. Changes take effect immediately.
Step 2: Set up lock codes (skip if you use a Lock Manager)
Lock codes come from one of two (2) places. Which one applies to you depends on your Guesty setup.
If you use a Lock Manager - No additional setup needed. Aloware pulls codes directly from the Guesty access-codes API.
If you do not use a Lock Manager - You need to tell Aloware which Guesty custom field holds the lock code.
Go to Integrations → Guesty → Lock Code section.
Select the custom field(s) where lock codes are stored on your Guesty listings, for example "Front Door" or "Garage".
You can select multiple fields.
Save.
The agent will now read lock codes from those custom fields as a fallback.
Step 3: Check your WiFi custom field (if applicable)
WiFi passwords are pulled from a Guesty property-level custom field automatically.
For this to work, the field name in Guesty must contain "wifi" or "wi-fi" (not case-sensitive). No other setup is needed.
If no matching field exists, the agent will tell the guest that WiFi details are unavailable and direct them to the host.
Step 4: Test the agent
Call or text the agent's number as if you were a guest.
Try: "Can you give me the lock code?"
The agent looks up your phone number in Guesty, finds your active reservation, and replies with the property name, address, lock code, WiFi password, and stay dates. No reservation ID needed from the guest.
Open the Aloware communications panel and check the right sidebar under Guesty Reservations to confirm the data pulled correctly.
Test these edge cases too:
A phone number with no Guesty record
No active reservations on the account
A Lock Manager not configured and no custom fields selected
The agent should handle each one gracefully without errors.
What data the agent retrieves
All fields are retrieved automatically using the caller's phone number.
Field | Notes |
Check-in/ check-out dates | Auto-retrieved from Guesty |
Guest count | Auto-retrieved from Guesty |
Reservation status | Values: confirmed or checked_in. |
Property name | Listing nickname, falls back to listing title |
Property address | Auto-retrieved from listing address |
WiFi password | Property custom field (must contain "wifi" or "wi-fi" in the field name |
Lock codes / access codes | Lock manager API, or custom field fallback |
Confirmation code | Used in conversation only, not for lookup |
How the agent responds in different situations
Scenario | What the agent says |
Lock code is empty (no Lock Manager, no custom field configured) | Informs the guest the code is being generated and will be available soon. |
Lock code comes from a custom field (no Lock Manager) | Provides the code as normal. Status is CUSTOM_FIELD, purpose is GUEST, label reflects the custom field name. |
Lock code status is SCHEDULED | Informs the guest the code will be activated closer to check-in time. |
WiFi password is null | WiFi details are not available. Directs the guest to the host. |
Multiple reservations returned (up to 3) | Asks the guest to confirm which property they are calling about. |
No reservations found | "No active reservations found for this contact." Escalates or routes as configured. |