Illustrative idea · CANDIDATE EXPERIENCE
Coordinate a permission-aware follow-up plan
Keep every planned contact within the candidate’s preferences and the hiring team’s review rules.
Keep candidate contact timely, measured, and permission-aware.
Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.
Work through candidate outreach that has already been planned and approved. Respect each person’s local contact window, apply sending limits, and keep opt-outs and delivery outcomes connected to the campaign record.
Actual availability depends on published steps, supported connections, permissions, and provider approval.
Approved outreach dueA candidate contact task with its approved channel, timing, and message context
“Send due text or voice outreach according to the candidate’s approved sequence, while observing contact permissions, quiet hours, and retry limits.”
Work through the request.
Clear tasks, with review where it matters.
- Review contact tasks that are due
- Check permission and contact limits
- Respect local contact hours
A recorded contact attempt with the next eligible step scheduled when appropriate, or the sequence stopped for an opt-out or permanent failure.
What this workflow could do
Reviews due candidate contact tasks, selects the planned text or voice action, respects local quiet hours and weekend rules, and records the result with controlled retry handling.
Review points proposed in this idea
Only contact candidates with documented permission for the planned channel and purpose. Honor opt-outs immediately, apply quiet hours and contact caps, and require human review of enrollment and message content before sending begins.
How the idea could work
Select an illustrative task to explore its proposed role. No workflow runs here.
-
Gather approved candidate outreach tasks that have reached their planned contact time.
-
Confirm the candidate is not opted out and the planned attempt stays within the agreed sequence and sending cap.
-
Use the candidate’s local quiet hours and weekend rules to determine whether contact should wait.
-
Send the approved text or begin the approved voice contact using the context selected for that candidate.
-
Keep a record of each attempt and update the next planned contact based on whether the result was successful, temporary, or final.
-
Record a valid opt-out and suppress future outreach to that candidate.
Step 1 of 6
Review contact tasks that are due
Gather approved candidate outreach tasks that have reached their planned contact time.
Proposed setup considerations
These are planning notes for the concept, not instructions for a currently available template.
- 01
Prepare outreach records and sequence rules
Define the candidate contact tasks, approved messages, channels, and next steps for each campaign.
- 02
Set permission and suppression records
Choose how consent, opt-outs, contact history, and active enrollment are recorded and checked before every attempt.
- 03
Choose quiet hours and sending caps
Set candidate-local time rules, weekend handling, per-period limits, and how temporary failures are retried.
- 04
Test before contacting candidates
Review a safe test route and verify enrollment approval, message content, opt-out handling, and outcome records before live use.
Read the prelaunch status
Published templates and verified customer availability remain pending.
A little help with the whole task
A little less busywork.
A little less busywork.
A little more room for you.
Explore the sample experience while launch details are being finalized.
View pricing status Explore the simulation