Skip to content
Voice AgentBible

AI outbound rebooking and loyalty calls for travel: consent, offers and opt-outs

How an outbound voice agent invites past guests to rebook and services loyalty members inside TCPA, PECR, AI Act, PDPA and ACMA rules, with KPIs and a demo script.

By · 5 min read

Last verified 01 Oct 2026v1.0Published 01 Oct 2026

Hotels · #5 of 5Outbound reminders and collectionsOutboundAdvancedtarget ≤ 900 ms turn

KPIs at a glance

Key performance indicators with baseline, target and how to measure
KPITypical baselineTargetHow to measure
Consent coverage before dialLoyalty terms often cover email; channel-specific consent for automated calls is usually missing. Audit your consent records before you plan a campaign100% of dialled numbers carry a dated, per-channel consent record and a registry check where required; zero dials without oneDial log joined to the consent table and registry-check log, daily; any dial without both is a defect.
Calling-hour complianceNot applicableZero dials outside the member's local-time window for their jurisdictionDial timestamps converted to the member's local time, checked against the configured window, daily.
Contact rateCount how many past guests your team actually speaks to in a month today; for most properties it is near zeroA live conversation on 20-35% of attempted members within the attempt cap you set (rule of thumb; cold lists sit lower)Conversations / members attempted, per campaign.
Rebooking conversionYour current rebooking rate from email win-back on the same segment, measured for one quarterA measurable lift on the same segment, with agent bookings identified by source and rate codeBookings from agent conversations / members attempted, against the email cohort, per campaign.
Offer integrityNot applicableZero offers outside the configured rate codes and live availability; zero invented discountsTranscript audit of every offer against the campaign rate codes and PMS availability at call time, weekly.
Opt-out honouredNot applicable100% of 'stop calling' requests applied before the next dial to that number, across all campaignsOpt-out events joined to subsequent dial logs; any later dial is a defect.

What it is

A rebooking and loyalty agent calls past guests and programme members. It identifies the brand and itself as an automated assistant, confirms it is speaking to the member before mentioning anything personal, makes one offer from campaign rate codes and live availability, books the stay with dates said aloud, the PMS total and the cancellation policy, or captures the reason the member is not travelling, and writes every outcome to the CRM. "Stop calling" is applied to a group-wide suppression list before the call ends.

It is the most regulated call in this industry, because it is marketing by an artificial voice to a list. The consent record and, where the jurisdiction requires it, a Do Not Call registry check run before the dial. The calling window is computed in the member's time zone. The opening is fixed. The offer is bounded by rate codes that exist and rooms that exist. And identity gates everything: points balances and stay history are personal data, and the person who answers is not necessarily the member.

Independents call this win-back calls. Groups and travel brands call it loyalty outbound or rebooking campaigns and run it under marketing with legal sign-off.

Who buys it

  • Groups and brands with a loyalty programme and a segment of lapsed members whose email engagement has faded.
  • Resorts and leisure properties with a repeat-guest base and a seasonal pattern, where a call in the booking window beats a newsletter.
  • Travel brands and operators servicing members on itinerary changes and disruption, where the same outbound controls apply to a service call that also carries an offer.

Budget owner: the head of loyalty or CRM, with legal or compliance signing off on the consent model, the registry checks and the opening script, and revenue management owning the rate codes.

KPIs

Audit your consent records by channel before planning anything; the gap between "we have their number" and "we may call it with an automated voice" is the first finding of most projects. Measure email win-back conversion on the target segment for a quarter. Then track consent coverage before dial, calling-hour compliance, contact rate, rebooking conversion against the email cohort, offer integrity and opt-outs honoured.

The traps: a conversion lift that is not tied to source and rate code is a story; a contact rate that rises because the attempt cap was raised is a compliance problem; and an offer that converts because the agent improvised a discount is a revenue leak the audit will find later.

Demo script

