The view from Gokyo Ri over the lakes and glacier

Bookings from request to the end of the trek

A booking in TripNerve is a group of travellers holding seats on one departure. Requests from your website wait for you to accept or decline them, and staff enter phone, email and walk-in bookings directly. Each booking keeps the price, line items and cancellation policy it was made under, moves from confirmed to in progress and completed on its trip's dates, and records every change.

Free during early access · No card needed

app.tripnerve.com
Sample data

Bookings

Who is travelling on which departure, and where each booking stands

Export CSVNew booking
UpcomingNeeds a reply (1)PendingConfirmedIn progressCompletedCancelled
BookingLead travellerTrip and datesTravellersTotalStatus
#1094Akiko Nakamura[email protected]Everest Base Camp Trek13–26 Mar 20272USD 2,900Requested
#1091Tom Collins+61 412 555 019Everest Base Camp Trek13–26 Mar 20273USD 4,570Pending
#1088David Okafor+44 7700 900412Manaslu Circuit TrekPrivate · from 3 Apr 20274USD 7,560Confirmed
#1072Priya Sharma[email protected]Langtang Valley Trek4–13 Nov 20262USD 1,580In progress
Statuses
Requested, pending, confirmed, in progress, completed, cancelled
Seats held by
Pending and confirmed bookings
Kept as booked
Price, line items and cancellation policy
History
Every status change and edit, with who made it

What's included

What bookings includes

  • Website requests

    Travellers send a booking request from your trip pages. It holds no seats until you accept it as pending or confirmed.

  • Bookings by staff

    Enter phone, email and walk-in bookings with New booking, on a scheduled date or a private date of their own.

  • Seats held

    Pending and confirmed bookings hold their seats at once, and a booking that needs more seats than are left is refused.

  • Kept as booked

    The price per traveller type, add-ons, promo code and cancellation policy are stored with the booking and don't change with the trip.

  • Trip stages

    Confirmed bookings move to in progress on the first day and completed the day after the last, unless you set a stage by hand.

  • History and refunds

    Every change is recorded with who made it. Cancelling records the refund the kept policy owes.

Part of Sales and CRM

Two ways a booking starts

Most Nepal operators take bookings in more places than their website: a WhatsApp chat that ends in a yes, an email from a returning client, a couple at the Thamel office. Staff enter these with New booking, either joining a scheduled departure or giving a private group its own date, which stays off the website. Starting from an enquiry fills in the customer, trip and rough date for you.

Travellers can also send a booking request from your website, choosing a departure, how many adults, children, seniors or students, any add-ons and a promo code. The request lands under Needs a reply, your company gets an email and a push on the phone app, and the traveller gets an email saying you have it. Nothing is promised and no seats are held until you accept it as pending, confirm it, or decline it.

What each status means

Statuses follow how a trekking office actually works, rather than an online shop.

  • Requested: sent from your website, waiting for your reply; holds no seats
  • Pending: agreed but not final, for example while you wait for a bank transfer; holds seats
  • Confirmed: final; holds seats and can email the traveller a confirmation
  • In progress: the trip has started; set automatically on the first day
  • Completed: the trip is over; set automatically the day after the last day
  • Cancelled: seats go back on sale at once, with the refund owed recorded

Prices and policy that don't move

When you raise next season's price or change your cancellation terms, bookings already made shouldn't change with them. Each booking stores its price per traveller type, its add-ons and promo discount as line items, its total, and the cancellation policy that applied on the day it was made. The trip can change freely; the booking keeps what the traveller agreed to.

TripNerve doesn't take or record payments. You take deposits and balances the way you already do, usually by bank transfer, and use the pending and confirmed statuses to show where each booking stands.

Trip stages, history and cancellations

Confirmed bookings move along by themselves in your company's time zone, so the list of who is on the trail is always current. If a group starts early or you want to mark a trip completed after an evacuation, set the stage by hand: it is pinned there until you let it move on by itself again.

Every booking keeps a history of status changes and edits, such as a new departure date, a traveller added, an add-on removed or the total changed, with who made each one and when. Cancelling asks for the day the traveller cancelled, works out the refund from the policy the booking kept and its stored total, and records it. The money itself is paid back outside TripNerve.

