Reservations & Bookings: Systems, Processes & Challenges

TAKEAWAYS:

• Reservations are time-bound commitments (flights, hotels, tours) requiring real-time inventory checks, while bookings are confirmed payments tied to contracts.
• Global Distribution Systems (GDS) like Amadeus and Sabre act as central hubs for airlines, hotels, and car rentals, enabling interoperability.
• Overbooking is a strategic risk: airlines overbook by 5–10% to offset no-shows, but must manage bumps (denied boardings) ethically.
• Cancellation policies vary by service—flights (non-refundable vs. flexible), hotels (prepaid vs. on-arrival), and tours (group vs. private).
• Technology tools (e.g., Cloudbeds, Travelport) automate confirmations, e-tickets, and dynamic pricing, reducing human error.
• Customer service in bookings hinges on transparency, quick resolution of conflicts (e.g., double bookings), and compliance with laws (e.g., Nepal’s Consumer Protection Act).

1. Definitions and Key Concepts

Reservations and bookings are the backbone of travel operations, ensuring services are allocated efficiently while managing risks. Here’s how they differ:

2. How Reservations and Bookings Work

A. The Reservation Process

Reservations start with a request and end with either a confirmation or rejection. The flow is:

flowchart TD
    A["Customer Request"] --> B["Inventory Check"]
    B -->|"Available"| C["Provisional Reservation"]
    B -->|"Unavailable"| D["Rejection/Waitlist"]
    C --> E["Customer Confirmation"]
    E -->|"Payment"| F["Booking Confirmed"]
    E -->|"No Payment"| G["Reservation Expires"]
    F --> H["E-ticket/Voucher Issued"]

Key Steps:

1. Customer Inquiry: Via phone, email, or online portal (e.g., Daraz Travel, NTC’s bus booking).
2. Inventory Check: The agent verifies availability in real-time using GDS (e.g., Amadeus for flights, Cloudbeds for hotels).
3. Provisional Hold: A temporary reservation is placed (e.g., "Hold for 24 hours").
4. Customer Decision: The customer confirms and pays (booking) or cancels.
5. Confirmation: An e-ticket (IATA standard) or voucher is issued.

B. Booking Confirmation and Documentation

Once a reservation is confirmed and paid, it becomes a booking. Key documents include:

• E-ticket (for flights): IATA-standard electronic ticket with a PNR (Passenger Name Record).
• Hotel Voucher: Digital or printed confirmation with check-in/check-out dates.
• Tour Voucher: Includes itinerary, payment receipt, and contact details (e.g., from Himalayan Java Tours).
• Car Rental Agreement: Contract with terms (e.g., insurance, fuel policy).

Worked Example: Booking a Flight via Ncell

1. A traveler calls Ncell’s travel desk and requests a Kathmandu–Dhaka flight.
2. The agent checks availability on Amadeus and finds a seat on Biman Bangladesh Airlines.
3. The traveler pays NPR 12,000 via Khalti.
4. The agent issues an e-ticket with:
   • PNR: ABC123
   • Flight: RG 256
   • Seat: 12A
   • Check-in deadline: 2 hours before departure.

3. Global Distribution Systems (GDS) and Technology

GDS are the backbone of reservations, connecting airlines, hotels, car rentals, and travel agencies. The Big 3 are:

• Amadeus (used by Yeti Airlines, Nepal Airlines)
• Sabre (used by Nabil Bank’s travel services)
• Travelport (used by Daraz Travel)

How GDS Works:

flowchart TD
    A["Travel Agent/Customer"] --> B["Query via GDS Portal"]
    B --> C["GDS Server"]
    C --> D["Airlines/Hotels Database"]
    D --> C
    C --> E["Real-time Availability & Pricing"]
    E --> A
    A --> F["Booking Confirmation"]

Advantages of GDS:

• Real-time updates: Instant availability and pricing.
• Multi-carrier access: Book flights, hotels, and cars in one system.
• Automated confirmations: E-tickets and vouchers generated instantly.
• Commission tracking: Agencies earn commissions (e.g., 10% on flights).

Disadvantages:

• High costs: GDS subscriptions are expensive (e.g., Amadeus charges agencies per transaction).
• Complexity: Requires trained staff to navigate the system.
• Dependence on technology: Downtime can halt bookings (e.g., during Nepal’s load-shedding).

4. Overbooking and Conflict Resolution

A. Why Overbooking Happens

Airlines and hotels intentionally overbook to offset:

• No-shows (e.g., 10% of hotel bookings are canceled last-minute).
• Overestimation of demand (e.g., Daraz Travel overbooks a Pokhara tour by 2 spots).
• Operational constraints (e.g., a hotel has 50 rooms but sells 52 to ensure occupancy).

Overbooking Rates by Industry:

B. Managing Overbookings: The Bump Process

When overbooked, airlines and hotels use denied boarding (bumping) with compensation:

