App Guides. how to use the apps of traveller.org
Guides / Amapas 353 (app) / After a Request Comes In Amapas 353 (app)

After a Request Comes In

Where reservation requests land, how the owner confirms them, and how availability and prices are controlled.

Nothing in this app confirms a stay by itself. Every submitted request needs a human decision, and this page is about making it.

Where the request lands

When a guest presses “Request to Book,” two things happen:

  1. A Tentative reservation is created in Lodgify — the property-management system — with the guest’s name, email, phone, dates, guest count, and the server-calculated total.
  2. Two emails go out (when email sending is configured on the server): a confirmation to the guest, and a notification to the owner’s address with all the request details. If email is not configured, the reservation is still created in Lodgify — email failures never block a booking request.

The guest’s email promises confirmation within 24 hours. That clock is yours.

What you do

  1. Open the notification email, or open Lodgify and find the new reservation marked Tentative.
  2. Decide: confirm or decline.
  3. Act on the reservation in Lodgify. (This app has no screen for confirming — Lodgify is where reservations are managed.)
  4. If the guest needs anything further — payment, questions — handle it by replying to them directly; their email and phone are on the reservation.

How availability is controlled

The dates shown as unavailable in the guest’s calendar come straight from Lodgify: owner-blocked periods plus any reservation that is not declined, cancelled, or expired. So:

  • To block dates (personal use, maintenance), block them in Lodgify. The app picks this up automatically.
  • A Tentative request blocks its dates too. A request you never act on keeps those dates unavailable to everyone else — one more reason to decide within the promised 24 hours. Declining or cancelling it in Lodgify frees the dates.

How prices are controlled

Nightly rates come live from the Lodgify rate calendar; change them there and the app follows, no code change needed. Three amounts are fixed inside the app rather than read from Lodgify: the $65 cleaning fee and the fallback tax percentages (ISH 5%, IVA 16%). Changing those requires a small code change — ask whoever maintains the code, and see the note on the next page about what is safe to change.

Testing the booking flow

There is a standing rule worth repeating from the project’s own records: every successful test booking creates a real Tentative reservation in Lodgify and blocks those dates until you remove it.

What you do

  1. If you run a test booking, note the reference number shown on the confirmation screen.
  2. Go into Lodgify and delete (or decline) that test reservation as soon as you are done.
  3. Check the calendar afterwards to confirm the test dates are open again.