Driver Identity & Validation
Last updated: September 12, 2026
BETA — This feature is still in active development. It's available to customers who want early access, and behavior may change as we refine it. Interested? Email [email protected].
Conduit can confirm three separate things about a driver who arrives at your facility: that the phone number they gave is one they control, that they are who their ID says they are, and that they are the driver the carrier said would show up. Each one is turned on independently, and each shows up in a different place — the check-in steps the driver sees, the appointment, and the driver's profile.
Conduit also keeps a profile for every driver who checks in, so the next visit starts from what you already know about them.
Verifying a Driver's Phone Number
When phone verification is on, the driver cannot finish check-in until they enter a PIN that Conduit texts to the number they typed in. This proves they are holding that phone right now.

What the driver sees:
They enter their name and phone number at the start of check-in.
Conduit texts them a 6-digit PIN.
They type the PIN into the next screen and continue.
The PIN is good for 10 minutes and allows 3 attempts. If the driver runs out of either, they can request a new one. After the PIN is accepted, they have 30 minutes to finish check-in before they need to verify again.
NOTE that the PIN can be requested on one device and entered on another. A driver who starts at your kiosk can finish on their own phone.
Verifying a Driver's Identity
When identity verification is on, the driver is asked during check-in to photograph their government ID and take a selfie. Conduit checks the two against each other and records the result.
The result appears on the appointment as one of:
Identity Verified: The ID and selfie passed.
Identity Verification Failed: They did not pass.
Unverified: The check has not been completed.
Conduit attaches the ID photo and the selfie to the appointment, and where it can read a name off the ID, it fills that name in as the driver on the appointment.
NOTE that this is a per-visit check, not a permanent credential. The driver's profile shows the most recent result.
Collecting a License or Self-Photo
Separately from identity verification, you can require the driver to photograph their license, take a self-photo, or both. Conduit stores them on the appointment and on the driver's profile, but does not check them against anything.

Both are set per direction, so you can ask for them on inbound and not outbound. You can also write your own instruction text for each, which the driver sees on the photo screen.
Naming the Driver in Advance
When pre-assignment is on, whoever books the appointment can say which driver to expect:
Open the appointment, or start a new one.
Fill in Expected Driver Name, Expected Driver Phone, or both.

Save.
If the driver who actually checks in does not match, Conduit shows a warning icon on the appointment. Hover it to see the expected values next to the actual ones.

Name matching ignores capitalization and extra spaces. Phone matching ignores formatting, so (555) 123-4567 and +15551234567 are the same number. A field you leave blank is never counted as a mismatch.
NOTE that the warning is a heads-up, not a block. The driver still checks in normally. A mismatch usually means dispatch swapped drivers or the name was spelled differently, not that something is wrong.
Opening a Driver's Profile
From an appointment: open the appointment, go to the Details tab, and expand the Driver section. Status badges show there, and View Driver opens the full profile.

From the sidebar: click Drivers to see every driver at your organization.

Reading a Driver Profile
A profile shows:
Name and status badges: Trusted, Employee, or Flagged, where they have been set.
Phone numbers: All numbers Conduit has for this driver, with one marked primary.
Internal notes: Free text for your team. Drivers never see this.
Driver License: The license on file, behind a Show License button.
Verifications: The most recent identity verification result.
MC numbers: Every MC number this driver has run under, with the carrier names and how many visits each accounts for. Conduit reads these from past appointments, so values your team entered as placeholders are counted separately rather than listed.
Recent and upcoming appointments: Their visit history, and what they are booked for next.

Finding a Driver
On the Drivers page, search by name or phone number. You can sort by name or by most recent visit, and filter to only Trusted, Employee, or Flagged drivers. Where you work at more than one facility, you can narrow the list to one.

Viewing a Driver's License
Open the driver's profile and click Show License under Driver License.
Every time someone views a license, Conduit records who viewed it, which images, and which appointment it came from. You can only view a license if you have access to the facility that captured it.

Marking a Driver Trusted, an Employee, or Flagged

Open the driver's profile and set any of:
Trusted: A driver your team knows and vouches for.
Employee: Someone who works for you, not a third-party carrier driver.
Flagged: A known problem — harassment, repeated no-shows, safety issues. This is deliberately separate from simply not having marked someone Trusted yet.

The flags show as badges on the profile, on the appointment's Driver section, and in the Drivers list, and you can filter the list by any of them.
NOTE that these are notes for your team, not rules. They do not change what the driver has to do at check-in.
Setting Up Check-in Requirements
License and self-photo capture are yours to change:
Go to Settings, then your inbound or outbound direction settings.
Find Driver Check-in Configuration.
Check Driver's License, Driver Self ID Verification, or both.
Save, then repeat for the other direction if you want it there too.
Phone verification, identity verification, and pre-assignment are enabled by the Conduit team. Contact [email protected] to have them turned on.
Frequently Asked Questions
What is the difference between phone verification and identity verification?
Phone verification proves the driver is holding the phone number they gave you. Identity verification proves the person matches their government ID. Neither one implies the other, and they are turned on separately. A facility that mostly wants to stop bad phone numbers wants the first; one with a security requirement wants the second.
Does a trusted driver still have to enter a PIN?
Yes. Whether a PIN is required depends only on your facility's setting. Marking a driver Trusted does not skip it, and neither does a phone number that has been verified before.
The driver did not get the PIN. What now?
Have them request a new one from the same screen. Each request sends a fresh PIN. Check the number they typed first — a wrong digit is the most common cause, and the PIN went to whoever owns that number.
What does the verified badge on a phone number mean?
That the driver has confirmed a PIN on that number several times. It is a note about the phone number, not about the driver, and it does not let them skip anything.
The driver who arrived is not the expected driver. Does check-in stop?
No. Conduit shows the mismatch on the appointment and lets the check-in continue. It is there so your team notices, not to turn drivers away.
Does flagging a driver block them from checking in?
No. Flagged is a note your team sees. Acting on it is up to you.
Why did identity verification not run for a driver?
Facilities can have a monthly limit on how many identity checks they run. Once the limit is reached, check-in continues without the check for the rest of the month, and the driver is not told anything is missing. If verifications stopped part-way through a month, this is usually why — contact support to review the limit.
Who can see a driver's license?
Anyone with access to the facility that captured it, at an organization where driver profiles are turned on. Every view is recorded against the driver, including who looked and when.
Is a driver profile shared between my facilities? With other companies?
Between your facilities, yes — profiles belong to your organization, and a driver who visits two of your sites is one profile. Across companies, no. Another Conduit customer sees nothing about your drivers, and you see nothing about theirs.
What happens when a driver gets a new phone number?
Conduit recognizes drivers by phone number, so a new number creates a new profile. You can add the second number to their existing profile so both are recognized going forward.
How do I turn all of this on?
License and self-photo capture are in your direction settings. Phone verification, identity verification, pre-assignment, and driver profiles are enabled by the Conduit team — contact [email protected]