Skip to main content
Use case

Sales call coach

A coaching agent the head of sales authors once. AEs use it before calls; sales managers use it during 1:1s; enablement uses it to refresh the playbook.

The problem

Every sales team has a playbook. It lives in a Notion doc, a Google Slides deck, and the head of sales’ Friday all-hands recording. New AEs read it once during onboarding and never again. Veteran AEs don’t reread it because they already know it. The most effective coaching happens in 1:1s where a manager walks an AE through “what would you have said differently here?” — and that scales linearly with how many 1:1s the manager can fit in a week. The result is a team where the floor is set by the playbook, the ceiling is set by manager bandwidth, and the gap between the two is where most deals quietly leak.

Author

The head of sales and a sales enablement lead co-author the call coach in the AgentBundle dashboard wizard. They paste in the canonical playbook: the discovery framework (MEDDIC, BANT, or whatever the team uses), the objection-handling library, the value-prop matrix per ICP segment, and the qualification-disqualification rubric. They wire MCP connections to the CRM (so the agent knows the deal stage and history) and to the call-recording platform (Gong, Chorus, or equivalent — so the agent can ingest call transcripts). No code; the wizard generates the bundle. The whole thing takes a Tuesday afternoon. The reviewer-workflow controls referenced below ship on Business tier and above; see /pricing for what’s gated.

Review

The VP Sales approves the agent. Every change to the qualification rubric or objection library is reviewed by the head of sales and the enablement lead before publishing. N-required reviewers on Business tier; the audit log captures every edit. The coaching framework is the most important artifact the sales org owns, and now it has the same change-control rigor as any other piece of business-critical infrastructure.

Distribute

APM (Microsoft’s open packaging spec for AI agents) ships APM-compatible bundles to every runtime in the org. Engineers running Claude Code don’t get the call coach (it’s not relevant to them), but every sales seat does — Cursor for the SE team, ChatGPT-equivalents through whatever plugin sales prefers, or the AgentBundle dashboard for AEs who don’t want to leave the CRM tab.

Use

The same canonical sales call coach runs across multiple flows in different roles:

  • Account Executive — pre-call: an AE pastes in the deal context (the agent already pulls deal stage from the CRM via MCP) and gets a focused brief: “this prospect is in the qualification stage, watch for procurement objections around X based on the segment, the value prop ranked highest for their tier is Y, and these three discovery questions surface buying signal fastest.” Not generic call prep — call prep against THIS team’s playbook for THIS deal stage.
  • Account Executive — post-call: the AE pastes the call transcript and gets a self-coaching summary: which discovery questions landed, where the conversation drifted off the qualification framework, what the prospect said that signals the next-step opportunity. The 1:1 with the manager starts with shared context instead of “let me explain what happened.”
  • Sales Manager — 1:1 prep: the manager runs the agent on their direct’s recent calls before a 1:1. They get a pattern view across deals — “your three biggest opps all had unclear champions” — instead of recapping each call individually. The hour goes from rebuilding context to actually coaching.
  • Sales Enablement — onboarding refresh: when the team’s new ICP segment ships, enablement updates the playbook rubric in the agent. Every AE who runs the agent next gets the new segment’s value prop and qualification questions immediately. No deck to redistribute, no LMS module to assign.
  • Customer Success — handoff prep: when a deal closes, the CSM running the agent on the closed-won call gets the customer’s stated success criteria pulled out and structured — feeding directly into the kickoff call agenda. The handoff stops being “let me read the deal notes for the third time.”
  • Marketing — sharper messaging: marketing periodically runs the agent on aggregate call transcripts to surface the language customers use about the product (vs the language marketing uses about it). Ad copy, landing pages, and outreach templates pick up the actual customer vocabulary.

Composition

The same canonical sales coach is used directly by AEs in pre-call prep, by AEs again post-call for self-coaching, by managers before 1:1s, by enablement when the playbook needs to evolve, and by CSMs at handoff. One canonical definition, multiple invocation surfaces — and when the head of sales tightens the qualification rubric, every team picks up the new version on next sync. Teams who use the brand voice agent for outbound copy combine it with the call coach manually — paste the coach’s customer-facing draft into the brand voice agent before sending.

Iterate

A new buying motion lands — say, the team is moving from a SMB-self-serve into a sales-led enterprise mid-market segment. The qualification rubric changes, the value prop emphasis changes, the playbook for handling procurement evolves. The head of sales updates the canonical agent prompt with the new motion’s specifics, the enablement lead reviews, and v3 ships. Every AE running pre-call prep on Monday morning gets the new framework — no kickoff meeting that 30% of the team misses, no deck that gets versioned across folders, no Slack ping that gets buried. The audit log shows the exact moment the playbook changed and who approved it; if a deal closes against the new motion and the team wants to know what guidance the AE was working from, the version number is right there in the call-summary metadata.

Where it ships

Teams across the org that consume this canonical agent — different flows, one definition.

SalesSales EnablementCustomer SuccessMarketing

Try this use case.

Define it once. Ship it everywhere.

Try this use case
Copied to clipboard