Flight time changed, client missed it: why courts bill the agent

When an airline changes a client's flight time, whose job is it to tell them, yours or the airline's? For agents, Indian consumer commissions answered that through 2025 and 2026, and the answer costs money. A Bengaluru commission ordered a travel agent to pay ₹83,800 after a family's Baku flight moved from 2 pm to 10:30 am: the airline had told the agent, and the agent hadn't told the client (LawTrend, 14 Oct 2026).

That case went ex parte (the agent never showed up to contest it), so it isn't proof of how a defended case ends. It sits next to two 2025-26 orders that were actually argued and still landed on the agency. This post covers that gap: an airline-made schedule change stuck between the airline's notice and the client's phone, not a client's own no-show (that's its own playbook) and not an on-the-day delay.

What the 2025-26 orders actually decided

Three orders, and the outcome tracks the evidence on record, not a fixed rule.

Forum, date	What happened	What was owed
NCDRC, 28 Oct 2025	GoAir preponed a Delhi-Bengaluru flight 15 minutes; the booking portal had quoted the old time and never corrected it; GoAir's own SMS and call to the passenger were unrebutted, so the airline was cleared (Indian Kanoon)	₹50,000 per complainant (awarded below) set aside; replaced with a refund of the fare paid
Chandigarh SCDRC, 24 Feb 2026	Air India cancelled a Delhi-Sharjah flight; it said it had told the agent; the passenger learned only at the airport (Indian Kanoon)	Agent and airline jointly and severally liable: refund of the ₹6,075 fare gap with 9% a year from 20 Dec 2022, plus ₹1,00,000 compensation and ₹35,000 costs
Bengaluru commission, reported 14 Oct 2026	Airline moved a Baku flight from 2 pm to 10:30 am and told the agent; the agent didn't forward it; the case went ex parte	₹83,800: ₹61,800 rebooking, ₹12,000 lodging, ₹10,000 costs

The NCDRC never found the portal had received GoAir's notice; GoAir's own SMS to the passenger was unrebutted, so the airline walked free. What the NCDRC held against the portal was simpler: it had quoted 6:00 am and never updated it, "this partial deficiency of not intimating the reschedulement" (Indian Kanoon). On that reasoning, the duty ran from having told the client a time, not from who the airline notified.

Chandigarh reached the agent by a different route: the duty to inform "cannot be compartmentalized...so as to absolve one at the cost of the other," since airline and agent are "part of the same chain of service" (Indian Kanoon). It held the agent liable without finding whose number the notice reached. A missed forward also fits the Consumer Protection Act, 2019's definition of deficiency, which includes "any act of negligence or omission or commission" that causes the consumer loss (Section 2(11), Indian Kanoon).

A separate Chandigarh order with no agent in the chain called timely communication of schedule changes "a fundamental obligation of an airline" and raised compensation from ₹7,000 to ₹50,000 (Indian Kanoon). With no agent involved, the airline carried that duty alone; with an agent in the chain, Chandigarh shared it.

Why the notice reaches your phone, and what changed in February 2026

Agents' own mobile and email often end up on the booking, whether out of habit or because a portal fills in the agency login. DGCA has recorded that "in many cases" bookings carried the contact details of travel agents or intermediaries instead of the passenger's, and as of October 2026 directs that passengers "shall provide their own valid mobile number and email ID...including bookings made through travel agents or other intermediaries," that substituting an intermediary's contact "shall be avoided," and that "all airlines, travel agents, online travel portals, and other booking entities shall ensure strict compliance" (DGCA, Air Transport Circular 01 of 2026, 9 Feb 2026). It states no penalty for a lapse; it tells airlines to sensitise agents and run periodic checks, and advises them to write the direction into their agency agreements.

There's a sharper reason to get this right: on cancellations, DGCA's passenger-facilities CAR bars financial compensation to a passenger who didn't give "adequate contact information" at booking, and says airlines "shall require travel agents to provide that information to the airline for operational purposes only" (para 3.3.3, DGCA CAR Section 3, Series M, Part IV, Rev. 4, as of October 2026). Whether an agency number counts as "adequate" is untested in any order found here, but an airline can raise it, and a client who loses that fight turns to you next.

One rule that doesn't apply: the CAR's two-week notice is for cancellations, not retimings, and Part IV has no separate timeline for a flight merely preponed, a gap the retiming orders above fill with ordinary consumer-protection reasoning instead. Your exposure for a missed forward runs through consumer law, not the CAR: DGCA's own March 2026 circular on the refund look-in and name corrections limits those benefits to airline website and app bookings "as DGCA primarily regulates airlines and not the travel agents" (DGCA, ATC 03 of 2026).

The set-up to use from today

Put the client's own mobile number and email in the passenger contact fields on every booking. Add your agency's number only where the system has a separate field for it, never in place of the client's. The forward-and-confirm duty stays yours either way: the NCDRC case turned on a quoted time nobody revisited, so updating it when it moves is on you regardless of whose number sits in the contact field.

Tell the client why their number is going to the airline, and keep that reply. The Digital Personal Data Protection Rules, 2025, notified 14 November 2025 with an eighteen-month phased compliance runway, require a separate, clear consent notice explaining the specific purpose for which personal data is collected and used (PIB); send this at booking either way.

Hi [client name], registering your own mobile [number] and email [email]
with the airline for flight updates, as DGCA now directs. Our desk also
stays on this booking and will forward any change to you directly.
Reply YES if these details are correct.

The daily schedule-change sweep

Run this every morning, and again after any airline disruption advisory.

Step	Where	Done when
Check notifications/schedule-change page	Every portal you ticket through	Every active PNR reviewed
Check inbox(es) and number on bookings	Filter for airline senders	Every unread airline mail actioned
Check manage-booking by PNR and surname	Flights departing next 7 days	Live time matches what client was told
Flag tickets bought through another agent	Their contact may sit on that booking	Confirmed directly with them

Name an owner and a backup. Any change with no client reply by end of day gets a call, not another message.

The message to send the moment a change lands

Send this within the hour of finding a change.

FLIGHT TIME CHANGED, please reply
[Passenger name], [Airline] [Flight no.], [Date]
OLD: [time], Terminal [X]
NEW: [time], Terminal [Y]
New airport reporting time: [time]
This affects: [pickup / hotel / connection]
Reply by [time] with the new time to confirm you've seen this.
If we don't hear back by [time], we will call you.

If the change moves the flight to a different airport or terminal in the same city, the airline bears the transfer cost only with less than 6 hours' notice; past that, getting there is on the passenger (DGCA CAR, Rev. 4, para 3.10.1).

Reconfirm at T-72 and T-24, with a read-back

Recheck the live time against the airline or portal first, not your own earlier voucher: a quoted time nobody revisited is exactly what the NCDRC held against the portal above.

T-72h: [Flight] on [date], departure [time], Terminal [X], reporting
time [time]. No change since booking. Reply to confirm.

T-24h: Please reply with the departure time you have for [flight] on
[date], so we know you've seen the current time. Call us immediately
if anything looks different from this.

A reply that reads back the actual time is stronger evidence than a plain "ok".

The forwarding log that wins the case

Ex parte orders like the Bengaluru one run entirely on what the complainant puts before the commission; an agency with nothing in writing starts the hearing already behind. Keep one log entry per change, with the exported WhatsApp or email thread attached, and keep it in a form you can prove as evidence later.

PNR: [ ]  Passenger(s): [ ]  Flight/date: [ ]
Change received: [date, time, source: portal alert / airline mail /
found on sweep] to [which contact]
Old time/terminal -> New time/terminal: [ ]
Forwarded: [date, time, channel, by whom]
Client acknowledgement: [date, time, exact reply]
Follow-up call if no reply: [date, time, outcome]
Client decision: accept / change / refund

Complaints can be filed up to two years from when the cause of action arose (Consumer Protection Act, 2019, s.69); Chandigarh took nearly four years from flight to appellate order, so keep this log well past the trip. If a notice arrives, reply factually and inside the time given; see the reply playbook for the mechanics.

Found a missed change: the first hour

1. Confirm the new time and what the client can still make.
2. Pull the airline's own notice: when it was sent, to which contact, and save it.
3. Ask the airline or portal what it offers; check rather than assume.
4. Rebook first if the client needs to travel, and put the cost split in writing before, not after.
5. Re-time the hotel, transfer and any handler to match.
6. Decide early whether to settle. Chandigarh shows what losing a contested one can cost: ₹1,35,000 in compensation and costs on a ₹6,075 fare gap, before interest, owed jointly with the airline.

Keep the first client message factual, and don't argue fault either way.

Common questions

Agent ne flight ka time change nahi bataya, paisa kaun dega?

In the orders above, the agency paid. Where the airline said it had told the agent and the client never heard, commissions ordered the agent to pay: rebooking, lodging and costs in the uncontested Bengaluru case, and a fare refund, compensation and costs jointly with the airline in Chandigarh (Indian Kanoon; LawTrend).

PNR mein kiska mobile number dalna chahiye, agent ka ya passenger ka?

The passenger's own, per DGCA's February 2026 circular, which directs bookings to carry the passenger's own mobile and email "including bookings made through travel agents or other intermediaries" (DGCA, ATC 01/2026). Add the agency's own number only in a separate field, if one exists.

How long should I keep the record of a change?

Well past the trip. Complaints can be filed up to two years from when the cause of action arose, extendable for sufficient cause (Consumer Protection Act, 2019, s.69); Chandigarh ran almost four years from flight to appellate order.

The short version

• Once a schedule change reaches a number or inbox you control, or you've quoted a client a time, 2025-26 orders treat passing it on as your job, not just the airline's.
• Chandigarh (24 Feb 2026) held agent and airline jointly liable for ₹1,35,000 in compensation and costs, plus a ₹6,075 fare refund with interest; Bengaluru reportedly ordered ₹83,800 after an uncontested hearing.
• Put the client's own mobile and email in the passenger contact fields; add your agency's number only in a separate field, per DGCA's February 2026 circular.
• Run the daily sweep anyway: the right contact on the PNR doesn't remove your duty to confirm the client got the message.
• Reconfirm the live time at T-72 and T-24, and ask for a read-back, not an "ok".
• Log every change received, forwarded and acknowledged, and keep exports past the two-year complaint window.
• If a change slips through, confirm the time, pull the airline's notice, rebook first, and decide early whether to fight or settle.