Booking a Stay

This page walks through what a guest sees and does, step by step. It is worth knowing even if you never book a stay yourself — when a guest phones with a question, this is the screen they are looking at.

Reaching the booking screen

In ChatGPT, a guest either asks directly (“book a condo in Puerto Vallarta”) or simply plans a trip in conversation; when the condo fits, the assistant offers it and opens the booking screen as a card inside the chat. The same screen is also available in a normal browser at https://booking.amapas353.com/widget.

Step 1 — Property and dates

The first screen shows a photo carousel, the property name and location, the key numbers (2 beds, 2.5 baths, 4 guests max, 3-night minimum stay), a description, and amenity tags. Below that are two date pickers and, once dates are chosen, a live price breakdown.

What you do

1. Look through the photos using the arrows on the picture, or the dots underneath it.
2. Tap Check-in and pick an arrival date from the calendar. Past dates are greyed out; dates that are already booked or blocked appear crossed out and cannot be selected.
3. Tap Check-out and pick a departure date. This picker stays disabled until a check-in date is chosen, and the earliest date it offers is three nights after check-in.
4. Wait a moment while the price appears (“Fetching live pricing…”), then review the itemized breakdown.
5. Press Request Availability.

If the chosen range overlaps an unavailable period, a red banner says “These dates are unavailable. Please choose different dates.” — pick different dates.

What the price is made of

Every quote is fetched live from the reservation system at the moment the dates are picked, and is itemized on screen:

• Nightly rate × number of nights — the rate varies by season (roughly $250 to $720 per night).
• Cleaning fee — a flat $65.
• Jalisco Lodging Tax (ISH 5%) and Mexico IVA (VAT 16%) — both calculated on the nightly subtotal only, not on the cleaning fee.

All prices are in US dollars. The server recalculates the price itself when the request is submitted, so the total on file is always the live one — a guest (or the chat assistant) cannot type in their own price.

Step 2 — Your Details

What you do

1. Set the number of guests with the plus and minus buttons (1 to 4).
2. Enter first name and last name.
3. Enter an email address — this is where the confirmation goes.
4. Choose a phone country code from the list and enter the phone number.
5. Check the dates and total shown at the top, then press Request to Book (the button shows the total, e.g. “Request to Book — $1,234”).

The button stays disabled until name, a valid-looking email, and a phone number of at least 7 digits are filled in. Directly under the button, the screen says plainly: “Submits a reservation request. Confirmation sent by email.”

Step 3 — Request Submitted

On success the guest sees a green check, “Request Submitted!”, a reference number, and a summary of dates, guests, and total. The screen states that the request “is not yet confirmed” and that an email will follow with a link to complete the confirmation. It also shows which email address the confirmation was sent to. A Start Over button clears everything for a fresh request.

The guest then receives an “Availability Request Received” email listing the reference number, dates, guest count, and estimated total, and saying the request will be confirmed within 24 hours.

Booking in conversation, without the screen

The assistant can also take a booking entirely in chat: it collects the same details — first and last name, email, phone with country code, dates, and guest count — confirms the dates back, and submits the same reservation request. It never asks the guest for a price; pricing always comes from the live system.

The house rules the app enforces

• 3-night minimum stay. Shorter requests are refused with a clear message; nothing is filed.
• Maximum 4 guests. The guest counter will not go higher.
• Adults only, no pets — stated on the screen and in the trip-planning guidance.
• No double-booking. Unavailable dates are blocked in the calendar, and availability is checked again on the server at the moment of submission.