Scheduling / asynchronous interview delivery

3. Scheduling / asynchronous interview delivery

Priority: High

What users said

• Chantel said the scheduled interview did not produce the prompt at the intended time.

• She said there was no way to return to that scheduled slot.

• Because of this, she never managed to do the scheduled interview and had to switch to a live session.

• Eric reportedly had the same issue.

Underlying requirement

• Scheduled interviews must reliably trigger and remain accessible even if the recipient misses the original moment.

Implementation guidance

• Treat schedule time as:

  • preferred start time, not single-use expiry

• Add durable scheduled-session objects:

  • pending

  • available

  • started

  • paused

  • completed

  • expired

• If a prompt is missed:

  • keep the interview accessible from link/dashboard

  • offer “start now” and “reschedule”

• Send redundant reminders:

  • at scheduled time

  • grace-period reminder

  • recovery reminder if not opened

• Log delivery failures separately from user no-shows

• Expose clear status:

  • “Your interview is available”

  • “Scheduled time passed; you can still complete it”

• Ensure timezone handling is explicit

Acceptance criteria

• Missing the scheduled time does not make the interview inaccessible.

• Users can re-enter the scheduled interview later.

• Prompt delivery failures are visible and diagnosable.

• Scheduling works for multiple users consistently.