AI nudge for a stalled deal
Drafts a personalized re-engagement email for stalled deals using CRM deal context, leaving it for the rep to review and send.
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
Recall why it stalled
Coming soonBlu builds a step
- 2
Draft a nudge that names it
Coming soonBlu builds a step
- 3
Compare against a rep's own
Coming soonBlu builds a step
About this recipe
When to use it
Generic check-in emails get ignored because they don't reference anything real. This generates a re-engagement message that names the specific blocker and the last meeting's context, so it reads like a person paying attention, not a sequence step.
What it delivers
When a deal is detected as stalled, generates a personalized AI-drafted re-engagement message referencing the specific blocker, last meeting context, and an offered next step, for the rep to review and send.
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
“Drafts a personalized re-engagement email for stalled deals using CRM deal context, leaving it for the rep to review and send.”
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.
- 01Recall why it stalledCreate an AI-derived attribute 'nudge_context' on the Deal object, computed when the deal enters stalled status. Aggregates: (a) which stage stalled (Discovery / Demo / Proposal / Closing (each requires different nudge angle); (b) last meeting_summary if available) most useful is the 'next step' that was agreed and apparently not happening; (c) most recent objection raised (from call summaries); (d) any mentioned timeline / decision-window that may now be expiring; (e) replacement-stakeholder candidates if the original contact has gone quiet.
- 02Draft a nudge that names itCreate a workflow firing when a deal is newly detected as stalled (consumer of the stalled-deal-detection workflow's output). Step sequence: (1) compute nudge_context; (2) generate AI-drafted nudge email using the context. Distinct from the template-based nudge in stalled-deal-detection: this version is HIGHLY personalized using meeting-summary specifics ('Last time we talked, you mentioned [verbatim objection]. Has anything changed on [specific blocker]?'); (3) save draft to rep's outbox; (4) create rep task labeled 'Review AI-drafted nudge: deal [name]' with the draft preview; (5) Slack DM with deal context. Always rep-reviewed-before-send. If deal stays stalled 14 days after first nudge draft sent, escalate to manager with manager-version draft (this needs your sign-off). Use the result of "Recall why it stalled".
- 03Compare against a rep's ownCompose an AI nudge effectiveness dashboard: stalled-deals that received AI nudge drafts (vs. drafts not yet reviewed = backlog), reply rate to AI-nudge-drafted emails vs. baseline manual nudges, revival rate (deals stage-advanced after AI nudge), and ARR resurrected via this workflow. Compare to control: stalled deals where reps wrote their own nudge: typically AI-drafted personalized nudges win on reply rate by 1.5-2x. Use the result of "Recall why it stalled", "Draft a nudge that names it".
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 /ai-stalled-deal-nudge 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.
