Keep a voice session running in the background

Talk to VEXA while you use another app or move around the web app, and know what actually ends a call.

Same on every platform Updated

What this does

A voice session does not need the VEXA screen in front of you. On an iPhone or iPad you can switch apps or lock the screen and keep talking, the way a call or a music app keeps playing. In a browser you can move between pages of the web app and the call follows you.

Before you start

The rule is different on each of the three, and the difference is real rather than cosmetic.

iPhone and iPad hold the call properly. VEXA runs voice as background audio, the same way a music app does. Switching apps or locking the screen keeps you talking, and the screen will not auto-lock by itself while a session is connected.

On the web, the tab has to stay open. The call lives in the page. Closing the tab or the window ends it, and the session is lost rather than saved. Other tabs and other apps in front of the browser are fine.

On Android, stay in the app. Moving between VEXA’s own screens is fine and the mini player keeps the session with you. Leaving VEXA or locking the screen is not protected the way it is on iPhone, and the screen is only held awake while the Voice screen itself is open. Treat an Android session as something to finish before you go elsewhere.

Steps

  1. Start a session on VEXA Voice, or with the microphone toggle in the chat bubble.
  2. Navigate anywhere else in the web app. A small player stays on screen with the session on it.
  3. Use that player to mute or hang up from any page.
  4. Leave the tab open until you are done.
  1. Start a session on the Voice tab.
  2. Swipe home, open another app, or lock the screen. Keep talking.
  3. Return to VEXA when you want the transcript or the controls.
  4. Tap hang up to end the call.
  1. Start a session on Voice in the sidebar.
  2. Switch apps or lock the screen. Keep talking.
  3. Return to VEXA for the transcript or the controls.
  4. Tap hang up to end the call.
  1. Start a session on the Voice tab.
  2. Move around VEXA as you like. A floating player stays on screen with the session on it.
  3. Tap the player to get back to the voice screen.
  4. Tap hang up to end the call before you leave VEXA or lock the screen.
  1. Start a session on VEXA Voice in the sidebar.
  2. Move around VEXA as you like. The floating player stays with you.
  3. Tap the player to get back to the voice screen.
  4. Tap hang up to end the call before you leave VEXA or lock the screen.

What ends a call

  • Hanging up.
  • Closing or reloading the browser tab, on web.
  • Force-quitting the app.
  • Leaving the app or locking the screen on Android, in most cases.
  • Losing your connection for long enough that it cannot recover.

On iPhone and iPad, neither backgrounding the app nor the screen going dark is on that list.

What you should see

On iPhone and iPad the timer keeps counting while you are away and VEXA keeps replying. Coming back to the voice screen you find the transcript filled in with everything said while you were elsewhere.

On the web and on Android, the mini player follows you with the timer still running, and tapping it returns you to the session.

A pause part way through is not a dropped call

Long sessions are handed to a fresh connection from time to time, at a moment the service picks rather than a fixed interval. You may hear a short gap. The conversation, the transcript and everything VEXA has looked up carry across, so keep talking. See Voice troubleshooting.

If it doesn’t work

An Android call ended when you left the app. That is the current behaviour rather than a fault. Finish the conversation in VEXA, or use the web app on a computer if you need to work elsewhere while you talk.

An iPhone call ended when you switched apps. Check the app was not force-quit, by you or by the system reclaiming memory. Reopen VEXA and start again.

The web call ended when you reloaded. A reload rebuilds the page, which ends the session. Moving between pages with the sidebar does not, and a session lost to a closed tab is not saved to your summaries.

Your phone screen keeps turning off and you are using a Bluetooth heart-rate strap for Sentinel. Those straps need the screen on. That is a Sentinel requirement rather than a voice one.

Related

Still stuck? Email support@vexatrade.ai.