Viki watches your operation and reaches out when something needs a person. AI notifications are short, specific messages about things you'd otherwise have to go looking for: a driver who just declined tomorrow's shift, a route falling badly behind, a schedule week sitting unacknowledged. Each user picks their own set, so the dispatcher and the owner don't get the same alerts.
Where notifications arrive
Every AI notification is delivered on the channel picked for that setting. SMS sends it as a text message to the phone number on your user record. Chat files it in your in-app Viki feed.
With Chat selected, open Chat in the left sidebar and look at the Notifications section at the top of the conversation list. That's your Viki feed. It's a record, not a conversation: the message box is replaced by 'Viki notifications are read-only.' The Chat item carries an unread count so you can tell at a glance whether something new landed.
You can also be pushed. From the chat page's menu, choose Notifications to open Notification preferences. Under 'Where you get notified' are switches for Web push, Mobile push (pushes in the VoiceERP app), and Banners while viewing chat. Further down, under 'Defaults by conversation type,' the row labeled Your Viki feed controls how loudly these particular notifications push you.
What Viki notifies you about
Around scheduling: Schedule Generated (a week is ready to review, flagging shifts it couldn't fill), Schedule Published (the week went live, and to how many drivers), Schedule Progress Update (how tomorrow's shift confirmations are going), Schedule Acknowledgements Summary (who acknowledged, viewed, or hasn't looked at the published week), Marketplace Activity (drop and swap postings needing approval, and offers ready for your final review), and Driver Declined Shift.
Around drivers on the road: Route At Risk, Route Badly Behind, Low Phone Battery, and Driver Inactivity Alerts. Around your fleet: Maintenance Reminder Due and New Damage Detected. Around dispatch: Dispatch Rule Suggestions, sent when Viki's weekly review of dispatch calls produces new rule suggestions to look over on the Dispatch page. Plus Timecard Checking Summary and Product Updates, which is how VoiceERP tells you about new features or something you need to act on.
Around training: Training Assigned (a Viki University course was assigned to you), Training Reminder (a course is due about a week or two days out), Training Overdue (a course passed its due date incomplete), and Training Content Updated (a completed course has new material; your completion still stands).
Not every type appears for every company: Timecard Checking Summary only shows up in the Add Notification list if timecard checking is turned on for you, New Damage Detected only if AI damage scanning is, and Dispatch Rule Suggestions only if the Dispatch page's rule suggestions are turned on for your company. The four Training types never appear in that list at all; see below.
Setting them up
Go to Settings and choose Notifications in the left list to reach the AI Notifications section. Every user in your company gets their own block, with their name at the top and their configured notifications underneath. Someone with nothing set up shows 'No notifications configured for this user.'
Press Add Notification next to a name to open the 'Add Notification for [name]' dialog. Pick a Notification Type, choose the Enabled Days (all seven are on by default; tap a day chip to turn it off), choose the Delivery Method, Chat or SMS, with SMS pre-selected, and set the timing, which depends on the type:
Recurring types, the daily summaries, ask for a Send Time. You can also add Automated Progress Update Follow-ups and set the minutes between them, if one summary a day isn't enough.
Event-triggered types fire the moment something happens, so instead they offer a Snooze Window. Turn it on and set a Snooze Start and Snooze End: anything that happens inside that window is held and delivered when the window ends, rather than waking you at 2 a.m.
Press Create. Each configured notification then appears as a card summarizing itself in chips: 'Recurring Daily' or 'Event-triggered,' the delivery method, the send time, the snooze window, and the days it's active. Edit expands the same fields inline; the trash icon removes the subscription.
Types you don't set up here
Route At Risk, Route Badly Behind, and Low Phone Battery deliberately don't appear in the Add Notification list. Their recipients are the admins you pick on the Route Assistance page under Settings → Rules, alongside the thresholds that define 'at risk' in the first place. Likewise, Maintenance Reminder Due goes to whoever is listed under Fleet → Reminders → Configuration → Notification Subscribers. That keeps each alert next to the rule that produces it.
The four Training notifications are always on and never appear in the list either. They go straight to the person the course was assigned to, so there is nothing to subscribe to: assign a course in Viki University and the learner gets them.
What actually sets one off
A driver declines a shift. Viki asks a driver to confirm tomorrow's shift, by call or by text, and they say they can't make it, so the shift is marked unable to confirm. That fires a Driver Declined Shift notification naming the driver and the date, with their reason if they gave one.
A driver goes inactive. When a driver turns inactive in Cortex, subscribers get a text naming the driver and saying they are excluded from schedules. If the driver still holds upcoming scheduled shifts, the alert adds how many and tells you to review the schedule to reassign or unassign them: 'Marcus Bell went inactive in Cortex and is excluded from schedules. They still hold 3 upcoming scheduled shifts — review the schedule to reassign or unassign them. If they are expected back, mark them suspended with an anticipated return date so scheduling includes them from that day.' The held-shift sentence appears only when the driver still has upcoming assigned shifts. The same subscription also covers a suspended driver whose expected return date passes without them coming back.
A damage scan finds something new. When an AI damage scan turns up damage that doesn't match an already-known case, you get a message naming the vehicle and a link into the damage workspace. Two guardrails keep it quiet: a vehicle's very first scan never triggers it (that scan just records the vehicle's existing condition), and low-confidence detections don't count.
A training assignment moves through its reminder stages. When a Viki University course is assigned to an admin, Viki creates a Training Assigned notification. The hourly reminder cadence then creates due and overdue notifications for active assignments, and a content update on a completed course creates the informational Training Content Updated notification.
AI notifications are the 'here's what happened' half of Viki; the 'here's what I did about it' half lives in AI Actions and Admin Tasks, covered separately.