Schemes are the backbone of Trava’s automation engine. They define what the system should look for in each reservation, what actions to perform, and in which order.
A scheme is a structured set of rules and actions that Trava executes when a reservation enters the system. Schemes allow travel agencies to automate complex sequences of actions, reduce errors, and speed up operational workflows.
Schemes consist of segments: Trigger → Conditions → Actions → Finish
Each scheme:
- Defines when it should run (conditions and priorities)
- Contains logic describing what to check or transform in the PNR
- Includes actions the system performs (e.g., add remarks, update fares, email passengers, create tasks, push data to CRM, etc.)
- Ensures automated, predictable, repeatable outcomes for every reservation
Schemes work like a workflow blueprint for processing bookings. Once configured, they run automatically and require no manual intervention.
Schemes consist of steps. Each step analyzes the current PNR, makes a decision, and executes a sequence of commands in Amadeus, Sabre, or Galileo.
Start
A scheme starts automatically. All trigger settings are defined at the Start step, and a PNR can enter a scheme in several ways:
- when the PNR appears in a GDS queue
- via API or webhook
- from another scheme (through the PNR Redirector scheme)
- manually, by an operator
Processing flow
Once started, the system moves through the scheme step by step, following the connections between them.
Decision-making
Each Condition evaluates the current state of the PNR and determines the next path:
Condition → Yes path / No path → next steps
Action execution
Each Action performs a specific task at its step. The action can either complete successfully or fail (due to an error or an inability to execute).
Completion
Each scheme run can end with different outcomes:
- Finish – processing is completed successfully, no повтор run is required
- Pause / Repeat – processing is postponed for a defined period and then resumed
A scheme continues to process the PNR until it reaches the Finish state according to the defined rules.
For schemes to function correctly, Trava provides reference directories and settings that scheme steps use when performing specific actions. For example:
- Carrier settings – control reissue and revalidation logic
- Offices – define where pricing and ticketing should be performed
- Variables – store and reuse dynamic data during processing
- Templates – work faster using pre-built scheme templates
Trava enables travel agencies to work faster, more accurately, and more efficiently – and schemes are what make this possible.
Schemes provide several key benefits:
- Consistency: Every reservation is processed the same way – according to your business logic
- Speed: Actions that take minutes manually are executed instantly
- Accuracy: Fewer mistakes, fewer missed conditions, fewer human-factor issues
- Scalability: New lines of business or seasonal peaks can be handled without extra staff
- Transparency: All executions are logged and auditable
- Flexibility: Schemes allow highly customized automation per carrier, agency, fare, passenger type, PCC, or workflow scenario