A guest has a confirmation number from Agoda but the reservation never appears in your PMS or channel manager, and this covers where it likely went and how to get it back.
A guest messages you with an Agoda confirmation number, but your property management system shows nothing for that date. This is one of the more unsettling extranet problems because the booking is real to the guest and real to Agoda, just invisible to you. Here is what is actually happening and the steps to get the reservation into your system before it causes a walk-in surprise.
Guest arrives or calls, quoting an Agoda booking ID and a rate. You search the PMS by guest name, date and reference number and find nothing. The room may still show as available in your calendar, or worse, another guest has already been placed in it.
This is different from a booking that synced late — those eventually appear once a scheduled poll or webhook catches up. A booking that is not received usually stays missing until someone intervenes manually, because the message that should have created it never reached your system in a usable form.
Three mechanisms cause most cases. First, room or rate-plan mapping: Agoda sends a reservation tagged to a specific room type and rate plan ID on their side, and if that ID isn't mapped to the matching item in your PMS, the message has nowhere to land and gets dropped or logged as an error nobody sees. Second, the connection between Agoda and your channel manager can drop silently — expired credentials, a token that needs reauthorization, or a temporary outage on either side — so new reservations stop arriving until someone reconnects it. Third, a webhook or notification can fail to deliver even though the booking itself is confirmed and paid on Agoda's side, which is why the guest's confirmation is completely genuine while your system knows nothing about it.
Open the Agoda extranet first and pull up the exact reservation — confirm the room type, rate plan, dates and status it shows there, since that is the version of the truth you are trying to match. Then check your channel manager's activity or error log for that date range; most systems log a mapping failure or a connection error even when they don't surface it loudly on the main dashboard. If you see other recent bookings from Agoda arriving normally, the issue is almost always mapping on this specific room type or rate plan, not a dead connection. If nothing at all has arrived from Agoda recently, check whether the connection itself needs reauthorizing.
Automatic recovery of a missing reservation — pulling in a booking the channel never delivered — is available today for Booking.com, Expedia, Trip.com and Airbnb. It is not yet available for Agoda specifically, so for Agoda the honest advice above — check the extranet, check mapping, reauthorize if needed — still applies manually. What the platform does do for every channel, Agoda included, is keep an activity history of what changed and when, so when a booking does go missing you can see exactly where the chain broke instead of guessing. You can open the live demo at try.primehostpartners.com without signing up and look at the activity log yourself.