Skip to main content
The Coaching Agent evaluates every call against configurable competency frameworks — automatically, on every call. It is not limited to sales calls: competencies are assigned per Salesforce role, so you can configure a different set of skills for AEs, SDRs, Sales Engineers, or any other role in your org. Your job as the prompt author is to define what good and bad look like for each competency. The evaluation and output are handled by Momentum.
Coaching prompts: use the structured format. Competency prompts are rubrics, not questions. They need a clear purpose statement and observable positive and negative indicators — none of which translate cleanly to a single plain-language instruction. Structure is the right tool here.
Coaching prompts are evaluation prompts — not extraction prompts. Autopilot and Signals extract information. Coaching evaluates behavior against a defined standard. You are writing the rubric the AI uses to assess the call — define what observable behaviors qualify as strong, adequate, or absent performance for each competency.

Writing competency prompts

Competency examples

Each competency follows the same structure: a PURPOSE statement, numbered areas to evaluate with positive and negative indicators, and example questions or statements. Two examples below — the same pattern applies across every competency in your framework.

Example 1 — Discovery Excellence

Example 2 — Identify Pain

Competency aggregation types

Coaching Agent — QA checklist

  • Competency prompt has a clear PURPOSE statement defining what is being evaluated
  • Positive and negative indicators use observable behaviors — not subjective judgments
  • Negative indicators include common failure modes, not just absence of positive ones
  • Rules section states what to do when the call is too short to evaluate
  • Scoped correctly: Core Skills vs Stage-Based
  • CRM conditions set if competency should only evaluate on certain call types