Part of AI
What Ask AI does
Ask AI sits in the top bar of your TripNerve workspace. Open it with ⌘J (Ctrl+J on Windows) from any page and type what you need. It has the same actions as the screens you click through: trips and itineraries, departures, bookings, enquiries, customers, crew, vehicles, accommodation, promo codes, reports, the website, the blog, the newsletter and the media library.
It looks things up first and never guesses which record you mean. Ask it to move "the Müller booking" and it searches your bookings, and if there are two Müllers it asks which one. When it's done it says in a sentence or two what changed and can open the page so you can see for yourself.
- What still needs doing before my draft trips can go live?
- Show me this week's new enquiries and bookings
- Add departures for the Annapurna Circuit every Saturday in March and April
- Move the Collins booking to the 24 October departure
- Put Pasang on the 10 October Everest departure as lead guide
- Change the hero photo on the home page and publish the site
Nothing changes until you approve it
Reading is free: lists, reports and lookups run straight away. Anything that adds, edits, deletes, publishes or emails shows as a card with a short plain description, such as "Add 8 departures to the Annapurna Circuit", and waits for you. You can open the details to see exactly what it will send, then Approve or Deny.
Some requests need several changes. When two or more are waiting, a bar above the message box shows how many, with Approve all and Don't do any. Website edits go to your draft site; the public site only changes when you ask it to publish and approve that too.
It works as you, never as more than you
Every action the assistant takes goes through the same rules as a click in TripNerve: your role's permissions, the same checks on seats and dates, and the same history. A booking moved by Ask AI shows in that booking's history under your name, as if you'd done it by hand. If your role can't delete trips or change team roles, neither can your assistant.
Chats belong to you in one company. Switch to another company you work for and you start with that company's chats.
The same rules keep it honest when something can't be done. Ask for a 13th traveller on a 12-seat departure and the booking is refused exactly as it would be on the Bookings screen; the assistant reads the error and tells you, or offers the next date with room. Ask for something your role doesn't cover and it says so instead of finding a way round it. It doesn't show you raw ids or code, just plain sentences and short lists, and when a request is genuinely unclear, such as which of two Everest trips you mean, it asks one question before going on.
Close the tab and come back later
Replies run on the server, not in your browser. Ask for a season of departures at the airport in Lukla, close the laptop, and the reply is waiting when you open TripNerve in Kathmandu. Past chats are listed so you can carry on where you left off, and Stop cancels a reply you no longer want. In the mobile app you get a notification when the assistant has replied.
Bigger writing jobs use the tools built for them. Asked to draft a whole trip or write a blog post, Ask AI starts the same research-and-write job as the Draft with AI and Write with AI buttons, and the result arrives as a draft for you to check.
Worked example
A Monday morning at Mero Himal Treks
On Monday 9 November the owner of a Thamel trekking company clears four jobs with Ask AI before the office opens, from a laptop at home.
| Request | What Ask AI did | Waiting for approval |
|---|---|---|
| Which enquiries from last week have no follow-up set? | Listed enquiries and found 3 with no follow-up date | Nothing, it only looked |
| Annapurna Circuit every Saturday, 6 Mar to 24 Apr 2027, 12 seats, minimum 2, cut-off 10 days | Found the trip and worked out the 8 Saturdays | 1 change: add 8 departures |
| Move the Müller booking from 14 Nov to 21 Nov on Everest Base Camp | Found the booking (2 travellers) and checked 21 Nov has 5 seats left | 1 change: move the booking |
| Set Poon Hill to USD 650 and publish Mardi Himal | Found both trips | 2 changes, approved together |
The first request only reads, so the answer comes back at once: three enquiries, one from a family in Lyon asking about Langtang Valley for December. The owner sets the follow-ups herself from the list it gives.
The departures request becomes one change card listing 8 dates, Saturday 6 March to Saturday 24 April 2027, each with 12 seats, a minimum of 2 and bookings closing 10 days before. She approves it. The Müller booking moves to 21 November after its own approval, and the 14 November date gets its 2 seats back. The last request needs two changes, so she uses Approve all. Four requests, four approved changes, and every one of them sits in TripNerve's history under her name.
Common mistakes
Approving without reading
The card says what will happen. Check the date, the trip and the number before you approve, as you would check a colleague's work.
Widening a role so the AI can do more
The assistant can do what the person can. Give staff the role their job needs and let the assistant work inside it.
Expecting edits to go live
Website changes go to the draft. Ask it to publish, or publish from Website, when you're happy with the preview.
Asking it to record a payment
TripNerve doesn't take or record payments, so the assistant can't either. Keep taking deposits the way you do today.

