Travel Agency
Bring the journey and the back office together.
2026
Development recorded in the project repository. Earlier work may predate this history; this is not a confirmed launch date.Business systems
Inside Travel Agency
The repository's purpose-built preview uses fictional agency data.
The problem
A travel agency coordinates the customer relationship and the trip operation at the same time: enquiries, travellers, payers, guardians, suppliers, documents, reminders, costs, charges and currencies. Spreadsheets and generic customer records collapse people with different responsibilities into one unreliable booking view.
The person paying may not travel or receive updates, a group may include children with guardian controls, and documents and supplier arrangements keep changing after the first reservation.
The solution
The developing platform gives the agency a complete booking workspace that separates travellers, billing accounts and communicating contacts while keeping them connected to the same trip. Supplier costs, client charges, currency records, documents, notes and scheduled communication stay attached to that operation.
Document drafts are reviewed before confirmation, guardian permissions are explicit and renewals preserve prior records. Queued updates and reminders include duplicate protection. Provider delivery and 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