Draft summaries for approval
AI meeting notes and call summaries on your records
Everything promised on a call becomes a draft note on the right record and a scheduled task for your team, waiting for you to approve.
Drafts ready for approval
Summaries are drafted for the person on the call
Draft notes land directly on the matching record, broken into specific fields for agreements, requests and next actions. Each summary is written for the person who took the call, waiting for them to review, correct and approve before becoming permanent.
- 1
Named fields separate facts
Fields capture what was agreed, asked for and promised, plus next actions and record changes. Each field links directly back to its original transcript passage.
- 2
Speaker separation shows sides
Transcripts separate speakers automatically, recording exactly who said what and indicating clearly which side of the call they were on during the conversation.
- 3
Approvals keep humans in control
Drafts go to the person on the call to approve or correct. Unapproved summaries stay marked as drafts until reviewed, keeping your team responsible for accuracy.
Summaries map to your specific business records
Matching your call to the right system is part of our build process. We write the summary automatically to a CRM opportunity, a claim, a matter, or a job, depending on your business.
Pick your business type
View pages for your business
Steps from call end to a finalized record
Building your summary automation covers the schema, matching to the right record, and writing back. Unapproved summaries stay marked as drafts until the person who was on the call approves or corrects them.
Follow the summary timeline
Meeting minutes already built into Microsoft Teams
Teams already keeps a recap and transcript of recorded conversations natively. Approved applications read transcripts through existing interfaces, while intelligent recap features require a Premium add-on or a Copilot license.
Select a Teams feature
Decisions made before the first call is recorded
Custom rules for uncertain matches are built directly into your design. We configure recording notification, capture, retention, and access in your platform before the first call is recorded.
Recording rules set early
Recording notification, capture, retention and access are configured initially. Access to recordings is usually narrower than access to the record itself.
Mismatch rules defined completely
Uncertain record matches happen more often than expected. Rules for handling these mismatches are built directly into the design.
Scoring done field by field
Accuracy varies heavily with accents, crosstalk and speakerphones. Scoring uses your firm's own recordings field by field against known correct entries.
Retesting on model changes
Summary prompts tuned to one model do not transfer cleanly. Scoring is repeated entirely whenever the deployed model version changes.
Building your summary automation step by step
Our build process starts when you pick one meeting type. We write the schema with the people on the calls, score it against recorded calls, and then wire the write-back.
- 1
Pick one meeting type
Selecting one meeting type gives us a starting point. We write the schema with the people on those calls to capture what was agreed, asked for, and promised.
- 2
Write the summary fields
Work closely with the people taking the calls to define the schema. Customizing fields ensures the summary captures exactly what your team needs.
- 3
Score against recorded calls
Test the new schema against your own past recordings. Field-by-field scoring verifies that the summary extracts information correctly despite crosstalk.
- 4
Wire the write-back
Connect the approved summary format back to your record system. Automation pushes the final notes and tasks directly to the destination.
Common questions about call summaries
- Where do recordings and transcripts come from?
Transcripts come from the platform your business already runs. Most cloud phone systems and Teams expose recordings and transcripts through an interface.
- What if our phone system produces no transcript?
Systems lacking an interface for transcripts are identified during scoping. Side-by-side transcription is added alongside your platform where a system produces none.
- What happens when a call matches the wrong record?
Phone numbers, calendar invitations and customer records agree less often than expected. Custom rules for uncertain matches are part of the design, ensuring notes go to the right place.
- Does a person approve the summary?
Drafts go straight to the person who was on the call. They must approve or correct the notes, and unapproved summaries stay marked as drafts.
- How accurate are the summaries?
Accuracy varies with accents, crosstalk and speakerphones. Testing uses your firm's own recordings to score outputs field by field against calls whose correct entries are known.
- What has to be set up before the first call is recorded?
Recording notification, capture, retention and access are configured in the platform before any call is recorded. Access to these recordings is usually narrower than access to the record.
Start capturing your call promises
Book a conversation to see how draft summaries map onto your existing business records.