From a call to a breakdown

How CLUE turns a call into a finished breakdown

You set the phone system up once. After that every finished conversation runs automatically: recording, transcript, analysis, dashboard. Every step below comes with real timings.

5 calls a month. $0. No card.

Four steps

What you do, and what the system does

STEP 01 · YOU Signing up and onboarding

Email or Google, then 5 short steps: role, team size, main goal and current stack. The starting dashboard is assembled around your role.

about 3 minutes
STEP 02 · YOU Connecting the phone system

Settings, the integrations tab, your provider, a key and a webhook. Then you link each rep's extension so a call lands in the right profile.

about 15 minutes
STEP 03 · THE SYSTEM Processing the call

The phone system sends the recording, CLUE fetches it, encrypts it, turns it into text with the rep and the customer split apart, and runs it through 10 sections of analysis.

1 to 5 minutes after the call
STEP 04 · THE TEAM Act

The rep gets their breakdown first. The lead sees the team overview, the weak stages and the top objections. The one-to-one starts at a timecode, not at an impression.

the same day

Step 2, in detail

Connecting the phone system, step by step

This is the only technical step in the whole rollout, and it happens in the interface, without a developer.

01Settings → Integrations

This section is available to the workspace admin

02Pick your provider

Binotel, UniTalk, Ringostat and others

03Paste the access key

Encrypted with AES-256-GCM the moment it is saved

04Copy the webhook into the phone system

One line in your phone system's settings

05Link the reps' extensions

So a call lands in the right profile

Step 3, in detail

7 stages of call processing

Scroll to follow a call from the webhook to a finished breakdown. If a stage fails, the call returns to the queue rather than disappearing.

  1. PENDINGCall received
  2. DOWNLOADING_AUDIORecording downloading
  3. UPLOADING_TO_S3Encrypted storage
  4. TRANSCRIBINGTranscription and speakers
  5. ANALYZING10 sections of analysis
  6. INDEXINGIndexed for search
  7. COMPLETEDDashboard updated
PENDING queue · call-processing

Your phone system tells CLUE the moment a call ends

The webhook arrives on its own, the record is created, and the call joins the queue call-processing.

sourceUniTalk · webhook typeINCOMINGduration08:27 retriesup to 5 attempts

CLUE fetches the recording from the provider

The audio is pulled from the provider's link. A slow provider does not break processing: the queue waits and retries.

filecall_8f21.mp3 · 7.4 MBstatedownloading

The audio goes into encrypted storage

Backblaze B2, S3 compatible. Encrypted at rest and in transit, with companies' data isolated.

storageS3-compatible bucket encryptionat rest + in transitisolationper-company

Speech becomes text, with the speakers separated

Three transcription tiers with fallback: Whisper large-v3 on GPU, Deepgram, and local Whisper. If the first tier is unavailable, the next one takes over.

Rep · 00:12Let me show you how the integration works.
Customer · 00:19Sounds good. What about the price?
Rep · 00:24Let us price it for your volume.
Customer · 00:41We need to compare with others.

The model breaks the conversation into 10 sections

Quantitative measures, qualitative judgements, structure, objections, recommendations, strengths, areas to work on, the scoring formula, stages, and the summary.

talk ratio pauses rep questions customer questions objections time to first objection interruptions time on price next steps engagement buying signal competitor mentions trust deal risk
0
  • Objection handled
  • Next step captured
  • Risk: a competitor came up

The conversation becomes searchable

The transcript, the keywords and the analysis JSON go into Postgres indexes. Search works across the whole call history.

indexeskeywords · analysis · date+user searchacross all history

The breakdown is in the dashboard

The lead sees the team overview, the rep sees their own conversation. Notifications can go to Slack or Telegram.

score7.5 / 10stages5, each scored recommendations5 areasnotificationsSlack · Telegram · beta

How long it takes

Real processing times

~3 minsign-up and onboarding shaped to your role
~15 minconnecting the phone system and linking reps
1 to 5 minprocessing one call after it ends
1 daythe first meaningful team overview, once enough calls have gathered
Why the team overview does not appear instantly You will see the first breakdown on the very first call. But team averages, trends and rankings only become honest once a day's worth of conversations is in the system, not three recordings.

Get started

15 minutes to connect — after that the system runs itself

Free: 5 calls a month, no card.