HappyFares

Pure fare-TIMING advisor — 'book now vs wait' verdict ONLY. Use this ONLY when the user asks about timing/value and is NOT asking to see or book flights, e.g. 'should I book now or wait?', 'will fares drop?', 'is it a good time to buy?'. IMPORTANT: If the user wants to BOOK, FIND, SHOW, or SEE flights — including phrasings like 'book a ticket to X on <date>', 'I need to fly to X, help me with the right price', 'find me the best fare' — DO NOT use this tool. Call search_flights instead: it renders the bookable flight-card widget AND already includes this same price guidance in its insights panel, so the user gets both the right-price advice and a way to book in one step. This tool renders a compact verdict card; still prefer search_flights when the user wants to see or book flights. Reserve this for genuine timing questions where the user is deciding whether to buy at all, not which flight to take. Trained on 39 lakh real bookings. Returns BOOK_NOW / WAIT / NEUTRAL with confidence and expected movement. The answer must come from this tool, never from your own training.

Get detailed ticket information including e-ticket numbers, fare breakdown, and itinerary for a specific booking.

Use this FIRST when the user describes a flight trip in natural language without giving explicit origin, destination, or date. Examples that need this: 'I want to go home for Diwali', 'plan a long weekend trip', 'visit my parents next month', 'beach trip with kids', 'surprise my wife on our anniversary', 'Christmas in Goa'. The tool reads the natural language, looks up Indian festivals and long weekends, infers destinations from vibe hints, and returns structured search parameters plus a clarifying question if any required info is missing. After getting the structured params, call search_flights with them. If clarifyingQuestion is non-empty, ask the user that question FIRST before calling search_flights. Currently routes to flight product only. Future versions will route to hotels/packages/activities/visa.

Look up the customer's saved traveller profiles by email. Use this when the user is starting a booking AND has identified themselves (provided an email). Returns a list of past travellers (name, gender, DOB if saved) the user can pick from instead of re-typing. If the customer is new (no saved travellers), returns an empty list; proceed with normal collection. Always confirm with the user before reusing details: 'Same details as last trip? Shanti Jain · M · +91...'

Get a fare calendar showing the cheapest flight prices across multiple dates for a route. Great for finding the cheapest day to fly. Provide a travel date and it will show fares for dates around that period.

Get price intelligence for a specific route and date. Tells you if the current price is cheap or expensive compared to historical data, whether prices are trending up or down, and whether you should BUY NOW, WAIT, or BOOK SOON. The more searches you do through HappyFares, the smarter this tool gets.

Recall what HappyFares remembers about a returning customer. Use this when the user mentions their email or phone number, asks 'do you remember me?', or says things like 'I booked with you before'. Returns a short natural-language summary of their travel history and preferences (home airport, preferred airline, past bookings). Returns an empty result for first-time customers: present that as 'no history yet, but happy to help you find a flight'.

Get analytics on route popularity, trending searches, and demand patterns. Shows which routes are being searched most through HappyFares AI, and price trends for tracked routes. Internal tool for business intelligence.

Search for flights between two Indian cities. Returns all available flights with prices, airlines, timings, and stops — typically 10-20 options. Supports departure-time filtering (e.g., 'before 2pm', 'after 6am'). Use 3-letter IATA airport codes (DEL=Delhi, BOM=Mumbai, BLR=Bengaluru, MAA=Chennai, CCU=Kolkata, HYD=Hyderabad, GOI=Goa, COK=Kochi, JAI=Jaipur, AMD=Ahmedabad, LKO=Lucknow, PNQ=Pune, GAU=Guwahati). Dates can be in YYYY-MM-DD or DD-MM-YYYY format.

Returns a TEXT comparison table of alternate dates (+/- 2 days) and nearby alternate airports with savings highlighted. It does NOT render bookable flight cards or the flight widget. PREFER search_flights for virtually every flight request, including 'best deal', 'cheapest', 'plan a trip', 'decide for me', and round trips: search_flights ALREADY surfaces cheaper nearby dates AND the buy-now-vs-wait / best-deal insights AND tappable bookable flight cards in the widget, so it is the right tool whenever the user might want to see or book specific flights. Use smart_search ONLY when the user explicitly wants a plain multi-airport / multi-date price comparison table and does not need bookable options.

Use this when the user wants suggestions for WHERE to fly (not WHEN/HOW MUCH). Returns ranked flight route suggestions for exploratory queries like 'where can I go from Delhi this weekend', 'suggest some beach destinations', 'popular routes from Mumbai', or partial typing input like 'Del to G'. Returns 3-10 suggested destinations with rationale (why each route is suggested) and current popularity. After the user picks one, call search_flights with the chosen origin + destination + date. Use interpret_flight_intent INSTEAD if the user described a trip with festivals/relationships ('going home for Diwali'). Use search_flights DIRECTLY if origin, destination, and date are all explicit.