Have the vendor call your own phone from a sandbox with a test member profile, stay history, a points balance and two campaign rate codes. Put the member's phone country in a jurisdiction that requires a registry check.

  1. Pre-dial checks. Remove the call-channel consent flag and start the campaign. Pass: the dial is skipped and logged. Restore it and mark the number as on the test registry. Pass: skipped and logged again. Fail: your phone rings on either.
  2. Window check. Set the member's time zone so it is currently 7 a.m. there. Pass: the dial is held until the window opens.
  3. Opening and identity. Take the call. Pass: within ten seconds, the brand, automated assistant, purpose and a callback number, then "am I speaking with..." before any history or balance is mentioned. Fail: "Hi, I see you stayed with us in March" to whoever answers.
  4. Interruption. Cut in during the opening with "who is this?" Pass: it stops and repeats the brand and purpose in one sentence.
  5. Wrong person. Say you are the member's partner. Pass: it asks whether the member is available or offers a callback, and discloses nothing. Fail: it continues with the offer and the stay history.
  6. Ambiguous dates. As the member, say you might come "around Easter". Pass: it names candidate calendar dates and checks live availability for the campaign rate code. Fail: "we have availability around then."
  7. Party-size change and the offer. Say two adults, then "and our two kids this time". Pass: it rechecks for four once and states the PMS total including taxes and fees for the campaign rate; one offer, declined offers not repeated. Fail: an invented discount or a rate code not in the campaign.
  8. Eight seconds of silence. Pass: one short prompt, then a graceful close with a callback number.
  9. Out-of-scope. Ask it to transfer your points to an airline partner and to tell you whether the other brand's programme is better. Pass: the points question handled from your programme rules or handed to the loyalty desk; no comparison.
  10. Book, then opt out. Accept the offer. Pass: the cancellation policy spoken, dates restated, a plain yes, the reservation in the PMS with the rate code and member number, the guarantee link in the message log. Then say "and don't call me again". Pass: confirmed, and the suppression list shows your number before the call ends.

Then check the record: outcome, reason code, attempt count, consent reference, registry-check 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; a rebooking offer is a solicitation. 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; loyalty terms that mention email do not supply it. 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 Act on Specified Commercial Transactions requires the caller to state the business, the person and the purpose up front and prohibits re-solicitation after a refusal; recordings are personal information under the APPI. In Singapore, telemarketing calls to Singapore numbers must be checked against the Do Not Call Registry under the PDPA 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, 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 only from a vendor who can show the pre-dial consent and registry checks, the window logic and the identity gate running as platform rules in your demo. Build or use a platform if your loyalty team already runs consent, suppression and campaign scheduling for email and SMS and wants voice under the same controls, with the agent limited to campaign rate codes and live availability. In either case the acceptance test is the three skipped dials in turns one and two of the script, and nothing personal said to the partner in turn five. A vendor whose agent rings your phone on a skipped dial, or tells a stranger where you stayed in March, has shown you where the compliance lives.

Questions to ask vendors

  1. 01

    Show me the consent and registry checks that run before each dial, per country, and what happens when either fails.

    A good answer: Per-number, per-channel, dated consent plus a Do Not Call registry check where the jurisdiction requires it, both enforced by the platform before dialling, with skipped dials logged. Not prompt text.

  2. 02

    How does the platform work out each member's local time and the applicable calling window?

    A good answer: Time zone from the member's phone country and profile address, a per-jurisdiction window table, and a log of the rule applied to each dial.

  3. 03

    What does the agent say in the first ten seconds, and how does it identify the member before discussing their history?

    A good answer: Hotel or brand, automated assistant, purpose, callback number, then a confirmation that it is speaking to the member before any stay history or points balance is mentioned.

  4. 04

    Where do the offers come from, and what stops the agent inventing a discount or promising a date that is not available?

    A good answer: Campaign rate codes and live availability from the PMS or CRS at call time, one offer per call, and a hand-off to reservations for anything outside them.

  5. 05

    How is 'stop calling me' handled, and does it apply across campaigns and properties?

    A good answer: Recognised in one turn, confirmed, applied to a group-wide suppression list before the call ends, and logged with a timestamp.

  6. 06

    How does the agent book, and how is payment taken?

    A good answer: Dates said aloud, total from the PMS including taxes and fees, cancellation policy spoken, a plain yes, the reservation written, the guarantee by secure link. The agent never hears a card number.

  7. 07

    How many attempts per member, over what period, and who sets that?

    A good answer: A cap you configure, enforced by the platform, visible per member, with the attempt history exportable.

Matrix rows that apply

Rows from the global compliance matrix that apply to this page. Informational only, not legal advice; dates change, confirm with counsel and the regulator.

JurisdictionConsent for automated callsAI disclosureCalling hoursRecordingVerified
United States (federal)confidence high
Required

The FCC's February 2024 declaratory ruling confirms that AI-generated or cloned voices are "artificial or prerecorded" voices under the TCPA. Outbound calls using them need prior express consent; marketing calls to mobile numbers need prior express written consent. Inbound calls initiated by the consumer are outside this consent rule.

Conditional

No federal statute yet requires an agent to announce that it is AI. TCPA rules already require prerecorded or artificial-voice calls to identify the caller at the start and give a callback number. An FCC proposal (2024) would add an explicit AI disclosure; several states have their own bot-disclosure laws. Disclose by default.

Required

Telephone solicitations only between 8 a.m. and 9 p.m. in the called party's local time (47 CFR 64.1200(c)(1)).

Conditional

Federal law is one-party consent; roughly a dozen states (including California, Florida, Washington and Pennsylvania) require all-party consent. Announce recording at the start of every call unless counsel confirms otherwise.

2026-09-30
United Kingdomconfidence medium
Required

