Overview #
Journey Completion defines when a Journey is considered finished and what the Candidate sees at the end. Getting this right ensures a clear and professional conclusion to every Journey.
What You Configure #
Completion Rules #
Define the exact conditions that mark the Journey as complete:
- All required Steps must be finished
- Specific Milestones must be reached
- Certain Outcomes must be assigned (e.g., Approved, Completed)
Completion Message #
The final message shown to the Candidate. This should clearly communicate:
- They are done — "Your application has been submitted successfully"
- What happens next — "Our team will review your application within 3 business days"
- Any remaining actions — "You will receive a confirmation email shortly"
After Completion #
What happens after the Journey is marked complete:
- A button to close or return (e.g., "Back to Home")
- Optional follow-up actions (e.g., email notification)
- The Journey status is updated in your system
Best Practices #
- Make completion obvious — The Candidate should clearly understand they are finished
- Be specific about next steps — Avoid generic messages like "Thank you" without context
- Keep it short — A few sentences is enough
- Match the message to reality — If you say "We will contact you within 3 days," make sure you do
- Test completion — Go through the full Journey as a test Candidate to verify the end experience
What to Check Before Going Live #
- Completion triggers are tested for both the normal path and alternative paths
- The completion message accurately describes what happens next
- No required Steps are left incomplete at the end
- The completion status shows correctly in reports and the Dashboard
Common Mistakes #
- Showing "Complete" before all required actions are actually finished
- Using a generic message with no next-step information
- Different Agents having inconsistent completion behaviour
- Not testing the completion flow end to end