Why do generic helpdesks struggle with airline customer service?
A generic helpdesk files work by requester and ticket. Airline work hangs on a booking, a flight and a travel date.
- One flight, a planeload of conversations. A cancellation brings in everyone booked on that flight at once. Without flight number and travel date as fields, nobody can see those threads together.
- Several parties per trip. Passengers, the travel agency that sold the ticket, codeshare partners and claims firms all write about the same journey, and DOT's refund rules split duties between the seller and the operating carrier (14 CFR 260.6).
- Regulators set the clocks. DOT gives carriers 30 days to acknowledge a written complaint and 60 to answer it (14 CFR 259.7), and 30 days for a dispositive reply to a written disability complaint (14 CFR 382.155). EU passengers can turn to a national authority after 2 months without a reply (Your Europe), and UK passengers can escalate after eight weeks (CAA). A first-response SLA tracks none of this.
- Travel date sets urgency. Someone flying in three hours comes before a refund question about last month, whatever order they arrived in.
- Claims run for weeks. DOT sets a $4,700 per-passenger floor for domestic bag liability (14 CFR 254.4), so receipts, photos and tracing history must stay on one record.
How should an airline set up its helpdesk inbox?
Queue by how soon the passenger flies and which team owns the outcome, then give every queue its own clock. These targets are starting points; check them against each market's rules.
| Queue | What lands there | SLA target | Owner |
|---|---|---|---|
| Same-day travel | Flying within 24 hours, misconnects, cancellations | 15 minutes, 24/7 | Disruption desk |
| Accessibility | Assistance requests; any disability complaint | 1 hour if travel is within 48 hours; written replies well inside 30 days | Accessibility team with CRO-trained staff |
| Refunds | Cancelled or changed flights, unused extras | 1 business day, so card refunds land inside DOT's 7 business days | Refunds team |
| Baggage | Delayed, damaged and lost bags, interim expenses | 4 hours for delayed bags; 2 business days for damage | Central baggage |
| Compensation | EU261 and UK261 claims, denied boarding, third-party claims | Acknowledge in 1 business day; decide well inside 8 weeks | Customer relations |
| Complaints and referrals | Written complaints, DOT or national authority referrals | Acknowledge in 2 business days; reply well inside 60 days | Customer relations lead |
| Trade and loyalty | Travel agencies, tour operators, top tiers, missing miles | 2 hours for top tiers; 1 business day otherwise | Trade and loyalty desks |
Routing rules
- Fields. Booking reference, ticket number, flight number, travel date, operating carrier, tier and bag file reference, used as filters and columns in Inbox views.
- Travel-date priority. A workflow moves anything with travel in the next 24 hours to same-day travel and starts the 15-minute clock.
- Flight views. During a cancellation, filter by flight number and work the whole flight at once.
- Keywords. Wheelchair, oxygen or service animal go to accessibility; lawyer, DOT or discrimination go to complaints.
- Assignment. Round-robin inside skill groups (Growth and up), plus Slack side conversations with operations control or a station, kept on the thread.
What reply templates do airline service teams need?
Templates matter most where a reply could understate a passenger's rights or promise what operations cannot deliver. Each one says what happened, what the passenger can choose and when they will hear next. Have legal check the wording for each market.
Cancelled flight: new flight and refund option
Hi {first_name}, I'm sorry flight {flight_number} on {travel_date} was cancelled. I've held a seat for you on {new_flight}, leaving {new_departure} and arriving {new_arrival}, at no extra cost. If those times don't work, reply with what suits you. You can also choose a full refund of {refund_amount}, including taxes and the extras you paid for, to your original form of payment. Tonight's hotel and meals: {care_details}.
Bag still missing after 48 hours
Hi {first_name}, your bag (file {file_reference}) still hasn't reached you, and I'm sorry. Our tracing team last located it at {last_scan_location} on {last_scan_time} and is now {tracing_action}. Keep receipts for essentials you buy while you wait and claim reasonable costs here: {expense_link}. Because the bag missed our delivery standard, the {bag_fee} bag fee is being refunded to your {payment_method} without you having to ask. I'll update you by {update_time}.
Compensation declined: extraordinary circumstances
Hi {first_name}, thank you for your claim for flight {flight_number} on {travel_date}. The flight arrived {delay_hours} late because of {cause}, which was outside our control, so compensation under {regulation} is not payable in this case. {supporting_detail}. Your right to meals, refreshments and accommodation during the delay still applies: send receipts for anything you paid for yourself and we will reimburse reasonable costs. If you disagree, you can refer this decision to {enforcement_body_or_adr}.
Written disability complaint: response
Hi {first_name}, thank you for writing about the assistance you received at {airport} on {travel_date}. We reviewed {records_reviewed}. {admit_or_deny_statement}. {facts_summary}. {steps_we_are_taking}. If you are not satisfied with this response, you have the right to pursue enforcement action with the U.S. Department of Transportation: {dot_link}.
Schedule change: your choices
Hi {first_name}, your {travel_date} flight now {change_detail}, so you have three choices: keep the new time, move to another flight at no extra cost, or take a full refund of {refund_amount} to your original payment. The travel credit in our earlier email is optional; if you choose it, it is valid until {expiry_date} on these terms: {credit_terms}.
The disability reply follows DOT's requirement to admit or deny a violation, summarize the facts and mention DOT enforcement (14 CFR 382.155). Never send it with the admit-or-deny line left vague.
How should an airline customer service team be structured and staffed?
Organize by urgency and ownership: a desk for people traveling today, specialists for bags, refunds and claims, and trained staff for accessibility.
- Disruption desk, staffed 24/7, with a direct line to operations control.
- Reservations and service for changes, seats, extras and loyalty.
- Central baggage, owning each file from report to settlement.
- Customer relations for complaints, compensation and refund disputes.
- Accessibility desk, working with the Complaints Resolution Officials US carriers must make available at every airport they serve while operating there, in person or by phone (14 CFR 382.151).
- Social care and a trade desk, plus outsourced partners for overflow.
Hours and peaks
- The travel calendar. TSA checkpoint counts so far in 2026 run from about 1.3 million travelers on the quietest day to nearly 3 million on the busiest, June 18. Staff written channels to that curve, not to office hours.
- Seasons. Summer and holiday weekends bring the most travelers; winter storms and summer thunderstorms bring the most disruption.
- Schedule changes. A new schedule retimes flights and sets off change and refund requests.
- Outages. IT and air traffic control failures come without warning.
Write the irregular operations playbook before the season: a disruption tag, a view per affected flight, approved templates, a help center banner, customer relations staff cross-trained for same-day work, and station managers on free Lite seats. Agree in advance which queues pause. Refunds can wait a day; a passenger stranded at a hub cannot.
Where does AI help an airline service team?
AI handles the repeat volume and the long threads; compensation, accessibility and judgment calls stay with people.
- Drafts with sources. Copilot drafts replies citing the conditions of carriage or fare rule behind them. Aftersales measures a 2.4× faster median reply when teams use Copilot on all of their conversations (Aftersales' own figure).
- Summaries. A bag claim that has run for weeks reads as one paragraph for whoever picks it up next.
- Translation in 31 languages, right-to-left scripts included, with no queue per language. See our multilingual support software guide.
- Monitors review every conversation, so a reply offering credit without the refund option can be flagged without waiting for a monthly sample. When Monitors replaced sampling at Helio Energy, its quality scores went up 14 points.
- Agent can close flight status, bag updates and rebooking inside your rules before a person sees them, and passes anything needing medical, legal or financial advice to your team; see AI customer service for airlines.
Which customer service metrics matter for airlines?
Track the regulatory clocks, the contact rates that show where operations create work, and cost per conversation, with CSAT split between AI and human replies.
| Metric | Formula | Target guidance |
|---|---|---|
| Refund turnaround | Refund due to refund issued, by payment type | Inside 7 business days for card and 20 calendar days for other payments |
| Complaint acknowledgment | Written complaint to written acknowledgment | Well inside 30 days |
| Complaint resolution | Written complaint to substantive reply | Well inside 60 days |
| Disability complaint reply | Written disability complaint to dispositive reply | Inside 30 days, with the admit-or-deny line every time |
| Contacts per disrupted passenger | Conversations about a disrupted flight ÷ passengers booked on it | Falling as alerts and self-service rebooking improve |
| Repeat contacts per booking | Bookings with 3+ conversations in 7 days ÷ bookings with any | Fix the flows behind the highest rates |
| Compensation decision time | Claim received to decision | Inside the EU and UK escalation windows |
| Cost per conversation | (Seats + AI resolutions + channels) ÷ conversations | Compare normal and disruption weeks |
Insights covers resolution rate, CSAT and cost per conversation. The Events API and CSV export come with every plan for joining support data to delay codes, and Scale adds warehouse sync to Snowflake, BigQuery or Redshift.
How do airlines switch helpdesk software?
Most airline teams run several tools at once, so switching means pulling them into one queue.
- Voice on a contact center platform, with email and forms in a ticketing tool such as Salesforce Service Cloud or Zendesk. Keep it and add Agent inside, or move written channels to Aftersales.
- Separate web forms for refunds, bags and compensation, each feeding a different mailbox.
- A social care tool, and outsourced partners on their own systems.
If voice runs on a contact center platform with its own IVR and workforce management, keeping it for calls while written channels move first is a sensible start.
- List every form, mailbox and social account, and map each to a queue above.
- Recreate fields: booking reference, ticket number, flight number, travel date, file reference and tier.
- Rewrite macros as templates and have legal check them per market.
- Set up phone numbers per brand with recording consent; a multi-brand messenger and help center need Scale.
- Move open claims, run both systems side by side for a week, then switch forms and chat.
If you are on Growth or Scale, the Aftersales team runs the migration with you. Most teams finish in an afternoon, though an airline with several forms and brands should still plan the side-by-side week. Growth is $69 per seat a month and Scale $109, billed annually, with details on the pricing page.