Know the traveller before you ask for the same details again.
Keep customer history, booking records, passenger details, notes, and e-Invoice information connected, so sales and operations can serve people with context.
Customer
Nur Aisyah
Booker, payer, and invoice recipient
Relationship context
The buyer record stays connected without replacing the passenger list.
Travelling party
One booking, four individual passenger records
Nur Aisyah
Adult · Lead traveller
Amir Hakim
Adult · Twin room
Puan Mariam
Adult · Mobility assistance
Adam Hakim
Child · Passport detail missing
Operations sees who is travelling and exactly which record still needs attention.
One customer history
See related quotations, bookings, invoices, notes, and activity.
Passenger-level detail
Track each traveller, not only the person who paid.
Self-entry option
Let customers submit passenger information through a secure link.
Where the process breaks
The buyer is not always the traveller
One customer may pay for a family, company team, or Umrah group. A simple contact list cannot tell operations who is travelling or what information is still missing.
- 1
Repeated questions
Returning customers are asked for details your agency has already collected.
- 2
Missing passengers
A booking looks confirmed while some traveller records are still incomplete.
- 3
No shared history
Sales, operations, and finance each know a different part of the relationship.
Build a useful record around the whole journey
WauHub separates the customer relationship from the passenger list, then connects both to the commercial documents and trip.
Keep customer context
Store contact, address, tax details, notes, and the history of quotations, bookings, and invoices under one customer.
Manage every passenger
Track adult, child, and infant travellers with identity, nationality, passport, room, and special requirement fields where needed.
Collect details securely
Generate a time-limited passenger entry link so the booking contact can complete traveller details without accessing your back office.
Check booking completeness
See passenger counts and completion status before operations prepares manifests and departure documents.
Better service with fewer last-minute surprises
Your team can recognise the customer relationship while still managing the practical details of every person travelling.
Respond with history
Sales can see what the customer enquired about, booked, and paid for before making the next recommendation.
Prepare departures earlier
Operations can spot missing passenger information before check-in day.
Reduce sensitive data in chat
A structured entry flow gives customers an alternative to sending every passport detail through WhatsApp.
Malaysia, in practice
Ready for families, groups, MICE, and Umrah
Malaysian agencies regularly manage one payer with many travellers. The customer and passenger model supports that real relationship.
- Malaysian and international passenger records with nationality and passport fields
- Room, transport, meal, accessibility, and special request context for operations
- Customer TIN and identification support for eligible e-Invoice workflows
From booker to pax list
Travel CRM means knowing who bought and who is travelling.
That distinction matters whether the file is a two-person FIT, a family booking, a corporate movement, or a full GIT departure.
Booker
Not always pax 1
The enquiry owner, payer, invoice recipient, emergency contact, and lead traveller may not be the same person.
Pax
More than a CRM contact
Passport validity, room, meal, mobility, and manifest details belong to the travelling person, not only the customer account.
Ops file
Context changes the record
FIT, GIT, MICE, Umrah, inbound, and outbound files do not ask operations for the same passenger view.
MOTAC regulates licensed travel activities in Malaysia. A well-kept customer and passenger record supports daily operations, but it does not replace the agency's regulatory obligations.
Questions agency owners ask
Is a customer the same as a passenger?
Not always. The customer can be the buyer or booking contact, while the passenger list contains everyone travelling.
Can customers enter passenger details themselves?
Yes. WauHub can generate a public passenger entry link for a booking, subject to the link controls in the app.
Can I see a repeat customer's booking history?
Yes. Related bookings, quotations, invoices, notes, and activity can be viewed from the customer record.
Connect the customer record to sales, travel, and tax work
A useful travel CRM should support the journey around the customer, from the first enquiry to passenger readiness and the documents issued after confirmation.
Bookings and passengers →
Prepare pax, passports, rooms, transport, documents, and departure status.
Travel lead management →
Give each customer enquiry an owner, stage, notes, and next action.
Lead-to-payment workflow →
Move customer context forward from enquiry to quotation, booking, and invoice.
LHDN MyInvois e-Invoice →
Use the appropriate customer identification and tax details for e-Invoice work.
Give your team the full customer story
We will show how one family or group booking moves from customer record to a departure-ready passenger list.