Skip to main content

Scenario

Call recordings from sales calls, support calls, and consultations contain the richest customer language — tone, objections, questions, and commitments. This job fetches recordings, transcribes them (via Twilio’s built-in transcription or an external service), then runs the transcript through Mave for meeting-style analysis: key topics, action items, sentiment flow, and follow-up recommendations. Flow: Twilio GET /Recordings → Fetch transcription → Mavera POST /mave/chat → Meeting-style analysis report

Code

Example Output

Error Handling

Twilio’s built-in transcription is English-only and may not be enabled by default. Enable via TwiML <Record transcribe="true">. For higher quality, use AssemblyAI or Deepgram on the recording audio URL.
Recordings are stored for the retention period configured in your Twilio Console (default: indefinitely). Access the audio at https://api.twilio.com/2010-04-01/Accounts/{sid}/Recordings/{RecordingSid}.mp3.
Calls over 15 minutes produce large transcripts. The code limits to 3,000 chars. For full analysis of long calls, split the transcript into segments and analyze each separately, then summarize.
Twilio transcription doesn’t separate speakers. For speaker-attributed analysis, use a service like AssemblyAI with speaker labels, then format as Agent: ... / Customer: ... before sending to Mave.