Name correction on a ticket or booking
How do we correct a name on a ticket or a booking with the correction checked against the supplier's rules and the traveler's ID, approved where needed, and the ticket reissued?
Classify the mismatch before anyone touches the ticket. When a name on a booking does not match the traveler's identity document, Callvu chases the document through a link and reads it, classifies the mismatch (a typo within the carrier's free correction tolerance, a transposition, a missing middle name, a legal name change with evidence, a different person which is a name change the fare forbids), checks the carrier's and the suppliers' name correction rules and fees for the ticket and the hotel and car bookings, executes a correction inside the rules by rule with the reissue, routes a correction that needs a waiver, a fee above the agent's limit or a change of passenger to the agent or the carrier's desk in the Decision Desk, and writes the corrected name, the reissued ticket and the fee to the booking system with the secure flight data updated.
In scopeSimpleCallvu moves: chase and verify, decide, write back
Last updated November 7, 2026.
The problem today
A missing hyphen became a denied boarding because the correction request sat in a queue until the day of travel.
Names on tickets must match the identity document, and the mismatches are constant: a typo at booking, a transposed first and last name, a maiden name on the passport, a nickname from a profile. Each carrier has its own tolerance for free corrections, its own fees, and its own forbidden changes (a different passenger is a new ticket). The request arrives by email, the agent looks up the carrier's rule from memory, and the traveler finds out at the gate.
The correction is a classification: what the document says, how the booking differs, and which rule the difference falls under for each supplier on the itinerary. Inside the tolerance it is a reissue by rule; a legal name change needs the evidence; a fee above a limit or a waiver needs a person; a change of passenger is not a correction. The secure flight data must be updated with the ticket, or the mismatch returns at check-in.
A name checked against the document at the first chance costs nothing; at the gate it costs the trip.
How it runs
From the requestto the system of record.
A traveler or an agent reports a name mismatch, or the secure flight data check flags one. Callvu opens the correction on the booking.
- Traveler
- Uploads the identity document and confirms the correct name on a secure screen.
- Carrier and suppliers
- Apply their name correction rules and reissue or confirm.
- Agent
- Decides waivers, fees above the limit and passenger changes in the Decision Desk.
- Callvu
- Chases the document, classifies the mismatch, applies the rules, executes by rule, routes and writes back.
Chase and verify the document
The traveler is asked through a link to upload the identity document they will travel on (the passport for international travel, the government ID for domestic) and to confirm the name as it appears; the document is read and the name, the date of birth and the gender are compared with the booking, the ticket and the secure flight data.
Classify the mismatch
The difference is classified: a minor correction within the carrier's tolerance (a few characters, a transposition, a missing or extra middle name, a hyphen or an accent), a legal name change with evidence (a marriage certificate, a court order), a format issue (a name too long for the carrier's field), or a change of passenger which the fare rules treat as a new ticket; the carrier's name correction policy and fee, and the hotel's, the car's and the tour's name change rules, are applied to each component.
Decide
A correction inside the tolerance and the fees the agent may apply is executed by rule; a correction that needs a carrier waiver, a fee above the agent's limit, a legal name change whose evidence is unclear, a correction after check-in or a request that is in fact a change of passenger goes to the agent in the Decision Desk with the classification and only the allowed outcomes (correct with the fee, request the carrier's waiver, require the evidence, or decline as a passenger change with the rebooking option).
Reissue and write back
The ticket is reissued with the corrected name and the fee charged where it applies, the hotel, car and tour bookings are corrected with their confirmations, the secure flight and advance passenger data are updated through their process, and the corrected name, the reissue, the fee and the document reference are written to the booking system with the traveler receiving the corrected documents.
Where it ends: The name was corrected against the document under each supplier's rules, reissued by rule where it fit and decided by a person where it did not, with the secure flight data updated and the booking system holding the correction. The Decision Trace shows the classification, the rules applied and any decision; the Audit Trace shows the document, the reissue and the writes 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.
The handoff
Between the front doorand the back office.
The front door
The traveler's or the agent's report, or the secure flight data check; the traveler uploads the document on a secure screen.
The back office
The agent decides only waivers, fees above the limit and passenger changes; corrections inside the tolerance reissue by rule.
The Decision Desk
- A waiver, a fee above the limit, unclear name change evidence, a correction after check-in or a passenger change goes to the agent in the Decision Desk with the classification and only correct with the fee, request the waiver, require the evidence, or decline with the rebooking option.
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.
What counts as a correction rather than a change?
A correction keeps the same passenger: a typo, a transposition, a missing middle name, a legal name change with evidence. A different passenger is a new ticket under the fare rules.
Is there a fee?
Inside the carrier's tolerance usually not; larger corrections carry the carrier's fee, applied by rule, and a fee above the agent's limit or a waiver request goes to the agent.
Why is the document required?
Because the name must match the document the traveler will board with, and the secure flight data must match it too; the process reads the document and compares, then updates both.
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.