Intake form · For body shops

The form that routes before it submits.

Drivable goes to the drop-off scheduler. Non-drivable goes to dispatch. OEM aluminum and EV flag themselves on year-make-model lookup. Every submission carries a third-party certified consent artifact your defense counsel can show in court.

Live sample

What the Carrera Auto Body intake looks like mid-flow.

Step two of a four-step flow. The year-make-model has resolved to a 2024 Tesla Model Y and the OEM / EV flag has fired. The form has already decided the submission routes to the EV estimator.

Illustrative mockup · fictional shop · four steps, two routes

What you'd get

Everything in the intake-form module.

  • Four-step mobile flow: scene, vehicle, insurer, drop-off
  • Year-make-model lookup with OEM and EV auto-flagging
  • Drivable fork: drop-off scheduler for drivable, tow dispatch route for non-drivable
  • Insurer field with DRP-match detection against your relationships
  • Optional photo upload (4 slots, in-browser compression, EXIF stripped)
  • Third-party certified consent artifact with timestamp, IP, user agent, form fingerprint
  • Email + SMS + CSV output; CCC ONE / Mitchell / Audatex push available
  • Embeddable on a Collision Bureau shop build, your existing site, or a landing page
Why body shops need this

The intake decides the first 90 minutes.

  • Non-drivable misrouted costs a day of cycle time

    A tow request that lands in the estimator's generic inbox adds hours of lag before the dispatcher sees it. Hours become days when the submission arrives Friday after 4. The fork at step one puts the right record in the right queue the moment it is submitted.

  • OEM and EV flagging prevents the wrong estimator writing the file

    An aluminum F-150 or a Model Y written by the wrong estimator means a supplement cycle and a parts delay. The flag at step two routes the file to the certified writer before anyone touches it.

  • The consent artifact is the only thing that survives a TCPA letter

    Shops that text owners from a form submission need a defensible consent record. Timestamp alone is not it. The artifact captures IP, user agent, form fingerprint, and the exact disclosure text, retained for the statutory window plus three years.

Related reading: Collision Bureau on how estimate leads are delivered to shops, and the guide to who legally picks the shop after a crash.

FAQ

What shops ask before installing the module.

Is the consent artifact TCPA-defensible?

Yes. Each submission generates a third-party certified consent record with timestamp, IP, user agent, form fingerprint, and the exact disclosure text shown. Retained for the statutory window plus three years, available on demand.

Can the form route non-drivable intake differently?

Yes. Drivable submissions go to the drop-off scheduler. Non-drivable submissions capture the vehicle location, flag whether a tow is needed, and route to the dispatcher queue.

Does it ask for insurer information?

Yes, with a soft requirement. The owner can skip and the form still submits. When provided, the insurer field triggers the DRP-match block so the shop knows if the owner's carrier is one you work with.

How are OEM and EV flagged?

The vehicle year/make/model lookup auto-flags OEM aluminum (F-150, Rivian, Tesla, Lincoln) and EV high-voltage (Mach-E, Ioniq, Lightning, Rivian). The flag drives routing and reporting.

Does it send photos?

Optional photo upload with four slots (front, rear, driver side, damage close-up). Compressed in-browser, EXIF stripped, delivered to the estimator with the submission.

Where does the submission go?

Email to the estimator, SMS to the shop line, CSV to the queue, and optional push to CCC ONE / Mitchell / Audatex via the integration add-on.

Start it

Install it in a week.

$295/month, embeds on any site. Bundled into every Collision Bureau subscription tier.