← Navan
Something new at Navan

Keep changed stays in chat without losing the original reservation

You’re the software engineer. Your team is in the room. Printed Oct 17, 2026.

An extra night can preserve a reservation or force a traveler into a new search.

Keeping the original stay intact protects continuity, while current rates and policy may make a replacement the better choice.

Who you’d be doing this for

“My client added a day, and I’m staring at two hotel tabs because chat can’t tell me what happens to my room.”

Luisa Castillo · Frequent Business Traveler

A corporate traveler whose client meeting has been extended after checking into a hotel.

What is at stake

Travelers extending hotel stays restart their search even when the assistant knows their original reservation. You must weigh continuity for the traveler against reliable, current options and explicit approval.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • reservation continuity vs current hotel availability
  • conversational simplicity vs informed approval
  • first-release focus vs modification coverage
  • shared platform reuse vs direct learning

Why Navan

Navan Edge already guides corporate travelers through hotel booking with loyalty and trip context, so changed stays test whether that context remains useful after booking.

Written with these in mind

product-minded backend engineerconversational systems engineerreliability-focused full-stack engineer

Not your kind of problem? 54 more at Navan, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.