How to use this checklist
Before starting a session, go through this checklist from top to bottom. The goals are:
- The session can start successfully.
- Transcripts can continue to appear.
- Answers can trigger as expected.
1. Account and resource status
- The account is signed in and APIs are reachable.
- Remaining voice minutes are sufficient.
- There is no old session stuck in an abnormal active state.
2. Input and permissions
- Microphone is enabled and can capture audio normally.
- If interviewer audio needs to be recognized, system audio is enabled.
- Browser and system permissions have been granted: microphone and screen sharing.
Key point: when using system audio, you must tick "share system audio / tab audio" in the sharing dialog.
3. Session configuration
- Answer language is confirmed: Chinese / English.
- Speech model is selected.
- Auto-answer strategy is confirmed: on / off.
- Knowledge-base toggle matches the goal of this session.
4. First 30-second validation after launch
After starting, use 30 seconds for a quick check:
- Say one sentence and confirm that the transcript appears on the left.
- Trigger one answer automatically or manually.
- Check whether the answer is readable and relevant.
If any step fails, do this first: stop -> check permissions and sharing -> restart the session.
5. Frequent failures and immediate handling
Cannot hear interviewer audio
- Start sharing again.
- Tick system audio.
- Confirm that the audio source is not a muted device.
Only your own voice is recognized
The system audio stream is not connected. Usually the audio checkbox was not selected during sharing.
Start fails immediately or interrupts quickly
Check these first:
- Browser permission is blocked by the system.
- Input device changed and needs authorization again.
- Old session status did not converge correctly.
6. Practical advice
- Complete at least one full rehearsal before a formal interview.
- Record the trigger condition for each abnormal case so you can avoid it next time.
- For frequent real use, use the desktop client for a more stable experience.
Related docs: