Candidate updates
Keep candidates informed about the next step.
- Candidates do not know when the stage changes or what happens next.
Example paths: the agreed action or human review. This diagram does not run on your live data.
- 01Input: New stage.
- 02A stage change prepares a message from an approved template; exceptions go to the recruiter.
- 03Output to verify: To candidate.
- 04Exceptions go to staff; permitted actions are agreed before launch.
- ✓The message matches the confirmed stage and approved template.
- ✓We check repeated processing and connection failures using agreed examples.
An illustration of the logic, not a customer case. Connections and results are agreed before implementation.
What inputs do we need?
We need an example of “New stage”, processing rules and an owner for “To candidate”. Access is requested after connections are agreed.
What happens if data is missing or an error occurs?
We check “Stage confirmed?”. Exceptions go to staff; permitted actions are agreed before launch.
How is the result accepted?
The message matches the confirmed stage and approved template.
How long does implementation take?
Scope, price and timing are defined after checking systems, access and exceptions. This page describes a possible workflow, not a ready connection to your data.
Other automations
Document preparation
Draft contracts, acceptance records and letters from approved templates.
View details →HRInitial candidate interviews
Run an initial conversation and prepare a factual summary for the recruiter.
View details →SALESEnquiries from every channel
Bring website, email and messaging enquiries into one sales queue.
View details →