4. Recruit Applicants
Good drivers may apply to several jobs and receive multiple calls and texts quickly. The carrier must respond before another recruiter establishes the relationship first.
When no direct API is available, the recruiter can download the resume from Indeed or another source and upload it into DQ Vault. AI-assisted parsing extracts the information the resume supports and prepares a working application for review — the information is not treated as complete or verified merely because it was parsed. The email identifies the job, provides private access to the prepared application, explains that the driver should review and correct the information, and states that a recruiter will follow up shortly.
The recruiter uses a prepared message that opens through the recruiter's own phone number. The message introduces the recruiter, identifies the job, asks whether the driver is available, and tells the driver what number or area code will be calling. The outbound message is recorded in DQ Vault when supported by the current workflow. Replies return to the recruiter's phone unless inbound capture has been separately implemented. The recruiter then calls promptly, explains the job, answers questions, identifies possible mismatches, and helps the driver decide whether the opportunity deserves the next step. Speed matters, but coordinated and accurate communication matters more than an automated blast.
The recruiter can use pay explanations, home-time information, equipment details, carrier-specific templates, visual job graphics, family-oriented cartoons, and team-driver compatibility materials where appropriate. An OTR job may be a family decision, and the driver may need a clear way to explain the schedule and tradeoffs at home. Notes, status, communications, and follow-up should remain attached to the applicant record — the recruiter should not have to reconstruct the relationship from Post-it notes, a personal inbox, and memory.