Budget Airline Aggregator / Regional Carrier — India Research Note

Who does it: Small travel agents in tier-2 and tier-3 cities — towns like Ranchi, Jodhpur, Udaipur, Vadodara — run ticket sales over phone and WhatsApp. They are not IATA-accredited agents. They are neighborhood shops with a phone number, a WhatsApp broadcast list, and a relationship with a "consolidator" above them in the chain.

The consolidator buys blocks of seats at negotiated rates from airlines (or from airline-appointed GSA network), then sells individual seats to sub-agents at a margin. Sub-agents sell to end customers at a further markup. The entire chain runs on phone calls, WhatsApp texts, and a physical or WhatsApp-shared Excel sheet of available seats and fares.

Where airlines fit: Regional carriers under the UDAN scheme — Star Air, Fly91, Air India Aureoss — have thin margins, limited distribution staff, and no robust B2B portal. They rely on GSA networks (general sales agents) who manage a chain of sub-agents via WhatsApp groups. The GSA enters bookings manually into airline systems.

Where time and money leak:

• Sub-agents spend 2–4 hours a day on WhatsApp groups manually copying PNRs, seat numbers, and fare changes from consolidators
• Consolidators cannot see real-time inventory — they call or WhatsApp the GSA, who calls the airline, who may or may not respond fast
• Mispelled passenger names, wrong PNRs, date errors — all caught at check-in, requiring rebooking with no refund
• Customers in unserved UDAN routes have no transparent comparison — they take whatever the local agent has or go direct to the airline website with poor UX
• Payment collection is cash or UPI, settled manually at end of week, with float risk

The human in the loop is not a feature — it is a tax. Every link in this chain adds 3–8% margin and one hour of latency.

---

Who profits from it staying manual:

• Consolidators and GSAs: their value is access and relationship, not efficiency. A more transparent market erodes their margin.
• Airline revenue management teams: they prefer controlled distribution through known GSAs rather than open aggregation that might race-to-the-bottom fares
• Traditional IATA-accredited travel agents: they have GDS access (Amadeus, Sabre) which is expensive and complex — their institutional moat disappears if a WhatsApp bot does the same

Who is hurt:

• Sub-agents in tier-2/3 cities: they lose sales because they can't respond fast enough or don't know inventory across consolidators
• Regional carriers: UDAN routes are loss-making or thin-margin — better distribution tools could increase load factors
• End customers: no price transparency, no easy rebooking, no certainty on regional routes

Who would pay to change it:

• Sub-agents with 50+ monthly bookings would pay Rs 200–500/month for a tool that keeps their WhatsApp inventory updated automatically
• Small corporate travel desks in non-metro cities would pay a per-ticket fee for a reliable booking agent
• UDAN carriers would pay for distribution tooling if it increased load factor without eroding yield management — but procurement cycles are long

The honest answer: The sub-agent is the most willing payer. They are the most squeezed and the most manual. But they are also the hardest to reach digitally and the most price-sensitive.

---

The wedge: A WhatsApp-first B2B booking agent for sub-agents selling regional airline tickets.

Not a consumer app. Not an OTA. A tool for the person sitting in a travel shop in Jodhpur who currently has 6 WhatsApp groups open.

Day one function: A sub-agent messages a WhatsApp number with: "DEL → JDH, 25 Sep, 2 pax" The agent replies with live fares from consolidator inventory, shows seat availability, books with one confirmation message, sends a PNR. The sub-agent collects payment via UPI and confirms. Everything stays in WhatsApp. No app to install. No training session.

What it replaces: The sub-agent's 6 WhatsApp groups + 3 phone calls + one Excel sheet.

Pricing SHAPE:

• Per successful booking confirmed: Rs 25–50 per ticket (not per order — per ticket)
• A sub-agent doing 100 bookings/month at Rs 35/ticket = Rs 3,500/month cost, recovering it from one avoided error rebooking per week

Who pays: The sub-agent pays. Airlines and consolidators get connected for free initially to build inventory.

Why this is the wedge: The broader problem (OTA for regional routes) requires airline APIs, GDS connections, payment gateway integration, customer acquisition spend. The sub-agent tool requires only a WhatsApp Business API account, a small team to manually seed inventory from consolidator WhatsApp groups, and a simple booking confirmation workflow. It can be built in 3 weeks. Validated in one city.

---

Consumer-facing OTAs with regional airline coverage:

• MakeMyTrip: covers IndiGo, Air India Express, SpiceJet, Akasa Air, Star Air, Fly91. Strong in metros, thinner in UDAN-specific routes.
• Ixigo: similar coverage, strong mobile UX
• ClearTrip: covers major regional routes, but UI is dated and conversion on UDAN routes is poor
• EaseMyTrip: budget-focused, competes on price transparency

WhatsApp or chat-based booking:

• Ixigo has a WhatsApp chatbot for flight search and booking confirmation (confirmed public feature)
• MakeMyTrip has WhatsApp support for booking status updates (confirmed)
• Various unverified Telegram bots and WhatsApp bots exist — no named, funded player has productized this specifically for the B2B sub-agent segment

