Refund complaint under DOT rules

How do we answer a passenger's refund complaint under the DOT rules from the booking record within the required time, with the outcome recorded?

Build the answer from the record and send it on the DOT clock. When a refund complaint arrives (directly, or forwarded by the Department of Transportation), Callvu matches it to the booking and the refund request history, classifies the complaint (a refund not received, a credit given where money was due, a refund to the wrong method, a delay beyond the period, a denied refund the passenger disputes, a complaint outside the rules), assembles the facts from the booking system (the ticket, the events, the refund decision and its basis, the payment and its posting), applies the DOT rules to decide whether the refund was due and timely, routes a case where the record shows an error or a judgment call to the complaints handler in the Decision Desk, generates the substantive response with the facts and the rule, sends it within the required time, and writes the complaint, the response and any corrective refund to the booking system and the complaints register.

In scopeComplex: multi-party handoffsCallvu moves: classify, decide, write back

Talk to an expert Try it in the sandbox

Last updated November 7, 2026.

The problem today

The DOT forwarded the complaint; the response quoted the fare rules; the record showed the carrier had cancelled the flight.

Today, without Callvu

Refund complaints are where the regulator looks, and a response that argues the fare rules when the record shows an automatic refund was due is the worst outcome: the passenger is right, the regulator sees it, and the pattern across complaints is what the enforcement action is built on. Complaints are answered from templates because the facts take too long to assemble by hand.

The DOT requires a substantive response to a consumer complaint within sixty days (and an acknowledgment within thirty), and its refund rules say when a refund was due and how fast; the booking system holds the facts. A complaint answered from the record, with the rule applied and a corrective refund where the record shows one was due, closes the complaint and the pattern.

The complaint is a test of the refund process, and the record should pass it.

How it runs

From the requestto the system of record.

A passenger's refund complaint arrives directly or is forwarded by the DOT. Callvu matches it to the booking and opens the case with the clock.

Passenger: Complains, provides any missing reference, and receives the substantive response and any corrective refund.
Department of Transportation: Forwards complaints and receives the response where it forwarded.
Complaints handler: Decides cases with an error or a judgment call in the Decision Desk.
Callvu: Matches, classifies, assembles the facts, applies the rules, routes, generates and sends the response, and writes back.

Match and classify
The complaint is read and matched to the booking, the ticket and the refund request history (the request, the decision, the amount, the payment and its posting); the complaint is classified: no refund received, a credit given where money was due, a refund to the wrong method, a refund later than the period, a denied refund the passenger disputes, a complaint about a party other than the agency, or a complaint outside the refund rules; the acknowledgment goes out on the clock.
Assemble the facts and apply the rules
The facts are assembled from the booking system: the fare and its rules, the events on the flight (a carrier cancellation or significant change, a schedule change refused, a voluntary cancellation), the refund decision and its basis, the payment method, the amount and the date issued and posted; the DOT rules are applied to decide whether a refund was due, in what form, to which method and by when, and whether the record meets them.
Decide
A complaint the record answers (the refund was issued correctly and timely, or was correctly not due) is answered by rule; a record that shows an error (a refund due and not issued, a credit where money was due, a late refund), a judgment call on the cause, a complaint involving the carrier or another party, or a complaint forwarded by the regulator goes to the complaints handler in the Decision Desk with the facts and the rule and only the allowed outcomes (confirm the record, issue the corrective refund with the explanation, refer to the carrier with the passenger told, or respond with the reasons and the passenger's further rights).
Respond and write back
The substantive response is generated from the facts and the rule in plain terms, with the corrective refund issued where decided, and sent to the passenger (and to the regulator where it forwarded) within the required time; the complaint, the classification, the facts, the decision, the response and any corrective refund are written to the booking system and the complaints register, and the pattern report shows complaints by cause for the refund process.

Where it ends: The complaint was answered from the record with the DOT rules applied, a corrective refund was issued where the record showed one due, the response went within the required time, and the booking system and the register hold the case for the regulator and the pattern report. The Decision Trace shows the classification, the facts and the rule; the Audit Trace shows the complaint, the acknowledgment, the response and any refund with time.

Runtime enforcement

What is enforcedwhile the work runs.

The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.

Regulations

US DOT refund rules (14 CFR 260) and the customer service plan complaint rules (14 CFR 259.7): A carrier (and a ticket agent as merchant) must refund automatically in money to the original form of payment within seven business days for cards and twenty days otherwise where the refund is due for a cancellation, a significant change, a delayed bag or an unprovided service; a carrier must acknowledge a written consumer complaint within thirty days and send a substantive written response within sixty days of receipt; a complaint forwarded by the DOT's aviation consumer protection office is answered to the passenger with a copy to the office; the response and the clock apply these.
The DOT's unfair and deceptive practices authority (49 USC 41712) and the enforcement office's refund guidance: A pattern of failing to provide refunds that are due, or of giving credits where money is required, is an unfair practice the enforcement office pursues with civil penalties; the complaint register and the pattern report are the agency's own early warning.
Supplier and fare rules: Where the refund was correctly not due (a voluntary cancellation of a non-refundable fare), the response cites the fare rule and the credit the fare provides, with the unused taxes refunded where refundable.

Company policies

Every complaint is matched to the booking and the refund history, and answered from the facts, never from a template.
The DOT rules are applied to the record to decide whether the refund was due and timely; an error leads to a corrective refund, not an argument.
The acknowledgment and the substantive response run on the DOT clock.
The booking system and the complaints register are the systems of record, and the pattern report feeds the refund process.

Controls

Complaint matching and classification.
Facts assembly from the booking system.
Rule application to the record.
Decision Desk for errors, judgment calls and forwarded complaints.
Response generation and timed sending.
Register write and pattern reporting.

Clocks and deadlines

Acknowledgment: Within thirty days of receipt.
Substantive response: Within sixty days of receipt.
Corrective refund: On the DOT refund clock from the decision.

Documents and checks

The complaint and its classification
The facts assembled from the record
The decision
The response as sent and any corrective refund
The register entry

In the Decision Trace

The classification and the facts.
The rule applied and its result.
Any decision and the person.

In the Audit Trace

The complaint with receipt time.
The acknowledgment and the response with time against the clock.
Any corrective refund and the writes.

The handoff

Between the front doorand the back office.

The front door

The passenger in any channel, or the DOT's forwarded complaint; the passenger supplies a missing reference on a secure screen.

The back office

The complaints handler decides only errors, judgment calls and forwarded complaints; the response is generated from the record.

The Decision Desk

A record that shows an error, a judgment call on the cause, a complaint involving another party or a forwarded complaint goes to the complaints handler in the Decision Desk with the facts and the rule and only confirm, issue the corrective refund, refer with the passenger told, or respond with the reasons and the rights.

Proof

In scope.Proof at scale, not one process at a time.

The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.

More than 1,000 processes are live across Callvu customers.

Across Callvu customers

Questions

What buyers ask next,answered plainly.

How fast must the complaint be answered?

An acknowledgment within thirty days and a substantive response within sixty days of receipt under the DOT rules, with the clock on the case from arrival.

What if the record shows the refund was due?

A corrective refund is issued on the DOT refund clock with an explanation, rather than an argument; the complaints handler decides it with the facts in view.

Why keep a register?

Because a pattern of refund failures is what the DOT enforces against; the register and the pattern report let the agency see and fix the cause first.

Related processes

Refund request Schedule change acceptance EU261 delay and cancellation compensation claim Goodwill credit and voucher issue Try it in the sandbox All travel and ecommerce processes

Bring this process, or the one that costs you most.

We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.