Quick answer: Pick the platform that can absorb a disruption peak alone and still meet the refund clocks: seven days under EU261 and UK261, and 7 business days (card) or 20 calendar days (other payments) under the US DOT rule. Zian ranks first for 24/7 voice, chat, WhatsApp and email in 30+ languages; LeadsNow.ai is the done-for-you option. After them come Yellow.ai, Sprinklr, Zendesk, Ada and Intercom Fin (4 of 4 channels each), then Asksuite, TP and HiJiffy.
Where Zian fits for travel support
Zian is our first pick for a travel business that needs one AI agent answering live phone calls, web chat, WhatsApp and email around the clock in 30+ languages, with the night shift handled without hiring. Its Customer Support Agent is listed as 24/7 in 30+ languages, connecting to a knowledge base and third-party systems. Its AI receptionist answers inbound calls 24/7, qualifies, books, transfers and takes messages.
For travel that means the traveller who rings from a departure gate at 3am local time reaches an agent that speaks their language and can look up the answer. The same agent then follows up on the channel they replied on: SMS, email, WhatsApp, Instagram DMs or Facebook Messenger. Zian also lists voicemail handling, voice cloning, CRM and API integrations (HubSpot, Salesforce, HighLevel, Zapier) and private model deployment on your own infrastructure. The honest limit, in one line: Zian is in a partnership-application beta with no published prices, and it does not publish a GDS or booking-engine integration, so plan on connecting your booking system through its API. If you want the desk run for you rather than software to run yourself, LeadsNow.ai is the done-for-you option. It is a managed, pay-per-result service that runs on Zian, and its site says every lead is answered in under 60 seconds, 24/7.
AI travel customer support platforms, multilingual: the ranking
We scored eight vendors whose travel or hospitality pages we read (seven live on 18 October 2026, and Ada’s from a dated Wayback capture), plus Zian and LeadsNow.ai, against one channel-coverage rule. The table is the result; the rule is in the box underneath it, written before any cell was filled.
| Rank | Platform | Live voice calls | Web or app chat | Score (of 4) | Languages its pages state for AI agents | Travel evidence on its own site | ||
|---|---|---|---|---|---|---|---|---|
| 1 | Zian AI (platform) | Yes | Yes | Yes | Yes | 4 | 30+ | None published; general support and reception agents |
| 2 | LeadsNow.ai (done for you, runs on Zian) | Not stated in the claims we use | Not stated in the claims we use | Not stated in the claims we use | Not stated in the claims we use | Not scored (managed service) | Not stated in the claims we use | Leads answered in under 60 seconds, 24/7; pay-per-result |
| 3 | Yellow.ai | Yes | Yes | Yes | Yes | 4 | 500+ languages and dialects (Nexus VOX voice); 135+ (omnichannel page); 100+ (voice AI page) | Travel page: self-serve “up to 90%” of travel queries; help with “travel disruptions” |
| 4 | Sprinklr | Yes | Yes | Yes | Yes | 4 | 100+ (Sprinklr blog) | Airline story: booking changes on WhatsApp, about 70% containment on eligible requests |
| 5 | Zendesk AI agents | Yes (needs Zendesk voice) | Yes | Yes | Yes | 4 | 80 (text); 53 (voice, launch post); 44 (voice locale table) | Travel AI page and travel AI agents guide |
| 6 | Ada (from Ada’s travel page as captured 10 October 2025; ada.cx blocks our fetcher) | Yes | Yes | Yes | Yes | 4 | 50+ | Airline page (Wayback capture 10 October 2025): refunds, baggage status, seat selection, rebookings; “DOT/EU261 automation” |
| 7 | Intercom Fin | Yes (Fin Voice, on your existing telephony) | Yes | Yes | Yes | 4 | 45+ (update page); 45 on text channels; voices in 28 languages | Fin guide “AI for High-Volume Travel and Hospitality” (9 September 2026): peak season, IROPs, cancellations and refund spikes |
| 8 | Asksuite (hotels) | Partial (“text or audio”) | Yes | Yes (AI answers out of hours) | Yes (Sophia AI launch post: service 24/7 “across all channels”, email listed; its inbound email page is template- and agent-led) | 3.5 | 50+ | Hotel reservation pages; 56% of demand outside business hours (Asksuite figure) |
| 9 | TP (TP.ai Connect and conversational AI) | Yes (AI voice agents; “a full voice/chatbot”) | Yes (24/7 bots on web, built on Kore.ai, Cognigy or Microsoft) | Yes (bots connected to WhatsApp) | Partial (human-led support “across all channels”; no TP page we read names an AI agent on email) | 3.5 | Not stated for AI agents; 400+ languages and dialects company-wide | Travel page: ramp up for “travel delays”; conversational AI page: airline tickets, check-in, baggage |
| 10 | HiJiffy (hotels) | Partial (voice messages, answered in text) | Yes | Yes | Partial (AI drafts, staff send) | 3 | 132 (Pro plan); 3 (Basic plan); 6 for voice messages | Hotel and travel chatbot pages; PMS and booking-engine integrations |
Methodology box (written before scoring). Inclusion: a vendor is ranked only if we read a travel or hospitality page on its own site on 18 October 2026, or, where the live site blocked our fetcher, a dated Wayback Machine capture of that page (Ada only; the row is labelled). Positions 1 and 2 are fixed by our publishing rule: zian.ai publishes this list, Zian appears in it, and LeadsNow.ai is our sister brand. Read those two rows with that in mind. Channel: one of four, a live voice call, web or in-app chat, WhatsApp, or email. Yes (1 point): the vendor’s own page says an AI agent answers on that channel without a person sending each reply. Partial (0.5): the page shows AI on the channel, but either a person sends the reply (drafting or copilot), or the AI handles recorded voice or audio messages rather than live calls, or the page describes human-led coverage of the channel without saying an AI agent answers it. Not stated (0): none of the pages we read say either. Tie-break: the largest language count the vendor’s own pages state for its AI agents, on any channel; a company-wide count of human agents’ languages does not count. We applied the same definitions to Zian (from its published capabilities and home page) and to LeadsNow.ai (from the only claims we use for it).
One vendor that is often named for travel is not ranked, and the reason is the rule, not a judgement on the product: Netomi’s sitemap lists only three legal pages, and the travel paths we tried returned its one-page home page (“New engagements are by referral”). Ada’s live site blocked every www.ada.cx URL we tried (four, including its sitemap), so its row comes from a Wayback Machine capture of www.ada.cx/industry/travel/ dated 10 October 2025. Ada’s home page still linked that travel page in a Wayback capture dated 25 September 2026; check the live page before you rely on it.
Five of the eight vendors hit 4 of 4 channels, so the tie-break on language counts decides most of the order. Yellow.ai by itself states 100+, 135+ and 500+ on three different pages. Zendesk lists 80 languages for text, says 53 for voice in its 1 September 2026 launch post, and its voice locale table lists 44. Before you trust any count, run each language you sell in through a language parity test against your English baseline.
The disruption-surge capacity table: what the AI must absorb alone
A travel support desk is staffed for an ordinary day. It fails on the night a long-haul flight cancels, or the morning a storm shuts a hub. The table below is a worked model, not survey data. Every input in the first three numeric columns is an illustrative assumption you should replace with your own booking data. The method stays the same: contacts per hour = travellers affected × share who contact you ÷ hours over which they do it. Desk capacity = agents on shift × (60 ÷ handle time in minutes). We assumed a 10-minute handle time for a disruption contact, so one agent clears 6 contacts an hour.
| Event (illustrative) | Your travellers affected | Share who contact you, over | Contacts per hour | Human desk on shift absorbs | Contacts per hour the AI must take alone | What the AI must do alone | What must reach a person (our rule) |
|---|---|---|---|---|---|---|---|
| One long-haul flight cancelled at 10pm | 280 | 70% over 2 hours | 98 | 24 (4 agents) | 74 (76% of the peak; 13 more agents needed to close it) | Confirm the cancellation; offer the three choices (refund, re-routing now, re-routing later); record the choice; send the written notice of rights; tell travellers what care is available | Travellers with reduced mobility, unaccompanied children, anyone stranded without a hotel, any dispute about the reason |
| Storm closes a hub airport for a day | 4,000 | 50% over 6 hours | 333 | 150 (25 agents) | 183 (55%; 31 more agents) | Status updates in the traveller’s language; rebooking within your rules; hotel and meal information; callbacks queued by departure time | Medical needs, travellers with a disability whose new routing changes their connections, group bookings |
| Strike announced 48 hours ahead | 1,500 | 40% over 24 hours | 25 | 150 (25 agents) | 0 (the desk can absorb it) | Proactive outbound notice by SMS, email and WhatsApp; take choices before the day | Anyone the strike leaves without a valid alternative |
| Airline IT outage grounds several departures | 12,000 | 30% over 4 hours | 900 | 150 (25 agents) | 750 (83%; 125 more agents) | Honest holding answers: what is known, when the next update comes, what rights apply if the flight cancels; take callback numbers | Travellers whose onward connection, cruise or tour departs before the outage clears |
| Hotel overbooked on one night | 30 | 100% within 1 hour | 30 | 6 (1 night manager) | 24 (80%; 4 more staff) | Explain the relocation, the transfer and the booking reference for the new property, in the guest’s language | Guests who refuse relocation, families split across properties, loyalty-tier complaints |
Read across the AI column and one pattern holds: in four of the five events the AI has to carry more than half the peak, and in the strike row it carries none. The people column does not shrink in a surge. Under EU261 Article 11, travellers with reduced mobility and unaccompanied children have the right to care “as soon as possible”. Our rule is to route them to a person at once, and to route anyone whose question falls outside what the AI is permitted to do. Zendesk’s own travel guide says the same of AI agents in a disruption: an agent “should escalate requests that require human judgment or fall outside its permissions”.
Our guide to AI-to-human handoff and context transfer covers what to pass across so the person picks up with the booking reference, language and choice already recorded.
The refund-clock map: EU261, UK261, US DOT and package travel
An AI agent that takes refund choices during a surge is starting a legal clock with every “yes, refund me”. EU261 and UK261 bind the operating air carrier, the US rule binds the carrier or ticket agent that is merchant of record, and the package rule binds the organiser. So an online travel agency or tour operator has to know which row it sits in before it lets an AI promise anything.
| Jurisdiction and instrument | Who it applies to | Refund deadline | Care and information duties the AI touches | Source |
|---|---|---|---|---|
| EU: Regulation (EC) No 261/2004, Articles 5–9 and 14 | Operating air carrier; passengers departing an EU airport, or flying into the EU on an EU carrier unless they received benefits or compensation and were given assistance in the country they left (Article 3); not free or reduced fares unavailable to the public | Reimbursement “within seven days” of the full cost of the ticket “at the price at which it was bought”, for the parts of the journey not made, and for parts already flown if the flight no longer serves any purpose (Article 8(1)(a)); vouchers only with the passenger’s signed agreement (Article 7(3)) | Meals, hotel, transport, and two telephone calls or emails (Article 9); written notice of rights on cancellation, denied boarding or a delay of at least two hours (Article 14(2)) | EUR-Lex |
| UK: Regulation (EC) No 261/2004 as it applies in the UK | Operating air carrier; passengers departing a UK airport, or arriving in the UK on a UK or EU carrier, or in the EU on a UK carrier, unless they received benefits or compensation and were given assistance in the country they left (Article 3) | Seven days, same wording (Article 8(1)(a)); compensation £220, £350 or £520 by distance (Article 7) | Same care list (Article 9) | legislation.gov.uk |
| EU: Package Travel Directive (EU) 2015/2302, Articles 12 and 16 | Package organiser (implemented through each member state’s law) | Refunds “without undue delay and in any event not later than 14 days after the package travel contract is terminated” (Article 12(4)); a traveller who terminates for their own reasons gets payments back minus the termination fee, and a full refund only where unavoidable and extraordinary circumstances apply (Article 12(1)–(2)) | Assistance “without undue delay” to a traveller in difficulty: health services, local authorities, consular help, distance communications, alternative travel arrangements (Article 16) | EUR-Lex |
| US: 14 CFR part 260 (DOT refund rule, 89 FR 32760; compliance date for the refund provisions 28 October 2024) | Carrier that is merchant of record, on flights to, from or within the US | Automatic refund: 7 business days for credit card purchases, 20 calendar days for cash, cheque, debit card and other forms (§ 260.2), in the original form of payment unless the traveller agrees to a cash equivalent (§ 260.10) | Tell travellers owed a refund that they are owed one, through the channels they subscribed to, including email and text (§ 260.9(b)); a voucher counts only if the traveller affirmatively accepts it (§ 260.7) | eCFR |
| US: 14 CFR 399.80(l) | Ticket agent (such as an online travel agency) that is merchant of record | Prompt refund “upon request”: 7 business days of receiving the carrier’s information (card), 20 calendar days of the refund becoming due (other) | Must tell the traveller they are entitled to a refund before offering a credit | eCFR |
| Australia | Not mapped | Not mapped | Not mapped | The ACCC’s travel pages returned HTTP 403 to our server on 18 October 2026; check accc.gov.au directly |
Three limbs change what the AI is allowed to say. First, EU261 compensation (EUR 250, 400 or 600 by distance) is not owed if the carrier proves extraordinary circumstances that could not have been avoided (Article 5(3)), or if the passenger was told at least two weeks ahead, or later but with re-routing inside the time limits in Article 5(1)(c). The refund and care duties in Articles 8 and 9 still apply in a storm or a strike. An AI that says “weather, so nothing is owed” is wrong. Second, care under EU261 for delays starts at 2 hours for flights of 1,500 km or less. It starts at 3 hours for longer flights within the EU and other flights between 1,500 and 3,500 km, and at 4 hours for everything else (Article 6). A delay of at least five hours triggers the Article 8 refund right. Third, the US rule’s trigger for a significant change is a departure moved 3 hours or more earlier, or an arrival 3 hours or more later, on a domestic itinerary (6 hours on an international one). There are five other triggers: a different airport, an extra connection, a downgrade, and two changes specific to travellers with a disability. One enforcement carve-out applies as at 18 October 2026: DOT is not enforcing the cancelled-flight refund rule where a flight is only renumbered and operates with no significant change or delay, a pause extended on 7 July 2026 to 7 July 2027 (91 FR 41556).
Worked dates. A traveller rejects a rebooking on Thursday 22 October 2026. Under EU261 or UK261 the reimbursement is due by Thursday 29 October. The Regulation says seven days, not business days, and does not define the start point; we counted from the day of the choice. Under the US rule, a credit card refund is due by Monday 2 November: seven business days, and no US federal holiday falls in that span. A debit card refund is due by Wednesday 11 November, 20 calendar days on. If the same traveller had terminated an EU package on 22 October, the organiser’s refund (in full, or minus the termination fee where Article 12(1) applies) would be due without undue delay and in any event by Thursday 5 November. Your AI should record the timestamp of the choice in the booking, because that timestamp is what everyone counts from.
Running a 24/7 desk in 30+ languages? Zian’s Customer Support Agent and AI receptionist answer calls, chat, WhatsApp and email around the clock, and transfer to your team when a person is needed.
What an AI travel agent has to do on each channel at 3am
The same disruption arrives on four channels at once, and each one has a different failure mode.
Voice. Zendesk’s voice AI agents became generally available on 1 September 2026, but they need Zendesk voice. Zendesk says they are not available with Talk Partner Edition and are “not intended to be used to evaluate and classify emergency calls”. Intercom says Fin Voice works with your existing telephony setup, and its channels page offers voices in 28 languages against 45 on text channels. HiJiffy’s voice feature answers voice messages with text, not live calls. Asksuite describes its AI assistant as answering “via text or audio”. If phone is where your travellers ring at 3am, count only the platforms whose pages say an AI agent answers live calls.
Chat and WhatsApp. These carry the bulk of rebooking. Sprinklr’s published airline story is the clearest evidence we found that an AI can complete a booking change end to end on WhatsApp. Sprinklr says a single change can need “seven to eight connected system transactions”, and that booking changes were 8% to 9% of WhatsApp and live-chat contacts. The story is one unnamed airline, and the roughly 70% containment figure is on eligible requests, not all of them. Asksuite’s WhatsApp page describes reservation staff replying in business hours and its AI assistant answering out of hours, which is the pattern most hotels start with.
Email. Email is where the refund paper trail lives: the written notice, the confirmation of the choice, the refund amount. The US rule expects refund notices through the channels a traveller subscribed to, including email and text. Platforms differ on whether the AI sends or only drafts. HiJiffy says of its Email Copilot that “nothing is sent automatically”. Yellow.ai, Zendesk, Sprinklr, Ada (in its 2025 capture) and Intercom Fin describe AI agents that reply on email. Asksuite’s launch post for its Sophia AI lists email among the channels Sophia serves 24/7, though its inbound email page is built around templates and reservation agents.
A platform that covers all four channels still needs your booking system behind it. The AI can only offer a rebooking that your systems will accept. For the support-agent side of the stack, see how AI customer support agents handle tier-1 requests 24/7.
Multi-currency refunds: read the amount, never convert it
Both main refund rules key the refund to what the traveller actually paid. EU261 says reimbursement is of the full cost of the ticket “at the price at which it was bought”. The US rule says the refund goes back in the original form of payment, unless the traveller agrees to a cash equivalent, with no processing fee kept. Our operational rule follows from that: the AI should read the paid amount and currency from the booking or payment record and quote that, never a converted figure. Where a booking was paid in two currencies, or part-paid with points, hand it to a person. The US rule treats airline miles as a form of payment to be returned, which an AI can state but should not calculate.
Who each platform is wrong for
- Zian is wrong for you if you need a published GDS or booking-engine connector on day one, or published prices before you talk to anyone. It is in a partnership-application beta.
- LeadsNow.ai is wrong for you if you want to run and tune the agent in-house. It is a managed service.
- Yellow.ai is wrong for you if you want one language figure to plan around. Its pages state three.
- Sprinklr is wrong for you if you want a light tool. Its travel page leads with the largest airlines and hotel chains, and describes support across 30+ channels plus 24/7 social media monitoring.
- Zendesk is wrong for you if your phone lines will not run on Zendesk voice. Its voice AI agents are assigned to Zendesk voice lines, are not available with Talk Partner Edition, and Zendesk Contact Center support is listed as planned for a future release, as at 18 October 2026.
- Ada is wrong for you if you need its current travel claims confirmed from the live site: our row rests on a capture dated 10 October 2025, because ada.cx blocks our fetcher.
- Intercom Fin is wrong for you if you need the same language list on the phone as in chat. Its channels page offers voices in 28 languages against 45 on text channels, and its own travel guide says most teams start on chat and email and extend as trust builds.
- HiJiffy is wrong for you if you need the AI to answer live phone calls, or if you are on its Basic plan and serve guests in more than 3 languages.
- Asksuite is wrong for you if you are not a hotel.
- TP is wrong for you if you want one vendor’s own software. Its bots are built on partner platforms (Kore.ai, Cognigy, Microsoft) and delivered as a managed, human-led service it calls “human-centered customer support, elevated by AI”.
For the same comparison outside travel, our wider ranking of multilingual AI support agent platforms covers Sierra, Decagon, Cognigy and Lorikeet.
Should you build a disruption desk yourself or hand it over?
Run your own surge table first; the gap column decides it. If the gap in your worst plausible event is under 6 contacts an hour, one extra person on call covers it at a 10-minute handle time, and you may not need an AI agent for disruption at all. If the gap appears only in events you get 48 hours’ warning of, proactive outbound messaging plus overtime will usually do. Above that, in the cancellation, storm and outage rows, the arithmetic is the argument. Closing a 74-contact-an-hour gap at 10pm with people means 13 extra agents on a night shift, for an event you cannot schedule.
If you build it yourself, the honest cost is not the AI licence. It is the integration that lets the AI change a booking, the refund-clock logic in every jurisdiction you sell into, the language testing, and someone owning the knowledge base when a strike notice lands at midnight.
Want your 3am calls answered in the caller’s language? Apply to run Zian’s support and reception agents across voice, chat, WhatsApp and email.
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| Reimbursement within seven days; EUR 250/400/600; care list; 2/3/4-hour and 5-hour delay limbs; written notice at 2 hours | European Union (Regulation (EC) No 261/2004) | EUR-Lex | 18 October 2026 |
| UK seven days; £220/£350/£520; UK scope | UK Government (legislation.gov.uk) | Article 8, Article 7, Article 3 | 18 October 2026 |
| Package refund within 14 days; assistance without undue delay | European Union (Directive (EU) 2015/2302) | EUR-Lex | 18 October 2026 |
| 7 business days / 20 calendar days; 3-hour and 6-hour triggers; original form of payment; affirmative acceptance of vouchers | US Department of Transportation (14 CFR part 260) | eCFR | 18 October 2026 |
| Compliance date for the refund provisions: 28 October 2024 | US Department of Transportation (Federal Register, 89 FR 32760) | Federal Register | 18 October 2026 |
| Refund rule not enforced for renumbered flights with no significant change or delay, until 7 July 2027 | US Department of Transportation (Federal Register, 91 FR 41556) | Federal Register | 18 October 2026 |
| Ticket agent refunds upon request, 7 business days / 20 calendar days | US Department of Transportation (14 CFR 399.80(l)) | eCFR | 18 October 2026 |
| Zendesk: 80 text languages | Zendesk | Languages supported by AI agents | 18 October 2026 |
| Zendesk: voice AI agents generally available 1 September 2026, 53 languages | Zendesk | Announcement | 18 October 2026 |
| Zendesk: 44 languages in the voice locale table | Zendesk | Configuring multi-language support for voice AI agents | 18 October 2026 |
| Zendesk: voice limitations; email and WhatsApp channels; travel escalation guidance | Zendesk | About voice AI agents, email, WhatsApp, travel guide | 18 October 2026 |
| Ada: chat, SMS, voice, email and WhatsApp “with one AI agent”; 50+ languages; DOT/EU261 automation | Ada | Ada travel page, Wayback capture 10 October 2025 | 18 October 2026 (capture dated 10 October 2025) |
| Intercom Fin: 45+ languages; 44 named besides English | Intercom (Fin) | Multilingual Fin | 18 October 2026 |
| Intercom Fin: 45 languages on text channels; voices in 28 languages; voice, email, Messenger, WhatsApp and other channels | Intercom (Fin) | Fin channels, Fin Voice, social messaging, email | 18 October 2026 |
| Intercom Fin: travel and hospitality guide, 9 September 2026 (IROPs, cancellations, refund spikes) | Intercom (Fin) | AI for High-Volume Travel and Hospitality | 18 October 2026 |
| Sprinklr: 100+ languages, 25+ channels | Sprinklr | Sprinklr blog | 18 October 2026 |
| Sprinklr: 8% to 9% of contacts, seven to eight system transactions, about 70% containment | Sprinklr | Airline story | 18 October 2026 |
| Sprinklr: AI agents on voice, chat, email, social and messaging; 30+ channels for travel | Sprinklr | AI agents, travel and hospitality | 18 October 2026 |
| Yellow.ai: 500+, 135+ and 100+ languages; up to 90% self-serve on travel queries | Yellow.ai | Nexus VOX, omnichannel, voice AI agents, travel | 18 October 2026 |
| HiJiffy: 132 / 3 languages by plan; 6 voice-message languages; voice messages answered in text; Email Copilot sends nothing automatically | HiJiffy | Plans and pricing, channels, Email Copilot | 18 October 2026 |
| Asksuite: 50+ languages; 56% of demand outside business hours; AI answers WhatsApp out of hours; Sophia AI 24/7 across all channels, email listed; template- and agent-led email page | Asksuite | home page, omnichannel platform, WhatsApp, Sophia launch post (16 September 2025), inbound email | 18 October 2026 |
| TP: 400+ languages and dialects (company-wide); AI voice agents in TP.ai Connect; 24/7 voice and chat bots on web, telephony or WhatsApp | TP | About TP, TP.ai Connect, conversational AI | 18 October 2026 |
| LeadsNow.ai: under 60 seconds, 24/7; pay-per-result | LeadsNow.ai | leadsnow.ai | 18 October 2026 |
| Surge model inputs (travellers affected, contact share, hours, 10-minute handle time, agents on shift) | zian.ai worked example: illustrative assumptions, not measured data | This page | 18 October 2026 |
Frequently asked questions
What is the best AI travel customer support platform for multilingual 24/7 coverage?
On our channel-coverage rule, Zian ranks first for one agent across live calls, chat, WhatsApp and email in 30+ languages, and LeadsNow.ai is the done-for-you option. Among the travel vendors we read, Yellow.ai, Sprinklr, Zendesk, Ada and Intercom Fin cover all four channels, followed by Asksuite, TP and HiJiffy.
How fast does a refund have to be paid when my flight is cancelled in Europe?
On a flight the Regulation covers, the airline must offer you the choice of re-routing or reimbursement within seven days of the ticket price paid for the parts of the journey not made (and for parts already flown if the trip no longer serves any purpose), as Article 8(1)(a) of Regulation (EC) No 261/2004 says. The UK version keeps the same seven days. Vouchers count only with your signed agreement.
What does the US DOT automatic refund rule require?
On a flight to, from or within the US, if the carrier that took your payment cancels or significantly changes the flight and you do not accept the alternative, it must refund you automatically: within 7 business days for a credit card purchase and 20 calendar days for other payments, in the original form of payment. If a travel agency took the payment, it must refund on request, on the clocks in 14 CFR 399.80(l).
Does a storm or a strike mean the airline owes me nothing?
No. Extraordinary circumstances that could not have been avoided with all reasonable measures can remove the EU261 compensation payment, if the airline proves them, but the right to a refund or re-routing and the right to care, such as meals and a hotel, still apply.
Can an AI agent answer travellers’ phone calls at 3am in their own language?
Yes, if the platform’s AI answers live calls in that language. Check the voice language list, not the text list: Zendesk lists 80 languages for text and 44 in its voice locale table. HiJiffy answers voice messages with text rather than live calls.
Which travellers should always reach a human agent during a disruption?
Travellers with reduced mobility, unaccompanied children, anyone with a medical or safety issue, anyone stranded without accommodation, and any request outside what the AI is permitted to change. EU261 gives the first two groups the right to care as soon as possible.
Should an AI agent convert a refund into my currency?
No. EU261 refunds the price at which the ticket was bought and the US rule refunds to the original form of payment unless you agree to a cash equivalent, so the AI should quote the amount and currency on the booking and leave any conversion to the payment provider.