VoiceERP holds chat, SMS, and push messages from Viki's AI actions to drivers between 11pm and 8am in your company's timezone. A message that would send in that window is sent at 8am instead.
What this applies to
Quiet hours apply only to messages Viki sends as part of an AI action, whether by chat, SMS, or push. That includes shift confirmation texts, Netradyne alert texts, incident coaching and signature requests, timecard discrepancy notifications, driver login reminders, and most other AI-action outreach that is not a call.
What goes out right away
Calls are never held. Mid-route operational messages are not held either: pace updates and battery alerts still reach a driver while they are on a route, no matter the hour.
Roster texts are not AI actions, so they are not held. Wave times and other roster messages sent from Daily Ops go out the moment you send them, whatever the time. The same is true of chat messages you write to a driver yourself from the Chat page: those are your messages, not Viki's, and they deliver immediately. If a driver did not get a wave-time text, quiet hours are not the reason. Start with the phone number on their profile.
When it matters for you
If you create an incident or approve a timecard discrepancy after 11pm, the driver won't receive the message until 8am. You don't need to change the message or follow up. It stays queued and sends at 8am.
This runs on your company's timezone. If your company's timezone isn't where your drivers are, the quiet window shifts with it. Check the timezone under Settings → Shift Confirmations.
Related topics
AI Actions & Viki's Activity lists the messages and calls Viki works on.
Timesheets and Timecard Discrepancies covers those driver notifications.
Netradyne Alerts and Coaching and Incidents cover their specific outreach.