Intake form · For tow operators

The scene intake your dispatcher does not have to retype.

A tow intake has one job: deliver a dispatcher-ready record before the caller forgets the policy number. GPS pin, equipment class, insurer, lien-holder, caller phone, Twilio SMS consent. Eleven fields, three sections, one submit.

GPS pin drop Equipment-class radio Twilio SMS consent Towbook / TOPS / Beacon
Live sample

What a Metro Dispatch intake looks like.

Fictional operator. The form opens with the scene location and a GPS button. The vehicle-state radio collapses into one of three states. The equipment-class row is five chips, one tap. Insurer, policy, lien-holder, and caller phone fit in two rows. SMS consent is the only required checkbox, so the submit button lights up when it is checked.

Illustrative mockup · non-submitting · your form uses your yard, your rates, your statutes

What you'd get

Everything in the scene-intake module.

  • GPS pin drop with reverse-geocode and typed-address fallback (Google Places autocomplete)
  • Three-state vehicle radio: drivable, not drivable, rollover; routing rules per state
  • Equipment-class chip row: light-duty roll-on, flatbed, rollover, heavy-duty, catastrophic
  • Insurer autocomplete against the top 40 US carriers plus a free-text fallback
  • Policy number optional at submit; prompted via SMS 15 minutes later for the lien-letter workflow
  • Lien-holder free-text, writes directly to the storage-billing header
  • Caller phone capture with Twilio SMS driver-arrival consent (TCPA-compliant checkbox)
  • State non-consensual tow statute citation on the authorization line (editable per state)
  • Posts into Towbook, TOPS, or Beacon (one included; second platform is an add-on)
  • Confirmation screen with truck ETA plus a tracking link SMS
Why tow operators need this

Dispatchers spend 7 minutes retyping what the caller already said.

Most tow intake forms are a 1998 PHP shop's idea of a contact form: name, phone, "message." The dispatcher re-interviews the caller to fill in the eleven fields that actually matter. That is seven minutes per call, every call, every night.

  • GPS pin cuts six minutes off a shoulder call

    Asking "what mile marker are you at" fails about 40% of the time. The caller is on a dark shoulder, scared, and does not know. The GPS button drops a pin inside 12 feet of the actual position. Dispatch pastes the coordinates into Towbook and the driver has turn-by-turn. On a 2:00am I-70 call that is the difference between a 22-minute response and a 40-minute response.

  • Equipment class routing is the whole point of the form

    A heavy-duty call cannot go to the on-call light-duty driver. Most intake forms have one email that goes to one phone, and the dispatcher triages by hand. The build routes the submit by equipment class: light-duty and flatbed to the driver queue, rollover and up to a rotator-dispatcher alert with a 60-second escalation. If no one acknowledges in a minute, the rotator-dispatcher gets a second alert plus a backup. Scenes stop sitting.

  • Lien-letter prep starts at the form, not at the yard

    By the time the truck is back in the yard, the caller is asleep and the lien-holder closed at 5pm. The intake writes directly to the storage-billing header: insurer, policy, lien-holder, caller phone. The Dispatch Ready tier on the Collision Bureau tow lane assumes this is already there. If it is not, you are doing intake twice.

FAQ

What dispatchers ask before signing the build.

  • How does the GPS pin field work?

    The phone browser asks for geolocation permission on form open. If the caller approves, scene coordinates drop into the location field with a reverse-geocoded street. If not, the field falls back to a typed address with Google Places autocomplete.

  • Can the form route by equipment class?

    Yes. The equipment-class radio drives routing. Light-duty roll-on and flatbed go to the on-call driver queue. Rollover, heavy-duty wrecker, and catastrophic trigger a rotator-dispatcher alert on the on-call phone with a 60-second escalation if unanswered.

  • Does the form capture insurer, policy, and lien-holder?

    Yes. Insurer name uses an autocompleted list of the top 40 US carriers. Policy number is optional at form submit but prompted again by SMS 15 minutes later for the lien-letter workflow. Lien-holder is a free-text field that writes directly to the storage-billing header.

  • Is the Twilio SMS consent GDPR and TCPA compliant?

    TCPA yes: the consent checkbox names Collision Bureau and the operator by legal name, scopes the messages to driver-arrival notices, and timestamps the IP. GDPR is not applicable to US-only operators; EU operators get an EU-hosted Twilio messaging profile and a Legitimate Interest notice.

  • Does it post into Towbook, TOPS, or Beacon?

    Yes. One integration is included: Towbook via webhook, TOPS via REST, or Beacon via CSV sync every 60 seconds. A second platform is an a la carte add-on.

  • Can it capture multiple callers on one scene?

    The scene gets one record. If a second caller submits for the same scene (within a 500 ft radius in a 20 minute window) the record is merged and a dispatcher gets a dedupe alert. The original caller's SMS consent is preserved.

  • What happens on form submit?

    The caller sees a confirmation with the truck ETA. The dispatcher gets a push to the on-call app plus a line in Towbook. A Twilio SMS fires to the caller with a tracking link. If the caller is still at the scene, a second SMS fires 10 minutes before truck arrival.

Start it

Wire it a la carte or bundle it with a plan.

$295 per month, included free with the website build. Bundled with Live Transfer or Dispatch Ready on the tow operator lane, the intake ships inside the subscription.