Travellers on the booking

A booking is made by one lead traveller and can carry up to 50 travellers. Name the rest after saving on the Travellers card, with each person's nationality, date of birth, email and phone or WhatsApp number, and edit them later without touching the rest of the booking. Nationalities feed the traveller nationality report you need for Nepal Tourism Board and association returns, and the bookings CSV export lists every traveller under their booking.

Bookings can be searched and filtered by trip and departure, and the tabs (Upcoming, Needs a reply, Pending, Confirmed, In progress, Completed, Past, Cancelled) show where each one stands. Each lead traveller is linked to a customer record, so a repeat client's earlier trips are one click away.

Worked example

A spring booking from request to completed

A company runs its 14-day Everest Base Camp Trek on Saturday 13 March 2027 at USD 1,450 a person. Its cancellation policy refunds 90% at 60 days or more, 50% at 30 to 59 days and nothing under 30 days.

DateWhat happensStatusSeats held
Tue 10 Nov 2026Akiko Nakamura requests 2 seats on the websiteRequested0
Wed 11 Nov 2026Office accepts it while waiting for a bank transferPending2
Mon 16 Nov 2026Transfer arrives; Confirm and email travellerConfirmed2
Sat 13 Mar 2027Trek startsIn progress2
Sat 27 Mar 2027Day after the last day, Friday 26 MarchCompleted2

In January the company raises the 2027 price to USD 1,550. Akiko's booking still reads USD 2,900 for 2 travellers, with the policy she booked under. Her history shows each step above, who did it, and the change when the office added her partner's nationality and date of birth on the Travellers card.

On the same departure, Tom Collins's booking for 3 (USD 4,350, plus an extra night in Kathmandu at USD 60 each and an airport pickup at USD 40, for USD 4,570) is cancelled on Friday 5 February 2027, 36 days before the start. The 30-day tier applies, so TripNerve records a refund of 50%, USD 2,285, and the 3 seats go back on sale on the website straight away. The office pays the refund by bank transfer.

Common mistakes

  • Leaving requests unanswered

    A website request holds no seats, so the date can fill while it waits. Accept or decline requests the same day.

  • Confirming before payment

    If you wait for a transfer before committing, use pending. It holds the seats without telling the traveller the booking is final.

  • Editing the trip to fix one booking

    Changing the trip price won't touch existing bookings, by design. Edit the booking itself, and the history keeps a record of the change.

  • Picking today as the cancellation date

    The refund counts from the day the traveller cancelled. If they emailed last week, pick that day so the refund matches your policy.

How it works

Set up bookings in four steps

  1. Step 1

    Set up the trip

    Give the trip its prices, departures and a cancellation policy, or use your company's default policy.

  2. Step 2

    Take bookings

    Answer website requests under Needs a reply, and add phone and walk-in bookings with New booking.

  3. Step 3

    Name the travellers

    Add each traveller's name, nationality, date of birth and contact details on the booking.

  4. Step 4

    Let it run

    Confirmed bookings move to in progress and completed on their dates; cancel with the refund recorded if plans change.

Questions

Common questions

Something else on your mind? Email us and a person on our team will answer.

Do website booking requests hold seats?

No. A request holds no seats until you accept it as pending or confirm it. Declining a request doesn't email the traveller, so you can tell them yourself.

Can travellers pay online when they book?

No. TripNerve doesn't take or record payments. Travellers send a request, and you take payment the way you already do, such as by bank transfer.

What happens to a booking if I change the trip's price?

Nothing. Each booking keeps its price per traveller, add-ons, promo discount, total and cancellation policy as they were when it was made.

Does TripNerve refund the traveller when I cancel?

It works out the refund owed from the policy the booking kept, its total and the day the traveller cancelled, and records it on the booking. You pay the refund yourself.

Can I change a booking's status by hand?

Yes. You can mark a trip in progress or completed early, and it stays there. Choosing to let it move on by itself puts it back on its dates.

Can I manage bookings on my phone?

Yes. The TripNerve mobile app can answer requests, add and edit bookings, change their stage and cancel them with the refund shown.

A lone trekker on the trail to Tilicho Lake

Ready before the spring season

Set up your company this afternoon and have your trips, dates and booking site live by the weekend.