On this page
Build the transfer workflow as three distinct stages: collect a complete inquiry, send a quote, then record customer confirmation before dispatch. Store the pickup’s local date, local time, and time zone explicitly; a driver should receive an assigned trip only after the required fields are complete and the customer has accepted the quote.
This design responds to a recent operator question about capturing pickup and destination, travel date, passenger count, and contact details, then routing valid requests to a spreadsheet or CRM. The author was unsure how to handle missing fields before passing data downstream. The original question shows a request for that validation step.
Download the sample CSV · Download the form field specification
Capture the fields dispatch needs
Start with six tables:
trip_requests: customer ID, status, creation time, and update time.pickup_details: pickup address, destination, local pickup date, local pickup time, time-zone identifier, and airport terminal when relevant.passengers: passenger count, luggage count, contact name, email, and phone.quotes: immutable quote version, request ID, pickup-details snapshot, amount, currency, expiry, and staff owner.quote_acceptances: customer ID, accepted quote ID and version, and timestamp.assignments: confirmed quote ID, driver ID, vehicle label, assignment time, and assignment status.
Keep quote and trip confirmation separate. A quote is the operator’s proposed price and conditions; it is not a confirmed trip. A customer confirmation records acceptance of a specific quote version. If the operator changes the price or pickup details, issue a new quote and ask the customer to accept that version before dispatch.
Mark required fields by route type. For every request, require pickup, destination, local date, local time, passenger count, and a contact method before generating a quote. For an airport pickup, require a terminal if it affects meeting instructions. Ask for a flight number only if the operator uses it; keep it as customer-provided reference text unless a flight-status integration is deliberately scoped and verified. Do not make the workflow depend on an assumed flight API.
When a field is missing, save the inquiry as needs_information, list the missing fields, and send the customer a direct follow-up form. Do not export it as dispatch-ready or notify a driver. Once all required details are present, move it to ready_to_quote for an operator to review.
Preserve the pickup’s local time
A pickup at 12:30 a.m. can fall on the day after a late-night booking was made. Store the date, time, and IANA time-zone name as separate values, such as 2026-11-08, 00:30, and America/New_York. Display all three in dispatch views. Do not derive the trip date from the browser’s current time zone or shift it silently during daylight-saving changes. Validate the local time against that zone: if the clock time occurs twice or does not occur during a daylight-saving transition, request an explicit offset or corrected time before quoting. Save the resolved UTC instant alongside the original local values.
Synthetic overnight row: a customer requests pickup at 11:50 p.m. on November 7, 2026, in America/New_York, from an airport terminal to a city address. A second trip at 12:30 a.m. on November 8 is a different local calendar date and should remain so in the form and dispatch list. These dates and trips are examples, not actual bookings.
Move from inquiry to dispatch

AI-generated editorial concept; not a screenshot of a deployed app.
Use a small, explicit state model:
| Current status | Allowed next status | Who can change it |
|---|---|---|
needs_information |
ready_to_quote |
Customer completes fields; staff validates |
ready_to_quote |
quoted |
Dispatch staff |
quoted |
customer_confirmed, declined, expired |
Customer or system on expiry |
customer_confirmed |
assigned |
Dispatch staff |
assigned |
completed, cancelled |
Dispatch staff; assigned driver reports completion |
Validate the transition on the server, and record who acted, which quote version was accepted, and when. A system should never assign a driver directly from needs_information, ready_to_quote, or quoted.
Customers can create a request, add missing information, and read their own trip. Dispatch staff can manage the operator’s requests, quotes, and assignments. A driver should read only the trips assigned to that driver, with only the contact and pickup details needed to perform the trip. Keep internal quote notes, other customers’ details, and unassigned trips out of driver views. If using Supabase, configure and check row-level policies for each table and operation; connecting a backend alone does not implement those rules. Atoms’ Supabase guide
After a request changes state, send the relevant event to the team’s notification or spreadsheet workflow. Connector actions and permissions depend on the connector and account, so verify the exact available write action before designing around it. Atoms’ integrations guide
Optional deposit after confirmation
Collecting an inquiry does not require payment. If the operator needs a deposit, offer payment after the customer confirms a quote. Keep the charge tied to the confirmed request and process the payment result on the server. With Stripe Checkout, a success-page redirect alone cannot guarantee fulfillment; Stripe’s guide calls for server-side webhook fulfillment that safely handles the same Checkout Session more than once. Store a unique session key and processed state before changing the trip’s payment status. Stripe’s Checkout fulfillment guide
Form template and acceptance checks
The accompanying form-template.json lists the customer fields, conditional airport fields, quote acceptance, and confirmation message. The sample.csv contains synthetic requests: one missing an airport terminal, one complete request awaiting a quote, and one overnight pickup. Use these to check:
- An airport inquiry missing its required terminal enters
needs_information; no quote or driver assignment is created. - Completing required fields moves the request to operator review, but does not imply the customer has accepted a price.
- Accepting a quote records the exact quote version; only then can dispatch assign a driver.
- The November 7 late-night pickup and November 8 after-midnight pickup retain their respective local dates and
America/New_Yorkzone after refresh. - Customer A cannot open customer B’s request. An unassigned driver cannot read or claim the trip; an assigned driver sees only that trip.
- If deposits are enabled, submitting the same successful payment event twice results in one payment-state change.
The Atoms Supabase guide recommends using harmless sample data, refreshing the app, and checking the matching saved row as part of verifying persistence. Atoms’ save-data verification steps
Build prompt
Use this prompt to create the first version in Atoms:
Copy the build brief and use it to create your version in Atoms.
The workflow can start with manual dispatch and customer-entered flight references. Add an external API only when its provider, permissions, failure handling, and actual behavior have been verified for the operator’s account.