Best for
- Teams that learn process details on calls but fail to update SOPs afterward
- Sales and CS leaders turning repeated call patterns into onboarding guidance
- Small GTM teams that need process discipline without heavy documentation work
Convert sales, support, and internal calls into approved process updates, onboarding notes, and recurring checklists that live outside random AI chats.
Create a call-to-process system that captures operational learnings, routes approvals, and updates recurring checklists in Manifestly or Notion.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
5 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
AI chat summaries are useful, but they disappear if the output stays inside a chat window. This workflow turns transcripts into operational artifacts: SOP updates, checklist changes, onboarding notes, and review tasks. The approval step keeps process changes from becoming AI-generated chaos.
Expected results
Call artifacts processed
5-20 calls per month
This range is realistic for processing only calls that contain operating decisions or repeatable lessons.
Process updates
3-10 approved updates per month
A useful system filters most calls and only turns validated learnings into SOP or checklist changes.
Time saved
3-6 hours per week
Transcript capture and structured routing reduce manual note cleanup, SOP drafting, and follow-up coordination.
Operational quality
Approved process changes
Human approval ensures recurring workflows change only when a responsible owner accepts the update.
Step-by-step workflow
The first 2 steps are open. Confirm your email to unlock all remaining steps, prompts, and implementation tips for free.
45-60 min
45-60 min
Scope: Choose the meeting types that are eligible to feed the process system, such as sales handoffs, customer onboarding, implementation reviews, support escalations, postmortems, and recurring GTM operating reviews.
Set up: In Notion, create fields for Call Type, Business Process, Process Owner, Meeting Owner, Eligible for SOP Change, Eligible for Checklist Change, Required Approver, and Review SLA. Write inclusion rules based on whether the call can produce a repeatable decision, operating constraint, failure pattern, control requirement, or handoff change.
Build: Write exclusions for routine status updates, one-off customer preferences, unverified opinions, confidential discussions that cannot be documented, and decisions outside the meeting participants' authority. Assign one accountable process owner for every included call type so proposed changes do not sit unowned. Review the matrix with RevOps, Enablement, Customer Success, and any functional leaders whose procedures may be changed.
Output: Publish the approved intake rules in the process knowledge base before processing transcripts.
An approved call-intake matrix with eligible meeting types, exclusions, process owners, approvers, and review SLAs.
Eligibility should be based on the authority and repeatability of the learning, not simply on how important the meeting felt.
45-75 min
45-75 min
Capture: Document when Granola or Fathom may record or transcribe meetings and how participants are informed according to company policy and applicable consent requirements. In Notion, record Allowed Meeting Types, Consent Method, Restricted Topics, Transcript Access Group, Storage Location, Retention Period, Redaction Owner, and Deletion Process.
Guardrails: Exclude or redact credentials, sensitive personal information, medical or financial details, confidential customer data, legal advice, and unrelated employee performance discussions before process analysis. Define which links may be stored in a broadly accessible SOP and which evidence must remain in a restricted workspace.
Exceptions: Limit transcript access to the people who need to review the change and use summaries or approved excerpts for wider communication. Assign an owner for responding to access, correction, and deletion requests.
Approval: Obtain approval from the relevant privacy, legal, security, or operations owner before the workflow goes live.
A documented recording and transcript-governance policy covering consent, access, redaction, retention, evidence links, and deletion.
Confirm your email to read the remaining 13 steps, prompts, and implementation tips. One sign-in unlocks the whole library.
By joining, you agree to the Terms and Privacy Policy.
Already have an account? Sign inDo not make a process document depend on permanent access to a sensitive transcript. Preserve only the approved evidence needed to explain the decision.
Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
Launch a Slack battlecard assistant that retrieves sourced competitor context and gives reps approved talk tracks, traps, and follow-up resources.
Create a sourced campaign brief with audience insights, messaging pillars, evidence, risks, and a practical asset production plan.
Create an intent-to-action routing system that pushes high-fit accounts into the right sales, marketing, and RevOps workflows.