A travel enquiry form has one job: give your team enough information to start a useful conversation. Ask too little and the first reply becomes a questionnaire. Request a complete passenger record before you've even discussed the holiday and you've made the customer do the admin too early.

We'd start with the decision your adviser needs to make next. That might be whether a trip is realistic within the budget, which specialist should respond or whether a short call would save everyone time. Each field should help that decision. Anything else needs a reason to stay.

Start with the trip, then the contact details

For a general holiday enquiry, useful starting information includes the destination or type of trip, approximate dates, departure preferences and party size. Give people a way to say they're flexible or still deciding. A customer who hasn't chosen a destination can still have a perfectly workable brief. Forcing them to invent an answer makes your information less reliable.

Budget needs a little explanation. Ask whether the amount is for the whole party or per person and say what you expect it to cover. A budget that includes flights and accommodation means something different from a hotel-only budget. If the customer isn't ready to specify an amount, a conversation may be more useful than blocking the form.

Contact fields should reflect the promised response. An email address is useful if you're going to send an initial reply, while a phone number becomes necessary when someone specifically asks for a call. Label optional fields clearly. Don't insist on every contact method simply because your software provides a box for it.

Make room for the constraint that changes the search

A small free-text box can explain more than another row of filters. Invite the traveller to tell you what matters most about the trip. They might need adjoining rooms, a late departure or somewhere suitable for a mixed-age group. Those details can change the shortlist before you spend time preparing it.

Here's a fictional enquiry to show the difference: two adults and two children, travelling during the school break, with a total budget of £4,800. The customer adds that one parent cannot leave work before Friday evening. That last sentence changes the flights you should consider. A form that records only a departure date has missed part of the brief.

Avoid collecting passport copies, payment details or detailed medical information in an ordinary initial enquiry form. The ICO's data minimisation guidance says personal information should be relevant and limited to its purpose. Where a customer needs to discuss particular support requirements, provide a suitable route for that conversation. Your privacy information should explain how you use what they submit.

Write the acknowledgement before you build the form

The message after submission is part of the service. Tell the customer that the enquiry arrived, what happens next and when they can reasonably expect a reply. Use a response window your team can meet during its working hours. A promised same-day quote is unhelpful when the adviser first needs to clarify the trip.

For a fictional enquiry, the acknowledgement could read: "Thanks for telling us about your holiday plans. An adviser will review your enquiry during our opening hours and contact you using your preferred method. If we need anything else before preparing options, we'll ask you first." Adapt the timing and wording to your actual process. Don't present an automated receipt as a personal review.

Give the adviser a reference and keep the customer's original wording available. Record which page or offer produced the enquiry where your setup supports it. Someone asking about a particular holiday shouldn't have to describe it again because the form discarded the page context. A useful brief survives the journey into the sales system.

Check the handover into quoting

TProfile CRM describes enquiry and booking histories alongside workflows and scheduled reminders. That is a useful example of the connection to look for: the enquiry remains part of the customer record. Ask a supplier to demonstrate the actual fields arriving from your form. A general integration claim doesn't show whether your budget note or preferred callback time will transfer.

Our Quick Quote page describes turning a website enquiry into a draft quote. The adviser still checks the content, adds or verifies prices and decides what to send. Treat the handover as the start of preparation. Missing dates and uncertain requirements still need a conversation.

Try a proposed handover test with a fictional enquiry that includes a flexible date and an unusual requirement. Follow it through receipt, assignment and the first draft response. Confirm who owns it if the usual adviser is away. This is a test to run in your own setup, not a claim that every form connects automatically.

Judge the form by the conversations it creates

Submission totals alone won't tell you whether the form is helping. Review a small sample of enquiries and record what your advisers had to ask again before they could act. Look for repeated confusion about budgets, dates or the kind of help being requested. Then change the field or explanation responsible.

Use our enquiry accessibility guide for the separate task of checking barriers in the journey. Open your current form on a phone and complete it as that fictional family. Stop wherever you need to guess what a label means. Give the resulting enquiry to a colleague without explaining the trip yourself. Their first question will tell you what to improve next.

Download the enquiry form brief