Your Recruiting Pipeline Has a Memory

A recruiter makes forty calls a day. Most go to voicemail. A few land. The ones that land matter — the driver mentioned they want sixty-five cents a mile, they're finishing a SAP program in two weeks, they need weekends home. That's the intel that decides whether this lead becomes a driver or a ghost.

In most shops, that intel lives in the recruiter's head until they scribble it on a sticky note, type it into a spreadsheet, or forget it entirely. Then somebody asks "did we ever call that guy back?" and nobody knows, because the answer is in a text thread on someone's personal phone.

Leads don't die of rejection. They die of neglect.

So we built a pipeline where every call leaves a paper trail — automatically, privately, and in a format that feeds every downstream decision.

The Call Happens. The System Listens.

When a recruiter clicks Call on a lead, the call goes out through the office phone system and the system logs it against that lead — incoming or outgoing, with timestamp and duration. No manual entry. Texts and emails are logged the same way.

If the call was recorded, the recording goes through a private transcription pipeline — speech-to-text running on your own hardware, never leaving your server. The raw transcript is then distilled by a local language model into structured intel:

• Driving experience — years, CDL class, endorsements, employment history
• Pay expectations — CPM, percentage, target income
• Home time — how often, how long, any hard constraints
• Concerns — SAP, employment gaps, medical, criminal history
• Suggested follow-up — the concrete next step and when

Then both the audio and the raw transcript are deleted. No recording is stored. No raw transcript touches the database. The only durable record is the structured summary — the intel without the liability.

One Lead, One Timeline

Every interaction with a lead — calls, texts, emails, notes, and call summaries — lands on the same activity timeline, in chronological order. Open a lead and the full history is right there: when they were first contacted, what was said, what was promised, and what happened next.

The call summary sits in the timeline with its own icon and expands to show the structured bullets. The same intel also appears in the Notes section with the full detail. A recruiter picking up someone else's lead doesn't need a handoff meeting — the timeline is the handoff.

Tomorrow's Briefing Writes Itself

This is where the pieces connect. Every morning, the recruiter's Workflows briefing opens with what needs attention — and the call summaries feed directly into it.

Follow-ups from calls. If the last call with a lead ended with "send the application link Thursday" and Thursday came and went with no outreach, it's in the briefing. The follow-up action was extracted by the language model, and the system checked whether anyone actually did it. Rows clear themselves the moment the follow-up contact happens.

Forgotten leads. Two flavors — leads that were never contacted at all, and leads that went quiet past your stale threshold. The "last contact" clock counts actual outreach: a call, a text, a logged conversation. It does not reset when a document gets uploaded. A lead who sent in their MVR but hasn't heard a voice in two weeks is still forgotten.

The rest of the list: promised callbacks, missing documents, third-party results still pending, applicants ready to onboard, orientations this week, and leads that look misfiled. Recruiters see their own pipeline. Managers see everybody's.

Status Moves on Real Conversations

Lead statuses can advance automatically based on actual call activity — not button clicks, but calls that happened and lasted long enough to matter. You set the rules: advance to Second Contact only on calls lasting sixty seconds or more. Advance to Recruiting only after a completed application.

The pipeline reflects real outreach. A lead sitting at "1st Contact" for two weeks isn't a data-entry failure — it's a lead that genuinely hasn't progressed, and the briefing treats it that way.

One-Click MVR and PSP

When the lead is ready for the compliance check, the MVR and PSP reports are ordered from the lead's compliance tab — one click each. The MVR comes back summarized with a risk level and a violation count. The PSP report sits alongside it. The Clearinghouse pre-employment query is there too. Together, they're the file a DOT auditor asks for, built as you go.

MVR reports start at $4 per report, varying by state, with no subscription fee — full pricing by state is here. Order what you need, when you need it.

What We Won't Say

The transcription pipeline runs on commodity hardware and a four-billion-parameter model. It is not infallible. Truck-cab audio is noisy, accents vary, and a model trained on clean speech will sometimes mishear "Peterbilt" as "Peter built." The extraction layer corrects some of that from context, but not all of it.

What it does reliably is turn a twenty-minute phone call into a structured summary that's good enough to act on — and far better than what was there before, which was nothing.

The briefing surfaces what needs attention. It doesn't make the call. Somebody still has to pick up the phone, and somebody still has to mean it when they say "we'll send the paperwork tomorrow." The system just makes sure that promise doesn't evaporate.

There's a short walkthrough if you want to see it move.