Reliability — resume interrupted interviews

What users said

• Interviews can be interrupted by small issues: wrong button clicks, internet problems, or minor interferences.

• Once paused, there was effectively no working resume flow.

• This was especially important because internet instability is a practical constraint in their environment.

Underlying requirement

• Interview sessions must be recoverable from interruption without losing context, progress, answers, or user confidence.

Implementation guidance for LLM agents and product systems

• Persist state after every user turn:

  • current question

  • prior answers

  • pending follow-up thread

  • campaign config version

  • timestamp and device/session ID

• Build explicit resume states:

  • resumed after disconnect

  • resumed after accidental pause

  • resumed on new device

• On resume:

  • show short recap of last completed step

  • confirm whether to continue from last question or restart current question

• Add interruption-safe UX:

  • autosave every turn

  • visible “resume interview” CTA

  • avoid invalidating interview on minor navigation mistakes

• Handle partial answers:

  • if answer recording is incomplete, ask whether to retry, continue, or discard

• Add low-connectivity fallback:

  • cache turn data locally until sync succeeds

  • retry uploads in background

Acceptance criteria

• A dropped session can be resumed with prior context intact.

• A user who reconnects does not need to restart the interview.

• Accidental pauses do not destroy interview progress.

• Resume works across low-connectivity conditions.