When something goes wrong during a session, the fastest way for our team to see exactly what happened is to find your session in our diagnostic tools, including what Bola heard and what it produced. That lets us troubleshoot without asking you to reproduce the problem. How you point us to the right session depends on which version of Bola you use.
Using the Bola Voice desktop app
The session ID is shown at the bottom of the Bola Voice app window during and right after a session.
Bola starts a new session ID every time the microphone button is clicked. If you finish a patient, click the mic off and back on for the next patient, the previous session ID is replaced. When an issue happens, copy or photograph the session ID before starting anything else.
Desktop app session IDs are a short string of mixed upper and lower case letters and numbers, for example k3RtWq7zB1. If what you wrote down is all capital letters with no numbers, double-check it against the app, as it may not be the actual session ID.
Using the Bola Chrome extension
The Chrome extension does not display a session ID on screen, and that is okay. We can locate your session on our side. Send us:
Your account details: click the gear icon on the floating Bola toolbar, open Account, and click Copy info to clipboard. That copies your license key, app version, and User ID in one block.
The approximate time the issue happened (date and time, even rough).
Using AI Scribe (scribe.bola.ai)
In AI Scribe, your Session ID appears at the top left of the screen, just under the Bola logo, once you start a session. A copy icon next to it lets you copy it in one click.
The Scribe session ID is a long code with dashes, for example d5d50d93-cdee-4031-9393-df4aa6be8644. Copy it and include it when you contact support.
What to send support
The session ID (Bola Voice desktop app or AI Scribe) or your Account info and approximate time (Chrome extension).
One specific example from the session: what you said, what you expected, and what Bola did instead.
The approximate time the issue happened.
