Rules per team, grade or route
Each team gets its own cabin, caps and approvers.
Your team requests a trip, the policy check runs first, and your admin approves in one tap. Nothing is booked before that.
Most tools flag a broken policy after the ticket is issued. On Atravelx the check runs first, so your admin approves with the facts in front of them.
Each team gets its own cabin, caps and approvers.
Every fare at search and every request is checked before the admin sees it.
Over-cap requests route directly to your admin and finance before ticketing.
The fare, the policy result, the reason and the cheaper option, in one view.
Policy check: 134.00 USDC over the 120 USDC cap.
Traveller's note: “Client moved meeting, only refundable fare left.”
Travellers see the cheaper, greener choice first, so it becomes the easy one.
Under 4 hour route rule: rail preferred over flight. Saves 82 kg CO₂.
Four steps, usually a couple of minutes. Click through them.
Non-stop · 18:00 → 21:40 · 30 kg
134.00 USDC over the 120 USDC cap.
In-policy options on this route start at 19.00 USDC.
Move the rules an admin would set and watch each fare re-check itself.
Trip: DEL → BOM, Economy, booked 7 days ahead. Every request goes to the admin; flagged ones arrive with the reason attached.
Non-refundable · 15 kg check-in · Under the 120 USDC cap · booked 7 days ahead
Non-refundable · 25 kg check-in · Under the 120 USDC cap · booked 7 days ahead
Changeable · refundable · 30 kg · 134.00 USDC over the 120 USDC cap
Start with three fields and add rules as you grow.
Economy, a cap and a few days' notice. The founder approves every request in one tap, by email or on the dashboard.
Different rules for sales and engineering, and finance signs the big ones.
Cabin by grade, negotiated fares first, and two-level approvals across every entity.
Who requested, what the policy check said, who approved and when, what was paid: every booking keeps its history.
Can't find what you need? Your dedicated desk answers on +91 92500 00511, 24/7.
Cabin, price caps, advance-booking days, refundable-only fares, non-stop preference and who approves. Rules can differ per team, grade, route or entity.
Not by default. Every ticket waits for an admin's approval, and you can relax that for a team if you want to.
Hand approvals to a deputy for a set period. Requests go to them, and the audit trail records who approved.
Yes. Search results show in-policy badges and the cap, so travellers know where they stand before they submit.
Three fields to start, every rule you will ever need when you grow. Your travellers can book by evening.