How each bot conversation phase maps to the Booking / Appointment Services pipeline
| Bot Phase | Pipeline Stage | Movement Trigger |
|---|---|---|
| Phase 0 Greeting | New Lead | Contact created automatically when a WhatsApp message is received. Bot delivers greeting (Branch A, B, or C). |
| Phase 1 Intent Routing + Steps 1–3 Booking |
Responded / Qualifying |
Guest replies with travel-related information: desired dates, guest_count captured, or purpose_of_stay determined. Keyword-based intent routing completes.
|
| Step 4 Booking | Booking Link Sent |
Bot sends the direct booking URL haloplacett.com/book-direct/. Tag booking-link-sent applied. Timestamp written to booking_link_sent_at.
|
| Webhook WooCommerce | Direct Booking Confirmed |
WooCommerce order created via the direct booking page. Webhook fires → tag successfully-booked applied. Opportunity moves to Confirmed stage.
|
| Workflow Post-Stay | Stay Completed |
Customer's checkout date passes. Post-stay workflow triggers: review request, rebook nudge. Tag pre-arrival removed at stay start.
|
| DQ-A Spam / Irrelevant + DQ-B Out of Area |
Disqualified |
DQ-A: Message contains no accommodation keywords — spam, vendor, or unrelated. Tag dq-irrelevant.DQ-B: User asks about Tobago, other islands, or outside Trinidad. Tag dq-out-of-range.
|