TF Rooms

Which of the twelve New Leaf properties in Twin Falls has a room free tonight or on particular nights. Asks all twelve live at the moment you call it. Give the dates: the published availability feeds carry CAPACITY, not vacancy, and say nothing about which nights are taken. With no dates it answers for tonight and says so. It applies each property's live minimum stay: a single or a double can be one night, subject to availability, and a studio is 7 nights or more. For a stay under a week with a room free it gives the nightly rates. A stay over 30 nights is refused before anything else: every stay is capped at 30 days.

All twelve New Leaf properties: name, address, phone, which room types each sells online, its rates and its booking URL. Static facts only — it says nothing about whether a room is free tonight. Use find_rooms for that.

What a room costs across the portfolio, by the night and by the week, and the rules that govern a stay: the minimum stay, how a stay under a week is priced, the 30-day cap, the weekly-only studio rule, the 8% Idaho lodging tax, and why $1,000 is never a monthly rate.

Takes no parameters.

The total for one stay at one New Leaf property: the nights, the tax and what is paid at the property. Asks that property live and returns its answer word for word, so the figure is the one its booking form uses, and passes on its refusal when a stay cannot be sold. Use it once the property, room type and dates are known. It gives a price, not availability: use find_rooms to see which properties have a room free.

Validates and prices a stay, checks current availability without holding a room, and emails a six-digit code. Requires the property, room type, dates, guest name, email and contact phone. The intent and code last 15 minutes. An identical start while its intent remains open returns the same booking_id without another email; that booking_id can resend the code. A start with any changed detail replaces the earlier unproved intent at the same property. No stored contact stays are read before verification; the phone affects no pre-verification limit. Each normalized email can receive at most three booking codes per hour and six per rolling 24 hours across the portfolio. Configurable portfolio hourly and rolling daily ceilings and a property hourly ceiling apply; booking codes pause if the hub counter cannot confirm both budgets within two seconds. Reaching a ceiling returns the requested stay link and property phone. The resend mode takes only booking_id; at most two resends are allowed, at least 60 seconds apart. A room is held only after confirm_booking accepts the code. If chat booking is switched off, returns the prefilled reserve.html link.

Verifies the code the guest received by email for a booking_id, then holds an available room and submits the reservation for staff confirmation within 24 hours. Requires that booking_id and six-digit code. Repeating the same valid pair returns the same reservation. After email proof, checks stays matching only that proved email, overlapping dates and the 30-day continuous-stay limit, including a one-night gap. Starting over with the proved email for the same property, room type and dates returns the existing held chat reservation. Contact-based refusals give only the requested stay link and property phone. The guest brings photo ID and signs the guest agreement at check-in; no payment is taken.

Reads a reservation status, property, room type, dates and total using its reservation number and the last four digits of its contact phone. Does not return the guest name, email or full phone. Well-formed references with incorrect details return no reservation found; only failed lookups count toward the per-reference limit.

Cancels in two steps. The first mode takes reservation_number and phone_last4, emails a code and returns cancel_id. The second mode takes cancel_id and code, cancels the reservation, releases the room and notifies staff and guest. Automated cancellation is available more than 48 hours before check-in during office hours; other cancellations are handled by the property by phone. Cancellation codes have a separate budget of three per reservation in a rolling 24 hours and, by default, five across the portfolio in a rolling 24 hours, unaffected by booking traffic. The portfolio ceiling is configurable. Unavailable or over-budget cancellations give the property phone without a booking link. The published cancellation policy applies. No payment or refund is processed.