Admin Tasks

Viki does most of its work without you. Admin Tasks is where it puts what it can't finish alone — a driver with no phone number to call, a safety alert with a name nobody recognizes, a driver with no payroll ID. Each row waits on a human, and until someone acts, the work behind it sits still.

Admin Tasks lives in the sidebar under Viki, alongside Viki's Activity and Compliance, with a red badge showing how many tasks are open. The Home page carries the same numbers on its priority board — "Open admin tasks,""Missing phone tasks," and "Name match tasks" — so you can spot a backlog without opening the page.

The page is a single table, newest first. Each row shows the task type, a plain-language description ("Add phone number for Maria Lopez"), the person it concerns, how many of Viki's tasks it blocks, a status of Open or Resolved, and the created and resolved times. A date range picker narrows the list, chips count open versus resolved, and resolved rows stay hidden until you flip Show resolved.

The Blocked AI Tasks column is the one to watch. It counts the calls and messages Viki has queued and cannot send because of this task — three blocked items means three conversations are frozen.

Missing Phone Number. A driver has no phone number on file, so Viki can't call or text them. This is the most common task and blocks the most work.

Driver Name Unmatched. A Netradyne safety alert arrived under a driver name or ID that doesn't line up with anyone on your roster — usually a nickname, a misspelling, or a driver the camera system knows by a different name.

Missing Payroll ID. An active driver has no payroll ID, so they can't be matched to a person in your payroll provider.

Alert Dispute. A driver told Viki, on a safety callback, that they disagree with a Netradyne alert.

Dispatch Follow-Up. A dispatch call raised something needing a manager's follow-up. The description names the rule that triggered it.

Damage Review. A vehicle damage recorded by hand rather than detected automatically, flagged so someone can check earlier inspection photos and work out when it really started.

Every one of these is created automatically, and none is created twice for the same problem — a second alert or blocked call for the same driver is folded into the existing task rather than starting a new row.

Missing Phone Number tasks appear the moment Viki tries to reach a driver and finds no number: a safety alert needing a callback, an incident requiring a coaching call or a signature request, or any queued call with nowhere to dial. Driver Name Unmatched tasks appear when a Netradyne alert has been checked against every driver by ID, by name, and by known aliases and still matches nobody. Missing Payroll ID tasks are refreshed on every payroll sync against your active roster. Alert Disputes come from the driver's own words on a Viki call, and Damage Reviews open when a missed damage is logged by hand.

Most task types carry their own button in the Resolution Actions column, and using it both fixes the underlying problem and closes the task.

Add Phone opens a dialog to enter the driver's number. Saving it closes the task and — importantly — unblocks and retries the calls and messages that were waiting on it, so the queued work resumes on its own.

Match Driver opens the Match Netradyne Names page, which lists every unmatched name and pre-suggests roster matches. Confirm the ones that look right and press Submit Matches: the outside name is saved as an alias on that driver so future alerts match automatically, the waiting alerts are attached to them, and the tasks close.

Match Payroll ID opens a similar page listing active drivers missing a payroll ID beside the unmatched people from your payroll provider. Pair them up and press Submit Matches.

Mark As Disputed sets the alert to disputed and texts the driver to let them know. It can't be undone, so you'll be asked to confirm.

Dispatch Follow-Ups have an open-in-dispatch icon beside the description. Any task can also be closed by hand with the check mark at the end of the row, and reopened with the undo arrow if you close one too early.

Some tasks close themselves. A Missing Payroll ID task resolves as soon as that driver has a payroll ID or leaves active status, and an unmatched Netradyne name resolves if the matching driver later appears on your roster.

Nothing breaks loudly, which is exactly the risk. Blocked calls and texts don't wait forever — once they expire they drop off the task and simply never happen. Safety alerts stuck behind a missing phone number or an unrecognized name age out too: an alert that isn't matched and acted on within a couple of days is marked expired instead of being coached. Missing payroll IDs resurface at payroll time, when the driver can't be included in the file. Working the queue down to zero once a day keeps any of that from mattering.

Related topics: Viki's Activity covers the AI actions themselves, and Compliance covers call outcomes.