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.
| Date | What happens | Status | Seats held |
|---|---|---|---|
| Tue 10 Nov 2026 | Akiko Nakamura requests 2 seats on the website | Requested | 0 |
| Wed 11 Nov 2026 | Office accepts it while waiting for a bank transfer | Pending | 2 |
| Mon 16 Nov 2026 | Transfer arrives; Confirm and email traveller | Confirmed | 2 |
| Sat 13 Mar 2027 | Trek starts | In progress | 2 |
| Sat 27 Mar 2027 | Day after the last day, Friday 26 March | Completed | 2 |
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.

