Automation for hiring · Runs every Tuesday and Thursday at 09:00
Stalled candidates
Quiet candidate threads flagged with personalized re-engagement drafts. Your assistant runs it every Tuesday and Thursday at 09:00 and tells you when something needs your attention.
Stalled candidates — Sep 15
Automation run • Sep 15
Stalled candidates
Output
Harbor & Pine has two candidate threads that stalled over the past week. Proposed email drafts are waiting in your drafts folder for review.
Stalled candidates
- Ines Calloway (Portland Store Manager): Ines completed a screening call with Lena Vale on September 3. Lena asked for weekend schedule availability on September 7, but no reply has come in.
- Teo Brandt (Senior Ecommerce Engineer): Ezra Holt shared details about the storefront repo on September 8. Teo showed interest in modern web stacks, but scheduling the next conversation has stalled.
Draft in drafts folder
To: Ines Calloway Subject: Following up on Harbor & Pine store manager role
Hi Ines,
I wanted to follow up on your conversation with Lena regarding the Portland Store Manager opening at Harbor & Pine. We would love to discuss the schedule and next steps. Let me know if you have time for a short call later this week.
Best, Juno
Draft in drafts folder
To: Teo Brandt Subject: Next steps for Harbor & Pine engineering role
Hi Teo,
I am checking in following Ezra's note about our engineering stack. We are excited about your background and would like to set up thirty minutes with Ezra to discuss the role. Would Thursday or Friday work for a quick conversation?
Best, Juno
Automation steps. Your assistant follows these 4 steps each time it runs, using your connected email and calendar.
- 01
Twice a week, scan my active candidate threads and flag those who stalled: no reply in a while, a slipped next step, or interest that went dark.
- 02
For each worth reviving, pull where we left off: the role, what they last said, and what they care about.
- 03
Draft a short, warm nudge in my voice that picks up exactly there with a real reason to re-engage.
- 04
Skip hard passes and anyone already moving.
Adjust the automation in chat
Tell your assistant what to do differently and it sets up that version for you.
- Only check candidates who have been quiet for more than five business days.
- Focus only on engineering roles and skip store operations.
- Draft the follow-up notes with a more informal opening.
Results arrive as a message from your assistant. Each run posts to your conversation with your assistant, and can email you too. The automation keeps a log in your knowledge base and reads it before each run to see what has changed.
Adjustable schedule
Runs every Tuesday and Thursday at 09:00 by default. Pick another time when you add it, or ask in chat for a custom schedule.
Only useful reports
When nothing needs attention, the run says so in a line or stays quiet. When there are findings, you get them with a link to the full run.
What it does on its own
Finds stalled candidates and drafts nudges on its own. Every draft waits for you to send. An automated run has no tool that sends, posts, shares, or deletes anything.
This automation reads your email and calendar. Connect Google Workspace or Microsoft 365 to Fieldwork. The automation uses whichever you connect. It also uses your files when connected.
More automations for hiring.
Questions about this automation.
- How do I set this up?
- Open your assistant on the Agents page in Fieldwork, find Stalled candidates in the job library, and choose Add. If Google Workspace or Microsoft 365 is not connected yet, the card prompts you to link it first. It starts on the default schedule of Tuesdays and Thursdays at 9:00 AM, which you can adjust when adding it.
- Does it contact candidates on its own?
- It finds quiet threads and writes nudges on its own, but it never sends messages, replies, or changes your calendar. Every draft waits in your email drafts folder for your personal review and approval.
- Where do the results arrive?
- Results arrive as a message in your conversation with your assistant, and Fieldwork can also email them to you. When no candidates need follow-up, it tells you briefly or stays quiet.
- Can I run this outside the regular schedule?
- Yes, you can ask your assistant in chat to check for stalled candidates at any point. You can also tell your assistant in chat if you want to change days, adjust the timing, or alter how drafts sound.
Security first
No training on your data
Neither we nor our model providers train on your data. Inference runs with zero retention wherever the provider supports it.
Access
Agents only see what the person asking can see. Conversations, files, apps and connections stay private until shared, and admins have no way into conversations.
Encryption and isolation
Data is encrypted at rest and in transit. Each user's code runs in its own microVM, and secrets reach models by name only.
Continuity
Continuous backups, replicated to a second region. Data is exported on request and deleted within 30 days of a contract's end.