Send the meeting follow-up email, then keep the work moving.
steer can use the completed meeting record to assemble the recap, proposed action items, a follow-up draft, and the next check-in—while keeping creation, sending, and monitoring as separate operations.
Meeting follow-up automation is a post-meeting workflow that turns the transcript and decisions into a reviewed recap, trackable action items, an email draft, and an optional later check. It should preserve the source and require the right authorization before external actions.
Meeting follow-up example: a customer onboarding review.
After a customer onboarding review, steer prepares the decision recap, places two confirmed actions in Focus, drafts the attendee email from the meeting record, and keeps the unresolved migration date available for the next configured check.
A meeting follow-up email template for a small group.
Use this when a few people agreed on next steps. Subject: “Follow-up: [meeting name], [date]”. Body: “Thanks for the time today. We agreed: [decision one]; [decision two]. Next steps: [owner], [action], by [date]. Still open: [question]. Tell me if I have any of this wrong.” The last line matters. A follow-up email after a meeting becomes the record people are held to, so invite corrections while memories are fresh. steer fills the brackets from the transcript and leaves a gap where nothing was actually agreed.
A meeting recap email template for a wider audience.
When the email goes to people who were not in the room, lead with the outcome. Subject: “Recap: [meeting name], decisions and owners”. Body: “Summary: [two sentences on what changed]. Decisions: [list]. Action items: [owner, action, date]. Risks and open questions: [list].” Keep the discussion and background out of the email and point readers to the notes instead. steer can build this recap from the meeting summary, with the source meeting still linked on your side for anyone who asks about a detail.
A follow-up email after a conference or networking conversation.
There is no shared agenda to recap, so anchor the message in what you discussed. Subject: “Good to meet you at [event]”. Body: “I enjoyed our conversation about [topic]. You mentioned [specific point]; here is [the link, introduction, or document I promised]. Would [specific next step] on [date] work?” Send it within a day or two. If you captured the conversation or dictated a voice note afterward, steer can draft the follow-up email after a conference from what was actually said. For more situations, see our ten follow-up email examples.
A meeting follow-up email example, drafted from the record
Illustrative draft using fictional project details; this is not a customer result or a live run.
Subject
Follow-up: customer onboarding review, 12 May
Opening
Thanks for the time today. Here is what we agreed and what is still open.
Decisions
The pilot starts with the two regional teams. Weekly check-ins move to Thursdays.
Action items
Sam: confirm the data export by Thursday. Elena: share the revised onboarding checklist by Monday.
Still open
The migration date. It depends on the export check, so it is not promised in this email.
Status
Saved as a draft in Gmail. Not sent; recipients and wording are waiting for your review.
What steer uses to write the follow-up.
This is one workflow across steer, not a bundle of disconnected products. Each feature owns a specific stage and keeps its own access boundary.
Ground the recap in what was said
The completed meeting transcript and summary supply the decisions, questions, and speaker context. Follow-up starts with that source rather than a generic template.
Draft in the right work account
Supported Gmail and Calendar integrations can provide the intended thread, recipients, event, and surrounding context. Reading, drafting, sending, and changing an event remain different operations.
Bring open work back later
A configured proactive AI check can surface an unresolved commitment before the next relevant moment. It is not blanket inbox monitoring or an invented notification guarantee.
From meeting record to follow-up email and tasks.
The handoff stays inspectable from source to result. Every stage names what it received, what changed, and what needs review.
Close the meeting record
steer uses the final transcript, speaker attribution, and meeting identity so the follow-up is tied to the correct conversation and attendees.
Produce a decision-first recap
The recap leads with what changed, what remains open, and which next steps were actually agreed. Background discussion stays available in the source instead of crowding the follow-up.
Create the trackable work
Confirmed commitments can move through meeting notes to tasks, retaining the stated owner, timing, and meeting link on each Focus item.
Draft the follow-up email
steer can prepare a Gmail draft that reflects the meeting and the user’s opted-in writing style. The recipients and claims should be reviewed before any separate send action.
Check the next calendar context
For a recurring meeting, steer can use the intended Calendar event to understand when the subject returns. Changing an event is separate and may notify other people.
Surface unresolved work at the right moment
Heartbeat or an explicitly scheduled run can revisit an open item later. The follow-up page does not assume that every Focus date creates a notification.
What steer will not do on its own.
Connected work still needs accurate sources, explicit destinations, and review where an action changes another person’s system.
A generated email is a draft, not a sent message. Sending requires its own requested and authorized action.
A connected inbox is not permission to continuously monitor every message or act on every thread.
Calendar changes, project-system updates, and recurring checks are separate operations with their own effects.
Continue after the follow-up.
Move to the stage before or after this one without losing the feature owners or the source trail.
Does steer automatically send meeting follow-up emails?
No. steer can prepare a grounded Gmail draft, but drafting and sending are separate actions. The intended recipients and content should be reviewed before a send is requested.
Can the follow-up include meeting action items?
Yes. Confirmed commitments can become source-linked Focus items with the stated owner and timing. Missing details remain visible rather than being silently invented.
Can steer follow up before a recurring meeting?
A configured Heartbeat or scheduled run can bring unresolved work back before a relevant meeting. The exact behavior depends on the requested cadence, available Calendar context, and configured delivery path.
Does meeting follow-up automation update Jira or a CRM?
Only when the relevant integration and operation are supported, requested, and authorized. Creating a steer Focus item does not itself update an external project or customer system.
Can steer monitor replies to the follow-up?
A specific supported thread check can be requested or scheduled. Connecting Gmail does not mean steer continuously watches every conversation by default.
Start with one real workflow.
Bring the source, the intended result, and the boundaries that matter. steer is in private beta for macOS.