Automation for hiring · Runs every Monday, Wednesday, and Friday at 09:00
Intro follow-through
A reply tally and drafted nudges for quiet email introductions. Your assistant runs it every Monday, Wednesday, and Friday at 09:00 and tells you when something needs your attention.
Intro follow-through — Sep 14
Automation run • Sep 14
Intro follow-through
Output
Two introduction threads are quiet past four days. I drafted one follow-up in your Google Workspace drafts folder for review. Nothing was sent.
Running introduction tally
- Introductions sent: 12
- Replies received: 9
- Reply rate: 75%
| Candidate | Role | Introduced to | Date sent | Status |
|---|---|---|---|---|
| Dara Finch | Store Manager | Lena Vale | Sep 8 | Quiet (6 days) |
| Teo Brandt | Senior Ecommerce Engineer | Ezra Holt | Sep 9 | Quiet (5 days) |
| Leo Marsh | Store Manager | Lena Vale | Sep 10 | Replied Sep 11 |
| Ines Calloway | Senior Ecommerce Engineer | Ezra Holt | Sep 11 | Replied Sep 12 |
Dara Finch has already received two follow-ups without an answer, so no further draft was created.
The draft below is waiting in your email drafts folder for the thread with Teo Brandt and Ezra Holt.
Draft nudge to Teo Brandt and Ezra Holt
Hi Teo and Ezra,
Following up on my note from September 9 connecting the two of you. Ezra is leading the search for Harbor & Pine's senior ecommerce engineer position and would love to compare calendars for a brief introductory call this week. Please let us know if your schedule allows.
Best, Juno
Automation steps. Your assistant follows these 3 steps each time it runs, using your connected email and calendar.
- 01
A few times a week, check the introductions I've sent for replies.
- 02
For those quiet for more than a few days, draft a short, friendly nudge in the original thread, never a new email, and stop after a sensible number of tries.
- 03
Keep a running tally: intros sent, replies or interest, and the reply rate, so I can see which kinds land.
Adjust the automation in chat
Tell your assistant what to do differently and it sets up that version for you.
- Only follow up on candidate introductions after five days of silence.
- Stop drafting nudges after one attempt instead of two.
- Separate the reply tally by hiring manager.
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 Monday, Wednesday, and Friday 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
Tracks replies and drafts nudges on its own. Every nudge 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.
More automations for hiring.
Questions about this automation.
- How do I set this up?
- Open your assistant on the Agents page in Fieldwork, locate this automation in the job library, and click Add. If your email is not connected yet, the card will prompt you to connect Google Workspace or Microsoft 365 before starting on its Monday, Wednesday, and Friday schedule at 9:00 AM.
- Does it send follow-ups on its own?
- No. It monitors your threads for replies and saves proposed nudges directly into your drafts folder. It can never send an email, alter your calendar, or message anyone on its own.
- Where do the tallies and drafts appear?
- Results arrive as a message in your conversation with your assistant, and can also be emailed to you. When all introductions are answered and no draft is needed, it says so briefly or stays quiet.
- How does it decide when to stop nudging a contact?
- It checks the message history in the original email thread and stops creating drafts once a thread reaches two follow-up attempts. It also stops immediately as soon as anyone on the thread replies.
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.