Describe your routes, pickup points, schedules, and passenger policies. Makeform creates a shuttle service reservation form that collects the trip details dispatch needs.
Route reservations to email, Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a complete prompt, adjust its route details, or send it to the Makeform builder.
Audience
Travelers reserving airport transfers
Format
Route booking with flight details
Prompt size
281 chars
Example form structure
Route booking with flight details
Lead passenger and contact details
Airport, terminal, airline, and flight
Travel date and pickup time
How many riders and bags?
Accessibility or child-seat needs
Suggested routing tags
New reservations
Accessibility review
Dispatch changes
Ask for both the pickup location and requested pickup window. A time without a location does not give dispatch enough information to plan a stop.
Step 1
Choose
route, date, stop, and departure
Step 2
Reserve
riders, seats, luggage, and trip details
Step 3
Review
dispatch checks capacity and special needs
Step 4
Confirm
rider receives the final trip instructions
Why use a reservation form
A structured form prevents calls and emails from omitting flight numbers, passenger counts, or pickup details.
Use route, stop, and departure dropdowns so dispatch can group consistent submissions.
Collect rider, luggage, mobility-device, and equipment counts before assigning a vehicle.
Keep contacts and trip choices together, then notify staff for review.
Useful for every shuttle model
Choose a scheduled-route or private-transfer starting point, then add your stops, times, and policies.
Capture flight, terminal, luggage, address, and timing.
Offer destinations and departures tied to guest details.
Organize riders by route, stop, shift, and return choice.
Gather headcount, stops, itinerary, equipment, and billing contact.
Reservation workflow
Generate, publish, and review each request before confirming the ride.
List your service area, stops, departures, passenger policies, and required dispatch details.
Replace sample routes and reveal flight, return, or accessibility fields when relevant.
Share a public link or embed the form on your website.
Send requests to staff, flag special needs, and issue confirmed pickup instructions.
Form vs calls and generic booking pages
Compare how each method delivers information to dispatch.
Field guide
Use these six field groups to give dispatch a complete request.
Rider contact
Collect a lead rider or organizer, a phone number for pickup changes, and email for instructions.
Route and stops
Use fixed choices for known stops. For private pickups, request full addresses and meeting-point notes.
Date and time
Collect the service date and departure or pickup window. Mark times as requested when staff must verify availability.
Passengers and capacity
Ask for the passenger breakdown, child seats, and equipment counts dispatch uses.
Trip-specific details
Use conditional logic to reveal flight, return-trip, and access questions only when needed.
Policies and handoff
Explain whether submission confirms a seat or starts a review, then show relevant trip policies.
Related tools
Use these live Makeform tools for nearby reservation, transport, travel, and pickup workflows.
Collect arrival details, terminal, pickup location, and traveler contact information.
Open toolCreate a broader intake form for transport services, riders, routes, and scheduling needs.
Open toolGather itinerary and traveler information for complete trip booking requests.
Open toolBuild a flexible reservation flow for services that need dates, times, and customer details.
Open toolOrganize airport departure rides with addresses, flight timing, and passenger counts.
Open toolCollect group size, organizer details, schedules, and special requests in one submission.
Open toolFAQ
Practical answers for shuttle operators replacing calls and scattered booking messages.
It is an online form riders use to request or reserve shuttle travel. It typically collects contact details, service date, route or addresses, pickup time, passenger and luggage counts, and any trip-specific requirements. The operator receives a consistent record for dispatch review.
Include lead rider name, phone, email, trip date, pickup and drop-off details, requested time or scheduled departure, seat count, luggage, one-way or round-trip selection, and accessibility notes. Add flight, hotel, employee, or event fields only when they support your service.
Yes. Add dropdown or multiple-choice fields for each active route, stop, and departure. Keep the options aligned with the schedule you operate. If capacity changes outside the form, explain that submission is a request and send confirmation after staff review.
Yes. Use conditional fields for arrival versus departure, airport and terminal, airline, flight number, pickup address, destination, luggage, and requested pickup time. These details stay attached to the rider's contact information in the same submission.
Ask whether the ride is one way or round trip. When round trip is selected, reveal return date, pickup point, destination, and departure time fields. This avoids showing unnecessary questions to one-way riders while keeping both legs in one record.
Yes. Include clear choices for mobility devices, boarding assistance, communication preferences, and child seats, followed by an optional details field. Route those submissions for staff review so the operator can discuss what is available and confirm arrangements with the rider.
No. You can present it as a reservation request and state that the ride is confirmed only after the operator reviews capacity, route coverage, and timing. Use the confirmation message to explain when and how the rider should expect a response.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. The paid tier removes the Makeform badge. You can start with a sample prompt, replace the example schedule with your routes, and publish when the form matches your operation.
Give every rider one clear place to reserve.
