Launching today
Tripmojo syncs your booking emails into one shared trip, then Mojo, your AI travel agent, helps run it. Plan in a group chat where Mojo answers, runs polls and finds places. On travel day Mojo tries to check you in, saves your boarding pass, flags delays and gate changes, and tells you when to leave. On the trip it keeps today's plan current and splits expenses. Free on iOS and Android.













Free
Launch Team / Built With

AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted





Hi team, congrats on the launch! I installed Tripmojo today and went through the app.
One thing I noticed while signing up: the phone number field changed my digits as I typed (I entered 78880 and it showed 78808, three times). Is the input being reformatted on every keystroke? I’d guess a state update is racing with the formatting.
I’m also curious about the booking sync from a technical side. How do you turn emails from so many different airlines and hotels into clean itinerary items? Is it an LLM reading each email into a fixed structure, or templates per provider with an LLM as a backup? And how do you catch it when a parse is wrong?
@kunal_bhalerao1 Thanks for catching this, and your guess is close. The field reformats as you type and also places the cursor itself. It decided where the cursor goes by comparing the old and new text from the end. When the digit you type matches the one before it, that check couldn't tell you'd added it at the end, so it moved the cursor back and your next digit landed before the last one. We've reproduced it, and a fix is on the way.
On emails: no per-airline or per-hotel templates. An AI model reads each email into a fixed structure for each booking type, so a flight has to come back with its airports, times and flight number, and a hotel with its dates and confirmation code. The model only proposes changes. Code checks each one before it's saved: dates must actually appear in the email, airport codes and time zones are validated, and duplicates and updates are matched across emails. Every real mistake we fix becomes a permanent test case.
Love that Mojo flags delays and gate changes with a leave-by time — that's the part of travel day that always stresses me out. Does it nudge the whole group chat too, or just the person whose booking changed?
@ms_harita_kanuri Both! 🙌
When a flight is delayed, cancelled or retimed, Mojo messages the travellers on that flight directly in their own Mojo chat. That's where the personal stuff goes, like the new leave-by time. Mojo also posts the schedule change in the trip's group chat. That way the friend picking you up, or the people on a different flight, know without anyone having to forward a screenshot.
The idea is that the person affected gets what they need to act on, and the rest of the group gets just enough to adjust their plans.
Congrats on the launch! I was just testing manual flight entry by typing just the flight number “6E 1079” fills in the times for today and tomorrow, but for 22 Nov it says “Schedule not found” every time. So the lookup seems to only see maybe 48h ahead, which makes me guess it’s a live flight-status API rather than a schedules feed. Time zones from the airports and the automatic +1 day handled the red-eye well though. I am just curious about when a booking comes in weeks before the trip via email or Gmail sync, do you go back and verify it once it’s inside that window, or does it stay as parsed?
@md_obaidullah_ansari
Thanks for testing this so closely, and glad the red-eye handling held up!
You read it right. Manual lookup uses a live flight-status feed, and that feed only covers about the next two days, which is why 22 Nov fails. Looking up flights further out is a gap, and we're looking into it.
And yes, we go back and check. A booking imported weeks ahead stays as it was parsed until the flight enters the feed's window. From then on we track it against live data. If the airline moves the time by 15 minutes or more, we update the booking and alert you. Gate changes, delays and baggage belts come through the same way. A schedule-change email from the airline also updates the existing booking rather than adding a new one.
@garg_rish
Thanks, super helpful! Since you’re already tracking flights live, have you ever thought about building a schedule cache from that history? Most flight numbers repeat on the same route and time each week, so you could fill in times beyond 2 days with a “provisional” tag and confirm once the flight is in the window. It would also catch parse errors at import instead of 2 days out. The main risk which I see is the schedule change in late March and October. Would that make a paid schedules feed simpler?
@md_obaidullah_ansari
Great idea, and you've named the real tradeoff. A cache built from flight history would cover the routes our travellers fly often, and a "provisional" tag keeps it honest. It would also catch parse errors right at import, which we like a lot.
The weak spots are the ones you pointed out: the March and October schedule changes, plus rarely flown flights we have no history for. A paid schedules feed handles both, but it costs money for every lookup. We'll probably end up mixing the two: history first, the feed for gaps and the season changes. Thanks for thinking this through with us!
Hi team! I'm curious about how Mojo handles AI-generated trip planning when users have multiple constraints, such as budget, travel dates, preferences and group decisions. Do you use an LLM with tool calling and structured outputs to generate itineraries, and how do you validate that the recommendations and booking information are reliable before presenting them to users?
@aman_mishra35 Great question! Yes, Mojo runs on Gemini with tool calling and structured outputs. The schemas are strict and every field we need is required, so the model can't quietly skip things.
The constraints come from the trip itself: dates, budget and preferences from what your group actually said in chat and what you've already booked. If something isn't clear, Mojo asks instead of guessing.
For reliability, the model never invents a place, price or booking detail. It uses tools to look things up: live flight status, visas, places, hotel and activity availability. Every place maps to a real Google Maps listing or curated dataset we have curated by collaborating with multiple travel enthusiasts and open web. Prices are fetched live from the supplier when you book, never taken from what the model wrote. Booking info comes from your actual confirmation emails, checked against live flight data.
We also keep a set of real-world test cases that every change has to pass before it ships.
Still after all these guardrails, LLM can hallucinate and we try to keep our eval set exhaustive which we run daily.
Thanks for asking! 🙂
Congrats on the launch! The app feels really smooth with an excellent UI, Two things I noticed while testing. First, a Kashmir route showed a curated estimate of about ₹21,000 per person, but when I asked for cheaper options, Mojo said it couldn't size costs without live prices. Are the estimates and live search results separate data sources, and how do you reconcile them? Second, Transfers showed no rides after I entered my details. Is that a partner coverage gap, and would Uber/Ola deep links work as a fallback, like the Google Flights link-out?"
@saniya_mihani
Thank you, really glad the app feels smooth!
Estimates vs live prices: you're right, they come from separate sources. The curated route estimate is a typical cost we work out ahead of time. Mojo's "cheaper options" answer only quotes live prices, so it won't size a budget without them. Mojo should have started from the estimate and then refined it with live prices. That's a gap on our side, and we're fixing it.
Transfers: that's a partner coverage gap. Our transfer partner's coverage in parts of India, Kashmir included, is still thin. Linking out to Uber or Ola when we have no rides is a great idea, the same way we link out to Google Flights, and we're adding it to the roadmap.
Thanks for testing this closely. Feedback like this is exactly what we need.
@garg_rish Thanks for the reply Rish! It’s good to know that estimates and live prices come from separate sources. Starting with an estimate and refining it with live prices makes sense to me.
One more thing I noticed: some of Mojo's answers feel a bit generic, like those from a general-purpose LLM. I'm guessing it runs on something like Gemini, though I could be wrong. Have you considered using a small fine-tuned model for travel-specific tasks, such as itinerary suggestions or budget estimates, with a larger model as a fallback for open-ended chat? That could also reduce latency, since replies seem to take a few seconds. I’m curious whether you're leaning toward fine-tuning or improving retrieval from your curated route data. In the emerging world of AI, strong applied AI integration could also be the deciding factor.
@saniya_mihani Good guess. Yes, Mojo runs on Gemini, as you'll see in our Built With section.
We're leaning towards better retrieval over fine-tuning, at least for now. Most "generic" answers come from Mojo not using enough of what it knows: your bookings, our curated routes and live prices. A fine-tuned model wouldn't fix that, but grounding every answer in that data does. It also keeps answers current, which fine-tuning can't do for prices or availability.
On speed, we already use a smaller, faster model for most steps and save the bigger one for harder reasoning. But you're right that a few seconds still feels slow, and that's a priority.
Agreed on the last point. The model matters less than what it's connected to.
A gate change being flagged for me, with a fresh time to leave, is the moment this earns its place, since the last trip hinged on a gate change I only saw at the airport. Does Mojo need my booking emails, or can I add a flight by hand if I booked somewhere it never sees?
@karimbenkeroum Good question! So right now we have kept all the options open i.e.
Gmail sync, Forward an email, Upload booking, Add it manually, or tell Mojo (our AI agent) to add your flight.
It works not just for flights but for any bookings and then our agent is smart enough to properly cataegorize it and automatically start tracking it, if it is a flight
Congrats on the launch! How do you guard against Mojo hallucinating details like timings or entry requirements? Is there a way for the group to see where an answer came from before it goes into the plan?
@devansh_verma8
The AI never gets the last word on anything that matters.
- Facts come from sources. Flights, places and prices come from live data, not the model.
- Blank beats a guess. Missing fields stay empty, and code rejects anything that doesn't add up.
- Humans check. Our concierge team validates bookings before they're confirmed.
- You approve payments. Nothing is charged until you've seen the exact item and total.
- Easy to fix. Every error report becomes a permanent test.
If it's ever wrong, you'll see it, we'll catch it, and it won't cost you.
@devansh_verma8 @garg_rish quite thoughtful design pattern btw while you've explained where the data comes from, it's not always clear to the user which source backs a particular claim.
i noticed this on the Japan package i was exploring, where the visa card mentioned specifics like eVISA, five working days, and no printouts at the airport, but I couldn't tell what was sourced versus inferred.
Have you considered adding small source tags to individual facts, such as Live, Booking, Curated, or AI-inferred, supported with links where possible?
That would make verification much easier. For visa and entry requirements, authoritative sources like IATA Timatic could be particularly useful.
@devansh_verma8 @adityap700 Thank you, and that's a really sharp suggestion.
You're right that it isn't clear today. Our visa info comes from a database we check against official government sources, with curated corrections where we've verified a rule ourselves. But the card doesn't show you which parts are verified and which aren't, and for visas that's exactly what you want to know.
Source tags on each fact, like Live, From your booking, Verified or AI-generated, with a link to the official page where we have one, are a great idea. We're looking at starting with visa and entry rules, since that's where trust matters most. Timatic is a good call too. It's the gold standard, and we'll look into it.
@devansh_verma8 @garg_rish thanks for acknowledging!! surely that would make it even trustworthy for the Users .