--- title: "WhatsApp for Travel Agencies and Airlines: Alerts and Templates" description: "WhatsApp for travel agencies and airlines: booking confirmations, itinerary, gate-change alerts, SMS fallback, visa reminders, opt-in upsell and peak season." canonical: "https://omnichannels.ai/blog/travel-airline-customer-messaging/" language: "en" updated: "2026-11-03" publisher: "BroadNet Technologies" brand: "OmniChannels.ai" category: "marketing" primaryQuery: "whatsapp for travel agencies and airlines" keywords: ["whatsapp for travel agencies", "whatsapp for airlines", "flight delay notification whatsapp", "booking confirmation whatsapp", "travel customer messaging", "gate change alert sms", "whatsapp business api travel", "itinerary whatsapp template"] published: "2026-11-03" author: "OmniChannels.ai Editorial Team" reviewer: "BroadNet Messaging Solutions Team" readingMinutes: 11 answer: "Travel agencies and airlines use WhatsApp for booking confirmations, itineraries, check-in and boarding information, delay and gate-change alerts, document reminders and support. Send trip-specific updates as utility templates, offers as marketing templates to opted-in customers, and add an SMS fallback for urgent alerts. Use one approved template per language, and plan peak-season volume against Meta's messaging limits." takeaways: ["Messages tied to a customer's own booking, such as confirmations, itinerary changes and document reminders, are utility template candidates; upsells and promotions are marketing and need opt-in.", "Meta classifies mixed-content templates as marketing, so keep an offer out of a delay alert or boarding message.", "A customer's message opens a 24-hour window for free-form replies, which suits rebooking questions during disruption.", "Urgent alerts need a second path: configure WhatsApp first and SMS as fallback so a gate change reaches travellers whose WhatsApp message is not delivered.", "Prepare for peak season in advance: quality rating, messaging limits and approved templates in each language decide how many travellers you can reach on the day."] faq: - q: "Can airlines send flight delay notifications on WhatsApp?" a: "Yes, through the WhatsApp Business Platform, with the customer's opt-in and an approved template for messages you start. A delay notice tied to the customer's booking is a utility template candidate, and Meta makes the final category decision. Keep offers out of it, and add an SMS fallback for travellers who do not receive the WhatsApp message." - q: "Do travel agencies need opt-in before messaging customers on WhatsApp?" a: "Yes. Meta requires the recipient's permission and leaves the method to you. Capture it at booking or enquiry, state what you will send, and record the source and time. Ask separately for marketing offers so that service alerts do not depend on a promotional consent." - q: "Which template category is a boarding or gate-change message?" a: "It is a utility candidate if it is non-promotional and specific to the customer's booking, but Meta's documentation does not list flight status among its examples, so the decision rests with Meta's review. Submit it without offers or marketing language, and expect that a mixed message would be treated as marketing." - q: "How do we handle several languages for one trip?" a: "Create a separate template per language and send the one that matches the customer's language preference, which you store at booking. A template submitted in one language with body text in another invites rejection. Keep variables and structure identical across languages so that your system can switch language without changing logic." - q: "Can we send upsell offers such as lounge access or insurance?" a: "Yes, as marketing templates to customers who opted in to offers, and with a clear way to stop them. Send them before the trip when the customer can act, not during a disruption. Do not add the offer to a service message, because Meta treats mixed content as marketing." - q: "What happens when thousands of travellers are affected at once?" a: "Your throughput depends on your phone number's messaging limit, quality rating and your platform's sending capacity. Approve templates early, keep quality high with relevant messages, and have an SMS fallback and an agent queue ready. Test the plan with a small group before peak season." sources: - title: "Template categorization, WhatsApp Business Platform, Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/template-categorization" - title: "WhatsApp Business Messaging Policy" url: "https://whatsappbusiness.com/policy/" - title: "Send messages and the customer service window, WhatsApp Business Platform, Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/messages/send-messages" - title: "WhatsApp Business Platform pricing, Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing" - title: "3GPP TS 23.038: Alphabets and language-specific information" url: "https://www.3gpp.org/dynareport/23038.htm" --- # WhatsApp for Travel Agencies and Airlines: Alerts and Templates Canonical: https://omnichannels.ai/blog/travel-airline-customer-messaging/ Language: en Publisher: OmniChannels.ai by BroadNet Technologies This guide is for travel agencies, tour operators, OTAs and airlines that want to use WhatsApp and SMS across the trip, from booking to return. It covers the messages travellers value, the Meta category each one is likely to use, sample templates, an SMS fallback for urgent alerts, and how to prepare for peak season. It is general information, not legal advice; aviation, consumer and data rules differ by country, so confirm them with your own teams. ## Why does travel suit WhatsApp? Travel has many short, time-sensitive messages tied to one booking, and travellers often use WhatsApp abroad on data or Wi-Fi. A single thread can carry the confirmation, the itinerary, a document, a change and a question, and the customer can answer in the same place. SMS is still valuable, because it works without data and reaches phones where WhatsApp is not installed. The strongest set-up uses both, with the order configured per use case. For hotels, see our guide to [hotel guest messaging on WhatsApp](/blog/hotel-guest-messaging-whatsapp/), and for the sector overview see [travel and hospitality solutions](/solutions/travel-hospitality/). ## Which messages should travel businesses send? Send what helps the traveller at each step and nothing else. The table maps the journey to a Meta category. "Utility candidate" means the message is non-promotional and tied to the customer's booking, but Meta makes the final decision. | Stage | Message | Channel | Likely Meta category | |---|---|---|---| | Booking | Confirmation with reference and key details | WhatsApp, SMS fallback | Utility candidate | | Pre-trip | Itinerary and documents | WhatsApp | Utility candidate | | Pre-trip | Visa, passport and health-document reminders | WhatsApp, email | Utility candidate | | Pre-trip | Check-in opens | WhatsApp, SMS | Utility candidate | | Travel day | Boarding or pick-up details | WhatsApp, SMS | Utility candidate | | Disruption | Delay, cancellation, gate or platform change | WhatsApp then SMS | Utility candidate | | During trip | Questions, rebooking, local help | Free-form inside the 24-hour window | Not a template | | After trip | Feedback tied to the specific trip | WhatsApp | Utility only if tied to the trip | | Anytime | Upgrades, lounge, insurance, next trip offers | WhatsApp | Marketing, opt-in only | | Login | Verification codes | WhatsApp, SMS | Authentication | Meta's documentation says a utility template must have no promotional or persuasive intent and be specific to or requested by the user, or essential to them. It lists account and order examples, including payment reminders and shipping and tracking updates, but does not list flight status, so treat travel updates as candidates and keep them clean. It also says a general feedback survey will not be approved as utility, while one tied to a specific order or interaction can be. Read the full rules in [WhatsApp template categories and approval](/blog/whatsapp-template-categories-approval/). ## How do you write booking confirmation and itinerary templates? Put the facts the traveller will search for in the first lines: reference, dates, places and what to do next. Use variables for the changing parts, keep the structure the same in every language, and add a button to the full itinerary on your own domain. - **Booking confirmed (Utility candidate):** "Hello {{1}}, your booking {{2}} is confirmed for {{3}}. Tap the button to view your itinerary and documents." - **Itinerary ready (Utility candidate):** "Hello {{1}}, your itinerary for {{2}} is ready. Departure: {{3}}. Check-in opens {{4}}. Tap the button for details." - **Document reminder (Utility candidate):** "Hello {{1}}, a reminder to check that your passport and any visa needed for {{2}} are valid for your trip on {{3}}. Reply here if you need help." For the visa and document reminder, state only that the traveller should check requirements and link to the official source for their destination. Entry rules change, so do not summarise them yourself. ## How do you send delay and gate-change alerts? Send the change, what it means, and what the traveller can do, in as few words as possible. A good alert has the flight or trip reference, the new time or place, a rebooking route and a way to reach a person. - **Delay (Utility candidate):** "Hello {{1}}, flight {{2}} on {{3}} is delayed. New departure: {{4}}. Reply here or tap the button for options." - **Gate change (Utility candidate):** "Hello {{1}}, the gate for flight {{2}} has changed to {{3}}. Boarding starts at {{4}}." - **Cancellation (Utility candidate):** "Hello {{1}}, we are sorry: flight {{2}} on {{3}} has been cancelled. Tap the button to choose a new flight, or reply here to reach an agent." Do not add offers, sales language or surveys to these. Meta says mixed-content templates are classified as marketing, and a marketing line in a delay message can change its category, its cost and its audience. ### Rules for alerts 1. **Trigger from your operations system**, not by hand; use a webhook or API event when the status changes. 2. **Send once per change** and suppress duplicates when the status flips back. 3. **Open the human path**: when a traveller replies, the 24-hour window opens, and an agent or bot can answer freely. See [WhatsApp 24-hour customer service window](/blog/whatsapp-24-hour-customer-service-window/). 4. **Use fallback** for urgent changes (next section). 5. **Show times with the time zone** so that cross-border travellers do not misread them. ## How does SMS fallback work for urgent alerts? If the WhatsApp message is not delivered or read within the time you set, send a short SMS with the essentials. Fallback protects the message that cannot wait, such as a gate change, and works for travellers without WhatsApp or data. Configure it per use case: WhatsApp first and SMS after a short wait for gate changes; email only for non-urgent documents. Delivery statuses from every channel arrive in one webhook format, so your system can stop the fallback as soon as the first message is delivered or read. Our guide to [channel fallback strategy](/blog/channel-fallback-strategy/) explains the design. An SMS must fit its limit. With GSM-7 a single message holds 160 characters; with Unicode, including Arabic, 70. Examples that fit one segment (character counts for the filled text): | Text | Alphabet | Length | Limit | |---|---|---|---| | `Flight EK201 gate changed to B14. Boarding 18:40. Info: omni.ai/f9k2` | GSM-7 | 68 | 160 | | `Flight EK201 delayed. New departure 21:15. Options: omni.ai/f9k2` | GSM-7 | 63 | 160 | For Arabic text, plan on 70 characters per segment and keep alerts shorter. Check drafts in the [SMS character counter](/tools/sms-character-counter/) and read [SMS character limits and Arabic](/blog/sms-character-limits-unicode-arabic/). Remember that SMS rules are national. Transactional alerts and promotions are treated differently in many markets, so check the market's rules and registration needs on the [sender ID pages](/sender-id/) before you launch. ## How do you offer upsells without annoying travellers? Ask first, send before the trip and keep service messages clean. Upsells are marketing: they need opt-in and an easy way to stop, and they should not appear in disruption messages. Good moments are right after booking (seat, baggage, transfers), a few days before travel (lounge, insurance, local tours) and after the trip (next destination). Keep the cadence low and let the traveller choose topics. - **Add-on offer (Marketing):** "Hello {{1}}, your trip to {{2}} starts on {{3}}. Want to add airport transfers or a lounge pass? Tap below to see options. Reply STOP to unsubscribe from offers." Record the marketing consent separately from the service consent, and read our guide to [opt-in and consent for multichannel campaigns](/blog/opt-in-consent-multichannel-campaigns/). For templates in general, try the [WhatsApp template preview](/tools/whatsapp-template-preview/). ## How do you support several languages? Create one template per language and send the one the traveller prefers. Store the language at booking, keep variables in the same order in every version, and make sure the declared template language matches the text. Arabic needs a right-to-left preview; check it in the phone preview before you submit. See our guide to [Arabic customer messaging](/blog/arabic-customer-messaging-best-practices/). ## How do you prepare for peak season? Peak days bring volume, disruption and support queues together. Prepare in advance so the system, the templates and the team are ready. 1. **Approve templates early**, in every language, and do not rely on one still in review. Meta can pause or recategorise templates, so watch template status. 2. **Check messaging limits and quality.** Your phone number's limit and quality rating affect how many people you can start conversations with. See [WhatsApp messaging limits and quality rating](/blog/whatsapp-messaging-limits-quality-rating/). 3. **Stage large sends.** Release alerts to affected travellers in groups rather than in one burst, and keep high-priority alerts first. 4. **Prepare the agent queue.** Assign by language and issue type, and use saved replies for common questions. 5. **Add automation for the top questions**: baggage, rebooking, refund status, documents, with a human handover. 6. **Run a dry run** with your own team's numbers to test templates, fallback and reporting. ## Worked example: a Dubai tour operator "Desert Compass Tours" (synthetic) sells holiday packages and sends about 400 travellers a week during peak season. 1. At booking, the website captures the traveller's number, language and two consents: service updates and offers. 2. A confirmation template (utility candidate) goes out in the traveller's language, and the itinerary follows ten days before travel. 3. A document reminder goes out two weeks before departure, linking to the official government page for the destination. 4. On travel day a pick-up message goes by WhatsApp, with SMS fallback if it is not delivered within a few minutes. 5. If a flight changes, the operations system fires a webhook and a delay alert goes out; replies open the 24-hour window for the agent. 6. After the trip, a feedback template tied to the trip is sent; offers go only to those who opted in. The operator reviews delivery, read and reply rates, the share of alerts needing fallback, agent time to first reply and opt-outs. ## Common mistakes - Putting offers in delay, boarding or cancellation messages. - Using one language for all travellers. - Sending alerts by hand instead of from an event. - No SMS fallback for gate changes. - Reminding about visas with your own summary instead of the official source. - Waiting for peak season to submit templates. - Asking for card numbers or passport numbers in chat. WhatsApp's business policy prohibits asking people to share full payment card numbers and personal ID card numbers; use a secure form. ## What does it cost? Meta charges per delivered message by category and market, and BroadNet charges WhatsApp at Meta's rate with zero markup. Meta's documentation says that from 1 October 2026 service messages and utility templates sent inside the customer service window are charged, with 1,000 free service messages per business phone number each month. We do not print rates; use [WhatsApp pricing by country](/whatsapp-pricing/), the [WhatsApp pricing calculator](/tools/whatsapp-pricing-calculator/) and our [SMS pricing](/sms-pricing/) pages. ## How OmniChannels.ai helps OmniChannels.ai connects WhatsApp, SMS, RCS, email and more through one platform. You can build WhatsApp templates for marketing, utility and authentication with a phone preview and approval tracking, run campaigns with scheduling, and set channel fallback such as WhatsApp then SMS per use case. Delivery statuses arrive in one webhook format, replies reach the [Omni Inbox](/platform/unified-inbox/), and chatbots and AI agents in English and Arabic hand over to a person. Our team helps with WhatsApp onboarding and sender ID registration; approvals stay with Meta and the operators. [Book a demo](/demo/).