The ICO treats conversational AI voice calls as automated calls under PECR Regulation 19, so direct marketing by automated call needs the recipient's specific prior consent. Live human marketing calls follow the softer Regulation 21 rules (screen against the TPS).

Recommended

No UK statute mandates announcing an AI caller, but PECR requires automated marketing calls to identify the sender and provide a contact address, and UK GDPR transparency duties apply.

Recommended

No statutory hours in PECR; Ofcom and industry codes expect reasonable hours and honouring "do not call again" requests.

Required

Recording is processing of personal data under UK GDPR; tell callers at the start and document the lawful basis. Financial firms have additional FCA recording duties.

2026-09-30
European Unionconfidence medium
Required

Automated calling systems without human intervention for direct marketing need prior consent under the ePrivacy Directive (Art. 13) as transposed by each member state; GDPR requires a lawful basis for the processing itself.

Required

EU AI Act Article 50 requires that people interacting with an AI system are informed they are doing so unless it is obvious. Transparency obligations apply from 2 August 2026. Proposed "Digital Omnibus" amendments may adjust timing or scope; verify before relying on this row.

Conditional

Set by member-state law and codes (for example, national telemarketing hour rules); no EU-wide statutory window.

Required

Recording needs a GDPR lawful basis and transparent notice at the start; several member states require all-party consent.

2026-09-30
Philippinesconfidence medium
Required

The Data Privacy Act of 2012 requires a lawful basis (usually consent or legitimate interest) for processing; the National Privacy Commission expects clear notice for marketing calls.

Not required

No statute requires announcing an AI caller. Announcing it is recommended and expected by the NPC's transparency principle.

Recommended

No statutory window; BSP consumer-protection rules for financial institutions prohibit harassment and unreasonable hours in collections.

Required

The Anti-Wiretapping Act (RA 4200) makes recording a private communication without the consent of all parties a crime; announce and obtain consent at the start of every call.

2026-09-30
Singaporeconfidence medium
Required

Telemarketing voice calls to Singapore numbers must be checked against the Do Not Call Registry unless the organisation has clear and unambiguous consent (PDPA Part 9).

Not required

No statutory AI-caller disclosure; the PDPC's Model AI Governance Framework recommends transparency.

Recommended

No statutory hours; PDPC guidance and industry codes expect reasonable hours.

Recommended

Recording is personal-data collection under the PDPA and requires notification of purpose; no all-party consent statute.

2026-09-30
Australiaconfidence medium
Required

Telemarketing calls must not be made to numbers on the Do Not Call Register without consent (Do Not Call Register Act 2006); research calls have narrower exemptions.

Conditional

The Telemarketing and Research Calls Industry Standard requires callers to identify themselves, the organisation and the purpose at the start. No general AI-caller law; broadcasting codes have begun requiring synthetic-voice disclosure in specific contexts.

Required

Telemarketing calls only Monday to Friday 9 a.m. to 8 p.m. and Saturday 9 a.m. to 5 p.m. local time; none on Sundays or national public holidays (Industry Standard 2017).

Conditional

State and territory surveillance-devices laws differ; several require all-party consent. Announce recording at the start.

2026-09-30
New Zealandconfidence low
Recommended

No statutory do-not-call register for voice calls; the Marketing Association's Do Not Call list is voluntary. The Privacy Act 2020 governs collection and use of personal information.

Not required

No AI-caller disclosure statute; Privacy Act transparency principles apply.

Recommended

Industry code expectations only.

Recommended

One-party consent for a participant; notify callers to satisfy Privacy Act collection principles.

2026-09-30
Japanconfidence low
Conditional

The Act on Specified Commercial Transactions regulates telemarketing: the caller must state the business name, the person's name and the purpose up front, and must not re-solicit after a refusal. No general opt-in register.

Not required

No AI-caller disclosure statute; identification duties above apply regardless of who or what is speaking.

Recommended

No statutory hours; industry guidance discourages early-morning and late-evening calls.

Recommended

Recordings are personal information under the APPI; specify the purpose of use and notify the caller.

2026-09-30

    Frequently asked

    Is an AI rebooking call legal?

    It depends on consent and jurisdiction. In the United States an AI voice is an artificial voice under the TCPA, so the call needs prior express consent, written consent for marketing to a mobile, and the 8 a.m. to 9 p.m. window. The United Kingdom needs specific prior consent under PECR, the European Union needs prior consent and AI disclosure, Singapore needs a Do Not Call Registry check, and Australia applies fixed hours and its register. Informational, not legal advice.

    Can the agent discuss a member's points and past stays?

    Only after confirming it is speaking to the member. Stay history and balances are personal data; disclosing them to whoever answers the phone is a breach, however friendly the voice.

    Why not just email?

    Email is cheaper and should run first. The call earns its place on high-value segments where a conversation books a stay email does not; measure conversion and revenue per attempt against the email cohort, and stop the campaign if it does not beat it.