Voice troubleshooting
I cannot find Voice
Section titled “I cannot find Voice”Voice is early access and must be enabled for your account. Sign in to the Windows app with the intended account. If enabled but the panel is hidden, use Show voice window in the tray menu. This opens the panel without starting a call or turning on the microphone.
If the Voice menu is absent, contact support to confirm account access and the installed app version.
The wrong employee answers
Section titled “The wrong employee answers”Check Voice employee in the tray menu and choose the employee you want. Confirm the name on the panel before starting another request. The selection matters: each employee has its own role and connected tools.
I cannot hear an answer
Section titled “I cannot hear an answer”Run the panel’s speaker test. Check your Windows output device and volume. The first use may need to download the speech model, so allow that setup to finish.
If the panel reports a playback error, the presence of reply text does not mean audio was heard. Keep the visible error when reporting the problem.
The call will not start or disconnects
Section titled “The call will not start or disconnects”Read the panel’s error, check your network connection and confirm you are signed in. If sign-in has expired, sign in again through the dashboard window. A call also depends on the selected employee’s workspace being available.
Do not repeatedly submit a consequential request when its outcome is unclear. Check the dashboard’s work and approvals first.
Hey Cruz does not respond
Section titled “Hey Cruz does not respond”Check whether Listen for “Hey Cruz” is enabled. Review any Hey Cruz is not working message in the tray menu. You can still use Call Cruz or the shortcut shown in that menu.
Check Windows microphone access and the selected input device. If another app is using the microphone, check its settings too.
Report a problem
Section titled “Report a problem”Include the app version, selected employee, approximate time and the visible error. Voice diagnostics are kept locally in a file named voice-debug.log in the app’s data folder. Logs can contain conversation text: review them before sharing and avoid sending private content unnecessarily.