What booking re-verification is, what gets checked with the hotel, why doing it by hand stops working, and how it runs at scale, with five real bookings where it caught what a confirmation number could not.
Booking re-verification is the step that comes after a booking is confirmed and before the guest travels: someone contacts the hotel and checks the reservation as the property holds it against the reservation as it was sold. A confirmation tells you a booking was created. Re-verification tells you what the hotel holds today, and flags anything that does not match while there is still time to fix it.
This guide covers the whole of it, what is checked, why the manual version breaks down, how rePUSHTI runs it, what happens when something is wrong, and what it looks like on real bookings.
What gets re-verified
rePUSHTI checks each booking across more than 50 parameters. Most of them fall into a handful of groups, and they are the same things that go wrong at a front desk:
- The reservation itself: that the hotel can find it, under the right guest name, with its own confirmation number
- Dates and occupancy: check-in, check-out, number of rooms, adults and children
- The room: category, bed type, view and anything else that was specifically sold
- Inclusions: meal plan, transfers, and facilities the guest is expecting
- Payment: whether the hotel has the booking as paid, pending, or payable at the property
- The property: that it is open and taking guests on those dates
- Special requests and conditions: late arrival, documents the hotel requires, anything the guest asked for
Checking things that are not on the standard list
Not every business need fits a default list. A corporate traveller may need an invoice carrying a specific tax code; a group may have a condition agreed with the property by email. Custom fields can be added to a booking's re-verification data, through the API, or directly when a booking is added offline, and they are checked with the hotel in the same way as any standard parameter. The point is not a fixed checklist. It is that whatever matters for a particular trip gets confirmed with the property rather than noted somewhere and hoped for.
Why manual re-verification stops working
Travel agencies have always re-verified bookings: someone picks up the phone and calls the hotel. It is a reasonable way to start. It runs into the same limits every time the volume grows.
- Language: a team books into countries whose language it does not speak. A call held in halting English produces an incomplete check, and an incomplete check misses the error it was meant to catch
- Persistence: calls go unanswered, lines drop, the person who picks up cannot access reservations. A human working one channel gives up; the booking stays unverified
- Time: the hotel's working day is somebody else's night. Calls made at the agency's convenience reach a night porter who cannot help
- Cost: dedicated staff, international call charges and hours on hold, work that peaks in high season and sits idle outside it
- Consistency: no two people ask the same questions in the same order, so no two checks cover the same ground
The result is that manual re-verification gets rationed. It is done for the bookings that look risky and skipped in the busy weeks, which are exactly the weeks when errors are most likely.
How rePUSHTI re-verifies a booking
Bookings reach rePUSHTI through an API connection or are added by hand. From there each one is re-verified with the property through whichever channel gets an answer, phone, email, WhatsApp, and the attempt does not stop at the first unanswered call. It runs around the clock, so a booking pushed at midnight is worked in the hotel's morning rather than the agency's.
The work is done by AI agents and trained people together, in the languages hotels actually answer in, among them English, Arabic, French, German, Russian, Turkish and Malay. More than two million bookings have been processed this way.
What happens when an error is found
Finding a problem is half the job. Ordinarily, once an agency learns a booking is wrong, it still has to chase its own supplier to put it right, across time zones, through a support queue, often in a language the team does not share. That effort can cost more than the original check.
rePUSHTI's approach is to carry the problem through: identify the discrepancy, then act as the bridge to the supplier who has to correct it, and keep at it until the booking is right. The agency's team stays on customers and sales instead of on the bookings that went wrong.
Getting more out of re-verification
- Re-verify offline bookings: reservations that were never recorded in any system can be uploaded and join the same queue, with the same report at the end
- Keep everyone informed automatically: status updates to the agent who made the booking, and a re-verification report to the customer by email or WhatsApp
- Settle disputes with evidence: every re-verification call is recorded and can be downloaded and shared with the hotel
- Choose what matters: pick the parameters you care about and mark the ones that are non-negotiable
- Decide what is sent: set criteria, destination, booking value, lead time, for which bookings go to re-verification automatically
How it stays efficient at volume
At scale, the waste in re-verification is always the same: a call to a number nobody answers, or a step repeated on a booking that is already settled. Four things keep that down without cutting corners on accuracy:
- Every hotel contact number is scored by answer rate and attempts needed, so each booking starts with the number most likely to work
- Speech-to-text analysis across thousands of hotel conversations a month estimates a call's chance of success before it connects
- Patterns across the full volume of bookings are acted on, rather than reacting one booking at a time
- What each property asks for is learned and remembered, because requirements genuinely differ from hotel to hotel
What it catches: five real bookings
- A booking sold with breakfast at a property that did not offer it, caught before check-in, with time for the agent to reset expectations
- A hotel in Thailand that had changed ownership while its old listing stayed live; the new owner's system had no record of the booking at all
- A booking that failed somewhere between systems; the fault was traced to its technical cause, not just reported as a symptom
- A cancellation that would have gone unnoticed and been charged for
- A same-day check-in with an unprocessed payment, where the hotel allowed two hours before cancelling, everyone who needed to know did, before the clock ran out
None of these are errors a confirmation screen ever shows. They only surface when someone checks with the property.
When to re-verify
Timing depends on how soon the guest travels. A same-day arrival needs an answer within hours; a booking a month out is better checked a week or two ahead, close enough to check-in that the answer is still true when the guest arrives.
The timing in detail: the best time to re-verify a booking.
For travel businesses that want this running on every booking: booking re-verification for travel businesses.
Travelling yourself? See it screen by screen: how rePUSHTI re-verifies your hotel booking.



