Call recording intelligence
Pulls the objections, the talk ratio, the sentiment and the buying signals out of every call recording, files them on the deal, and flags the bad calls.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon4 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Read every call transcript
Coming soonBlu builds a step
- 2
Write the manager alert
Coming soonBlu builds a step
- 3
File it and flag the bad ones
Coming soonBlu builds a step
- 4
Coach from the patterns
Coming soonBlu builds a step
About this recipe
When to use it
Managers can't review every call, so the risky ones slip through until the deal is already in trouble. This extracts objections, talk-listen ratio, and sentiment automatically and flags the at-risk calls directly. Try the standalone version with the AI Meeting Prep Generator or read how Blu's Sell agents actually work.
What it delivers
When a call recording becomes available, runs AI extraction for objections, talk-listen ratio, sentiment, and next-step signals, logs the results to the linked deal, and alerts managers on at-risk calls.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“Pulls the objections, the talk ratio, the sentiment and the buying signals out of every call recording, files them on the deal, and flags the bad calls.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Read every call transcriptCreate an AI-derived attribute on the Meeting object called 'call_insights'. Computed at call_recording_available from the transcript. Output: structured object with (a) talk-listen ratio per participant; (b) objections detected (list with quote + timestamp + category: price/timing/competition/feature-gap/authority/trust); (c) sentiment trajectory across call phases (open/discovery/demo/close); (d) buying signals detected (list with quote + timestamp + category); (e) discovery question count; (f) at-risk score (composite: high objections + low buying signals + negative sentiment shifts).
- 02Write the manager alertGenerate Slack alert content for sales managers when a call's at-risk score crosses threshold. Include: rep name, account name, deal value/stage, the 3 highest-severity objections with quoted clips, talk-listen ratio (flag if rep talked >65%), and a deep link to jump to the relevant transcript timestamps. Tone: coach-actionable, not punitive. Use the result of "Read every call transcript".
- 03File it and flag the bad onesCreate a workflow firing on call_recording_available. Step sequence: (1) compute call_insights attribute from the transcript; (2) update the linked Meeting record's notes with the structured insights and link to the deal; (3) if at-risk score crosses threshold (>=70), post the manager alert to Slack #sales-coaching and create a task for the rep's manager to review within 24h; (4) if buying signals are strong and no follow-up exists, create a high-priority next-step task for the rep. Use the result of "Read every call transcript", "Write the manager alert".
- 04Coach from the patternsCompose a coaching dashboard: talk-listen ratio by rep (rolling 30 days) flagging anyone outside the 40-55% rep-talk healthy range; top 5 objection categories by frequency (network-level + per-rep); discovery question count distribution (flag reps consistently below 5/call); at-risk call count by rep and week; and a leaderboard of calls with the highest buying-signal density (these are good listen-back examples for team training). Use the result of "Read every call transcript", "Write the manager alert", "File it and flag the bad ones".
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /call-recording-intelligence in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe 