Launched this week
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

LoomShow, don't just tell with Loom
Promoted





Great product team!
@kapilgadhire Thank you, feedback appreciated!
Congrats on the release! This looks really promising! 👍🎉
Connected my Gmail and it rebuilt my October Delhi–Ranchi trip by itself: both IndiGo flights, the right dates, ₹16K total, even the boarding passes and GST invoices in Docs. Really liked that.
You asked which booking email you read wrong, so here's one. Each of my flights shows two travellers under one PNR: "Yuvraj Tiwary" and "Yuvraj Tiwari". I flew alone and every document says Tiwary, so the trip says "You & 1 other" while the travellers page shows only me.
Saw in Built With that Gemini does the extraction with structured outputs. My guess is the schema keeps the shape right but not the spelling: on one of the documents the model "corrected" Tiwary to the more common Tiwari, and the merge added a new person. Do you check that extracted names actually appear in the source email or PDF? And would auto check-in have used the wrong surname here?
@yuvraj_tiwary Thanks Yuvraj, really useful, and glad the rest of the trip came through right.
You called it. None of your documents say "Tiwari". We checked all of them, and every one says Tiwary. The extraction slipped on the spelling of one, and two things on our side should have caught it but didn't:
1. We don't check that an extracted name actually appears in its source email or PDF.
2. Our step that decides whether a new name is the same person or another traveller wasn't switched on for every account yet, so the near-duplicate got added as a second traveller.
We're fixing both: a name has to appear in your documents, and near-identical names on one booking fold into one person instead of adding a traveller.
For auto-checkin, we would have not changed the names and would have used the name from the booking itself.
@sahilgoel Thanks Sahil, really appreciate such quick verification of docs.
Additionally, my e-ticket lists only me as a passenger, but booking still shows two travellers, so a simple comparison check between number of travellers and the passenger count on the ticket could catch this, without being dependent on spellings.
Also I just thought of an edge case of merge step, imagine 2 real people with almost same name on one PNR, like cousins Ankit Sharma and Ankita Sharma, just one letter difference but completely different people, so if both names are on same ticket then they should stay separate?
@sahilgoel @yuvraj_tiwary Both great points. Comparing against the passenger count on the ticket is a cleaner check than spelling, and we'll add it. If the ticket lists one passenger, the booking can't have two.
And yes, Ankit and Ankita on the same ticket stay separate. Two names that both appear on one ticket are two real people. We only fold near-identical names together when the documents never show both.
Congrats on the launch! I tried it with an old IndiGo ticket (DEL to DGH) and the PDF and the confirmation email ended up under one flight, on the right day. I didn’t expect that. I am curious how you match the two to the same booking. Is it the PNR or something looser? If they disagree like the email has a changed time which one does the itinerary go with? One more thing I noticed that the day showed “Flying home” and it did not change when I switched my home city in the profile. Is that worked out from the booking order?
@sahil_bhardwaj2 Thanks for testing it with a real ticket!
How they match: a PDF follows the email it came in, so your ticket attached to the flight that email created. Flights themselves match on flight number and date, and the PNR is stored with the flight.
When they disagree: a later email with a changed time, like a schedule change from the airline, updates the flight you already have. One gap: if two copies of the same flight show different times, today they can merge without the times being compared. That's a bug on our side, and we're fixing it so we check live flight data, or ask you, before picking a time.
"Flying home": good guess. It comes from the trip's shape, not your profile. The last day of a trip with a flight on it is labelled "Flying home", so a one-way trip like yours gets it wrongly. We'll make it check where the flight lands against your home city.
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!