Halo Condo — AI Agent Actions

0

Check Availability

HTTP Request (GET)

Panel Button: Activar un flujo de trabajo
Action Name: Check Availability
Type: HTTP Request (GET)

URL:
https://haloplacett.com/wp-json/halo/v1/bookings/

Description: Fetches all current bookings with check-in and check-out dates to verify availability.

When to trigger: When a contact asks about availability, dates, or wants to book specific dates.

Response Fields

check_in (YYYY-MM-DD)
check_out (YYYY-MM-DD)
guest_name
order_id

1

Calendar

GHL Action Button

NO CONFIGURAR — The bot redirects to haloplacett.com/book-direct/ for booking. No GHL calendar needed for this property.

The bot does not use GHL scheduling. All booking and availability check redirects to haloplacett.com/book-direct/

This action button should be left disabled in GHL. The bot will never attempt to check a GHL calendar, suggest appointment times, or schedule anything. When asked about availability, the bot responds with the direct booking link.

2

Workflows

GHL Action Button

Workflow Trigger
When: Bot sends booking link AND user has shared travel dates

→ Fire Workflow: "Booking Link Sent — 3 Day Follow-up"

Workflow logic: If no booking is recorded after 3 days, send a WhatsApp follow-up message to the contact.

Follow-up message template:

Hi {{contact.name}} — just checking in. If you had any questions about Halo Condo or the booking process, I'm here. Availability is live at haloplacett.com/book-direct/ whenever you're ready. No rush. — Candice

3

Field Mappings

GHL Action Button · One Action Per Field

Field: guest_count

Instruction: Extract the number of guests from the conversation. If the guest says "me and my wife," that's 2. "Just me" = 1. "Family of four" = 4. If uncertain, leave blank.

Example outputs:

"My wife and I are coming for Carnival" → 2
"Just me, solo trip" → 1
"Family of 4, two kids" → 4

Field: purpose_of_stay

Instruction: Extract the guest's reason for visiting from the conversation. Categories: business, leisure, Carnival, family visit, transit/layover, other.

Example outputs:

"I have meetings in Port of Spain" → business
"Coming down for Carnival 2027" → Carnival
"Just a weekend away" → leisure

Field: travel_dates_requested

Instruction: Extract any travel dates mentioned by the guest. Format as "Month Day–Day, Year" or "Month Day, Year" if single date. If no dates mentioned, leave blank.

Example outputs:

"Looking at February 15 to 20" → February 15-20, 2027
"I arrive March 3rd" → March 3, 2027
"Next week sometime" → leave blank (not specific enough)

Field: questions_asked

Instruction: Save any specific questions the guest asked about the property, area, or booking process. Use for follow-up context and to improve the bot over time.

Example outputs:

"Is there parking?" — "Guest asked about parking availability"
"Can I check in late?" — "Guest asked about late check-in"
"What's nearby for food?" — "Guest asked about nearby restaurants"

Field: booking_link_sent

Instruction: Set to "Yes" when the bot shares the direct booking link (haloplacett.com/book-direct/). Set to "No" by default.

Example outputs:

Bot sends "Check availability at haloplacett.com/book-direct/" → Yes
Guest asks a question, bot answers without sharing link → No (unchanged)

Field: booking_confirmed

Instruction: Set to "Yes" when the guest explicitly confirms they have booked. Triggers on phrases like "I booked," "Just booked," "All done," "Reservation made."

Example outputs:

"Okay I just booked" → Yes
"Done, all booked for the 15th" → Yes
"I'll book later tonight" → No (not yet confirmed)

4

Stop Bot

GHL Action Button

Trigger words/phrases:
thanks thank you will book ok bye goodbye got it all set appreciate it

Final message:

You're welcome! If you need anything before, during, or after your stay, just message here. Safe travels ✨

5

Transfer to Human

GHL Action Button

Trigger words/phrases:
speak to owner talk to human speak to Candice emergency complaint refund problem with stay real person not a bot issue

Bot message before transfer:

Of course — let me connect you. Candice will respond here as soon as she's available.

Transfer to user: Candice (info@haloplacett.com)

6

Follow-up

GHL Action Button

Default timing: 2 hours / 22 hours (GHL defaults)

Policy: No aggressive follow-up. The 3-day follow-up after booking link is sent is handled by the Workflow action (Action 2 above), not by this Follow-up button.

This button should use GHL's default settings. No custom modifications needed. The primary re-engagement mechanism is the workflow-based 3-day follow-up, not the automated follow-up button.