Before you start
- If you don’t see these controls, contact your dedicated CS Manager or support@heymilo.ai (or in-app chat).
- Candidates to use a current browser; allow camera and microphone when prompted (needed for video-based signals).
Browsers (keep updated): Chrome (best tested), Edge, Firefox, Safari (macOS/iOS). Other Chromium-based browsers (Brave, Opera, Arc, etc.) usually work. Internet Explorer is not supported.
1) Workspace default (usual starting point)
Path: Sidebar → Interviewers → Tools → Interview Integrity
Use this when you want one default across interviews.
Settings
- Enable Cheat Detection: Workspace-wide on/off for interviews that use these defaults.
- Detection Threshold (0–100): How strict flagging is. Lower = fewer flags; higher = more. A practical starting point is ~70.
- Detection Types: Which signals to monitor (see below). Use Select All / Deselect All.
Click Save Settings.
2) Per interviewer (override)
Path: Create or Edit Interviewer → Voice/Video (web interview) workflow step → Settings (cheat detection section)
You can use the workspace default (V1) settings here, or toggle on Enable Cheat Detection V2 (Beta) to use the newer detection service for this interviewer only. V2 replaces the legacy detection flow for that posting and exposes tunable sliders instead of a single threshold.
V2 Global Thresholds
| Setting | What it controls |
|---|
| Max Alerts Per Breach | How many alert events can be recorded per breach (1–10). |
| Minimum Continuous Breach Duration | Minimum seconds a signal must persist to count as a breach (0–60s). |
| Type | What it’s looking for |
|---|
| External Voice Assistance Detected | A non-candidate voice speaking during the candidate’s answer window (whispered prompts, off-screen guidance, third-party conversation). Tunable via Speaker-Cluster Distance Threshold (0.1–1.5). |
| Covert Response Sync Pattern | A pause-then-cue-then-immediate-answer pattern repeated across questions. Tunable via Max Acceptable Response Delay (1–60s). |
| Type | What it’s looking for |
|---|
| Synthetic Response Generation Suspected | AI-generated answer text. Whole-paragraph AI probability compared against a threshold. Tunable via AI Text Probability Threshold (0–1). |
| Paraphrased Response Suspected | AI-rephrased candidate answers. Tunable via Paraphrased Text Probability Threshold (0–1). |
Detection types (V1 workspace default)
These apply when V2 is not enabled. Signals are observational — they indicate something looked unusual, not intent.
| Type | What it’s looking for |
|---|
| Facial Behaviour | Sustained or repeated looking away from the screen (e.g. notes or another display). |
| Multiple People | More than one person visible in frame during the interview. |
| Phone Detection | A mobile device appears in view. |
| AI/Scripted Answer | Answer patterns that resemble scripted or AI-like structure/timing (heuristic, not proof). |
| Unusual Delays | Long or inconsistent pauses that may suggest off-screen help or lookup. |
| Tab Switching | Candidate leaves the interview tab/window during a response. |
Reviewing results
Path: Interviewers → [candidate] → Verify
Open Cheat Detection Overview. You will see:
- Risk level: Overall assessment with a recommended action (Reject or Further Review).
- Total Breaches: Number of flagged events in the session.
- % Compromised: Share of the session where signals were detected.
- Categories Triggered: Which detection types were activated.
- Severity Breakdown: High, medium, and low signal counts with percentage of session and duration for each.
- Cheating Timeline: A visual timeline of when flags occurred across the interview.
- By Category: Category name, severity, breach count, percentage of session, and duration.
- Breach Details: For each breach, timestamp range, severity, confidence percentage, recommended action, the candidate’s original response, and sentence-level analysis.
How to read confidence
- High confidence: Worth a careful look, not confirmation of cheating.
- Medium confidence: Check context, such as question difficulty, nerves, or environment.
- Low confidence: Often lighting, angle, movement, or a one-off glitch.
Patterns beat single events: repeated signals across several categories, or spikes on hard questions, matter more than one isolated low-confidence flag.
What cheat detection does not do
- Does not auto-fail or auto-advance candidates
- Does not raise or lower the interview score
- Does not replace recruiter judgment
- Does not use biometrics for “identity” decisions in the sense of facial recognition hiring outcomes—think behavioral / environmental signals for review
Flags are informational. Always pair them with transcript, answers, and video context before conclusions.
Best practices
- For V1: start near threshold 70, then tune up or down based on noise levels.
- For V2: start with default slider values, then adjust individual thresholds if a specific category is generating too many or too few flags.
- Only enable detection types you will actually review.
- Give candidates clear setup instructions (quiet room, stable camera, good light, supported browser).
- Align as a team on how you interpret flags so decisions stay consistent.
Troubleshooting
| Issue | What to check |
|---|
| No cheat detection data | Feature disabled; interview very short; camera/mic denied; unsupported browser. |
| Too many flags (V1) | Lower the Detection Threshold; improve candidate instructions and environment. |
| Too many flags (V2) | Raise the AI Text Probability or Paraphrased Text Probability threshold; increase the Minimum Continuous Breach Duration. |
| Weird inconsistency | Browser updates; lighting; camera placement; connection quality. |
Next steps
Help: support@heymilo.ai or in-app chat. 
