Automation for assistants and chiefs of staff · Runs every weekday at 09:00
Warm intro nudges
Introductions that went quiet, with follow-up nudges drafted in the thread. Your assistant runs it every weekday at 09:00 and tells you when something needs your attention.
Warm intro nudges — Sep 14
Automation run • Sep 14
Warm intro nudges
Output
Sol, here is your morning update on warm introductions sent from Google Workspace.
Two introductions have stayed quiet for more than three days. Nudges have been drafted in their existing threads and are waiting in your drafts folder. Nothing was sent.
Warm intro tally
- Tracked introductions: 8
- Replied: 5
- Still open: 3
- Response rate: 63%
| Introduction | Date sent | Days quiet | Status |
|---|---|---|---|
| Maya Calder and Avery Stone | Sep 8 | 6 | First nudge waiting in drafts |
| Lena Vale and Dara Finch | Sep 9 | 5 | First nudge waiting in drafts |
| Juno Pell and Teo Brandt | Sep 12 | 2 | Waiting (under 3 days) |
Drafts waiting in drafts
Thread: Intro: Maya Calder (Harbor & Pine) <> Avery Stone (Quillwork Labs) To: Avery Stone, Maya Calder
Hi Avery,
Following up on my note from last Tuesday to see if you have time for a brief chat with Maya about retail operations. Let us know if this week works for your schedule.
Best, Sol
Thread: Intro: Lena Vale (Harbor & Pine) <> Dara Finch To: Dara Finch, Lena Vale
Hi Dara,
Checking in to see if you and Lena had a chance to connect regarding the store manager opening in Portland. We would love to set up time if you are still open to talking.
Best, Sol
Automation steps. Your assistant follows these 5 steps each time it runs, using your connected email and calendar.
- 01
Each weekday, find the warm introductions I've sent where the other side hasn't replied.
- 02
For each quiet for more than about three days, draft a short, warm nudge in the original thread, never a new email, matching that thread's tone.
- 03
Space the nudges sensibly and stop after a couple.
- 04
Never add people who weren't on the thread, and skip any where a reply is in motion.
- 05
Keep a tally: sent, replied, still open, and the response rate.
Adjust the automation in chat
Tell your assistant what to do differently and it sets up that version for you.
- Wait five days instead of three before drafting a nudge.
- Do not draft nudges for recruiting candidate introductions.
- Stop preparing nudges after one follow-up on a thread.
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 weekday 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
Drafts nudges and tracks replies 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.
More automations for assistants and chiefs of staff.
Questions about this automation.
- How do I set this up?
- Open your assistant on the Agents page in Fieldwork, locate Warm intro nudges in the job library, and click Add. You will be prompted to connect Google Workspace or Microsoft 365 if your account is not linked yet. It runs every weekday at 9:00 AM, and you can edit this schedule during setup.
- Can this automation send nudges on its own?
- No, it cannot send emails, post messages, or alter your threads. It only writes follow-up drafts that wait in your mailbox drafts folder for you to review and send.
- Where do my results arrive?
- Summaries appear directly in your Fieldwork chat each weekday morning and can be sent to your email inbox as well. If there are no stalled introductions to review, your assistant will either send a brief confirmation or stay quiet.
- How does it detect whether someone already replied?
- Your assistant checks the existing email thread in Google Workspace or Microsoft 365 before preparing anything. If anyone on the thread replied or if a conversation is already underway, it marks the introduction as replied, updates your tally, and skips drafting.
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.