Rep activity and coaching
Shows sales rep activity volume for calls, emails and meetings alongside the revenue it produced, so managers can identify coaching needs and performance differences.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Build the rep leaderboard
Coming soonBlu builds a step
About this recipe
When to use it
Quota attainment alone doesn't show a manager whether a rep's activity is efficient or just busy. This adds calls, emails, meetings, and revenue-per-call efficiency alongside win-loss patterns, the canonical coaching artifact.
What it delivers
Tracks rep activity (calls, emails, meetings), revenue-per-call efficiency, and win-loss patterns for the Sales Manager coaching view.
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
“Shows sales rep activity volume for calls, emails and meetings alongside the revenue it produced, so managers can identify coaching needs and performance differences.”
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.
- 01Build the rep leaderboardCreate a Dash board (12-column composition canvas) titled "Sales Activity & Coaching". Persona: Sales Manager or frontline-coach. Question answered: "Which reps need coaching? What patterns differentiate top performers from the rest?" Distinct from Sales Pipeline (deal-focused, operational) and Sales Forecasting (period commitment). Sales Activity & Coaching is per-rep frontline-management: the dashboard a manager opens when planning weekly 1:1s. Board-level configuration: - defaultDateRange: last_30_days - exclusionPeriod: none - visibility: project - boardFilters: none by default; managers typically filter to owner_id IN (their direct reports) at runtime - boardBreakdowns: owner_id: pushed down throughout Layout: 4 rows. Row 1: Activity volume KPIs (heightPx: 200, four metric cards at widthUnits: 3): - Card 1: Insights metric to source recipe: rep-activity-leaderboard, vizType: metric, titleOverride: "Total Calls (Team, 30d)" - Card 2: Insights metric to source recipe: rep-activity-leaderboard, vizType: metric, titleOverride: "Total Meetings Booked" - Card 3: Insights metric to source recipe: rep-activity-leaderboard, vizType: metric, titleOverride: "Team Revenue per 100 Calls" - Card 4: Insights metric to source recipe: quota-attainment-by-rep, vizType: metric, titleOverride: "% Reps at ≥100% Attainment" Row 2: The leaderboard (heightPx: 520, full-width single card at widthUnits: 12): - Card 1: Insights to source recipe: rep-activity-leaderboard, displayMode: table (the sortable per-rep activity + revenue table: the centerpiece coaching artifact). Sort modes: Top Performers (revenue), Most Active (calls), Most Efficient (revenue per call), Rising/Falling Stars (week-over-week change). Row 3: Win-loss patterns (heightPx: 440, two cards at widthUnits: 6): - Card 1: Insights to source recipe: win-loss-analysis, displayMode: chart, vizType: bar (won vs. lost by source: ICP fit signal) - Card 2: Insights to source recipe: deal-velocity-by-stage, displayMode: chart, vizType: bar (which stages slow deals down: coaching focus areas) Row 4: Strategic deal hygiene (heightPx: 440, two cards at widthUnits: 6): - Card 1: Insights to source recipe: multi-threading-coverage-by-deal, displayMode: chart, vizType: stacked_bar (single-threaded deals are coaching opportunities: Gartner data shows they close at 50% lower rates) - Card 2: Insights to source recipe: quota-attainment-by-rep, displayMode: chart, vizType: bar (per-rep attainment with team-average benchmark) Annotations: - Row 1's "Revenue per 100 Calls" is the Gong-popularized leading-indicator metric. Below team-average × 0.5 indicates serious efficiency issue; coach the rep on qualification or talk tracks. - Row 2 (the leaderboard, full-width) is the dashboard's centerpiece. Manager workflow: open before weekly 1:1s, sort by "Rising/Falling Stars" to spot trend changes, then drill into specific reps for coaching topics. - Row 3 shifts from individual to pattern: which deal types/sources lose? Which stages stall? These are team-level coaching topics, not 1:1 topics. - Row 4 surfaces deal-hygiene issues that compound: single-threaded deals are pure coaching gold (advise the rep to multi-thread before proposal stage). Per-rep attainment with team-average overlay surfaces both the bottom (intervention) and top (replicate) of the distribution. - Recommended cadence: read this dashboard before weekly 1:1s and Friday team standups. The rising-stars sort changes weekly; the patterns view changes monthly. Taxonomy notes: - rep-activity-leaderboard pulls from Call completed, call_logged, Messaged email (direction=outbound), Meeting scheduled, Task completed, Deal won: all canonical events. - "Rep" identification is unified across events through created_by / assignee_id / owner_id resolving to the same Users object (owner_id is canonical). - quota-attainment-by-rep depends on workspace-level quota target configuration: see that recipe's notes.
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 /sales-activity-coaching-dashboard 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.
