What regional airlines put on one passenger record in Salesforce

3 September 2026
Arcsen

A passenger whose bag missed a connection does not think in systems. She calls the contact centre, sends a WhatsApp message in Arabic and emails customer relations, and expects each person to know what the last one said. At most regional airlines they do not. The booking sits in the passenger service system (PSS), the bag file in a baggage tracing tool, the points in the loyalty platform and the complaint in a shared inbox.

Salesforce has no airline cloud. Its travel, hospitality and transportation solution builds on Customer 360, Data 360 and Agentforce, so an airline assembles passenger CRM from standard products. The design work comes down to three decisions: what goes on the passenger record, what stays in the PSS, and where an AI agent may answer. This guide sets out how regional airlines make them, in Arabic and English.

What goes on the passenger record

Give each kind of work one home, and let the record show the rest. This is the split we use with airlines:

Work	Where it runs	What the record shows	System of record
Complaints, refunds and baggage	Service Cloud cases, one record type per reason	Open and closed cases, with the flight and booking each one concerns	Salesforce for the case. The PSS and revenue accounting for the refund itself
Corporate and travel-agent sales	Sales Cloud accounts, opportunities, quotes and contracts	The company or agency behind the booking, its agreement and its account manager	Salesforce for the agreement. The PSS for fares and tickets
Suppliers and partners	Experience Cloud portals, with cases behind them	Invoices, payments and documents the partner has raised	The ERP for invoices and payments
Loyalty	Fields and components fed by the loyalty platform	Member number, tier, balance and recent activity	The loyalty platform
Bookings and flights	Read from the PSS through integration	Upcoming and past trips, and any disruption to them	The PSS and the operations systems
Consent and preferences	Salesforce, shared with marketing	Language, channel and marketing consent, with proof	Salesforce

One record also needs one passenger. Bookings carry names typed by agents, and loyalty and web accounts carry emails and phone numbers, so agree the identifiers and matching rules before the first data load. Salesforce allows up to five active duplicate rules per object, but its documentation says their settings are overridden, with no alert, when records arrive through data import tools or the APIs. Every integration that loads passengers needs its own matching step.

Complaints, refunds and baggage as cases

Every contact becomes a case with a reason, a flight, a booking reference and an owner, whichever channel it arrived on. Four choices matter most:

Separate the reasons. Complaints, refund requests, delayed or damaged bags, special assistance and compensation claims follow different rules and approvers. Give each its own record type, queue and closure codes, so you can report cost and cause by route.
Keep the money elsewhere. The case tracks a refund; the PSS and revenue accounting process it. Show the refund status on the case through integration, and keep payment details out of Salesforce.
Link the bag file. Store the baggage tracing reference on the case and show the tracing status beside it, so the contact centre can answer without a second screen.
Route by language as well as reason. Arabic conversations go to Arabic-speaking staff first, and replies, templates and closure letters exist in both languages.

What stays in the PSS, and how integration carries it

The PSS remains the system of record for inventory, reservations, ticketing and departure control. Revenue accounting and the ERP keep the money, and the loyalty platform keeps the points. Salesforce needs a current view of all of them, carried by an integration layer such as MuleSoft, in three patterns:

On demand. When an agent opens a case or a passenger signs in, fetch the current booking and flight from the PSS. Store little, because a copied booking goes stale at the next schedule change.
Events. A delay, cancellation or gate change published by operations creates work in Salesforce: the list of affected passengers, proactive messages, and cases for those who need a person.
Batch. Trip history, loyalty statements and finance status, loaded overnight for reporting and segmentation.

Where an agent answers, and where a person takes over

Disruption and policy questions arrive in waves, at any hour and in two languages, which makes them a good fit for an AI agent. An Agentforce Service Agent answers conversations on channels including WhatsApp, web chat, in-app chat and SMS, and its Answer Questions with Knowledge action replies from knowledge articles and uploaded files, using only articles the requesting user can access. The line between the agent and your people is the design:

