AI Copilot for airline ops

The Copilot for airline operations

Cancel flights, refund bookings, create reservations from a passport photo - in plain language. Live across every airline running on Farel, in five languages.

Operates flights and bookings
Creates bookings from passport scans
Confirms before every action
Five languages

Most airline systems were designed to be clicked through

Every refund is a screen. Every cancellation is a workflow. Every new hire is months of training on menus.

Click-heavy workflows

Refunds, cancellations, and changes each take minutes through legacy PSS UIs. At call center scale, that's the whole budget.

Months of training per agent

Dozens of screens, conditional flows, edge cases. Every hire restarts the curve. Every turnover resets it.

English-only interfaces

Most PSS UIs ship in one language. Your call center, airport staff, and ops control don't all work in it.

IRROPS handled one-by-one

A delay or cancellation hits hundreds of bookings. Agents process them one at a time, in sequence, while passengers wait.

One Copilot. Every operation. Every role.

Farel Copilot operates on the same data as the rest of the platform. Type what you want done - refund a booking, cancel a flight series, create a reservation from a passport photo - and the system shows you the impact, then commits.

What Copilot does today

Operational scope, in one place. Same data and permissions as the rest of Farel.

Flight operations

Cancel, reschedule, open or close sale, edit pax quota or departure time - one flight or every flight in a period. Booking-side impact - involuntary operations, rebooking, notifications, remarks - flows automatically through the rest of the platform.

Booking operations

Create, refund pax-segments, edit remarks, process involuntary changes. One booking at a time or many at once.

Booking from a passport photo

Upload a scan; Copilot extracts name, DOB, document number, nationality, expiration. Agent confirms the flight and price; ticket issues in 20-30 seconds instead of 2-3 minutes of typing.

Bulk operations in one command

Refund fifty bookings, cancel a flight series, requote a season. One command does what a batch job or a queue of agents would handle elsewhere.

Plain-language targeting

"Next Tuesday," "this whole series," "all LAX flights this week." No filters, no query syntax. Copilot resolves the target and shows what it'll touch before it acts.

Nothing executes until you confirm

Refunds show the exact amount per passenger and segment; cancellations show every booking affected. The system commits only after the agent confirms and stamps the action with their identity - "Cancelled by [name] via Assistant" on the operation log, exportable for audit.

Holds context across the session

Look up a booking, refund it, then start on the next one - Copilot remembers what you were just working on. At Asman, 168 sessions in a month completed end-to-end without falling back to the interface.

Five languages, more coming

English, Russian, Spanish, Portuguese, French. Agents type in their language; Copilot replies in the same one.

Already running at scale

Live across every airline on Farel. Used daily by call center, airport, and ops teams.

Operations · last month

1,561

Copilot operations completed at Asman Airlines in a single month.

End-to-end sessions

168

Multi-step Copilot sessions completed end-to-end without falling back to the UI.

Coverage

Allairlines

Live in production across 4 continents - call center, airport, and ops teams.

Time per operationThrough the interfaceThrough Copilot

Flight cancellation

One flight, screen-by-screen

Interface~ 1 minute

Copilot10-15 sec

Booking creation

Manual entry vs passport scan

Interface2-3 minutes (manual entry only)

Copilot20-30 sec (from passport scan)

Involuntary refund - many bookings

IRROPS, schedule cancellation

Interfaceone-by-one

Copilotone command

Times measured against typical PSS workflows. Copilot times reflect production usage at Asman Airlines.

FAQ

Before you decide

Answers to the questions we hear most from airline teams

Copilot operates on the same records as inventory, reservations, DCS, and payments. Legacy PSS chatbots query through APIs and middleware, which means they're limited to what those APIs expose and lag the underlying data. Farel Copilot has the same access as the interface - because it's the same platform.

Every destructive action - refund, cancel, IRROPS - shows the full diff before execution. The agent sees exactly what will change and confirms before commit. If the interpretation is wrong, the agent rejects it and rephrases.

Same permission model as the rest of Farel. A call center agent has call center permissions in Copilot. An ops controller has ops permissions. Same access rules as the UI.

Every operation logs user identity, timestamp, source, and before and after state. "Cancelled by [name] via Assistant" appears on the operation history. Exportable for internal review or regulator request.

English, Russian, Spanish, Portuguese, French. Adding more on customer request.

Coverage is published and updated as scope grows. Today's gaps include flight creation, pricing edits at the flight level, and crew assignment - these stay in the schedule and flight interfaces.