The Driver Home App

Your drivers carry two apps on their phone. One is for the road (Zap by voiceERP). The other, VoiceERP at Home, is everything off shift: their schedule, the shift marketplace, their scorecard and incentives, chat, and any timecard days you've flagged. It runs on iPhone, Android, and the web. One login covers every company a driver works for, so someone on two of your rosters switches between them from Settings, which is also where they choose English or Spanish.

Drivers who open onto a Home tab: a greeting by first name, then a "Today" card with today's start time, shift type, hours, and end time. When there's no route it reads "No shift today," "Time off today," or "No schedule yet." The screen refreshes itself about every 30 seconds, so a week you publish while a driver is looking at their phone appears on its own.

Everything below appears only when it has something to say. A "Needs your attention" band carries the "Acknowledge this week" prompt until the driver confirms their latest published week; then quick actions into Schedule and Marketplace, a "View scorecard" card, and, only when they have open flagged days, a "Timecard discrepancies" card with a count badge. If your site doesn't have scheduling turned on, that content disappears and the app tells the driver their manager can turn it on.

The Scheduling tab shows one week at a time with arrows to step between weeks, a shift count, and total hours scheduled. A week you haven't published reads "No schedule published yet," with a note that they'll be notified when it's ready.

Once published, a card at the top invites them to "Review & acknowledge your week," and the Acknowledge schedule button is what feeds your acknowledgement tracking. It also gates the marketplace: until they acknowledge, their day cards read "Locked," and tapping one prompts "Acknowledge your schedule for this week before requesting a drop or swap."

Tapping a shift on an acknowledged week opens "Request a drop or swap." They pick Drop ("Ask to give it to another driver") or Swap ("Ask to trade for a different shift"), and a reason for you is required; the submit button stays disabled without one. The app is clear about what happens next: the request only reaches you, and they're still scheduled until you approve a change. Past shifts can't be dropped or swapped at all.

The Marketplace section has two tabs. "Open shifts" lists what coworkers and you have put up for the coming weeks, filterable by Drop, Swap, and Time off. Each posting is pre-checked against your work-hours rules: ones that would break a limit are marked "Can't take — work-hours limit," and ones that merely push someone into overtime carry an advisory "Heads up — this adds overtime" they can still submit through. Taking a dropped shift is "Take this shift"; offering a trade is "Send swap offer," and the app checks the offer against your work-hours rules before it goes out. VTO postings show spots remaining and a "Take time off" button.

"My posts" tracks their own requests with plain-language statuses: Waiting for manager approval, Live in marketplace, Offer received (someone has offered a swap), Awaiting manager approval (a taker or trade has been accepted and is waiting on you), Done, Declined by manager, and Expired, plus your note when you decline. A post nobody has acted on yet can be canceled. An incoming trade surfaces here as "Review trade," showing what they'd give up and what they'd work instead, with Accept & swap or Decline. Even then, your approval is what finalizes it.

The Scorecards tab has three segments: My scorecard, Incentives, and Metrics. My scorecard leads with their overall tier, headline stats for the week, the incentives they were eligible for with whether each was achieved, and what they earned. Incentives explains how each one works and its requirements; Metrics breaks out safety, customer experience, delivery quality, and compliance. When a week's scorecard hasn't been uploaded, the app tells the driver to ask you to upload it. Where multi-week viewing is on, arrows step back through earlier weeks.

Flagged days now live in the driver's own app, under the HR tab's Timecards entry. Only discrepancies from triggers set to notify the driver appear there; checks you've set to alert administrators only stay on your side. Each discrepancy is a card showing the date, the rule that fired, its limit, and the status; expanding one reveals the punch timeline, the supporting Flex evidence, and their previous response if they've already answered. A link from a notification or chat message opens straight to the relevant card, already expanded.

When VoiceERP can tell what the right time should be, the card leads with a Suggested fix such as "Add a clock in at 7:58 AM", showing the suggested time next to what's on their timecard, the evidence behind it ("Why we suggest this"), and a confidence label (High confidence or Best estimate). The panel reminds them that you approve changes in the payroll system and to check the suggested time against what they remember.

Their response asks "Does your timecard look right?" and offers two options to pick from before submitting: I'll fix my timecard means they see the issue and will correct it in payroll (a note is optional), and My timecard is correct means no change is needed. That one requires an explanation ("Why is your timecard correct?") before it submits, so you always get their reason in writing. If you've already dismissed the discrepancy yourself, they can only leave a comment; if you've identified it as a real issue, Acknowledge is their only action.

Chat is a tab on the phone app when your company has unified chat turned on. The web version has no Chat tab; a driver who follows a chat link there sees "Chat is available in the VoiceERP mobile app." Drivers see their conversations grouped and searchable, can start a new chat, and can add attachments. In their Viki conversation, a phone icon in the header offers Call Viki, dialing your company's Viki number. It appears only when one is configured.

Running a route is a separate app, and sign-in or notification problems are covered in the driver troubleshooting guide.