An Airtable vehicle service intake form can collect a driver’s description, vehicle details and requested work in one place before a service advisor reviews the request. Use miniExtensions for the submission form and Airtable for staff triage, with separate fields for what the driver reported and what the workshop later verified.

Fictional Riverbend Vehicle Service receives requests from local businesses with small fleets. A driver reports that van RB-018 makes a rattling noise when starting. The advisor needs enough context to arrange the next conversation, not a form that silently turns a symptom into a diagnosis or a repair order.

Separate the request from the vehicle record

Use a Service requests table with Request reference as an autonumber, Submitted at as created time, Contact name as text, Contact email as email, Contact phone as phone, Reported vehicle reference as text, Make and model as text, Model year as number, Reported symptoms as long text, Requested work as long text, Preferred contact method as single select and Photos as attachment.

Add staff-maintained fields: Verified vehicle as a link to Vehicles, Assigned advisor as text, Review state as single select, Clarification needed as long text, Estimate reference as text and Estimate review state as single select. Suggested review states are New, Needs information, Under review, Referred and Intake complete. These are custom workflow choices, not built-in miniExtensions service statuses.

In Vehicles, keep Vehicle reference as primary text, Make and model as text, Model year as number and Fleet organization as text. Staff matches a new request to this existing catalog after checking its identity. Avoid exposing a global vehicle picker on a public intake form, where similar names can lead to incorrect selections and unnecessary disclosure of other customers’ vehicles.

Ask for observations a service advisor can use

For RB-018, a useful submission is “Rattle for a few seconds during the first start of the day; noticed twice this week.” It is more useful than “Engine broken,” because it distinguishes an observed symptom from an assumed cause. Ask when the issue occurs, when it was first noticed and whether the reporter has already contacted the workshop.

Keep Requested work separate. A driver might request a scheduled inspection while also reporting a new noise. Staff should not have to infer the requested service from a photo or a free-text account. If mileage matters to your process, add Reported mileage as number and Mileage unit as single select; label it as reported rather than verified.

Use ordinary contact details and the minimum vehicle information needed for review. Do not request identity-document scans, payment-card details or unrelated driver information. Tell reporters not to take photos or interact with the form while driving. This example is an intake workflow, not emergency assistance or guidance on whether a vehicle is safe to operate.

Configure a focused submission form

Create a miniExtensions Form connected to Service requests. Show the contact, reported vehicle, symptoms, requested work and optional photos. Leave staff decisions and the verified catalog relationship out of the customer-facing inputs.

For this standalone intake, enable Allow users to create new records and disable Allow users to update existing records in Share. The record-creation guide distinguishes those main-form controls from linked child-form settings. Review the resulting shared experience before inviting customers.

If only photos are appropriate, open the attachment field under Form Fields, then Upload settings, and select Images under Restrict Attachment Types To. The attachment-type documentation explains that this restriction applies to new uploads, not files already stored in Airtable.

Make the staff handoff explicit

An advisor reviews the New queue, confirms the vehicle reference and checks for an existing request about the same symptom. If RB-018 is ambiguous, leave Verified vehicle empty and ask for clarification. Do not attach the request to the nearest-looking vehicle merely to clear the queue.

Record the advisor’s clarification separately from the original symptom. For example, the driver may later explain that the noise happens only with the cabin fan running. Preserve that chronology instead of replacing the original report with a presumed diagnosis. A small Review notes table can hold Request as a link, Recorded on as date/time, Author as text, Note as long text and Source as single select.

When an estimate exists, store its reference and review state. An estimate being prepared, sent or discussed is not repair authorization. Use your established approval process separately and reference its actual outcome. A submitted intake also does not reserve a service appointment; staff must agree and communicate any appointment through the workshop’s normal process.

Handle repeat reports and changed scope

If another driver submits the same van and symptom, mark the relationship in staff notes and link both requests to the verified vehicle. Retain each reporter’s account, because the circumstances may differ. If the customer adds a separate issue, distinguish it from the original request so an estimate for one problem does not appear to cover everything.

After performed work, use a separate service history rather than turning the intake description into a completion log. The related equipment-fault reporting workflow also separates reported observations from later assessment. Vehicle intake adds the advisor, vehicle identity and estimate-review handoff; it is not a replacement for specialist workshop management or regulated repair records.

Check the complete intake journey

Before launch, submit fictional requests for two similar vehicle references, a repeat symptom and an unknown vehicle. Check the saved fields, attachment behavior and customer-visible form. Confirm that staff can leave a request unverified and that a review status cannot be mistaken for an appointment, safety decision or authorization.

These are recommended checks, not reported test results. The useful outcome is a readable queue of reported needs with a named advisor and a clear next step, while diagnosis, estimates and repair decisions remain with the appropriate people and systems.