One screen for every trip. One file for every receipt.
The flight booking tool office admins and EAs actually want — built for the person who's been the human router between traveller, agent, policy, and finance for the last three years. The trip and the paperwork live in the same place. You stop chasing.
A week as a travel admin, before and after
Anyone who’s been the travel coordinator at a 100-person Indian startup recognises the rhythm. Monday morning: the founder asks if Arjun’s DXB flight was booked. You ping the agent on WhatsApp. He doesn’t reply till 11am. Wednesday: finance pings you for last week’s invoices. You ping the agent. He sends them Thursday — two of them are the wrong GSTIN. Friday: a new joiner asks if you have her passport on file. You do, in an Excel from 14 months ago, somewhere. You re-type it.
That’s not a software problem. That’s three different tools (WhatsApp, email, an Excel) pretending to be a workflow.
A week on Traviq, same 100-person team, same five trips:
- Monday 9:12am: Arjun’s BLR→DXB shows as BOOKED · IN POLICY · GST invoice attached. You haven’t messaged anyone.
- Tuesday 2pm: Three new bookings approved in one click — under the auto-approve threshold the founder set.
- Wednesday 11am: Finance opens the dashboard themselves. Every invoice is there, with IRN, GSTIN, GL code.
- Thursday: You don’t chase anyone.
- Friday: New joiner’s passport gets uploaded once. The next booking auto-fills.
Same five trips. Four fewer fires. The tool didn’t replace you — it deleted the work you weren’t being paid to do. You stop being the booker. You become the travel ops lead — the person finance, HR, and the founder all sync to.
Employee profiles that save themselves
Half the friction of corporate travel is data that lives in three places. Passport in an Excel. Skywards in an email signature. Meal preference in someone’s head. Emergency contact in HR’s spreadsheet. Every booking is a re-type.
Traviq stores it once. Each traveller has a profile: passport (number, country, expiry, scan), Aadhaar (optional, India-only), frequent-flyer numbers across every airline, GST cost-center, dietary preference, mobility needs, emergency contact, and travel-document expiry alerts that ping you 90 days out. The traveller can update their own profile; you approve changes. The next booking auto-fills — no re-typing, no asking, no Excel.
For founder EAs running travel for ten executives across regions: profiles are tagged. “VIPs fly business over four hours, premium economy under. Engineering travels economy. Sales travels premium economy. Co-founders pick their cabin.” Traviq enforces the bands at search; you don’t have to manually flag a violation.
Policy parsed from one sentence
Policy enforcement used to mean a 12-page PDF nobody read and you policing the gaps. Now you write the policy the way you’d write it on Slack. “Economy under four hours, premium over four. Hotel cap ₹8,500 a night — ₹12,000 in BLR, BOM, DEL. Auto-approve under ₹40,000. CFO approval over ₹1 lakh.” Traviq parses it. The search results respect it. Approvals route themselves.
You stop being the rule enforcer. The system is. When someone tries to book outside policy, the screen explains why before they click, with the plain-English trade-off (“Premium economy +₹3,400, in line with policy” or “Business +₹14,200, requires CFO approval — route to Priya?”). Exceptions reach you only when they actually need a human decision.
Same engine drives the close-week dashboard your CFO uses — one ledger, one rule set, no manual reconciliation.
Three rows admins ask about first
The fuller comparison is on the home page. The three rows below are the ones that change your Monday.
See the full comparison on the home page.
The 5% that still needs a human
Software handles 95%. The other 5% is what you’re actually paid for — the JFK flight that pushed back four hours, the founder’s visa-on-arrival that wasn’t, the BOM-to-BLR that needs to become BOM-to-HYD by 11pm tonight.
We don’t pretend software handles that. So the founder WhatsApp line goes to Jitesh (Bengaluru) or Nameet (Dubai) directly — whichever timezone is awake. You stop being the human router between a sleeping agent and a stranded traveller. The on-call number routes the same way for international disruptions affecting same-day departure. You loop in when you need to, not because the system can’t reach anyone else.
The decision to switch isn't yours alone
Three other people need to see it. One click, mailto pre-filled, the forward lands ready to send.
The travel tool that fixes our reconciliation
I've been looking at Traviq. The admin dashboard is what we need, but the GST close-week story is the bigger win — every invoice attached at booking, IRN captured, GSTR-2B match pre-built. Want to look at their CFO page before our next review? — [name]
The booking tool I want us to try
Traviq lets the team book their own trips in policy. I'd see only the exceptions, you'd stop being copied on every BLR-DXB. Their founder page covers the commercials. — [name]
Sanity-check Traviq's GST capture
Looking at Traviq for travel. They claim IRN capture at booking and Tally import in two clicks. Their CA page goes deep on the reconciliation mechanics. Can you give it a 10-min read? — [name]
The questions admins ask before they roll it out
The questions a finance head, founder, admin, or CA actually asks before they recommend a change to corporate travel. Direct answers, no marketing voice.
How long does it take to onboard a 100-person team onto Traviq?
Eight working days from kickoff to first live booking. Day 1-2: import existing traveller data (passport, FF numbers, dietary, emergency contact) — we accept CSV, Excel, or a direct sync with your HRMS if it's Keka, Darwinbox, or Razorpay Payroll. Day 3: policy parsed from a sentence and reviewed with you. Day 4-7: approval workflows, cost-center mapping, integration test with finance. Day 8: first booking goes live. No 6-week implementation.
Can I book multi-city and multi-traveller trips in one workflow?
Yes. Multi-city: search BLR→DXB→SIN→BLR in one query, with policy applied per leg. Multi-traveller: book three engineers on the same flight in one transaction, with each traveller's profile auto-filling separately. Group bookings (10+) route through the on-call founder line for negotiated fares — IndiGo 6E Corporate and Air India both offer group rates Traviq can apply automatically.
What happens to the data I already have in our spreadsheet?
Import it once. We migrate the traveller list (passport, FF numbers, dietary, emergency contact), the policy doc, the last 12 months of bookings (for the close-week reconciliation baseline), and the GL code / cost-center mapping. After import, the spreadsheet is read-only — bookings update Traviq, not the Excel.
Does Traviq handle hotel and ground transport, or just flights?
Flights and hotels at launch. Ground transport (Uber for Business, BluSmart, MakeMyTrip cabs) by Q3 FY26. For now, you can attach a ground-transport receipt to a trip record so it appears on the same close-week report — the GST invoice attaches the same way as a flight, just outside the auto-capture flow.
How are approvals routed?
Per the policy you wrote. Under the auto-approve threshold: no human in the loop, booking goes live, the founder gets a digest. Over threshold: routes to the named approver (manager, CFO, founder) with the trade-off explained in plain English. The approver clicks approve/decline in one tap, on phone or laptop. The approval is logged with timestamp, traveller, cost-center, and route — your audit trail is automatic.
What if a traveller wants to book outside the platform — direct on IndiGo or Emirates?
You can lock that down at the policy level (no off-platform bookings) or allow it with a receipt-upload requirement. Most teams start permissive and tighten over the first month once everyone's used to the workflow. Off-platform bookings still appear on the close-week report when receipts are uploaded — the GST invoice has to be matched manually in that case, which is the entire point of moving on-platform.
Who handles the trip when something goes wrong at 2am?
The founder WhatsApp line — Jitesh in Bengaluru, Nameet in Dubai, whichever timezone is awake. You loop in when you need to, but you're not the on-call. For schedule changes, the platform pings the traveller and you automatically; for cancellations and visa issues, the on-call founder picks up. There is no ticketing queue.
Do you import to Tally / Zoho Books / ClearTax?
Yes — Tally XML vouchers (auto-numbered, GL-coded), Zoho Books CSV, ClearTax, NetSuite. Your accountant can preview the import file before the first booking. If your team runs an ERP we haven't built for, we'll write the connector before pilot kickoff. Tickets issued by TravClan and Tripjack (IATA-accredited); payments via Razorpay (RBI-PA licensed); operated by Drumworks Ventures, GSTIN 27AASFD4920E1ZE. We're in private pilot with three Indian teams.
See the admin dashboard in a real workflow
A 2-min walkthrough shows booking a trip, routing an approval, and exporting the close-week report. No demo call required to watch it.