Automation for sales · Runs after a meeting is transcribed
Post-demo follow-up
A tailored summary document and follow-up email after every sales call. Your assistant runs it after a meeting is transcribed and tells you when something needs your attention.
Post-demo follow-up — Sep 17
Automation run • Sep 17
Post-demo follow-up
Output
Here is the recap from your call with Bram Ives at Kestrel & Finch today at 10:30 AM Portland time. The follow-up email is waiting in drafts in Google Workspace, and the customer recap document is proposed below for your review.
Meeting summary
- Attendees: Cal Brook (Harbor & Pine), Bram Ives (Kestrel & Finch).
- Stated goals: Stock regional apparel and home goods for their upcoming retail season.
- Pain points: Previous vendors delivered late and offered inconsistent knit quality.
- Discussed products: Cascade Merino Crew ($118 retail) and Alder Wool Throw ($158 retail).
- Deal context: Target order aligns with the $9,600 deal size noted in HubSpot.
- Agreed next steps: Cal sends product details and wholesale terms by Friday. Bram reviews line sheets with his buying team on Monday.
- Inferred versus stated: Bram explicitly asked for delivery guarantees. The assumption that they need counter display fixtures was inferred from store footprint notes, as Bram did not mention fixtures directly.
Email draft (waiting in drafts)
Subject: Harbor & Pine follow-up and next steps
Hi Bram,
Thank you for sharing Kestrel & Finch's retail plans today. Below is a summary of what we covered, including production timelines and order minimums for the Cascade Merino Crew and Alder Wool Throw collections.
Take a look and let me know if this lines up with your initial $9,600 order plan, and we can finalize terms.
Best, Cal
Proposed recap document
- Target assortment: Cascade Merino Crew and Alder Wool Throw.
- Fulfillment: Standard wholesale dispatches from Portland Warehouse.
- Next review: Follow-up check scheduled for Monday after your internal review.
Automation steps. Your assistant follows these 4 steps each time it runs, using your connected email and calendar.
- 01
When a sales call's transcript is ready, pull out the prospect's goals, pains, the use cases they cared about, objections, who was there, and the agreed next steps.
- 02
Write a short, customer-ready follow-up document tailored to them: what we discussed, how we address their specific pains, relevant proof points, pricing or next steps if they came up, and a clear call to action.
- 03
Draft a short email in my voice to send with it.
- 04
Flag what you inferred versus what was actually said.
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 where external prospects attended.
- Include a wholesale pricing tier table in the customer recap document.
- Exclude deal amounts from the internal summary when no pricing was mentioned.
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
Creates the follow-up document and drafts the email. Both wait for you to review and 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, CRM when connected.
More automations for sales.
Questions about this automation.
- How do I set this up?
- Open your assistant on the Agents page in Fieldwork, locate Post-demo follow-up in the job library, and choose Add. If Google Workspace or HubSpot are not connected yet, the setup card prompts you to link them first.
- Does it send the follow-up email on its own?
- No, it leaves the email draft waiting in your Google Workspace drafts folder and presents the summary document in your chat. It never sends emails, contacts prospects, or edits records on its own.
- Where do my follow-up summaries arrive?
- Results appear as a message in your conversation with your assistant and can also be emailed to you. When a recorded call contains no actionable sales discussion, it stays quiet.
- How does it identify what was inferred versus what was stated?
- It checks transcript text from Fieldwork against your CRM records to verify direct quotes. Any assumed buyer motivations or unconfirmed product needs are labeled under inferred points so you can edit them before sending.
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.