Overview #
Journey Completion defines when a candidate journey is considered finished and what the candidate sees at the end.
Completion components #
Completion criteria #
The exact conditions required to mark the journey complete.
Completion messaging #
Title and body content displayed on final confirmation.
Post-completion handling #
What happens after completion:
- Continue CTA behavior
- Return path behavior
- Optional downstream notifications/actions
Design guidance #
Make completion deterministic #
Completion should be based on explicit conditions, not inferred assumptions.
Keep confirmation concise #
Candidate should clearly understand:
- They are done
- What to expect next
- Whether further action is required
Align completion with business state #
“Completed” in UI must match internal operational meaning.
Validation checklist #
- Completion triggers tested on happy and edge paths
- Completion message reflects actual next steps
- No hidden unfinished mandatory actions
- Analytics/reporting marks completion consistently
Common mistakes #
- Showing “complete” before all required actions are finalized
- Generic completion copy with no next-step expectation
- Inconsistent completion logic across similar agents