Quest 2.0 gives company admins and travel managers powerful, flexible tools to control travel spend, enforce policy, and streamline approvals—while still keeping the booking experience simple for travelers.
In today’s corporate travel environment, organizations need the ability to balance cost control, traveler flexibility, and duty of care. Quest 2.0 is designed to do exactly that with modern, configurable policy settings built directly into the booking flow.
Setting Up Travel Policies in Quest 2.0
Company administrators can create and manage travel policies that align with organizational goals, budgets, and event requirements.
These policies can apply across:
Flights
Hotels (where enabled)
Ground transportation (where enabled)
Policies help ensure travelers only see or select options that align with company rules—or clearly flag those that require approval.
Flight Policy Controls
Quest 2.0 provides granular controls for managing flight behavior and spend.
💰 Price & Duration Limits
Admins can set maximum allowable:
Flight cost thresholds
Trip duration limits (when applicable)
If a search exceeds these limits, the itinerary is flagged as out of policy and may require approval before booking.
🛫 Cabin / Class of Service Rules
Companies can define allowable fare classes, such as:
Economy only
Economy + premium economy (if enabled)
Quest also allows you to select VIP status for certain travelers if needed
These rules ensure consistency while still allowing flexibility where needed.
⏰ Arrival & Departure Time Rules
Quest 2.0 supports time-based policy controls to align travel with event schedules.
Examples:
Require arrival before a specified time (e.g., before a welcome dinner or kickoff event)
Require departure after a certain time (e.g., after final sessions conclude)
This ensures travelers can fully participate in company events without unnecessary schedule conflicts.
✈️ Airport Preferences & Routing Rules
Admins can guide or restrict airport selection in multi-airport regions.
For example:
Prioritize JFK over LGA in New York
Standardize arrivals into a single airport for group transportation planning
Non-preferred selections can be flagged as out of policy and routed for approval if needed.
⚠️ Out-of-Policy Booking Workflow (Quest 2.0)
Even when a flight is outside policy, travelers are not blocked.
Instead, they can:
Select the itinerary they prefer
Submit it directly for approval at checkout or pay the difference on their own personal credit card
If traveler directs request for approval they can add note or reason for the request
The system then places the booking into an approval queue for review by an admin.
Approval Process
When a trip is submitted for approval:
The reservation is held temporarily (not fully ticketed until approved)
Admins have up to 20 hours to approve or reject the request
If no action is taken, the request is automatically canceled
The traveler must return to Quest to rebook if needed
This ensures timely decision-making while preventing unintended out-of-policy bookings.
Rejection Handling
If a request is rejected:
The traveler is notified with the admin’s reason
The traveler is directed back to Quest to modify their selection
In some cases, travelers may be instructed to select a compliant alternative or adjust cost (e.g., choose a lower fare or different timing)
This keeps communication clear while maintaining policy integrity.
Quest 2.0 Key Benefit
Quest 2.0’s policy engine is designed to strike the right balance between:
Control for administrators
Flexibility for travelers
Visibility across all bookings
Instead of blocking travelers, Quest guides them toward compliant choices while preserving the ability to request exceptions when necessary.
Summary
Quest 2.0 enables companies to fully customize travel policies around cost, timing, routing, and class of service—all while maintaining a smooth, consumer-grade booking experience for employees.
Admins gain control and visibility, travelers gain clarity and flexibility, and organizations gain a more efficient, policy-aligned travel program.