Automation for sales · Runs after a meeting is transcribed
Client call follow-up
Follow-up emails with agreed next steps, drafted right after client calls. Your assistant runs it after a meeting is transcribed and tells you when something needs your attention.
Client call follow-up — Sep 17
Automation run • Sep 17
Client call follow-up
Output
Cal, your follow-up email to Noor Hale at Driftline Supply Co is ready and waiting in your Google Workspace drafts.
We matched this call to the open Driftline Supply Co deal ($18,400, proposal sent) in HubSpot.
Summary of call
- Reviewed the $18,400 opening wholesale order proposal for Harbor & Pine goods.
- Noor confirmed interest in stocking the Cascade Merino Crew and Alder Wool Throw for fall.
- Noor requested size breakdowns for tops and payment terms clarification.
Agreed next steps
- Cal: share standard net 30 terms and size run recommendations by Friday.
- Noor: confirm final unit counts and delivery preferences by next Tuesday.
Draft email waiting in drafts
Subject: Harbor & Pine wholesale proposal follow-up
Hi Noor,
Thank you for your time today. It was great walking through the $18,400 opening wholesale proposal for Harbor & Pine.
As discussed, I will send over our standard net 30 wholesale terms and recommended size breakdowns for the Cascade Merino Crew by Friday. Once you review those with your team, please let me know your final unit counts for the apparel and the Alder Wool Throw.
Looking forward to partnering with Driftline Supply Co this fall.
Best, Cal
Automation steps. Your assistant follows these 4 steps each time it runs, using your connected email and calendar.
- 01
When a client call's transcript is ready, draft my follow-up email in my voice: what we covered, the agreed next steps, and anything I asked the client for.
- 02
Address it to the right client and engagement, and never mix in details from another client's call.
- 03
If you aren't certain which client or thread it belongs to, say so instead of drafting.
- 04
Keep it concise, warm and direct.
Adjust the automation in chat
Tell your assistant what to do differently and it sets up that version for you.
- Only draft follow-ups for calls linked to open deals in HubSpot.
- Include bullet points for client action items in every email draft.
- Keep follow-up email drafts under 150 words.
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.
What starts this automation
Runs after a meeting is transcribed.
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 the follow-up email after each call. 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 CRM, meeting notes when connected.
More automations for sales.
Questions about this automation.
- How do I set up this automation?
- Open your assistant on the Agents page in Fieldwork, find this automation in the job library, and click Add. If your email account or CRM is not connected yet, the card prompts you to link them before starting.
- Does the assistant send the email to the client directly?
- No, it never sends messages, replies to anyone, or alters your calendar. It creates a draft and places it into your email drafts folder so you can review, edit, and send it yourself.
- Where will I see the summary and draft?
- Results arrive as a message in your conversation with your assistant in Fieldwork, and can also be emailed to you. The drafted message will be waiting in your connected email drafts folder at the same time.
- What happens if a call cannot be matched to a specific client?
- If the assistant cannot identify the right client or CRM record with confidence, it will not guess. It lets you know in chat that matching information was missing and asks for clarification instead of drafting an email.
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.