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.
Keep the work moving after the meeting ends.
Ghost 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.
- Direct answer
- 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.
One complete example.
After a customer onboarding review, Ghost 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.
Where each capability enters.
This is one workflow across Ghost, not a bundle of disconnected products. Each feature owns a specific stage and keeps its own access boundary.
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.
How the work moves.
The handoff stays inspectable from source to result. Every stage names what it received, what changed, and what needs review.
Close the meeting record
Ghost 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
Ghost 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, Ghost 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 the workflow does not assume.
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.
Questions about meeting follow-up automation.
Does Ghost automatically send meeting follow-up emails?
No. Ghost 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 Ghost 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 Ghost Focus item does not itself update an external project or customer system.
Can Ghost monitor replies to the follow-up?
A specific supported thread check can be requested or scheduled. Connecting Gmail does not mean Ghost continuously watches every conversation by default.
Start with one real workflow.
Bring the source, the intended result, and the boundaries that matter. Ghost is in private beta for macOS.
Request access