Tripmojo - Agentic travel app that helps plan, book and run your trip

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.

Add a comment

Replies

Best

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?

 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

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?

 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.

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?

 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.

The booking emails into one shared trip part is the bit I'd actually use. How does Mojo handle it when two people forward conflicting versions of the same booking, say a hotel that got changed after the first confirmation?

 Glad that's the part that clicks! When two people forward the same hotel, we match it on the confirmation code first, then the property and dates. So it's recognised as one booking in the shared trip, not two cards. A changed booking, like new dates or a different room, is read as an update to that booking. We apply only what actually changed, and everyone in the group sees the same card. A plain duplicate of the same confirmation simply merges.

Where it gets tricky is when two copies genuinely disagree. We fixed a version of this for flights today, and the rule we're moving to everywhere is: never merge silently when details differ. Confirm against the source where we can, otherwise ask you which one is right.