Troubleshooting Get-Offer
What to check if sign-in, audio, hints, screenshots or window hiding don't work.
Can't sign in
First, figure out where exactly sign-in fails: on the website, in the app or when confirming the code from the app.
- Open the sign-in page.
- If you sign in successfully, open your profile and check the account.
- If the app shows a code, sign in again in the browser with that code.
- If the browser shows that authorization succeeded but the app hasn't updated, restart the app and try again.
No transcript
Without a transcript, the assistant doesn't have enough data to give hints about the conversation. Start by checking your devices and audio source.
- Check that the right microphone is selected.
- If you need the other person's voice, choose “System audio + microphone” or “System audio only”.
- Check the Windows microphone permissions.
- Turn off noise suppressors or virtual devices if they break recording.
- Test a short recording with the microphone only and then with system audio only. If the indicator reacts but no text appears in either mode, check the network, your limit and the error message from the speech recognition service.
No hints
There's a transcript but no hints? Check the network, limits, the active context and the selected model.
- An empty or overly generic context makes answers less useful.
- A corporate VPN can interfere with streaming answers.
- Send a short text question manually. The expected result is a complete text answer.
- If the manual answer works but the automatic one doesn't, check the transcript and the auto-replies toggle.
- If the answer cuts off, repeat a short request and note the time of the error; partial text doesn't mean the answer completed successfully.
Can't send a screenshot
- Add a screenshot of a small area with test text and no personal data. An attachment should appear in the interface.
- If there's no attachment, check the shortcut, permissions and the selected monitor.
- If the attachment is there but the request is rejected, check your visual request limit, the selected model and the network. Compare it with a regular text question.
Network or plan limits
- Open your profile on the website: a successful load only confirms access to the web service.
- Check your current plan and what's left of the relevant limit. If it's used up, wait for the limit to reset or choose an available plan.
- If you have limit left but streaming answers and audio don't work, repeat the test on an allowed alternative network. A difference points to the network path but doesn't prove what's causing the block.
- Write down the error text and the time with your time zone; don't turn off corporate security without approval.
The overlay is visible in the screen share
Don't go into an important interview with untested screen protection. First find a setup that works in a test call.
- Check that capture protection is turned on.
- Try the web version of the calling service instead of the desktop app.
- Share a specific window instead of the entire screen.
- Try another Chromium-based browser.
- If the service uses proctoring or an exam browser, treat the mode as unsupported until you've tested it separately.
What to send to support
To sort things out quickly, we need specifics: the app version, OS, calling service, time of the error and a short description of what happened.
- What you did before the error.
- Where the problem is: sign-in, recording, hints, screenshot, payment or window hiding.
- Which audio source was selected.
- A short log excerpt without private data.
- Remove passwords, tokens, one-time codes, resume text and other people's messages. To test audio, use a neutral test phrase; don't send a full interview recording.