Client success story
Travigence: an agency operations upgrade built for control and throughput
A European B2B travel technology team refreshed its core platform workflows so operators work with clearer controls, routine tasks move faster at busy times and managers can see where every active booking stands.
- Europe
- B2B
- Agency operations upgrade
- Launched in 2024
The brief
The Travigence success story in brief
Travigence works in travel technology and runs a B2B operation in Europe, where partner agencies book through the platform and an internal team keeps every booking moving. In 2024 it launched an agency operations upgrade on PHPTRAVELS.
The goal was not a new look. It was a calmer working day: controls that operators can find without thinking, routine tasks that do not stall when the queue gets long, and a status view managers can trust at a glance.
The upgrade was built on the same core that powers our B2B wholesalers and the B2B booking engine, refreshed around the way the Travigence team actually works.
Upgrade goals
- 01Group the controls operators use mostSettings and actions arranged around tasks, not around the order they were added.See the change
- 02Keep routine work moving at peak timesFewer detours between screens when the team handles a busy queue.See the change
- 03Show managers where bookings standOne clear status view of active bookings instead of piecing it together.See the change
Project record
- Industry
- Travel technology
- Region
- Europe
- Model
- B2B
- Scope
- Agency operations upgrade
- Launch
- 2024
- Stack
PHPMySQLREST API
Challenge 01 · Controls
From one long menu to controls grouped by task
When the important controls are spread across a flat menu, every operator builds their own mental map, and new staff take longer to find their way.
Control panel complexity
Important controls were not grouped in an operator-friendly way.
Menu, in the order items were added
- Settings
- Bookings
- Markups
- Staff users
- Vouchers
- Suppliers
- Reports
- Agents
- Invoices
- Payments
Bookings
- Bookings
- Vouchers
Partners
- Agents
- Suppliers
- Markups
Money
- Invoices
- Payments
- Reports
System
- Staff users
- Settings
Illustration of the principle, not a screenshot of the Travigence panel.
Challenge 02 · Throughput
Routine tasks handled from the booking record
The work that slows a busy desk is rarely one big task. It is the small repeated steps, each in a different place, multiplied by every booking in the queue.
Throughput bottlenecks
Routine tasks took longer than expected during peak handling periods.
- Core workflows were refreshed so the steps of a routine task sit close together.
- The focus was the peak periods, when a long queue makes every detour cost more.
- The team keeps working the way it knows, with less time spent moving between screens.
Try it: complete the routine steps from one place
- Service
- Hotel stay
- Destination
- Lisbon, city centre
- Booked by
- Partner agency
- Status
- PendingConfirmed
Actions
Activity
No actions yet
- Booking confirmed with the supplier
- Voucher sent to the partner agency
- Invoice issued to the agency account
- Internal note added for the team
Illustration of a routine flow, not the Travigence workflow itself.
Challenge 03 · Visibility
A clear status view of active bookings for managers
Managers should not have to ask around to know what is on hold, what is confirmed and what needs someone to act. The upgrade made that view part of the daily screen.
Limited operational visibility
Managers needed clearer status views for active bookings.
| Service | Trip | Agency | Status |
|---|---|---|---|
| Flight | Return flight, two travellers | Agency A | On hold |
| Hotel | City hotel, family room | Agency B | Confirmed |
| Tour | Old town walking tour | Agency C | Needs action |
| Car rental | Airport car pick-up | Agency A | Confirmed |
| Transfer | Hotel to port transfer | Agency D | Cancelled |
| Flight | One-way flight, group booking | Agency B | Needs action |
Sample rows that show the idea of a status view; they are not Travigence data.
In their words
What the Travigence team says changed
Our teams now work with clearer controls and a more predictable booking operation.
Reported results
- 01Operator experienceSimpler controlsAnswers challenge 01
- 02Team productivityHigher throughputAnswers challenge 02
- 03Ops monitoringClearer visibilityAnswers challenge 03
Results are reported in the client's own terms. We do not publish figures we cannot verify.
Under the hood
The stack behind the upgrade
Travigence runs on the standard PHPTRAVELS stack. It is self-hosted, the source code is included under a commercial licence, and the data stays in the client's own database, which is what made a workflow refresh like this possible without starting over. Read more on our Technology page.
PHP- ApplicationThe platform code the team can read, extend and customise.
MySQL- DatabaseBookings, agencies and settings stored in the client's own database.
REST API- IntegrationStatus and booking data available to other tools over HTTP.
GET /api/bookings?status=on_hold
Accept: application/json
200 OK
{
"status": "on_hold",
"bookings": [
{ "service": "flight", "agency": "agency-a",
"next_action": "ticket" }
]
}A sketch of how a status view can be fed over a REST API. Endpoint names vary by installation.
Your turn
Upgrade your agency stack
Improve control and execution across your travel operations. Start with a consultation, or explore the pages behind this story.
Questions
About this success story
Short answers about the Travigence project and what it means for your own agency platform.
Talk to salesTravigence, a European B2B travel technology business, launched an agency operations upgrade on PHPTRAVELS in 2024. It refreshed core platform workflows to improve control, clarity and day-to-day team throughput.
Three: important controls were not grouped in an operator-friendly way, routine tasks took longer than expected during peak handling periods, and managers needed clearer status views for active bookings.
No. Travigence reported its results as simpler controls, higher throughput and clearer visibility. We publish the results in the client's own terms rather than adding numbers we cannot verify.
The standard PHPTRAVELS stack: PHP for the application, MySQL for the database and a REST API for connecting other tools. It is self-hosted, with the source code included under a commercial licence.
Yes. Many changes, such as how controls are grouped or how statuses are shown, can be made through configuration or custom work on the source code. Book a consultation and we will review your current workflows first.
Plans are one-time payments: Startup, Agency and Enterprise, each with the source code included. Custom workflow changes are quoted separately after a review.
Keep exploring
More from the platform
- Success storiesAgencies running on PHPTRAVELS
- Engida Travel storyRegional agency in Africa, booking flow refresh
- Tunin Travel storyB2C customer journey cleanup in North Africa
- B2B wholesalersDistribute to sub-agents
- B2B booking engineNet rates, two levels of markup and agent credit
- CustomizationMake it yours
