Interview AiBox logo
Interview AiBox Docs
Troubleshooting
🎉✨ Interview AiBox v1.0 is liveA stealthy, stable interview copilot is live.Download

FAQ

Find help with sign-in, audio, sharing, and app errors.

Common FAQ

Choose the symptom below. Keep the exact error text and note whether the issue began after an update or device change.

ProblemStart here
Sign-in fails or the plan looks wrongAccount and plans
No transcription, missing headset audio, or delaysVoice and devices
Sharing, clicks, or window placement behave unexpectedlyWindow and client issues
Preparing for a new meeting platformPlatform checks

If you are stuck, send feedback with your app version, OS, and steps to reproduce. You do not need to complete every check before asking for help.

Plans, upgrades, and account

How does plan upgrade conversion work?

When upgrading from Pro to Flagship, remaining time converts at 50% only when the current and target billing periods match. Cross-period upgrades do not convert remaining time. Use the checkout page as the final calculation.

Example: for a same-period upgrade, 10 remaining Pro days can add up to five Flagship days before the newly purchased duration is added.

I can’t sign in

Common symptoms: sign-in timeout, connection failed, or web login works but the client still fails.

Recommended order:

  • Restart the app and try again
  • Check whether the network is stable, especially if you are on a proxy, company network, or campus network
  • Confirm your credentials on the website first
  • Update to the latest client version
  • If it still fails, contact support with the exact symptom
API key or network errors

Check these first:

  • whether you are already on the latest app version
  • whether the current network is stable or restricted
  • whether your subscription and remaining entitlements are normal

If the issue is intermittent during usage, fully quit the client and sign in again before deeper troubleshooting.

Voice and devices

Voice won’t start
  1. Check the on-screen error and remaining voice quota in Settings.
  2. Check the audio source: System Audio for the other person's voice, Microphone for your own. Confirm the required OS permissions are enabled.
  3. If paused, press Cmd/Ctrl + M to resume. Speak a short sentence and check for transcription.
  4. If a connection error remains, check the network and save the error before restarting the app.

See audio input settings for source and permission checks.

Headset audio is missing

Use headphones for playback to reduce echo. Playback and microphone input are separate settings:

  • Missing your voice? Check the selected microphone. Try the built-in microphone or another tested device.
  • Missing the other person's voice? Check System Audio, rather than changing the microphone.
  • Test each speaker separately using the 5-Minute Check.
Transcription or answers are delayed
  • Text appears late: check the audio source and network connection. Pause with Cmd/Ctrl + M, then press it again to resume and test.
  • Text is ready but no answer appears: check Auto/Manual mode. Press Cmd/Ctrl + Enter to submit manually; see Auto and Manual mode.
  • Text is duplicated: use headphones and check that playback audio is not also entering the microphone.

If delays continue, record whether the delay happens during transcription or answer generation and send feedback.

Screen sharing, window behavior, and client issues

The app appears in the shared screen

Do not assume the app itself is the only cause. More often, the issue comes from platform version changes, sharing mode differences, permission state, or multi-monitor layout changes. Go directly to Common Platform Issues and Stealth Mode, then verify once more in self-check tools or a rehearsal meeting on the target platform.

Clicks do nothing, but shortcuts work

This usually points to window focus or desktop-layer behavior rather than a broken feature. Try this:

  • switch back to the Interview AiBox window
  • press Cmd/Ctrl + B to hide or show the app window once
  • restart the app and test again
  • on macOS, also re-check Desktop & Dock behavior
The app crashes

If it happens once, restart and try to reproduce it. If it happens consistently, contact support with your OS version, app version, trigger steps, and whether you were using an external display.

Product and usage scope

Are virtual machines or dual-device setups safer than Interview AiBox?

Not necessarily. Virtual machines and dual-device setups come with their own detection risks and are not automatically safer than Interview AiBox. What matters more is whether you rehearsed on the target platform and confirmed that sharing, shortcuts, eye movement, and delivery all feel natural.

Will it work on my network?

Actual availability depends on the local network, proxy, and company or campus restrictions. Before the real interview, use the same network to sign in, generate one answer, and test both voice and sharing.

Does stealth mode mean every platform is always safe?

No. Stealth behavior has real boundaries. OS versions, meeting-app versions, sharing modes, and multi-monitor layouts can all affect the result. The stable path is to review Stealth Mode, then test in self-check tools and on the exact interview platform.

Usage notice

Can I use the same account on multiple computers at the same time?

Do not operate the same account from multiple computers during a real interview. It can create confusing sign-in state, usage displays, or session-sync behavior. Prefer one device that has already passed your self-check.

What is the most important thing to check before a real interview?

If you only have time for a short pass, prioritize these four:

  • sign-in and subscription state are normal
  • Cmd/Ctrl + B, Cmd/Ctrl + Enter, and Cmd/Ctrl + M all trigger correctly
  • capture and voice each complete at least one successful run
  • one minimal rehearsal is done in self-check tools or on the target interview platform

Continue reading

Something missing or unclear?

Tell us which page or step needs work.

Send feedback
FAQ | Interview AiBox Troubleshooting Docs