Keep the Hiring Pipeline Moving
By the end of this recipe, no strong candidate will quietly stall in your hiring pipeline — the moment someone sits too long in a stage, Copera nudges the recruiter who owns them with a specific next step, and the board keeps itself current every time a candidate advances. Because your hiring board and your team chat live in one workspace, the automation can spot the stuck candidate and reach the right person directly, instead of waiting for someone to notice at the weekly hiring sync.
Readiness: Available now (built as two Automations). The version where a named recruiting teammate watches the whole pipeline and keeps it moving on its own is rolling out in early access.
What it does
Good candidates are lost the same way deals and tasks are: to silence. A promising applicant lands in Screening and sits for a week. An interviewer never gets scheduled. An offer waits on an approval nobody chased. By the time someone notices, the candidate has taken another job. This recipe makes that stall impossible to miss — and takes the manual busywork out of every stage change.
It runs as two small automations that reinforce each other:
- Keep the board current. Every time a candidate's Stage changes, an automation stamps the date they entered the new stage, then branches on where they moved to fire the right follow-ups — assign the interviewer, notify the hiring manager, draft the candidate's next-step email, or celebrate a hire in the channel.
- Never let a candidate stall. A second automation watches that stage date. If a candidate has been sitting in the same stage past your threshold — say, four days — it drafts a short, specific nudge and direct-messages the recruiter who owns them with the candidate's name, how long they have waited, and the obvious next step.
One important thing stays true throughout: a person always decides who advances. The automation never silently pushes a candidate from Screening to Offer — hiring calls belong to humans. What it does is make sure nobody stalls, and handle all the follow-through the instant you move someone. Hired and rejected candidates are skipped, so no one is ever nudged about a closed candidate.
Build it yourself
Two automations do the whole job: a stage-change keeper that fires the right follow-ups whenever a candidate moves, and a stall nudger that reads the stage clock the keeper stamps. Both live in Automations.
Before you start
On your hiring board, give each candidate row the fields the automations read:
- A Stage field (single-select) with your pipeline: Applied, Screening, Phone screen, Onsite, Offer, Hired, Rejected.
- A Stage entered date field — stamped automatically below; this is the signal the nudger runs on.
- An owning Recruiter (a people column) — this is who gets nudged.
- A Hiring manager (a people column) — notified on the key moves.
- A Candidate email field, so outreach can be drafted from the row.
That is the whole setup — one row per candidate. See Creating a Board if you are building it from scratch, and let new applicants flow on automatically (see the tip at the end).
Automation 1 — keep the board current
This one fires on every stage change and does the follow-through, so the board and the people who care about it are always up to date.
Add a Field changed trigger watching the Stage column, so the automation runs every time a candidate moves from one stage to the next.
Add a Set date to now action on the Stage entered date. This restamps the stage clock on every move — and it is what re-arms the stall nudger in Automation 2 for the new stage. (Prefer to track it as a timer? Add an SLA timer control action to stop the previous stage's timer and start a new one, and skip ahead to SLA Tracking.)
Add a condition using a changed from → to check to branch on the destination stage. Different moves deserve different follow-ups, and this splits the flow so the right ones fire.
On each branch, add the actions that keep that move moving. A useful default set:
| Moved to… | Actions on that branch |
|---|---|
| Phone screen or Onsite | Assign user(s) to add the interviewer, Send notification to the interviewer and hiring manager, and Send email (as a draft) with the scheduling invite for the recruiter to review. |
| Offer | Send direct message to the hiring manager to kick off approval, and Create document to start the offer letter from a template. |
| Hired | Post channel message in your hiring channel to celebrate the win, and Update linked row to mark the open requisition filled. Then hand off to onboarding. |
| Rejected | Send email (as a draft) with a kind, on-brand rejection for a recruiter to review before it sends. |
Every candidate-facing email stays a draft so a person signs off before it reaches the applicant — see the Tips below.
Assign, notify, and draft in one move. The value here is that a single stage change fans out into everything that should happen next — the interviewer is on the row, the hiring manager knows, and the email is written and waiting for a quick review — instead of five manual steps a busy recruiter has to remember.
Automation 2 — nudge candidates that stall
Automation 1 keeps the Stage entered date fresh. This one reads it and makes sure nobody sits too long.
Add a Date reached trigger on the Stage entered field with an after offset — for example, 4 days after. This fires for a specific candidate exactly four days after they entered their current stage. Because Automation 1 restamps that date on every move, the timer automatically re-arms for each new stage. (You can also use the "N days after last comment" option if your team tracks activity as comments on the candidate row.)
Add a condition (a row filter) so the flow only continues when the candidate is still in play — Stage is not Hired and not Rejected. No one wants a nudge about a candidate who already crossed the line either way.
Add an AI → Generate step that writes a short, specific message from the candidate's fields — their name, the stage they are stuck in, how long they have waited, and the obvious next step. Prompt it for tone: "Write a brief, friendly nudge the recruiter can act on in a minute."
Add a Send direct message action to the candidate's Recruiter, including the drafted nudge and a link to the row: "⏳ Dana has been in Phone screen for 4 days — here's the next step." Prefer a lighter touch? Swap in a Send notification for an in-app ping instead of a DM.
Prefer one morning digest to per-candidate pings? Swap the trigger for a Schedule (say, 8:30 AM daily) and open with a Find rows action that returns every active candidate whose Stage entered date is more than four days ago, then a For each loop over them. Add an AI → Summarize step and a Post channel message action to drop a single "here's who's waiting" digest into your hiring channel. Same filtering you already use on views, run as one sweep.
Or just ask Copera AI
You do not have to build either graph by hand. Open Ask Copera AI and describe the whole thing:
"Create a Hiring board with a row per candidate — columns for Stage (Applied, Screening, Phone screen, Onsite, Offer, Hired, Rejected), the recruiter who owns them, the hiring manager, a Stage-entered date, and the candidate's email. Then build an automation that stamps the Stage-entered date whenever a candidate's stage changes, assigns the interviewer, and notifies the hiring manager. And build a second automation that DMs the owning recruiter whenever a candidate has sat in the same stage for more than four days, with a suggested next step."
Ask Copera AI can create the board and its columns, then assemble both automations for you. With the default Ask before acting permission mode, it shows a review card for each change before anything is created — so you approve the board setup and each automation before it exists. See What Copera AI Can Do for the full set of actions it can take, and ask it any day for the state of play: "Which candidates have been stuck in the same stage the longest?"
Make it a standing teammate
Standing AI teammates are rolling out gradually. When one reaches your workspace, a named recruiting coordinator can own this beat across the whole board: watch for candidates sitting too long, draft each nudge, DM the owning recruiter, and keep the board current as people move — on its own schedule and under its own identity. A teammate handles the internal side (reading the board, posting to channels, messaging recruiters, updating rows); candidate-facing email still runs through the automation's draft step, since teammates never send outside your workspace or delete data. Until a teammate is available, the two automations above do exactly this today — everything in this guide can be built now as an Automation.
Tips
Keep a human on anything the candidate sees. Interview invites, offer emails, and rejections should always run as a draft or approval delivery step so a recruiter reviews the wording before it leaves the workspace. The automation moves fast; a person still signs off on the message that goes out under your name.
Tier your thresholds by stage. A candidate quiet for four days in Applied is not the same as four days in Offer, where a slow reply loses the hire. Duplicate the nudger with a tighter window for late-stage rows — one day past Offer — so the candidates closest to the finish line get chased first.
Let applicants flow onto the board on their own. New candidates can land as rows automatically: a Form submitted trigger from a public application form, an Inbound webhook from your applicant tracking system, or an email received trigger with an AI → Extract step that pulls the name, role, and contact into a new row. A current board is what makes the stall detection trustworthy.
Fold interview debriefs back onto the candidate. Run the interview in a meeting channel and, when the transcription completes, an automation can summarize the debrief and attach it — or the agreed next steps — to the candidate's row, so the decision to advance is made with the panel's notes in front of you.
Set a spend cap. Because the nudger drafts a message per stalled candidate, give the automation a per-automation spend cap so a heavy hiring week can never run past a budget you choose. The usage dashboard shows exactly where credits go.
Frequently Asked Questions
How does Copera keep candidates from stalling in the hiring pipeline?
It stamps the date each candidate enters a stage, then a Date reached trigger fires a few days later if they are still in that stage. An AI → Generate step drafts a short, specific nudge and a Send direct message action delivers it to the recruiter who owns the candidate — so no one waits in Screening because everyone assumed someone else had it.
Does the automation move candidates through stages on its own?
No. A person always decides who advances. The automation makes sure nobody stalls by nudging the owner, and it does the busywork the moment a human moves a candidate: stamping the new stage date, assigning the next interviewer, notifying the hiring manager, and drafting the candidate's next-step email for review.
How does the hiring board stay current when a candidate advances?
A Field changed automation watches the Stage column. Every time a candidate moves, it stamps the Stage-entered date to now, branches on the destination stage, and fires the right follow-ups — assign an interviewer, notify the hiring manager, draft an email, or post a celebration when someone is hired.
Can it draft the emails candidates receive?
Yes. An AI → Generate step drafts the next-step, interview-invite, or rejection email from the candidate's context. Keep candidate-facing email on a draft or approval delivery step so a recruiter reviews and edits before anything leaves the workspace.
How do new applicants get onto the hiring board?
One row per candidate. New applicants can land automatically: a Form submitted trigger from a public application form, an Inbound webhook from your applicant tracking system, or an email received trigger with an AI → Extract step that pulls the name, role, and contact into a new row.
Related
- Automations — the field-changed, date-reached, condition, and AI-generate blocks this recipe is built from
- What Copera AI Can Do — surface stuck candidates and draft outreach on demand
- An AI Onboarding Buddy for New Hires — the natural next step once a candidate is hired
- Catch Blocked and Stale Tasks Automatically — the same stall-detection pattern applied to project work
- SLA-Breach Watchdog — put a stage timer on each candidate and auto-escalate when it breaches
- What You Can Build with Copera AI — the full playbook