Unused ticket tracking and reuse
How do we track unused tickets as credits against the traveler, flag them before they expire, and apply them to the next booking?
Treat every unused ticket as a credit with an owner, a value and an expiry. When a ticket goes unused (a cancelled or missed flight, a changed trip), Callvu classifies it under the supplier and fare rules (refundable, a credit with a change fee, a credit without, forfeited, the name restriction, the validity period and whether it runs from issue or from the original travel date), records the credit against the traveler and the cost center with its value, the carrier, the ticket number and the expiry, flags it to the traveler and the arranger ahead of expiry and at the next booking search for the same carrier, applies it to the next booking by rule with the residual tracked, and writes the credit and each application to the booking system.
In scopeSimpleCallvu moves: classify, write back
Last updated November 7, 2026.
The problem today
The company let hundreds of ticket credits expire because they lived in the agency's report and not in the booking tool.
Unused tickets are money the company already spent. The agency tracks them in a report; the traveler forgets; the booking tool does not know; the credit expires a year after issue, unnoticed. The sums are large in any organization with frequent changes, and the recovery is entirely a matter of knowing the credit exists at the moment of the next booking.
The fare rules decide what an unused ticket is worth: refundable to the form of payment, a credit for the same passenger less a change fee, a credit without a fee under the carrier's current policy, or forfeited; the validity typically runs one year from the original issue date, sometimes from the travel date; the name on the credit is fixed. Classified at the moment the ticket goes unused and recorded against the traveler, the credit can be offered at the next search.
A credit the booking tool knows about is a credit that gets used.
How it runs
From the requestto the system of record.
A ticketed flight is cancelled, changed or missed without a refund. Callvu opens the credit record.
- Traveler or arranger
- Is told the credit, its expiry and its rules, and uses it at the next booking.
- Travel desk
- Applies credits the booking tool cannot apply automatically and decides exceptions in the Decision Desk.
- Finance
- Sees the credits as an asset by cost center.
- Callvu
- Classifies, records, flags, applies and writes.
Classify the ticket
The ticket is classified under the supplier and fare rules: refundable (which routes to the refund process), a credit with or without a change fee, or forfeited; the value (the fare paid less any fee, with the taxes handled per the rule), the name restriction, the carrier and the validity (one year from issue under most fare rules, or from the travel date under some) are computed from the fare rule and the carrier's current policy.
Record the credit
The credit is recorded against the traveler and the cost center with the ticket number, the carrier, the value, the fee, the expiry and the rules, and shown in the traveler's profile and the finance view.
Flag and apply
The traveler and the arranger are told at recording, reminded ahead of expiry on the policy's schedule, and prompted at the next booking search on the same carrier; the credit is applied to the new booking by rule where the booking tool can exchange it, or routed to the travel desk for a manual exchange; the residual value and the new expiry are tracked.
Write back
The credit, each application, the residual and the expiry are written to the booking system, the system of record, and an expired credit is closed with the loss recorded by cost center; a credit for a traveler who left the company goes to the travel desk in the Decision Desk with the allowed outcomes.
Where it ends: Every unused ticket became a recorded credit with its value and expiry, was offered at the next booking, and the booking system holds the credit, its applications and any loss. The Decision Trace shows the classification under the fare rule; the Audit Trace shows the flags, the applications and the closure.
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.
The handoff
Between the front doorand the back office.
The front door
The booking tool prompt at the next search and the reminders; the traveler sees the credit in their profile.
The back office
The travel desk handles only manual exchanges and exceptions; finance reads the credits by cost center.
The Decision Desk
- A credit the booking tool cannot apply, a credit for a traveler who left, or a disputed value goes to the travel desk in the Decision Desk with the record and only the allowed outcomes.
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 long is an unused ticket credit valid?
Under most fare rules one year from the original issue date, with the new travel completed within it; the classification reads the rule and the carrier's policy in force and records the expiry.
How is the credit used?
The booking tool prompts it at the next search on the same carrier and applies it by rule, with the residual tracked; a manual exchange goes to the travel desk.
What happens if it expires?
Reminders go out before expiry; an expired credit is closed with the loss recorded against the cost center.
Related 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.