Voice troubleshooting

What this covers

The things that go wrong during a spoken session, and which of them are worth reporting.

VEXA interrupts itself mid-sentence

Interruption Mode lets you cut VEXA off while it is talking. The cost is that VEXA can hear itself through your speaker and treat its own voice as you interrupting. Each platform filters that echo differently, and none of them filter it perfectly on a loud speaker in a hard room.

Use headphones. Nothing loops back into the microphone and the problem goes away. Failing that, lower the volume, or turn Interruption Mode off and let VEXA finish before you speak.

The call went quiet for a moment and came back

Long sessions get moved onto a fresh connection periodically. The handover starts before the old connection expires, and the conversation, the transcript and everything VEXA has looked up carry over. Nothing on screen announces it.

This is not a session limit and it is not you being cut off. If you hear a brief gap and VEXA is still with you afterwards, nothing went wrong. Keep talking.

A pause after you ask a question

When VEXA has to fetch something, for example a month of trades or a chart, there can be a couple of seconds of silence before it starts speaking. It is fetching, not stuck.

Anything longer than about ten seconds with no reply is a real problem. Hang up and reconnect.

The transcript is empty afterwards

A small number of sessions save with no turns in them. The session itself happened and the minutes were counted, but the text was not captured.

There is no way to recover the text of a session this happens to. If you get an empty transcript more than once, report it with the date and time so it can be traced.

VEXA cannot hear you

1. Check the mute control. Muting is the first thing people forget.
2. Check the microphone permission for VEXA in your device or browser settings.
3. On a computer, check which input device the browser is using. A disconnected headset often stays selected.
4. Reconnect the session. The microphone is claimed at connect time.

It will not connect at all

• A consent dialog appears. Voice needs AI consent on every surface, web included. See Give or revoke AI consent.
• A general failure, along the lines of “Voice is temporarily unavailable. Please try again.” This one message covers several different causes, including running out of monthly minutes and hitting one of the daily caps. Check your usage before treating it as a fault. See Voice and chat limits.
• It hangs on connecting. A restrictive network can block the connection. Try another network, or a phone on mobile data, to tell the two apart.

Sentinel is not speaking to you during a session

Sentinel interventions are spoken through a live voice session, so there has to be one running for you to hear anything. There is also a setting for which device should speak. If it names a device that is not online, nothing is said out loud there. Phones and tablets receive a push instead, and web does not, because the web app has no push at all.

What you should see

A healthy session moves between listening, thinking and speaking without you doing anything, the timer keeps counting, and the transcript fills in as you both talk. Short gaps are normal. Silence with a frozen timer is not.

Still stuck

Report it with the date, the time, the surface you were on and what you heard. Voice problems are hard to reproduce after the fact, and those four things are what make a report actionable.