Skip to main content
Intempt
Coming soon

Account engagement scoring and plays

Scores each account from 0 to 100 on how its whole team uses the product, then runs a different play for healthy, slipping, declining and inactive accounts.

Authored by Intempt Technologies

Recipe curators

Agentic workflow

Coming soon

6 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.

  1. 1

    Score each account daily

    Coming soon

    Blu builds a step

  2. 2

    Group paying accounts by tier

    Coming soon

    Blu builds a step

  3. 3

    Write an email per tier

    Coming soon

    Blu builds a step

  4. 4

    Change what the admin sees

    Coming soon

    Blu builds a step

  5. 5

    Run the play for each tier

    Coming soon

    Blu builds a step

  6. 6

    See where the book is heading

    Coming soon

    Blu builds a step

About this recipe

When to use it

One power user can mask three teammates going quiet, so user-level engagement scoring misses the real account trend. This rolls activity up to the account and branches the journey by tier.

What it delivers

Aggregates B2B account-level engagement (user activity rolled up to the account) into tiers - green accounts get expansion-leaning content, yellow get reactivation, red get a save-flow plus CSM task, dormant get win-back.

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

“Scores each account from 0 to 100 on how its whole team uses the product, then runs a different play for healthy, slipping, declining and inactive accounts.”

recipe.md preview

Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.

Sign up to read the full recipe.md and run it with Blu Agent.

Sign up to see the full recipe

Inputs & outputs

What the recipe needs before it runs, and what it leaves in your workspace.

Inputs

  1. 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.

    1. 01Score each account dailyCreate an AI-derived attribute 'account_engagement_score' on the Account object, refreshed daily. Aggregates ACROSS all users at the account: (a) active-user ratio (active users / total seats); (b) engagement velocity (sessions/events trending up or down at account level); (c) feature breadth (count of features used by anyone at the account); (d) stakeholder distribution (engagement coming from multiple roles vs. single-user dependence); (e) sentiment signals from support tickets. Output: numeric 0-100 with tier: green (75-100 healthy growing) / yellow (40-74 stable but warning signs) / red (15-39 declining quickly) / dormant (<15 effectively inactive). The account-as-unit aggregation is the differentiator: most CDPs score users, this scores the buying entity.
    2. 02Group paying accounts by tierBuild a segment 'B2B accounts tiered by engagement' capturing all paying B2B accounts, partitioned by account_engagement_score tier. Refreshed daily. Excludes accounts <30 days old (need history) and accounts in active sales-led save-flows (avoid double-orchestration). The journey routes from this segment based on tier. Use the result of "Score each account daily".
    3. 03Write an email per tierGenerate per-tier email content. GREEN (expansion-leaning content sent to champion: 'Your team is in the top 25% of [Product] users) here's what high-growth accounts do next.' Plus subtle expansion CTA. YELLOW (reactivation content sent to admin: 'Noticing a few of your team members aren't logging in as often) want help re-engaging the team?' With a CSM-meeting CTA. RED (urgent personalized content sent to admin + executive sponsor: 'Your team's engagement has shifted) we'd like to understand what's going on. 15-minute call?' Direct CSM offer. DORMANT (last-chance content sent to champion: 'It's been a while) we miss you. Here's what's new since you last logged in.' With a fresh-start onboarding offer. Use the result of "Score each account daily", "Group paying accounts by tier".
    4. 04Change what the admin seesConfigure an in-app personalization on the admin dashboard that varies by account tier. Green: shows expansion roadmap + power-features for healthy growth. Yellow: shows team-engagement health stats + 'invite team members' nudges + use-case templates relevant to slow-adoption rescue. Red: shows direct-CSM-connect button + 'troubleshoot setup' resources prominently. Dormant: doesn't render account-engagement personalization (won't help: the user isn't logging in anyway; reach them via email instead). Use the result of "Score each account daily", "Group paying accounts by tier".
    5. 05Run the play for each tierBuild a tiered journey wired to account-engagement-tiered segment. Branch on account_engagement tier at entry AND re-evaluate weekly. GREEN: Touch 1 monthly (expansion-leaning content to champion. Personalization activates for admin. Touch 2 quarterly) handoff to customer-progress-business-case journey. YELLOW: Touch 1 Day 0 (reactivation content to admin. Touch 2 Day 7) CSM task to reach out if score hasn't recovered. RED: Touch 1 Day 0 (urgent content + CSM task SAME-DAY. Touch 2 Day 3) executive-sponsor task if no CSM contact made. DORMANT: Touch 1 Day 0 (last-chance email. Touch 2 Day 14) final outreach + warning before suppression. Exit on: tier escalation back to green (recovered: log retention_win), Subscription canceled (handoff to post-cancel-winback), or sustained dormancy 60+ days (suppress). Use the result of "Score each account daily", "Group paying accounts by tier", "Write an email per tier", "Change what the admin sees".
    6. 06See where the book is headingCompose an account-engagement dashboard: tier distribution across the book of business (green/yellow/red/dormant proportions: the health-of-business snapshot), tier-migration trends week-over-week (which direction are accounts moving), ARR-weighted at-risk pile (red + dormant tier sum), red-tier-to-recovered conversion rate (proof the intervention works), and per-CSM tier distribution (some CSMs handle red-heavy portfolios: informs workload balancing). The strategic NRR view for leadership. Use the result of "Score each account daily", "Group paying accounts by tier", "Write an email per tier", "Change what the admin sees", "Run the play for each tier".

    Install Intempt and run it

    1. 1

      Sign up

      Create a free Intempt workspace.

    2. 2

      Connect your data

      Add the sources this recipe reads from.

    3. 3

      Ask Blu

      Type /account-engagement-score-orchestration in Blu once this recipe is live there.

    4. 4

      Review and approve

      Blu builds each step and waits for your OK before anything goes live.

    Related recipes

    Intempt TechnologiesDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Intempt TechnologiesPost 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 Intempt TechnologiesReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    More recipes by Intempt Technologies

    Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post 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 Product swap in a sceneReplaces the product in a shot you already have with a different one, keeping the scene, lighting and shadow the same.View recipe

    Got a play worth sharing?

    Publish it to the Intempt Collective Marketplace and earn when other teams run it.

    Submit a recipe