A charter inquiry flow that filters serious buyers before they reach your desk

A form is a conversation with no one on the other side. Ask too little and you get "how much to Ibiza?" with no dates, no passengers and a Gmail address. Ask too much and the buyer who would have paid closes the tab, because he is not going to type his passport number for a quote. The flow that works sits between the two, and it is designed backwards from the quote, not forwards from the form builder.

Start from what a quote needs

A charter quote needs a route, a date or a window, a passenger count, and a way to reach the buyer. It helps to know the cabin class he has in mind and whether the trip is one way. Everything else is either derived from those (the aircraft that fits, the FBOs) or belongs to the conversation (catering, ground transport, pets, the real reason for the trip).

So the flow asks for exactly that, in the order a person would say it on the phone: where from, where to, when, how many. Then one channel and the name. Five to seven inputs, on one screen on a phone, with sensible defaults and autofill. This is the structure we built for Elite Vanta: a three-step journey, aircraft, route, summary, that hands the site a structured inquiry the operator can price without a second email.

Qualify with the fields, not with a wall

Qualification is not a gate. It is a few well-chosen questions whose answers tell you, before you pick up the phone, how serious the request is.

• Dates with a flexibility switch. "Exact" versus "within a week" separates a trip that exists from a trip that is being imagined.
• Passengers, as a number. Not a dropdown of ranges. A buyer who knows it is four people knows the trip.
• Cabin or aircraft class, optional. Buyers who choose one have flown before. Buyers who skip it need a shorter call, not a longer form.
• Preferred contact channel and time. A buyer who picks "WhatsApp, after 6 pm" is telling you how he wants to be sold to.
• One free-text line, optional. For the thing the form did not ask. Not the whole brief.

A budget field, where it fits, is the strongest qualifier and the most delicate. Ask it as a band, make it optional, and explain in one line why it helps ("so we quote the right cabin, not the biggest one"). Buyers who state a budget are usually the ones who intend to spend it.

What to leave for the call

Anything that identifies a passenger stays off the first form: names of travelers, dates of birth, documents. Anything that requires a decision the buyer has not made yet (catering, exact FBO, ground transport) also stays off. Asking it early does not make the operator look thorough. It makes the buyer feel processed, and it adds fields that the serious buyer, who is often not the traveler, cannot answer.

The call is where the trip becomes real. The form's job was to make sure the person on the call already has the four facts that a quote needs, and a sense of how serious the request is.

What happens in the first minute after sending

This is where most flows fail quietly. The buyer sends the request and sees a generic "thank you". He does not know who has it or when to expect a quote, so he sends the same request to two other operators while he waits. The fix costs nothing: a confirmation that names a person and a time ("Anna has your request; you will have a quote by 18:00"), on the page and in the inbox, and an internal message that lands with that person, tagged with the route, the dates and where the visit came from.

That tag is the second half of a sales system. Knowing that the last three serious requests came from one campaign and none from another changes what you spend next month. We wire the source of every inquiry through to the operator's inbox and, where the operator wants it, to a simple panel that shows which pages and sources produce buyers.

Handling client details like an operator

At this level, visible care with data is part of the product. The buyer is often sending someone else's trip. The form should say, in one line, where the request goes and who reads it; use a real privacy policy, not a template; send confirmations from a named address; and not run third-party trackers on the request page without consent. None of this is a legal exercise. It is the reason a family office sends the second request to you and not to the platform.

A checklist to compare your form against

1. Route, date or window, passengers, contact channel: all on one screen on a phone.
2. Flexibility, cabin class and budget band as optional qualifiers, each with one line of why.
3. No traveler identities, no documents, no decisions the buyer has not made yet.
4. A confirmation that names a person and a time, on the page and by email.
5. The internal message carries the trip facts and the source of the visit.
6. The page loads and works on a weak connection, with autofill and without a cookie wall over the button.
7. One plain sentence about who reads the request and how the details are handled.

If your current form fails three or more of these, the fix is usually a week of work, not a rebuild. We can tell you which three in a 15-minute call.