TG Guest Talk
Guide

Connecting Booking.com and Expedia to Guest Talk.

The two OTAs that carry the largest share of independent-hotel volume in Portugal, connected to Guest Talk in a way that survives peak season. This guide covers the credential dance, the mapping decisions and the specific traps that eat weekends when they go wrong.

Before you start

What you should have in hand

Talkguest connects to Booking.com through the official Booking Connectivity API as a certified partner. The connection requires the Property ID (a seven-digit number) and a Connectivity Password, both provisioned by Booking through the extranet under Account → Machine Accounts. Talkguest connects to Expedia through the Expedia Group Rapid Distribution and QuickConnect APIs, which require the Expedia Property ID (EID) and a signed connectivity agreement between Expedia, the property and Talkguest. Both connections are provisioned during onboarding but the property still owns the credentials.

  • Booking Property ID and a live machine account with password.
  • Expedia EID and a signed EQC (Expedia QuickConnect) agreement — usually one business day to countersign.
  • A frozen rate structure. Do not change any rate on the extranet in the twelve hours before the switch.
  • A weekday morning slot for the switch. Never do this on a Friday.
Step by step

The Booking.com switch, in order

  1. In the Booking extranet, generate a new machine account under Account → Machine Accounts → Create. Name it "Talkguest Connectivity". Copy the password to your onboarding engineer through the shared secure workspace, not email.
  2. In Talkguest, open Channels → Booking.com → Connect and paste the Property ID and password. The connection test should return green in under fifteen seconds. If it does not, the machine account probably has the wrong scope; recreate it with the "Full Property Management" role.
  3. Talkguest performs an initial reservation sync, pulling every future-arrival reservation into the tenant. On a fifty-key property this takes about forty seconds and shows a reconcile view that lists any deltas from the imported extract.
  4. Rate mapping opens next. Every Booking rate plan is matched to a Talkguest rate plan. The auto-matcher gets 90 percent right; you correct the rest by hand.
  5. Room type mapping runs alongside rate mapping. Confirm bunk versus single, en-suite versus shared bathroom, and any interconnecting logic.
  6. Once mapping is confirmed, Talkguest becomes the master. From this moment, do not change availability or rates on the Booking extranet directly. Every change flows from Talkguest.
  7. Send a test reservation from Booking to confirm the two-way flow. Delete it immediately.

The Expedia switch, in order

  1. Submit the EQC connectivity agreement through Expedia Partner Central. The countersign usually arrives within twenty-four hours.
  2. In Talkguest, open Channels → Expedia → Connect and paste the EID. There is no password on this side — Expedia uses partner-level authentication.
  3. Confirm the property status on Expedia. Some properties are dual-listed as "Hotel" and "Vacation Rental" — this affects the mapping and must be corrected before the switch.
  4. Rate map and room type map as above. Expedia's rate model is slightly different from Booking's; the mapper handles the differences but review the derived-rate math.
  5. Enable Expedia Traveller Preference (ETP) if your rate strategy supports pay-at-property. Talkguest handles the tokenisation logic on either side.
  6. Send a test reservation and delete it. As with Booking, Talkguest is now the master.
The traps

What eats weekends when it goes wrong

The single most common failure mode after a switch is a stale iCal export still running on the property side. Some hoteliers set up an iCal feed years ago to sync a spreadsheet, and nobody remembers it exists. That feed will overwrite Talkguest availability at unpredictable intervals. Look for it, kill it.

The second failure mode is a manual availability update in the extranet after the switch. Reception habit dies hard. If a receptionist closes a room in the Booking extranet on Saturday night, Talkguest will not know, and the property will oversell the next morning. Remove all extranet access from reception accounts on the day of the switch. The GM keeps read-only access for reporting.

The third failure mode is a mismatch between Booking's "flexible" rate and Talkguest's derived "non-refundable" rate. If the derived math produces a non-refundable price above the flexible price, Booking rejects the update silently and both rates fall back to yesterday's values. The rate audit view in Talkguest catches this within five minutes of the update.

Almost every "the OTAs are not updating" ticket we get is either an iCal feed nobody remembers or a manual extranet edit yesterday. Fix those two habits and the connection just works.

Cancellation policy alignment

Booking and Expedia both allow multiple cancellation policies per rate plan. Talkguest models them as derived attributes on the rate plan. If your Booking flexible rate has a 24-hour cancellation window and your Expedia flexible rate has a 48-hour window, decide which one is your master policy and align them before you switch. Divergent policies produce guest complaints that reception cannot resolve without a supervisor call.

Payment routing

Both Booking and Expedia support virtual credit cards for prepayment. On Talkguest these are captured, tokenised through the connected PSP (Stripe by default), and charged according to the rate plan's payment logic. If you use Ifthenpay or Multibanco on the direct channel and Stripe for OTA charges, the router sends each transaction through the correct PSP automatically. Confirm this routing in the Payment Settings during onboarding — see the VAT and factura guide for the tax implications.

What to look at for the first two weeks

After the switch, the Talkguest revenue analytics dashboard is where you spend most of your review time. Two views matter above all others in the first two weeks: the OTA delivery view (which shows every rate and availability update per channel with a success or failure status) and the reservation reconcile view (which shows any reservation still in the old system but not in Talkguest, or vice versa). Both should be at zero deltas by end of day three post-switch.

The revenue advisor at Talkguest reviews these with you at the first two-week check-in and correlates any anomalies with pace and pickup deltas. For most properties there is nothing to fix. For a few there is a mapping decision that becomes obvious once the first weekend of real bookings comes through — a Booking Genius rate that should have been derived rather than manually maintained, an Expedia opaque channel that was double-priced.

Get your Booking and Expedia switched cleanly