The passenger asks	The agent can	A person takes over
Is my flight delayed, and what are my options?	Give a verified passenger the status and the rebooking options your systems publish	Rebooking with a fare difference, a waiver or a group
What is my baggage allowance? Can I fly with medical equipment?	Answer from approved policy articles, in Arabic or English	Medical clearance, special assistance and anything the articles do not cover
Where is my refund?	Report the refund case status to a verified passenger	Refunds outside policy, chargebacks and disputes
My bag has not arrived	Open or update the baggage case and report the tracing status	Compensation, damaged items and repeat cases
I want to complain	Log the complaint as a case with the booking	Every resolution, apology and compensation offer

Four platform limits shape the design:

Inbound only. Salesforce says the service agent only supports inbound conversations. Disruption notices are outbound, so they go out through your messaging flows, and the agent picks up the replies. A session closes 72 hours after the conversation starts, so long claims live in cases.
Arabic is Beta. Salesforce’s language support list marks Arabic as Beta for service agents and employee agents. Plan Arabic review of answers and a quick route to an Arabic-speaking person.
Decide what the agent may read. For service agents, Salesforce disables data masking through the Einstein Trust Layer to improve performance and accuracy, so limit the passenger fields the agent can see before go-live.
One WhatsApp Business Account per org. Salesforce does not support one WhatsApp Business Account across two orgs, and a sandbox counts as a separate org. Airlines with several brands or countries should settle the structure early.

Arabic, English and consent

Bilingual service is a data question as much as a staffing one. Hold the passenger’s name as ticketed in Latin script and, where given, in Arabic, with a preferred language every channel respects. Write policy articles in pairs with one owner, so a baggage rule never changes in English and stays old in Arabic. Capture consent in the language the passenger saw. In the UAE, Federal Decree-Law No. 45 of 2021 requires consent you can prove and withdraw easily, and lets people stop processing for direct marketing. Check the equivalent rules in each country you sell in.

Our work with airlines

With Air Cairo, we are building passenger CRM on Service Cloud and Sales Cloud: one passenger record, service as cases, in Arabic and English, under a public agreement. Etihad runs corporate sales and loyalty on Salesforce, with a proposal-to-payment contract lifecycle, tiered approvals, budget control and corporate loyalty. Qatar Airways has a supplier portal on Experience Cloud for invoices, payments and documents, with Service Cloud cases, Einstein Bots and in-app messaging. Air Arabia runs its corporate and charter pipeline on Sales Cloud, with one-click branded quotes to travel agents and business cards scanned straight into Salesforce.

Where to start

Rank your contact reasons by volume in both languages, and mark which become cases and which an agent could answer.
List every passenger identifier and agree the matching rules before any data load.
Agree with the PSS, loyalty and finance owners what Salesforce reads on demand, what arrives as events and what it may store, for how long.
Write the baggage, refund and disruption policy articles in Arabic and English, one owner per pair.
Run a disruption drill on one cancelled flight, from the operations event to the last case closed.

Planning passenger CRM, or an agent for disruption? The Agentforce Readiness Assessment takes ten working days: it picks three use cases, checks the data and permissions they need, and gives you a costed pilot plan. See our travel and transportation work, or talk to our travel and transportation team.

Frequently asked questions

Does Salesforce have an airline cloud?

No. Airlines assemble passenger CRM from standard products such as Service Cloud, Sales Cloud and Experience Cloud, with Data 360 and Agentforce where they need them.

Should airlines copy bookings into Salesforce?

As little as possible. The PSS stays the system of record for reservations, tickets and departure control, and Salesforce reads current bookings on demand and receives disruption as events.

Can an Agentforce agent handle flight disruption?

It can answer status and policy questions and report case progress to a verified passenger on WhatsApp, web chat and other channels. The service agent only supports inbound conversations, so disruption notices go out through your messaging flows, and compensation, waivers and complaints stay with people.

Does Agentforce support Arabic?

Yes, with a Beta label. Salesforce’s language support list marks Arabic as Beta for service agents and employee agents, so plan Arabic review and a quick handover to an Arabic-speaking person.

How do airlines keep one record per passenger in Salesforce?

With an agreed set of identifiers and matching rules, applied in Salesforce and in every integration that loads data. Salesforce shows no duplicate alert when records arrive through data import tools or the APIs.