Part of Sales and CRM
One person, one record
A trekker who asked about Gokyo two years ago, booked Poon Hill last spring and is now asking about Island Peak is one person. In most offices they are three rows in three places. TripNerve keeps one customer record per person: name, email, phone, country, how they found you and notes, with every enquiry and booking listed beneath.
You rarely add customers yourself. A website booking or enquiry finds its customer by the lead traveller's email, or adds a new one. Logging an enquiry with an email or phone you already have adds it to that customer. Staff can also pick an existing customer when they create a booking. Customers with history can't be deleted, so a booking never loses its person.
Merging duplicates
Duplicates still happen: someone messages on WhatsApp from one number, then books on the website with an email you have never seen. Open the record you want to keep and choose Merge a duplicate in. The duplicate's enquiries and bookings move across, details missing from the kept record are filled from it, both sets of notes are kept, and the duplicate is deleted.
Merging is the reason one email can safely be one customer. Rather than guessing from a similar name, TripNerve only joins records on an exact email (or phone, for logged enquiries and imports), and leaves the judgement calls to your staff. Two Sharmas from Delhi stay two customers until someone who knows them says otherwise.
Tags and custom fields
Tags group customers the way your office thinks about them: VIP, Agent, Repeat client, Everest 2026. Each has a colour, and the list filters by tag. A Repeat badge appears by itself on anyone with more than one booking.
Custom fields hold the details you keep on everyone, in the order you set: a passport number, a date of birth, dietary needs from a list, the agent who sent them. A field's type is fixed once added, so dates stay dates. Each customer shows them under their details, and the CSV export includes them as columns.
- Field types: text, number, date, or pick from a list
- Deleting a tag takes it off every customer; deleting a field removes its values
- Only people whose role allows it can change tags and fields
Import from a spreadsheet, export to one
Most companies arrive with years of clients in Excel or Google Sheets. Save the sheet as CSV, or copy and paste the cells with the header row. Match each column to a customer detail or one of your custom fields, then Check rows shows what will happen before anything is saved: new customers, people you already have, and lines with problems.
People you already have are matched by email or phone. You choose to merge them, which fills in what is missing, adds tags and empty custom fields and appends notes without overwriting anything, or to skip them. Export CSV downloads the customer list as filtered, with tags and custom fields, in a file Excel opens with accented and Devanagari names intact.
Finding people quickly
Search the customer list by name, email or phone, or press Ctrl+K anywhere in TripNerve to jump straight to a customer. Each record shows open enquiries, bookings, last activity and when they first got in touch, and the email and phone open a new email, a call or a WhatsApp chat in one click. The same records are in the TripNerve mobile app, so your operations manager in Pokhara can look up a returning client's dietary needs before a trek.
Worked example
Moving 640 past clients from Excel
A Pokhara company has 640 past clients in an Excel sheet, with columns for name, email, WhatsApp number, country, trek, year and "veg?". It has already taken 230 bookings and enquiries in TripNerve this autumn.
| Column in the sheet | Matched to | Result |
|---|---|---|
| Name, Email, WhatsApp, Country | Name, Email, Phone, Country | Standard details |
| Trek and Year | Notes | Kept as a note on each customer |
| veg? | Dietary needs (custom field) | Vegetarian or blank |
| Tags (a column added saying "Past client") | Tags | New tag created on import |
Check rows reports 425 new customers, 212 people the company already has (matched by email or phone) and 3 lines with problems, two without a name and one with an email missing its @. The office chooses to merge the 212: their tag and dietary field are added and the old trek history is appended to their notes, but no name or phone already in TripNerve is changed. The 3 problem lines are left out to fix and import later. 425 + 212 + 3 = 640.
In January the sales team filters the list by the Past client tag, exports the 637 imported customers as CSV with their dietary field, and sorts the file by country to call the 58 German clients ahead of spring. When one of them, Hannah Müller, sends a website enquiry in February, it lands on her existing record with her 2023 Annapurna trek already in the notes.
Common mistakes
Importing without a header row
The import reads the first row as column names. Add a header row so each column can be matched.
Keeping details in notes
A passport number buried in notes can't be exported as a column. Make a custom field for anything you keep on everyone.
Ignoring duplicates
Two records for one trekker split their history and miss the Repeat badge. Merge them as soon as you spot them.
Treating customers as a mailing list
Being a customer isn't consent to marketing. Newsletters go only to people who signed up and confirmed.

