Hiring managers manually track candidates across pipeline stages, miss follow-up windows, and lose momentum with qualified prospects while spending hours on repetitive outreach instead of evaluation.
Your recruiting pipeline is a funnel with leaks. A candidate sits in "phone screen scheduled" for 10 days. Another passes a technical interview and vanishes into silence for three weeks. Your hiring manager knows this is happening—they just don't have time to fix it. This workflow automates the boring part: flagging when a candidate has been in a stage too long, triggering templated follow-ups at the right moment, and surfacing stalled deals before they go cold. How it works: 1. **Trigger**: A candidate record is created or updated in your ATS (Greenhouse, Lever, Workable, etc.). The workflow checks three signals: application date, last interaction timestamp, and current pipeline stage. 2. **Stage-aware logic**: Different stages have different SLAs. A candidate in "applied" should hear back within 2 days. A candidate in "offer stage" should hear back within 24 hours. The workflow knows the difference and acts accordingly. 3. **Templated outreach**: When a candidate hits the time threshold for their stage, the system sends a pre-written message (email, SMS, or Slack notification to the hiring manager). The message is personalized with candidate name, role, and stage context—not a generic blast. 4. **Stall detection**: If a candidate hasn't moved stages in 14+ days and no outreach has been logged, the workflow flags them for review. A hiring manager gets a weekly digest: "These 7 candidates are stalled. Decide: move forward, reject, or re-engage." 5. **Human approval gate**: Before any outreach goes out, a hiring manager or recruiter reviews and approves the message. This prevents tone-deaf or premature follow-ups. The payoff: Your pipeline stays warm. Candidates don't ghost because they feel forgotten. Hiring managers spend time evaluating, not remembering. And you catch drop-off early—before a strong candidate takes another offer. This workflow is most effective if you have: - An ATS with API access (Greenhouse, Lever, Workable, Bamboo HR) - Clear stage definitions and SLA targets - A small team (2–5 hiring managers) who can review approvals weekly - Templated messaging that doesn't require legal review every time
Trigger: Candidate record created or updated in ATS. Workflow checks: (1) time since last interaction, (2) current pipeline stage, (3) SLA threshold for that stage. If threshold exceeded, trigger approval request.
Read current pipeline stage from ATS. Route to appropriate nurture branch: Applied, Screening, Interview Scheduled, Post-Interview, or Offer.
If stage = Applied: Send templated confirmation email within 2 hours. Include job title, next steps, expected timeline, and link to candidate portal. Log send timestamp.
If stage = Screening: Send email with screening call details (date, time, format), prep tips, and hiring manager name. Include calendar invite link.
If stage = Interview Scheduled: Send interview prep guide, company background, interviewer names/roles, and logistics. Send 24 hours before scheduled interview.
If stage = Post-Interview: Send thank-you message within 4 hours. Include next decision timeline and point of contact for questions. Set follow-up reminder for hiring manager.
Check last activity date. If no update in 7+ days and stage is not Offer or Rejected, flag as stalled and trigger alert.
Send Slack or email alert to hiring manager: candidate name, stage, days stalled, and suggested action (follow up, move to next stage, or close).
Manager reviews stalled candidate alert and decides: send custom follow-up, advance to next stage, or close. Update ATS with decision.
If stage = Offer: Send formal offer letter, benefits summary, and deadline for response. Include hiring manager contact for questions.
Record email send, open, click, and reply events in ATS candidate record. Track which templates drive highest response rates by stage.
1. **Connect your ATS**: Use Zapier, Make, or native API to pull candidate records. Map fields: candidate name, email, phone, stage, application date, last interaction date. 2. **Define stage SLAs**: Create a lookup table. Example: Applied → 2 days, Phone Screen Scheduled → 3 days, Technical Interview Completed → 5 days, Offer Stage → 1 day. Store this in a spreadsheet or config file the workflow can reference. 3. **Write stage-aware templates**: Create 5–7 email/SMS templates, one per stage. Each should acknowledge where the candidate is and what's next. Example for "Phone Screen Scheduled": "Hi [Name], we're excited to chat about the [Role] position on [Date]. Here's the Zoom link: [Link]. Questions? Reply here." 4. **Set up approval gate**: Route all outbound messages to a Slack channel or email inbox where a hiring manager can approve/reject in <2 hours. Include candidate name, stage, days-in-stage, and draft message. 5. **Create stall report**: Weekly digest (Tuesday morning) listing candidates in-stage >14 days with no recent activity. Include action buttons: "Move Forward", "Reject", "Re-engage". 6. **Test with one stage**: Start with "Applied" stage only. Run for 2 weeks, measure approval rate and response rate, then expand to other stages.