Every time Viki needs to talk to somebody, an AI action is created for it. An AI action is one job — one driver, one topic — with a plan for how Viki will reach that person and a record of how it turned out. Viki's Activity is where the whole list lives, under Viki → Viki's Activity in the sidebar.
What an AI action looks like in practice
Three common ones:
Shift Confirmation — the roster for tomorrow goes out, so Viki calls each driver to confirm they are working. The action holds the shift date and start time, and closes when the driver confirms.
Netradyne Alert — a safety event comes in for a driver, so Viki calls to coach them on it. The action carries the alert type and description, with a link out to the Netradyne portal.
HR Signature — a write-up is ready for a driver to sign, so Viki texts them the document and tracks whether it came back signed.
Job applicant screenings, negative customer feedback coaching, and inbound calls where someone just has a question all create actions too. Not every automated nudge appears here — routine things like login and timecard reminders run quietly in the background.
Reading the page
Three cards sit across the top. Compliance is the share of the actions in the selected window that Viki managed to resolve. AI Calls counts the interactions attached to those actions. Blocked Actions counts the ones Viki cannot start, which today means the person has no phone number on file.
Below that sit a date range (the last three days by default), an All / Drivers / Managers toggle, a count of matching actions, and a Refresh button. Then the table, one row per action:
Task — the kind of action, such as Shift Confirmation or Netradyne Alert.
Person — the driver or manager it belongs to.
Created — how long ago it was raised; hover for the exact time.
Interactions — a row of colored dots, one per attempt. Click them for the list: "Outbound call", "Inbound call", "No answer", "Driver offline", "SMS sent", "Voicemail left". Call rows are clickable — "Tap to view transcript" opens the conversation in a side panel.
Status — where the underlying record stands: Confirmed, No response, Not contacted, Dealt with, Waiting for call, Pending signature, Signed, and so on.
Info — the specifics: the shift date, the alert description, the incident name, the applicant.
Blocked — a "Missing phone number" chip when that is the holdup.
Manual Actions — the buttons described below.
Nothing here waits on your approval
The actions on this page run on their own. When the roster publishes or an alert arrives, Viki starts working the action immediately, following the outreach plan for that type — a shift confirmation is a call plus however many reminder calls you have configured, while a Netradyne alert is a call with a text as backup. Viki's Activity is a record of work already in flight or already done, not a queue you have to clear.
The approval step you may be thinking of belongs to the assistant: when you ask Viki in chat to change something, that proposal comes back for you to approve first.
Acting on a row
The Manual Actions column gives you the handful of things worth doing by hand, and they change with the row. A blocked action offers Add Phone, which opens a dialog to put a number on the driver's record so Viki can proceed. A Netradyne alert waiting on a driver callback offers Send Reminder, which texts them, and Mark as Disputed (with a confirmation prompt) when the alert is being challenged rather than coached. Incidents that have not been signed or coached yet offer their own Send Reminder. Job applications awaiting review get a green check and a red X to mark the candidate as passed or failed screening.
When actions expire
Each type of action has its own shelf life, and once it passes, Viki stops chasing it and the driver can no longer call in about it. A Netradyne callback stays live for 48 hours; an incident coaching session for a week; a signature request for the best part of a year; a shift confirmation follows your confirmation window. Most actions also close out the moment they are resolved. Shift confirmations are the deliberate exception — once a driver confirms, Viki stops calling, but the driver can still ring back to change their answer while the window is open.
Settings that shape what Viki works on
Which actions get created is driven by the settings for each feature rather than by one master list. Settings → Shift Confirmations holds the AI Agent Settings: the shift confirmation window (when calls go out and how long drivers can call back), your drivers' timezone, the number of reminders, and the time between them. Settings → Integrations holds Netradyne Alert Coaching, where each alert type and category is set to Off, Minor, or Major — that decides which safety events are worth a call at all. Turning a whole action type on or off is handled by support.
Two neighboring pages are worth knowing: Admin Tasks collects the cleanup items Viki needs a human for, and Compliance reports on how reliably these actions get closed.