The Lead Capture Playbook
From email blast to booked appointment: how a verified-DOT landing page turns campaign clicks into managed, auto-populated leads — the theory, the design, and the operating playbook.
Interview contributor: Ronnie O'Dell, DOT Intel founder.
This guide was developed from interviews with Ronnie and drafted with AI assistance. DOT Intel, a Seven16 Group product, published it. The available record does not identify who finalized the original text or a separate fact-checker or editorial reviewer.
Published . Materially revised .
The dated product examples remain historical; check current product pages before relying on a workflow.
What happens after a campaign click?
A campaign landing page can ask for a USDOT number, show public carrier details for confirmation, and collect the contact details a prospect chooses to provide. A producer should verify the carrier and the person before using that intake in a submission. This paper describes the earlier workflow design, not a promise that every option is available on the current plan.
Design principle 1 — one field does the work
The prospect types their DOT number and the page answers with their own company: legal name, city, state, power units — public FMCSA facts, verified live. That single interaction does three jobs at once: it proves the page is legitimate, it saves the prospect from typing what the platform already knows, and it hands the agent a pre-verified account instead of a typo-ridden form entry.
Design principle 2 — structured intake matches the shop
Every field on the form exists because a producer needs it to quote: contact name and one reachable channel, the coverage lines wanted, and proposed call windows. The coverage checklist mirrors the real trucking insurance stack, so the lead arrives speaking the producer's language.
| Intake field | Why it's on the form |
|---|---|
| USDOT number (verified) | Anchors the lead to a real carrier; unlocks auto-population and the full workspace later |
| Contact name + phone/email | One reachable human; either channel accepted to keep friction low |
| Coverage checkboxes | Commercial Auto/Trucking Liability · Motor Truck Cargo · Physical Damage · General Liability · Workers' Comp/Occ-Acc · Trailer Interchange · Hired & Non-Owned · Umbrella — the quote request is pre-scoped |
| 2–3 proposed call windows | Appointment capture without calendar friction; the agent confirms one |
| Direct booking (optional) | Agents with a Calendly/Google booking page get one-click scheduling — and that calendar is viewable inside DOT Intel, not in a second tab |
Design principle 3 — the lead lands managed, not raw
A submission is not an email notification; it is a complete CRM object graph created in one transaction: the company (deduplicated by DOT), the contact, a high-priority opportunity carrying the coverage request and proposed times, an urgent "confirm appointment" task due tomorrow, and a feed event that rides the same daily-signals pipeline as everything else in Command.
From the lead, open the carrier record to review authority, fleet, insurance filings, and safety context. Access and usage follow the agency’s current plan and allowance. Use that research to prepare the conversation, then confirm the account’s current insurance needs with the prospect.
What safeguards did the earlier design specify?
The July 2026 design called for the controls below. This revision did not verify each control in the current application; confirm present behavior before using this table as an operating checklist.
| Concern | Design answer |
|---|---|
| Bots and abuse | Hidden honeypot field + a hard per-link rate limit (20 submissions/hour) enforced in the database |
| Data exposure | The public page can only read census-public facts for an exact DOT — never insurer, contact, or scoring data |
| Attribution | Every link is personal to a producer and labeled per campaign; hits and leads are counted per link |
| Prospect consent | The page states plainly who will contact them and that carrier facts shown are public FMCSA data |
| Excluded carriers | Do-not-resell carriers are honored at the verification layer |
The operating playbook
| Step | Action | Where |
|---|---|---|
| 1 | Create a capture link per campaign (“July renewal blast”) and add your booking link if you use one | Command → Lead Capture |
| 2 | Paste the link into the blast | seven16email.com |
| 3 | Watch hits vs. leads per campaign — that ratio is your subject-line and audience feedback | Command → Lead Capture |
| 4 | Work each lead: confirm a proposed time (or let them book direct), pull the DOT file, quote | Captured Leads |
| 5 | Won → pipeline. Lost-for-now → close as X-Date and let recycling bring it back before renewal | Opportunities |
Why this compounds
Each blast feeds the same system that runs the rest of the agency: captured carriers can be watched (daily change alerts), checked against Placement Fit before shopping, scored for submission readiness, and recycled at their next renewal if they don't close now. The funnel isn't a separate tool — it's a new front door into the machine.
Sources and limits
- FMCSA SAFER Company Snapshot — Shows the public carrier fields that a USDOT lookup can return; it does not verify the person submitting a form.
- FMCSA Licensing & Insurance carrier search — Provides separate public authority and filing records for producer review; a form response is not an insurance determination.
DOT Intel product counts and historical observations in this paper are internal figures. The linked public records explain the source fields; they do not verify DOT Intel's historical totals or predict a carrier's insurance needs.