flowchart TD
    A["Overbooking Detected"] --> B["Identify No-shows"]
    B --> C["Check-in Begins"]
    C --> D["Voluntary Bumps"]
    D -->|"Passengers Agree"| E["Compensation Offered"]
    E --> F["Boarding"]
    C --> G["Involuntary Bumps"]
    G --> H["Last to Check-in Selected"]
    H --> I["Compensation per EU Rules"]
    I --> J["Boarding or Rebooking"]

Compensation Rules (Global Standards):

Worked Example: Yeti Airlines Overbooking

• Scenario: Yeti Airlines sells 120 seats for a Kathmandu–Pokhara flight but only has 110.
• Day of Flight:
  • 5 no-shows → 115 passengers check in.
  • 5 more passengers arrive late.
• Solution:
  • Yeti offers voluntary bumps to 3 passengers: NPR 3,000 cash voucher for rebooking.
  • 2 passengers refuse → involuntary bumps (last to check-in).
  • Compensation: NPR 5,000 each + rebooking on next flight.

5. Cancellation Policies and Refunds

Cancellation terms vary by service provider. Here’s a comparison:

Worked Example: Daraz Travel Hotel Cancellation

• A traveler books a 3-night stay at Hotel Himalaya via Daraz Travel for NPR 15,000.
• Policy: 50% refund if canceled 48 hours before check-in.
• Scenario: The traveler cancels 36 hours before check-in.
• Refund: NPR 7,500 credited back to Khalti.

6. Technology Tools for Reservations

Modern travel agencies use software to streamline bookings:

How Daraz Travel Uses Technology:

1. Customer books a Pokhara tour via Daraz app.
2. Cloudbeds checks hotel availability.
3. Amadeus confirms flight seats.
4. Automated email/SMS sends voucher and itinerary.
5. Payment gateway (Khalti/eSewa) processes payment.

7. Customer Service in Reservations and Bookings

Poor handling of reservations leads to complaints, refund requests, and legal issues. Key service principles:

• Transparency: Clearly communicate cancellation policies.
• Quick Resolution: Handle double bookings or overbookings within 24 hours.
• Compliance: Follow Nepal’s Consumer Protection Act (2075) and IATA rules.
• Upselling: Offer upgrades (e.g., business class, better hotel) to compensate for delays.

Common Booking Conflicts and Solutions:

Worked Example: NTC Bus Booking Conflict

• Scenario: A traveler books a Kathmandu–Pokhara bus via NTC’s website but receives a confirmation email 2 hours before departure.
• Problem: The bus is already full due to overbooking.
• Solution:
  • NTC offers NPR 500 compensation + rebooking on the next bus.
  • The traveler accepts and is rebbooked on the 10 AM bus.

In the Real World

1. eSewa and Khalti for Instant Bookings

   • How it works: Travelers book flights, hotels, and tours via eSewa/Khalti’s travel partners (e.g., Yeti Airlines, Himalayan Java).
   • Idea used: Real-time payment integration with GDS (Amadeus) to confirm bookings instantly.
   • Example: A tourist books a Pokhara hotel via Khalti, and the confirmation is sent within 30 seconds via SMS.

2. Daraz Travel’s Automated Itineraries

   • How it works: Daraz Travel uses Travelport to bundle flights, hotels, and tours into a single booking.
   • Idea used: Dynamic packaging—customers see real-time availability and prices for entire trips.
   • Example: A traveler books a "Pokhara Adventure Package" (flight + hotel + tour) in one click, with an e-voucher sent instantly.

3. Ncell’s Travel Desk Overbooking Strategy

   • How it works: Ncell’s travel agents overbook Nepal Airlines flights by 8% to ensure full capacity.
   • Idea used: Statistical overbooking to offset no-shows (historically, 5–10% of flight bookings are no-shows).
   • Example: For a Kathmandu–Dhaka flight, Ncell sells 108 seats when only 100 are available. On the day, 6 no-shows mean no bumps occur.

Exam Tip

This unit is heavily tested in TU exams with:

1. Definitions: Expect 2–3 marks on reservation vs. booking, GDS, and overbooking.
2. Process Diagrams: Draw a flowchart of the booking process (like the one above) for 5–7 marks.
3. Worked Examples: Solve cancellation refunds, overbooking compensation, or GDS queries (e.g., "Calculate the refund for a canceled Yeti Airlines ticket").
4. Case Studies: Analyze Nepali companies (e.g., "How does Daraz Travel handle double bookings?").
5. Comparisons: Tables on cancellation policies or GDS features are common.

High-Scoring Tips:

• Use real numbers: If asked about overbooking, mention 5–10% for airlines.
• Link to Nepal: Always tie examples to Yeti Airlines, NTC, or Himalayan Java.
• Draw diagrams: A booking process flowchart or overbooking compensation table can earn 5+ marks.
• Mention laws: Refer to Nepal’s Consumer Protection Act or IATA rules for full credit.