From a visitor’s question to a teammate’s to-do
Every step happens inside TripCreator — nothing to forward, copy or re-type.
- 1Visitor fills in the formOn your tour page
- 2Questions adaptBy tour, party size, budget
- 3Enquiry createdOn your pipeline board
- 4Assigned & notifiedIn the app, by email, in Slack
- 5Followed upQuote, itinerary, booking
Built for how tour operators really get enquiries
Conditional questions
Show a follow-up only when it applies — a guide-language question for private tours, a pick-up area for self-drive — so forms stay short and answers stay useful.
Budgets that fit the trip
Offer budget ranges that change with the tour type, the number of travellers and the dates, instead of one list that is wrong for half your visitors.
Knows which tour they were on
One form serves every tour page and records which page each enquiry came from, so you know what drew them in.
Pipeline and CRM, automatically
Each submission becomes a Draft enquiry in the stage you choose and a CRM contact — matched by email so returning visitors are not duplicated.
Assign and claim
Route requests to a default owner, let the team take them with one click, or hand them to a colleague. Nobody has to ask who has it.
Nothing sits unseen
The assignee is notified straight away — in the app, and by email if they are away. Requests nobody takes trigger a reminder to the team.
AI-drafted itineraries
With an AI app enabled, each request can also get a draft itinerary built into its own enquiry — a head start for your team, never sent to the customer.
Slack, built in
Requests appear in a Slack channel with a one-click “I’ll take this one”, and your team can draft an itinerary with /tripcreator draft — all with the Slack add-on.
Why a request form beats a shared inbox
Faster first reply
Requests reach a named person immediately instead of waiting for someone to sweep an inbox once an hour.
Better enquiries
Structured answers — dates, party size, budget, tour — arrive with the request, so your first reply can be a proposal rather than a list of questions.
Every lead in your reporting
Because each request is a real enquiry with a lead source, you can see which pages and campaigns produce bookings.
A confirmation, on your brand
Visitors get an immediate, editable confirmation so they know it arrived — and your wording stays in your hands.
Request forms FAQ
- Can the form ask different questions for different tours?
- Yes. Questions can depend on earlier answers and on the tour page the form sits on, so a single form can serve every page and still ask tour-specific questions.
- Can the budget options change with the trip?
- Yes. Give a budget question conditional sets of choices — for example by tour type and number of travellers — and visitors only see the ranges that make sense for them.
- What happens when someone submits?
- A Draft enquiry is created on the pipeline board and stage you choose, the visitor becomes a CRM contact, and the assignee is notified. The visitor receives a confirmation email unless you turn it off.
- Can AI draft the itinerary from a request?
- Yes, if you have an AI app enabled in the App Store and switch it on for the form. The draft is built into the request’s own enquiry and stays a Draft for your team to review — nothing is sent to the customer, and anything the AI cannot match to your catalogue stays a placeholder.
- Who gets notified?
- The owner you set on the form is notified immediately, in the app and by email if they are not online. With no owner set, everyone who works the CRM is told and anyone can take the request. Requests nobody takes trigger a reminder.
- Do I need a developer to add the form to my site?
- No. Build the form in TripCreator, copy the embed snippet and paste it into your website. Add the tour name to the snippet and every enquiry is tagged with it.
- Can my team work requests in Slack?
- Yes. Add the Slack app from the App Store: new requests appear in a channel you choose with a button to take them, and with an AI app enabled you can draft an itinerary from a request or from a few sentences with /tripcreator draft. Requests are also available as webhook events for other tools.