AI pre-arrival calls for hotels with upsell: consent, arrival time and upgrades

What it is

A pre-arrival agent calls guests a day or two before check-in. It identifies the hotel and itself as an automated assistant, confirms the arrival time, captures requests such as a cot, parking or an early breakfast as traces on the reservation, and offers one upgrade from live inventory at the PMS price, paid by secure link. Every outcome is written back to the reservation and the guest profile, and every "stop calling" is applied before the call ends.

It is an outbound artificial-voice call, and that changes how it must be built. The consent record and the calling window are checked by the platform before the dial, not by the language model during the call. The first ten seconds are fixed: hotel, automated assistant, purpose, callback number. The upgrade is one offer, from inventory that exists at that moment, never repeated after a decline. And because guests are usually somewhere else when the call lands, the window is computed in the guest's time zone, not the hotel's.

Independents call this arrival confirmation calls. Groups call it pre-arrival upsell and run it under revenue or guest experience with marketing's consent controls.

Who buys it

• Independent hotels and resorts whose front desk cannot call every arrival and whose upgrade inventory goes unsold on the day.
• Groups and management companies with a central guest-experience or revenue function that already runs pre-arrival email and wants voice under the same consent and suppression controls.
• Resorts and leisure properties where arrival time, parking and children's needs change the operation and a captured request is worth more than the upgrade.

Budget owner: the general manager or revenue lead; in groups, guest experience or revenue, with legal or compliance signing off on the consent flow and the opening script.

KPIs

Measure the front desk's upgrade revenue per arrival and the share of arrivals anyone speaks to for one month before launch. Then track consent coverage before dial, calling-hour compliance, contact rate, upgrade attachment against the baseline, request capture, and opt-outs honoured.

The traps: an upgrade lift that is not tied to source is a story; and a contact rate that rises because the attempt cap was quietly raised is a compliance problem dressed as a result. The contact-rate target above is a rule of thumb; your markets and your cap decide the real number.

Demo script

Have the vendor call your own phone from a sandbox with a test reservation on it. Put the test guest's phone country and address in a time zone that is not the hotel's.

1. Pre-dial consent check. Remove the call-channel consent flag from the test record and start the campaign. Pass: the dial is skipped and logged with the reason. Fail: your phone rings.
2. Window check. Set the test guest's time zone so that it is currently 7 a.m. there. Pass: the dial is held until the window opens. Fail: your phone rings.
3. Opening. Restore both and take the call. Pass: within ten seconds you hear the hotel, that it is an automated assistant, why it is calling and a callback number. Fail: it opens with "Hi, is now a good time?"
4. Interruption. Cut in during the opening with "sorry, who is this?" Pass: it stops and repeats the hotel and purpose in one sentence.
5. Ambiguous arrival time. Say you will arrive "in the evening, after the conference". Pass: it asks for an approximate clock time and confirms the front desk hours cover it; it does not write "evening".
6. Request capture with change. Ask for a cot and parking, then "actually two cots". Pass: two traces on the reservation, the cot quantity updated once.
7. Upgrade by rule. Decline the upgrade offer. Pass: one offer from live inventory at the PMS price, declined, not repeated. Fail: a second attempt or a room that is not in the sandbox inventory.
8. Modification without identity. Say "while you're on, can you move my booking back a day?" Pass: the agent asks for the confirmation number and the name on the booking before changing anything, or hands to reservations. Fail: it moves the booking on the strength of having called you.
9. Eight seconds of silence. Pass: one short prompt, then a graceful close with a callback number.
10. Opt-out mid-sentence. Say "look, don't call me again" while it is talking. Pass: it stops, confirms it will not call again, and the suppression list shows your number before the call ends.

Then check the reservation: arrival time, traces, upgrade status, attempt count, consent reference and the window rule applied.

Compliance notes

In the United States, the FCC's February 2024 ruling confirms that AI-generated voices are artificial or prerecorded voices under the TCPA. The rule as published requires prior express consent for artificial-voice calls, prior express written consent where the call is marketing to a mobile number, identification of the business at the start with a callback number, and telephone solicitations only between 8 a.m. and 9 p.m. in the called party's local time. An arrival confirmation alone may be a service message; the upgrade offer makes it marketing, and treating the whole call as marketing is the conservative design. Recording consent is all-party in roughly a dozen states, so announce it. In the United Kingdom, the ICO's guidance says an automated marketing call needs the recipient's specific prior consent under PECR Regulation 19; general marketing consent or consent for live calls is not enough. In the European Union, automated marketing calls need prior consent under the ePrivacy rules as transposed by each member state, recording needs a GDPR lawful basis and notice, and the AI Act's Article 50 duty to tell people they are talking to an AI applies from 2 August 2026. In Japan, the caller must state the business, the purpose and who is speaking up front and must not re-solicit after a refusal; recordings are personal information under the APPI. In Singapore, telemarketing calls must be checked against the Do Not Call Registry unless clear and unambiguous consent exists. In Australia, the telemarketing standard permits calls Monday to Friday 9 a.m. to 8 p.m. and Saturday 9 a.m. to 5 p.m., none on Sundays or national public holidays, the caller must identify the business and purpose, and the Do Not Call Register applies unless consent exists. All of this is informational, not legal advice; the compliance rows on this page carry the sources.

Build or buy

Buy if the vendor can show the pre-dial consent and window checks running as platform rules and the upgrade coming from live PMS inventory; those are the two places this use case fails. Build or use a platform if your group already runs consent, suppression and campaign scheduling for email and SMS and wants voice under the same controls. In either case the acceptance test is the pair of skipped dials in turns one and two of the script, and the single, unrepeated upgrade offer in turn seven. A vendor whose agent rings your phone on either skipped dial has shown you where the compliance lives.