From raw transcript to customer record.
Four steps, the same pipeline as every other source.
Paste, upload .txt or .md, or pull from Google Drive.
Parsers cover Otter, Fireflies (SRT/VTT), Whisper (TXT/SRT/VTT/TSV/JSON), Grain, Google Meet Gemini and plain text. Title, date, customer name, company, email, plan, revenue band and transcript type are extracted from headers, speaker patterns, or the filename.
One call mentions billing, onboarding and an integration bug — three distinct signals, not one blurry "call notes" entry.
Even a zero-signal context call still creates the customer record. Your CRM-of-voice stays complete.
What the integration gives you.
Drop the file in, no metadata entry. Otter, Gemini and "Meeting with X" patterns all recognised.
Non-English transcripts translate before classification, so a Japanese sales call clusters with English customer feedback under one theme.
Re-uploading the same transcript doesn't double-count. SHA-256 hash scoped per account.
Text minimum 50 characters, maximum 500 KB; title 1–500 chars. Each transcript becomes background-segmented into multiple feedback rows tagged source=‘transcript’.
Asked and answered.
Otter, Fireflies (SRT/VTT), Whisper (TXT/SRT/VTT/TSV/JSON), Grain, Google Meet Gemini, plus generic .txt and .md.
Pattern-matched from the transcript’s own headers and filename — "Meeting with [Company]", Otter-style speaker labels, Gemini exports, and so on. Manual override is available.
Circuit translates before classification. The cluster ends up under your existing English themes.
Deduped via SHA-256 content hash scoped to your account. The second upload doesn’t ingest.
Part of Circuit’s autonomous product intelligence stack — see the full picture.