Resolve access failures, launch issues, and workflow blockers before escalating.
Candidate cannot open the portal or interview
Use the original workflow path first, validate the stage and access state second, and escalate only after you capture the failing route, timestamp, and visible symptoms.
- Confirm the invite link, token scope, and interview window.
- Verify the candidate is attached to the intended role and stage.
- Resend one clear re-entry path rather than creating duplicate sessions immediately.
- Escalate with candidate identifier, route used, timestamp, and exact error text if the first-path retry still fails.
Interview results or scoring look inconsistent
Use the original workflow path first, validate the stage and access state second, and escalate only after you capture the failing route, timestamp, and visible symptoms.
- Check whether the session completed fully before interpreting results.
- Compare the outcome against role criteria, priority signals, and red flags.
- Hold progression until the team can validate whether the issue is evidence quality or workflow state.
- Escalate only after you capture what stage was running, what looked inconsistent, and which decision was blocked.
Live interview scheduling or room launch fails
Use the original workflow path first, validate the stage and access state second, and escalate only after you capture the failing route, timestamp, and visible symptoms.
- Work from the original workflow context first.
- Confirm the session owner, meeting route, and participant readiness.
- Retry the original room context before generating replacement paths.
- Escalate with role name, candidate or session context, timestamp, and the exact step where the failure occurred.