Traveler profile setup and update
How do we set up and update a traveler's profile with the passport, the loyalty numbers and the preferences captured once, checked, and written to the profile system under the data protection rules?
Capture the profile once from the traveler, check it, and hold it under a lawful basis with an expiry. At onboarding or on a change, Callvu prefills the profile from the HR record and the existing bookings (the name as on the passport, the contact details, the cost center, the approvers), asks the traveler on a secure screen for what only they hold (the passport image read for the number, the expiry and the issuing country, the loyalty numbers, the known traveler and redress numbers, the seat, meal and hotel preferences, the emergency contact through its process), checks each (the passport name against the HR name, the expiry against the six-month rule, the loyalty number format), records the consent and the retention period for the passport data, routes a mismatch to the travel desk in the Decision Desk, and writes the profile to the profile system so every booking uses it.
In scopeSimpleCallvu moves: prefill, chase and verify, write back
Last updated November 7, 2026.
The problem today
The name on the ticket did not match the passport, because the profile had been typed by an assistant from memory three years ago.
A traveler profile drives every booking: the name that goes on the ticket, the passport data for advance passenger information, the loyalty numbers that earn the status, the preferences that avoid a call. Profiles are created by assistants from emails, never checked against the passport, and never expire; the passport in the profile expired last year and nobody knew until the airport.
The profile holds personal data, some of it sensitive (passport, date of birth, dietary preferences that reveal religion or health), under data protection rules that require a lawful basis, a purpose, a retention period and the traveler's rights. The passport name must match the ticket; the expiry must satisfy the destinations' six-month rule; the loyalty numbers must be in the member's name. Each is a check on data the traveler can supply once from their phone.
A profile the traveler verified is a ticket that matches the passport.
How it runs
From the requestto the system of record.
A traveler is onboarded to the travel program, or a profile change is needed (a new passport, a name change, a new loyalty membership). Callvu opens the profile update.
- Traveler
- Provides the passport image, the loyalty numbers and the preferences on a secure screen and consents to the retention.
- Travel desk or travel manager
- Decides mismatches in the Decision Desk.
- Callvu
- Prefills, captures, reads the passport, checks, records consent, routes and writes.
Prefill
The name, the contact details, the cost center, the approvers and the grade are prefilled from the HR record and the existing profile; the trips on file show which destinations the profile must support.
Chase and verify
The traveler is asked on a secure screen for what only they hold: the passport image, read for the number, the name, the date of birth, the expiry and the issuing country; the loyalty, known traveler and redress numbers; the preferences; each is checked (the passport name against the HR name with the ticketing name derived, the expiry against the six-month rule for the destinations on file, the loyalty number format against the program's pattern), and a missing or unreadable item is chased.
Record consent and decide
The notice and the consent for holding the passport and the sensitive preferences are presented with the purpose and the retention period, and the traveler's choice is recorded; a mismatch (a passport name that differs from the HR name, an expiry inside the window, a loyalty number in another name) goes to the travel desk in the Decision Desk with the data and only the allowed outcomes (accept with the ticketing name set, request a corrected document, or hold).
Write back
The profile is written to the profile system, the system of record, and synchronized to the booking tool so every booking uses it; the passport expiry and the retention period set reminders, and a change later runs the same process.
Where it ends: The profile was built from the traveler's own documents, checked for the name and the expiry, held under a recorded consent with a retention period, and written to the profile system that every booking reads. The Decision Trace shows the checks and any decision; the Audit Trace shows the capture, the consent and the write.
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 onboarding link or the profile change request; the traveler acts on a secure screen on their phone.
The back office
The travel desk decides only mismatches; the booking tool reads the profile.
The Decision Desk
- A passport name that differs from the HR name, an expiry inside the window, or a loyalty number in another name goes to the travel desk in the Decision Desk with the data and only accept with the ticketing name, request a corrected document, or hold.
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 does the traveler provide?
The passport image, the loyalty and known traveler numbers and the preferences, on a secure screen; the rest is prefilled from HR.
What is checked?
The passport name against the HR name with the ticketing name set, the expiry against the six-month rule for the traveler's destinations, and the loyalty numbers' format and ownership.
How is the passport data protected?
It is held under a recorded consent and purpose with a retention period, secured in the profile system, and deleted or re-consented when the period ends.
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.