GDS and B2B:

• Travelport, Sabre, Amadeus — global GDS platforms used by IATA-accredited agents, too expensive and complex for the sub-agent segment
• IndiGo's B2B portal (for GSA and corporate accounts), Air India Express B2B — functional but designed for larger accounts

Regional carrier own platforms:

• Star Air: has a website with booking, limited API distribution
• Fly91: launched 2023, website booking only, minimal distribution network
• Air India Aureoss: B2B-focused under UDAN, primarily through GSA network

The gap: No named player is specifically building a WhatsApp-first B2B booking layer for the tier-2/3 sub-agent segment. The gap is real.

---

Fact 1: Regional carriers already have or will build direct B2B API distribution that makes a middle layer obsolete. How to check cheaply: Call Star Air and Fly91's GSA/contact numbers (publicly listed on their websites), ask if they have an API or B2B portal for sub-agents. If yes within 6 months, the middle layer has no wedge. Budget: Rs 0 (phone calls). Time: 2 hours.

Fact 2: Sub-agents will not pay for a booking tool — they survive on commission from airlines/consolidators, not from efficiency gains. How to check cheaply: Spend 3 days in one tier-2 city, visit 10 sub-agents, show them a prototype and ask what they would pay. If 7/10 say "nothing," the willingness-to-pay assumption is wrong. Budget: Rs 5,000–10,000 travel + Rs 500 for prototype. Time: 1 week. Alternative: WhatsApp survey to 50 sub-agents via existing travel agent WhatsApp groups.

Fact 3: WhatsApp Business API is blocked, too expensive, or unreliable for this use case. How to check cheaply: Apply for WhatsApp Business API, get a green test number, send 100 test messages and measure delivery rates. If delivery is below 90% or approval takes longer than 4 weeks, the channel is unreliable. Budget: Rs 5,000. Time: 2–4 weeks.

---

Week 1–2: Seed inventory. Pick one consolidator in one city (e.g., a consolidator in Jaipur who sells Air India Express and Star Air seats on the DEL–JDH route). Manually maintain a Google Sheet with their available inventory. Build a simple Telegram bot that takes a query and replies with the Google Sheet data formatted as a message.

Week 3–4: Build the booking loop. Connect the Telegram bot to a small database. Add: search → seat confirmation → PNR entry → booking confirmation. Simulate the full loop with the consolidator manually entering data. Use free-tier hosting.

Month 2: Get 3 sub-agents. Go to the Jodhpur or Jaipur travel agent market physically. Bring the Telegram bot on your phone. Sit with 3 sub-agents and do every one of their bookings through the bot for one week. Charge them Rs 0. Collect feedback. Fix critical bugs.

Month 3: Charge. At the end of month 2, ask them to pay Rs 299/month for continued access. This is the earliest possible willingness-to-pay signal.

Budget:

• Travel (Jaipur/Jodhpur, 2 weeks): Rs 8,000
• Telegram bot dev (freelancer): Rs 15,000–25,000 if outsourced
• WhatsApp Business API setup: Rs 5,000
• Hosting (3 months): Rs 3,000
• Total: Rs 15,000–30,000

Pass mark:

• At least 3 sub-agents actively using the tool by end of month 2
• At least 2 of those 3 pay Rs 299/month at the month 3 ask
• At least 10 real bookings processed end-to-end without manual intervention

If all three met: proceed to 10 sub-agents in 3 cities. If not: kill it. The gate is willingness-to-pay, not usage.

---

AGENCIFY first, PRODUCTIZE second, AI-FY later.

The manual consolidator-to-sub-agent chain is fundamentally an agency relationship — someone manages inventory on behalf of airlines and passes it down. The right first move is to replace the human consolidator's WhatsApp coordination with a simple agent (initially human-in-the-loop, later partially automated) that sits in a Telegram/WhatsApp group and does what the consolidator does: receives inventory, formats it, sends it, books it. This is an agency model with a small team running it. Productization — a self-serve tool sub-agents use without the agency team — only makes sense after the workflow is validated and sub-agents show they will pay. AI-fying it requires volume that does not exist yet. Build the agency. Learn the workflow. Then productize the parts that scale.

Availability confirmed against the .in registry (RDAP) on 2026-09-21. Prices and ownership read from our own intelligence tables. Nothing here is estimated.

Single-word, available now

• budgets.co.in — available

Also available (compound)

• planehub.in
• planemart.in
• planekart.in
• planemandi.in
• planebazaar.in
• planedirect.in
• planesupply.in
• planeconnect.in

In the expiry pipeline — watch

• plane.co.in · 432 days · score 90

Taken and developed — do not chase

• plane.co.in · entropy 5.54
• airlines.in · entropy 6.85
• mybudget.in · entropy 4.68

---

Generated 2026-09-21 10:38 UTC. Topic from our research queue; no market-size figure appears here unless a source is named. The domain block above is read from our own intelligence tables and confirmed at the .in registry (RDAP); the model wrote the analysis, not the domain facts.