Features Sentinel Brokers Community Pricing About Us Why VEXA Support Get Access Now

Voice won't connect

Microphone permission, AI consent, monthly limits and network drops, in the order that actually causes voice sessions to fail.

Same on every platform Updated

What this does

VEXA Voice needs three things before it can say a word: permission to use your microphone, your consent for AI features, and enough of your monthly allowance left. If any one is missing the orb never gets past its connecting state.

Before you start

Voice minutes are not only spent on the Voice screen. Journal voice notes and Sentinel voice interventions draw from the same monthly pool. If you have been using either, your remaining minutes may be lower than you expect. Check the AI Usage card in your profile. See Read the AI Usage card.

The four causes

1. Microphone permission

Voice cannot start without it. The first attempt asks; a refusal is remembered by the operating system, and VEXA cannot ask twice. You have to grant it from the system’s own settings after that.

VEXA asks for one explicit consent before its first AI call, and Voice will not connect without it on any surface. On the phone and tablet apps, revoking consent turns Chat off as well, so a Chat that has also stopped working points at consent rather than at the microphone. On the web it does not work as a test: Chat keeps running whether or not you have granted consent, so a working Chat there tells you nothing about Voice. Check your consent setting directly instead.

3. You have reached a limit

Three separate limits can stop a session: your monthly voice minutes, a cap of 100 voice sessions per day, and a cap of 300 voice minutes per day. The two daily caps do not name themselves. Hitting either one reads “Voice is temporarily unavailable. Please try again.”, which is the same text a plain connection failure gives you. So if Voice worked earlier today and now gives you that line, count how much you have used before you blame the network. See What happens when you hit a limit.

4. The connection dropped

Voice runs over a live connection. A network change part way through ends the session rather than pausing it. The message reads “I apologize, but I’m having trouble connecting right now. Please check your internet connection and try again.”

Steps

  1. Tap the orb once. The tap itself is what lets the browser ask for the microphone, so the session cannot start from anything other than a deliberate tap.
  2. Accept the microphone prompt. If no prompt appears, open the padlock or camera icon in the address bar and allow the microphone for this site.
  3. If the AI consent dialog appears, read it and accept. Voice will not run without it.
  4. If the state text under the orb turns red, read the message. Microphone and consent failures name themselves. “Voice is temporarily unavailable. Please try again.” does not, and is either a daily cap or the connection.
  1. Open the Voice tab, third icon in the bar at the bottom of the screen.
  2. Tap the orb.
  3. Accept the microphone prompt. If you declined it previously, iOS will not ask again, and you have to turn VEXA’s microphone access back on from the system settings app.
  4. If the AI consent dialog appears, read it and accept.
  1. Open Voice from the sidebar.
  2. Tap the orb.
  3. Accept the microphone prompt. If you declined it previously, iOS will not ask again, and you have to turn VEXA’s microphone access back on from the system settings app.
  4. If the AI consent dialog appears, read it and accept.
  1. Open the Voice tab, third icon in the bar at the bottom of the screen.
  2. Tap the orb.
  3. Accept the microphone prompt. If you chose “Don’t allow” twice, Android stops asking, and you have to turn the microphone permission back on from the system app settings for VEXA.
  4. If the AI consent dialog appears, read it and accept.
  1. Open VEXA Voice from the sidebar.
  2. Tap the orb.
  3. Accept the microphone prompt. If you chose “Don’t allow” twice, Android stops asking, and you have to turn the microphone permission back on from the system app settings for VEXA.
  4. If the AI consent dialog appears, read it and accept. On Android tablet this dialog is the only place consent is asked, because the tablet profile has no AI Services row.

What you should see

The state text moves from “Ringing up your trading psychologist VEXA…” to “Listening…”, a session timer starts, and four round controls appear under the orb. A floating voice pill stays on screen while the session is live, which is also your reminder that minutes are still being counted.

Two behaviours that are not faults

  • You cannot talk over VEXA by default. Interruption Mode is off until you turn it on with the hand icon.
  • There is a short deaf moment right after VEXA stops speaking. For roughly two and a half seconds it is not listening, which stops it from hearing its own voice. If your reply gets missed, wait a beat and say it again.

If it doesn’t work

  • The message quotes a code. Look it up in Error messages explained.
  • Chat is broken too, in the phone or tablet app. Then it is consent or your allowance, not the microphone. On the web this test does not apply, because Chat runs there regardless of consent.
  • It connects and then ends after a few seconds, repeatedly. Move to a stable network and try once. Voice is more sensitive to a changing connection than the rest of the app.

Related

Error messages explained Every error message VEXA can show you, what it actually means, and the one thing to do about it. What happens when you hit a limit The difference between your monthly plan allowance and the daily voice cap, and what each message means. Read the AI Usage card Where to find your voice and chat meters, what the colours mean, and why the period does not start on the first of the month.

Still stuck? Email support@vexatrade.ai.