Simple request for one or two travelers
Leisure trips where the traveler accepts the agency's fare options and has no seat or class preference.
- Remove: Cabin
- Remove: Connections
- Remove: Traveler notes
A flight booking form collects what your agency needs to search fares: the route, the dates or flexibility, the number of travelers, and the cabin and timing preferences. It records a request, and it does not confirm a seat or issue a ticket. Keep passport numbers and card details out of the form, and have the traveler approve one itinerary before you ticket it.
Flight booking form: 20 average monthly searches.Google Ads Keyword Planner · 2026-10-09 · United States
Leisure trips where the traveler accepts the agency's fare options and has no seat or class preference.
One booking that covers several people, usually booked by a group leader on their behalf.
An employee whose fare search cannot start until a manager has approved the trip.
| Field | Type | Required | Why you ask it |
|---|---|---|---|
Traveler namesEnter one name per line, in the spelling on the travel document. | Long text | Required | Names go on the ticket, so the spelling has to match the traveler's document. Ask for the document number through your agency's own document process, not here. |
Number of travelers | Number | Required | Sets how many seats the search needs. A count that does not match the names list delays the search. |
Departure city or airportFor example: Austin or AUS | Short text | Required | Sets the origin. An airport code is precise; a city works when the traveler can use several airports. |
Destination city or airportFor example: Lisbon or LIS | Short text | Required | Sets the destination. For a multi-city trip, list each leg in the traveler notes. |
Departure date | Date | Required | The first day the fare search covers. |
Return dateLeave blank if you need a one-way flight. | Date | Optional | Leave this blank for a one-way request. A round trip with no return date needs a question back before any search starts. |
Date flexibilityExact dates onlyWithin two days either wayWithin a week either way | Single choice | Required | Tells the planner whether to search the exact dates or a window around them. |
Preferred time of dayEarly morningMorningAfternoonEveningNo preference | Single choice | Optional | Replaces a time field, since this form has no time-only input. Time windows are quicker to search than typed times. |
CabinEconomyPremium economyBusinessFirstNo preference | Single choice | Optional | Sets the cabin class to search. One class per request keeps the comparison simple. |
ConnectionsNonstop onlyOne connection is fineAny number of connections | Single choice | Optional | Tells the planner whether connections are acceptable before the search runs. |
Checked bags | Number | Optional | Baggage allowances differ by fare, so the planner needs the count before comparing options. |
Traveler notesDo not include medical details. Name the need, not the diagnosis. For example: a window seat, or two nights in Porto before Lisbon. | Long text | Optional | Captures seat or legroom requests and multi-city legs in the traveler's words. |
Contact email | Required | Where the agency sends the fare options and the questions it needs answered. | |
Contact phoneAdd the country code first, such as +1. | Phone | Optional | Used for a call only when a change needs to be discussed quickly. |
Estimate based on question types; actual completion time varies.
Tell us where you are going and when. We search fares and send you a short list of options. Nothing is ticketed until you approve one itinerary.
Thank you. We have your request for the route and dates you entered. Our team will reply with options at the reply window we gave you. Please do not send passport or card details by email or in this form.
Match the spelling on the travel document, one name per line.
Choose a window if your dates can move. The search then covers the days around your first choice.
For example: a window seat, extra legroom, or a stop in a second city.
Check the route, dates and window against the request, search fares, and send the traveler two or three options. Note which timing windows each option meets, so the traveler can compare like with like.
Ask the traveler to approve one itinerary in writing before you issue a ticket. Save that approval with the trip file so the record shows who chose what.
Each request is stored first, then an hourly production job processes it and notifies the form's creator. For a flight leaving within a few days, phone the traveler rather than wait for that notice.
Use the list above as the content of the template. Put names, route, dates and flexibility first, then cabin and connection preferences, because those choices drive the first search. Add a separate line for each leg of a multi-city trip.
Record the airline in the traveler notes, and ask whether a different carrier is acceptable. A named airline narrows the search, so treat it as a preference rather than a requirement.
Ask for the change in writing, and check the new spelling against the travel document before you issue a ticket. A name that does not match the travel document can stop a traveler at check-in.
Often, yes. If an employee needs approval before a fare search, collect that approval first with a travel authorization form, then send the approved trip details to this request. Add an approver field only when your approval process needs one.
Keep one request per itinerary. If travelers fly different routes, send a second request, so each itinerary gets its own fare search and its own approval.
Choose a category and a form type in the wizard. Answer three Atty Suggestions questions, then give the form a title. Atty builds the fields in the background. Edit the fields and ask Atty to refine them, then publish and share the /f/ link.