Renewal call summary fields
Customizes AI summaries for Renewal calls, extracting usage patterns, expansion signals, churn risks, stakeholder confirmation and contract changes.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon3 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Check the Renewal meeting type
Coming soonBlu builds a step
- 2
Set what renewals capture
Coming soonBlu builds a step
- 3
Track renewal risk and upside
Coming soonBlu builds a step
About this recipe
When to use it
A renewal call carries usage signals, expansion hints, and contraction risk that a generic summary flattens into nothing useful. This customizes the summary to capture all of it, feeding directly into renewal forecasting and the CSM motion.
What it delivers
Customizes how the AI summarizes renewal calls to capture usage patterns mentioned, expansion signals, contraction risks, stakeholder confirmation, and contract-term changes, feeding renewal forecasting and CSM workflows.
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
“Customizes AI summaries for Renewal calls, extracting usage patterns, expansion signals, churn risks, stakeholder confirmation and contract changes.”
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.
- 01Check the Renewal meeting typeRetrieve the Renewal meeting type from the meeting taxonomy. Confirm exists with notetaker autojoin enabled.
- 02Set what renewals captureConfigure the AI summary recipe for the Renewal meeting type. Extract: (1) Usage Patterns (features the customer mentioned actively using vs. struggling with vs. never tried; (2) Expansion Signals) explicit interest in additional seats, modules, tier upgrades; budget signal for expansion (verbatim quotes); (3) Contraction Risks: explicit signals of churn intent, reduced usage, team changes affecting fit, competitor evaluation; (4) Stakeholder Confirmation: was the decision-maker present, did stakeholders confirm continued commitment, any champion changes (departures, role changes); (5) Contract Terms Discussion (pricing pushback, term length preference, payment terms, custom contractual asks; (6) Health Score Movement) sentiment shift from prior interactions; (7) Next Step: proposal needed, additional stakeholders to loop in, agreement to terms. Use the result of "Check the Renewal meeting type".
- 03Track renewal risk and upsideCompose a renewal risk + expansion dashboard reading from summaries: (1) at-risk renewals (accounts with contraction signals or unresolved competitor evaluation, sorted by renewal date; (2) expansion-ready) accounts with explicit interest signals, sorted by ARR opportunity; (3) churn precursors (accounts where champion departed or stakeholders signaled disengagement; (4) renewal-call coverage) % of upcoming renewals where the call has happened (target: 100% by 60 days before renewal date); (5) win/loss patterns from past renewal-call summaries. Group by CSM owner. Use the result of "Check the Renewal meeting type", "Set what renewals capture".
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 /renewal-call-summary-recipe 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.
