Travel Agency
Bring the journey and the back office together.
Business systems
The problem
The person paying for a trip may not be the person travelling or the person receiving updates. A group booking can involve children, guardians, several documents, supplier costs and different currencies. Treating all of those roles as one customer record creates difficult exceptions.
The solution
The developing platform separates travellers, billing accounts and communicating contacts, then connects them through booking workspaces. Document drafts are reviewed and confirmed, guardian permissions are explicit, and document renewals preserve the earlier record.
Booking charges, supplier costs and currency-specific records support the financial view, while queued updates and renewal reminders include duplicate protection. Provider delivery and the adaptation of inherited workflows remain in development.
The decisions behind it
- Traveller, payer and contact
- A booking can involve different people in each role. Separating them avoids making a family or group fit a single-person model.
- Extraction requires confirmation
- Document information prepared by the office or assisted extraction needs an explicit review step before it becomes confirmed traveller information.
- Currency remains part of the record
- A booking's financial picture must preserve the organisation and currency of its charges and costs.
- Booking and traveller workspaces
- Document review and renewal reminders
- Agency-specific financial records