Voice transcription and call summarization

Requirements describe capabilities the pattern needs in your environment, not the vendors you must buy. Any system that fills a requirement satisfies it — that’s what makes the catalog portable across the long tail of SMB tooling.

1. call_audio_source

   REQUIREDREADstream

   Where call recordings or live audio streams come from. The pattern can consume either, with different architectures behind it.

   DATA SHAPE

   Audio file or stream with metadata: participants, timestamp, call duration, optionally call type (sales, support, etc).
   COMMONLY FILLED BY

   • telephony platform that posts recordings after each call
   • video conferencing system with recording export
   • dedicated call recording service
   • real-time stream from a softphone or browser-based caller
2. call_context_lookup

   REQUIREDREADrequest

   Who's on the call and what their relationship to the business is. Lets the summary reference the right account and prior context.

   DATA SHAPE

   Caller and recipient identifiers with associated account, deal, or ticket context.
   COMMONLY FILLED BY

   • CRM with contact records and deal associations
   • support system with customer history
   • billing system with account records
3. summary_destination

   REQUIREDWRITEevent

   Where the structured summary lands. Usually attached to a CRM record, ticket, or deal so the next person looking at that record finds it immediately.

   DATA SHAPE

   Structured summary attached to the relevant record: bullet-point summary, action items with owners, sentiment indicator, topic tags, link to full transcript.
   COMMONLY FILLED BY

   • activity logged in the CRM against the contact and deal
   • internal note added to a support ticket
   • summary posted to a team chat channel and linked from the deal
4. transcript_store

   REQUIREDWRITEcorpus

   Where the full transcript lives for later search and reference. Separate from the summary destination because transcripts are bulky and infrequently read.

   DATA SHAPE

   Full speaker-attributed transcript with timestamps, searchable.
   COMMONLY FILLED BY

   • dedicated transcript storage with search
   • indexed transcript attached to the CRM record
   • file store with full-text search enabled
5. action_item_router

   RECOMMENDEDWRITEevent

   Where action items captured from the call get sent so they don't sit dormant in a summary nobody re-reads.

   DATA SHAPE

   Individual action items with owner, due date if mentioned, source-call link.
   IF MISSING

   Action items still appear in the summary but require a human to translate them into tasks. About half of action items in practice fall through without explicit routing.
   COMMONLY FILLED BY

   • task created in the project management tool with the owner assigned
   • follow-up task created on the deal in the CRM
   • calendar reminder for the responsible person
6. speaker_voice_directory

   OPTIONALREADrequest

   Maps voice characteristics to known speakers so the transcript can attribute speech without manual labeling. Useful at higher volumes.

   DATA SHAPE

   Voice enrollment samples per team member: stored audio fingerprints, not raw recordings.
   IF MISSING

   Transcripts attribute speech by channel (caller vs. callee) only, or rely on diarization without identity. Works fine for two-party calls; degrades on group calls.
   COMMONLY FILLED BY

   • voice enrollment captured during onboarding
   • speaker identification module within the transcription service