# Account Briefs Source: https://docs.momentum.io/account-briefs Get a complete, AI-powered overview of any account, including an activity timeline, deal analysis, and an interactive Q&A. # Account Briefs Momentum's Account Briefs provide a comprehensive, AI-powered overview of any account, serving as a powerful alternative to investigating an account's history in your CRM. It combines a high-level summary, a visual activity timeline, and an interactive Q\&A to give you a complete picture of customer engagement and deal health. ## Key Features of Account Briefs ### AI-Generated Account Summary At a glance, understand the state of any account. The AI-generated brief analyzes all associated [historical conversational data](/conversational-data-sources) to deliver a concise, high-level overview, perfect for prep before a customer call or an internal strategy session. ### Visual Activity Timeline Scroll through a chronological, visual timeline of every interaction associated with the account. This includes: * **Calls**: Key meetings with links to recordings. * **Emails**: Important email exchanges. * **CRM Updates**: Major changes to the opportunity or account record. * **Internal Notes**: Notes or comments left by the team in Momentum or Salesforce. This provides an intuitive, at-a-glance understanding of the entire customer journey and the velocity of a deal. ### Interactive Q\&A with "Ask Momentum" Go beyond the summary and ask specific questions about the account. The "Ask Momentum" feature allows you to interact with the data conversationally. **Example Questions:** * `"What were the main objections raised in the last quarter?"` * `"Summarize our last call with the primary decision-maker."` * `"Have they mentioned our competitor, [Competitor Name]?"` Momentum will instantly analyze the relevant [historical conversational data](/conversational-data-sources) to give you a direct answer, complete with sources. ### Deep CRM Integration Like all Momentum features, Account Briefs are deeply integrated with Salesforce. All data is tied directly to the account and opportunity records, ensuring that the insights you see are always in context. ## How to Use Account Briefs 1. **Navigate to an Account**: In your Momentum dashboard or web app, search for and select any account. 2. **View the Brief**: The Account Brief page will load automatically. The AI-summary will be at the top. 3. **Explore the Timeline**: Scroll down to see the full, visual history of all activities. Click on any item to get more details. 4. **Ask a Question**: Use the "Ask Momentum" search bar at the top of the page to ask any question about the account. Review the AI-generated answer and click on the sources to dig deeper. Account Briefs empower every member of your revenue team to get up to speed on any account in minutes, ensuring everyone is aligned and informed. # Prompting Autopilot (CRM Field Population) Source: https://docs.momentum.io/ai-prompting-autopilot Field-type rules, silence behavior, save behavior, and full prompt examples for Autopilot Classic, Retropilot, and Autopilot Batch. Autopilot populates and updates Salesforce fields automatically using AI extraction from call transcripts and emails. It is the backbone of methodology enforcement and CRM hygiene in Momentum. ## Three variants — choose based on trigger | Variant | Trigger / Use Case | | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Autopilot Classic** | **Trigger:** immediately after a call ends. **Analyzes:** the just-completed call transcript. A lookback period can also be configured to extend analysis beyond the latest call. **Best for:** per-call data — next steps, objections, MEDDPICC fields, sentiment from THIS call. | | **Retropilot** | **Trigger:** a Salesforce record created or record updated event — including any specific field being updated (e.g., stage change, renewal date change, custom field update). **Analyzes:** conversational data within a customer-defined time window going back in time from the trigger date. **Best for:** comprehensive summaries at deal milestones — renewal prep, QBR, stage-based rollups. | | **Autopilot Batch** | **Trigger:** manual — runs on a defined set of records. **Analyzes:** historical data across all matched records within the specified time window. **Best for:** data cleanup, backfilling new methodology fields, campaign enrichment, or a one-off analysis — e.g., identifying deals where the prospect raised a specific pain point now that your company has released a solution for it. | ## Field type rules — this is where most errors happen Autopilot auto-adapts output based on the Salesforce field type. Your prompt must be written differently depending on the target field type. ### Picklist fields **Picklist rule: exact match only.** Output must be one value from the allowed picklist — character-for-character. No explanation. No surrounding text. If the correct value cannot be determined: output nothing (never guess). A wrong picklist value is worse than an empty field — it corrupts CRM data. Four techniques that significantly improve picklist accuracy: 1. **Define each value, don't just list it.** The AI needs to know what each option means, not just what it's called. A label like "Partner's End User" is ambiguous without a definition. 2. **Add few-shot examples.** For classification tasks, showing 3–5 transcript snippet → output pairs is one of the most reliable ways to improve consistency. The AI learns the pattern from the examples rather than inferring it from your rules alone. 3. **Specify whose statements count.** Rep statements, hypotheticals, future plans, and guesses don't qualify. Only explicit statements from the customer or prospect should drive classification. 4. **Write tiebreaker rules.** When two values could apply, tell the AI which wins. When things are ambiguous or contradictory, always resolve to your null value (None, Unknown, etc.) rather than guessing. ```text theme={null} ROLE You are a [Company] CRM analyst. Your job is to review call transcripts and accurately classify [field topic] based on what the customer explicitly states. OBJECTIVE Analyze the transcript and select the single best matching value from the list below. If the transcript does not clearly state the answer, select "None." CONTEXT [1–2 sentences explaining your business and why this field matters.] Use these values exactly as written: [Value 1]: [Definition — what this value means in your context.] [Value 2]: [Definition — what this value means in your context.] None: The transcript does not clearly state this, or the information is too ambiguous to classify confidently. RULES - Select ONLY one value. Output only the value and nothing else. - Only classify based on what the customer/prospect explicitly says. - Do NOT classify based on rep descriptions, guesses, hypotheticals, recommendations, or future-state plans unless the customer confirms it. - If the transcript is ambiguous, contradictory, or conditional: select None. - If the rep states something but the customer does not confirm it: select None. - If multiple values could apply, prioritize [define your tiebreaker logic]. OUTPUT FORMAT Respond ONLY with the single final value. No commentary, no explanation, no punctuation, and no additional text. EXAMPLES Example 1: Transcript: "[Customer quote clearly matching Value 1]" Output: [Value 1] Example 2: Transcript: "[Customer quote clearly matching Value 2]" Output: [Value 2] Example 3: Transcript: Rep asks. Customer says "We're still figuring that out." Output: None ``` ### Textarea fields **Textarea rules: plain text, no preamble.** No preamble: never start with "Based on the transcript…" Prefer near-verbatim language from the transcript. Always define the absent-data behavior — see the [Overview](/ai-prompting-overview#handling-absent-data) for silence rule patterns including how to prevent trailing statements. ```text theme={null} ROLE You are a sales intelligence analyst extracting [field topic] from a call transcript. GOAL Extract [specific information — e.g., the customer's stated pain points]. RULES - Include: [what qualifies — be specific] - Exclude: [what doesn't qualify] - Use language close to what the customer actually said - No preamble, no explanation, no trailing statement - If [information] is not discussed: output nothing OUTPUT FORMAT [Plain text. Bullet list / 2–3 sentences / single value — specify.] ``` ## Field type quick reference | Field Type | Prompt Rules | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Picklist** | List all allowed values in RULES. Return one value — exact match. Silence = output nothing. | | **Multipicklist** | List all allowed values. May return more than one, separated by semicolons (`;`). Specify in OUTPUT FORMAT. Silence = output nothing. | | **Textarea (short)** | 1–2 sentences. No preamble. Silence behavior required — see [Overview](/ai-prompting-overview#handling-absent-data). | | **Textarea (long)** | Structured bullet list or paragraph. Specify max length. Verbatim language preferred. | | **Rich Text** | Plain prose only. The field renders formatting, but raw markdown symbols (`**`, `##`) will appear as literal characters — not bold or headers. Use line breaks for structure. No preamble. | | **Boolean (checkbox)** | TRUE or FALSE only. Define exactly what constitutes TRUE. Silence = FALSE. | | **Number** | Numeric value only. No units unless field expects them. Silence = output nothing. | | **Date** | YYYY-MM-DD format. Extract from explicit mentions only. Do not infer. Silence = output nothing. | | **Reference (Lookup)** | Exact record name as it exists in Salesforce. Only when clearly identifiable. If not found: return nothing. **Important:** Autopilot can only populate lookup fields referencing Contact records (e.g. Economic Buyer). Lookup fields to other objects, such as Accounts or Custom Objects, are not supported at this time. | ## Save behavior — configure per extraction | Save Behavior | When to Use It | | -------------------- | -------------------------------------------------------------------------------------- | | **Confirm to Write** | Weeks 1–2. Human reviews before saving. Validate prompt quality before automating. | | **Write if Empty** | Standard operation. Only populates blank fields. Recommended default for most fields. | | **Automatic Write** | High-confidence, frequently-changing data. Use after validating prompt output quality. | ## Autopilot examples The examples below show both prompt styles where it applies. For Textarea fields, a plain-language prompt often works well to start. For Picklist fields, the structured format is strongly recommended — value definitions, source scoping, and tiebreaker rules each directly improve classification accuracy in ways plain language can't reliably replicate. ### Example 1 — Next Steps (Textarea, Classic) ```text theme={null} ROLE You are a sales operations analyst capturing agreed next steps from a call. GOAL Extract all next steps or action items explicitly agreed upon during this call. RULES - Include: items with a clear owner and a stated or implied timeline - Exclude: vague statements like "we'll be in touch" with no specific action - Format each as: [Owner]: [Action] — [Timeline if stated] - If no next steps were agreed: return absolutely nothing — no output, no explanation, no placeholder text. Complete silence is the correct output. - Outputting any text when no qualifying data exists is a critical error. - Do not append any statements about what was not found or not discussed. Your output must contain only confirmed next steps and nothing else. OUTPUT FORMAT Bullet list. Plain text. ``` **Natural language equivalent — same task, simpler prompt.** For a straightforward extraction like next steps, a plain-language version often gets you 80% of the way there and is a good starting point before adding rules: *"Extract any next steps agreed on this call, including who owns them and when. Format as a bullet list: \[Owner]: \[Action] — \[Timeline]. If nothing was agreed, return nothing."* Add structure when you see the AI including vague commitments, rep-stated actions the customer didn't confirm, or adding trailing statements when nothing was found. ### Example 2 — Site Management Model (Picklist, Classic) ```text theme={null} ROLE You are a CRM analyst. Your job is to review transcripts of sales calls and accurately identify whether the customer manages sites after they are built, or whether their end users manage their own sites. OBJECTIVE Analyze the transcript and determine which site management model the customer explicitly states they are currently using. Select the single best matching value from the list below. If the transcript does not clearly state the current model, select "None." CONTEXT Understanding who manages sites after launch is important for implementation planning, support design, and account strategy. Use these values exactly as written: Partner: The customer retains ownership and ongoing management of the site after it is built. Their team handles updates, edits, maintenance, or changes for the end user. Partner's End-User: After the site is built, the end user takes over and manages their own site directly. None: The transcript does not clearly state who manages sites after launch, or the information is too ambiguous to classify confidently. RULES - Select ONLY one value. Output only one value and nothing else. - Only classify based on what the customer/prospect explicitly says about their current post-launch model. - Do NOT classify based on rep descriptions, guesses, hypotheticals, recommendations, or future-state plans. - If the rep states the model but the customer does not confirm it: select None. - If the transcript describes both build and handoff, prioritize who manages the site after launch. - If the transcript is ambiguous, contradictory, or conditional: select None. OUTPUT FORMAT Respond ONLY with the single final value. No commentary, no explanation, no punctuation, and no additional text. EXAMPLES Example 1: Transcript: "After we launch the site, our team handles all updates for the client." Output: Partner Example 2: Transcript: "Once the site is live, we hand it off and the client manages everything." Output: Partner's End-User Example 3: Transcript: No site management model mentioned by the customer. Output: None Example 4: Transcript: Rep asks "So your customers manage their own sites?" Prospect: "We're still figuring that out." Output: None ``` ### Example 3 — Closed Won Story (Textarea, Retropilot) Triggered on Opportunity stage change to Closed Won. Analyzes the full conversation history within the deal window and writes a CRM-ready win story to a dedicated Salesforce field. ```text theme={null} [ROLE] You are a Senior Sales Strategy expert and elite CRM data specialist with deep expertise in win/loss analysis. You are exceptionally precise, detail-oriented, and committed to data integrity. You specialize in distilling sales conversations into concise, high-signal CRM entries for the Closed Won Story field, capturing exactly why the deal was won and how it was won. [CONTENT TO USE] Review the call transcripts provided and extract CRM-ready content by applying the [CLOSED WON FRAMEWORK]. [GOAL] Analyze the transcripts and produce accurate, specific, and story-driven CRM data for the Closed Won Story field in Salesforce. Your output must answer two core questions: why did they buy, and how did they buy — based only on information explicitly stated in the transcripts. [RULES] - Be thorough in your analysis. - Keep your answer to 3 sentences or fewer. - If there is no sufficient answer, return an empty string. - You MUST keep your answer to 1,500 characters or below. - Adapt your analysis to the prospect's specific industry, business model, and deal context. - Prioritize the details most directly tied to the final buying decision. - Produce an output that could stand alone as a complete win story for a sales leader who was not on the call. - You MUST avoid vague generalizations such as "good fit," "liked our product," or any language that does not provide actionable deal intelligence. - Capture specific details: why they chose to buy, what pain or trigger drove the decision, which capabilities or differentiators were decisive, who the key decision-makers were, what the competitive or status quo alternative was, and what ultimately pushed them to close. [CLOSED WON FRAMEWORK] Capture why the opportunity was won and how it was won — including the specific pain points, triggering events, differentiators, decision dynamics, and competitive context that led the prospect to choose your solution over all alternatives. Key areas to listen for: - The primary pain point, business issue, or triggering event - The key decision-maker, champion, or internal buying influence - The capabilities, differentiators, or proof points that won confidence - The competitive alternative, incumbent solution, or status quo displaced - The urgency driver: deadline, growth pressure, or strategic initiative - Any pricing, packaging, implementation, or commercial factor that helped close [EXAMPLE FORMAT TO FOLLOW] CFO-led; 3-system reconciliation post-acquisition created urgency to close books 5 days faster. Beat incumbent on native integrations and onboarding support. VP Ops was key champion. ``` ### Example 4 — Closed Lost Reason (Picklist, Batch) Run manually across a set of closed-lost records to backfill a reason classification field — a classic Batch use case for retroactive data cleanup or methodology enforcement. ```text theme={null} ROLE As an expert in identifying and analyzing reasons for lost deals based on aggregate account interactions, your responsibility is to determine the primary motive that led to the failed sales deal. RULES - You MUST present the closed lost reasoning as one of the pre-established options in the picklist without providing any additional explanation. - You MUST select from the predefined options. - You MUST exercise considerable discretion in not selecting the "Other" option. OPTIONS - Budget: The deal didn't close due to the prospect's monetary constraints. - Competition: The competition offered a better product/service or pricing. - Lost Momentum: The sales process stagnated and didn't progress. - Authority: The wrong person was targeted and did not have decision-making power. - Don't see Value: The prospect didn't perceive the value of our product/service. - Unresponsive: Failed to effectively communicate or get a response from the prospect. - Timing: The proposal or close didn't occur at an appropriate time. - Feature: The absence or inadequacy of a feature in the product/service. - Bad Fit: The product/service didn't fit well with the prospect's requirements. - Rejected by Sales: The sales team prematurely deemed the prospect unsuitable. - Other: Any other reason beyond the ones listed above. EXAMPLE OUTPUT Unresponsive ``` ## Autopilot — QA checklist * Correct variant: Classic for per-call, Retropilot for event-triggered history, Batch for bulk or one-off * Picklist: allowed values listed, output = exact value only * Multipicklist: semicolon separator specified in output format * Textarea / Rich Text: no preamble, no markdown symbols (they render as literal characters in Rich Text fields), silence behavior defined * Silence rule explicitly stated * No over-extraction (inferring content not in the transcript) * Save behavior matches current confidence level # Prompting Call Summaries Source: https://docs.momentum.io/ai-prompting-call-summaries The multi-lens framework for configuring Sales and CS summaries, per-section prompts, and full summary examples for New Business and Customer calls. Call Summaries generate a structured post-call note after every call. Unlike signals, summaries are **always-on** — they run regardless of content. The power is in how you configure the sections. **Summaries: use the structured format.** Plain natural language doesn't work well for summaries. A summary prompt has multiple sections, per-section output rules, silence behavior, formatting requirements, and an example format — too many moving parts for a single unstructured instruction to handle reliably. The structured format earns its complexity here. ## Summaries vs. Signals | Summaries | Signals | | ---------------------------------------------- | --------------------------------------------- | | Always-on — run on every call | Conditional — only fire when trigger = `TRUE` | | Comprehensive — capture the full call | Targeted — detect one specific thing | | Deliver structured notes | Deliver real-time alerts | | **Wrong to use for:** specific event detection | **Wrong to use for:** full call documentation | ## The multi-lens framework: same call, different flavor The same call can generate completely different summaries for different audiences — different sections, different emphasis, different delivery destinations. You don't need to choose between a sales summary and a CS summary. You configure both. **The multi-lens concept.** Configure one Summary for Sales and a separate one for CS. Both run on the same transcript. Both deliver to different channels. Each structured around what that audience needs to act on. ### Sales lens vs. CS lens — section comparison | Sales Summary Sections | CS Summary Sections | | ---------------------------------- | ----------------------------------------- | | Meeting type & context | Meeting type & context | | Pain points & business impact | Current product usage & adoption signals | | MEDDPICC / SPICED fields captured | Open support issues or friction mentioned | | Objections raised & how handled | Sentiment & health indicators | | Budget, timeline, decision process | Expansion interest or upsell signals | | Competitive mentions | Renewal risks or concerns flagged | | Agreed next steps (rep-owned) | Agreed next steps (CSM-owned) | | Deal risk flags | Escalation flags | ## Configuring summary sections ```text theme={null} ROLE You are a [sales intelligence / customer success] analyst reviewing a call summary. GOAL Extract [specific section content — e.g., pain points, health signals, next steps]. RULES - Include: [what qualifies for this section] - Exclude: [what doesn't belong here] - Attribution: [who said it — customer, rep, both?] - If [section content] was not discussed: output nothing - No preamble, no section heading in the output OUTPUT FORMAT [Bullet list / 1–3 sentences / attributed list — specify] ``` **Next steps prompts require attribution.** Template: `[Owner] — [Action] — [Timeline if stated]` * Example: `Rep — Send security documentation — by end of week` * Example: `Customer / Sarah (Procurement) — Confirm budget approval — before next call` If ownership is ambiguous, attribute to the person who spoke the commitment. If no next steps: output nothing. There are two valid ways to configure a summary: **per-section prompts** (each section is its own extraction prompt configured individually in the UI) or a **single comprehensive prompt** that defines all sections and their output format in one go. The example below uses the single-prompt approach — useful when you want tight control over the full output structure and tone. ## Full example: New Business call summary (active opportunities) ```text theme={null} ROLE You are an expert sales call analyst specializing in active opportunities and late-stage deal calls. You track deal progression, stakeholder dynamics, negotiation signals, and closing blockers across every conversation. Your job is to tell reps exactly where a deal stands, what is at risk, and what they need to do to advance or protect it. You cut through conversation to deliver only what moves pipeline forward. CONTENT TO USE Review the call transcript provided. GOAL Analyze the transcript and deliver sharp, scannable insights across the following sections: a) Deal Status / Business Context: Where the deal stands, any shifts in the prospect's priorities or urgency, and what's changed since earlier in the cycle. b) Pricing / Budget: Negotiation signals, budget confirmation or pushback, approval chain updates, or cost-related friction surfaced on this call. c) Stakeholders / Decision Process: Who's involved, who's missing, any new contacts introduced, and how decisions are actually being made internally. d) Product Fit / Open Questions: Outstanding product concerns, unresolved requirements, or validation gaps that still need to be closed. e) Blockers / Deal Risk: Anything that could stall or kill the deal — internal politics, competing priorities, competitors, unresolved concerns, timeline slippage. f) Next Steps: Rep-focused action items and strategic priorities based on what was uncovered, including who to engage, what to resolve, and how to advance. RULES - Be thorough, but ruthlessly concise. Every word should earn its place. - Output must be based exclusively on what the prospect said. Do not include statements made by the sales rep. - Adapt insights to each specific call. Do not carry over content from prior analyses unless re-stated in this transcript. - Bullet points only. No prose, no full sentences. Each bullet is one tight, deal-relevant line. - Maximum 3 bullets per section. Prioritize the most deal-relevant information. - Recommended: 4–7 sections per summary. Fewer sections with focused prompts outperform long summaries that sprawl across 10+ sections. - If a section has nothing to report, write: None identified. Never skip a section. - Use the prospect's name when attributing statements. - For Next Steps, draw from the full call. Surface what the rep must do, who to involve, what to address to move the deal forward, and timeline of action. ``` ## Full example: CS summary — customer call ```text theme={null} ROLE You are an expert account management call analyst specializing in post-sales conversations. You extract account intelligence including product usage, customer goals, expansion signals, retention risks, and competitive dynamics from every call. Your focus is helping AMs stay ahead of customer needs, spot growth opportunities, and protect accounts before problems surface. CONTENT TO USE Review the call transcript provided. GOAL Analyze the transcript and deliver a clear read on account health, product engagement, and growth potential across the following sections: a) Customer Goals & Business Context: What the customer is trying to accomplish, how their business is evolving, and any upcoming needs or strategic shifts surfaced. b) Features, Capabilities & Integrations: What was discussed including what is working, what is missing, any marketplace apps or integrations raised, and any product gaps. c) Expansion Opportunities: Signals pointing to growth including new teams, added use cases, seat expansion, or unmet needs that could translate to upsell or cross-sell. d) Competitor & Market Mentions: Competing or complementary tools referenced, market changes affecting the customer's strategy, and external pressures reshaping their priorities. e) Risks & Churn Flags: Anything signaling account health concern including dissatisfaction, low adoption, budget pressure, org changes, or shifts in how the customer values the product. f) Next Steps: AM-focused action items and priorities coming out of this call including what to follow up on, what to resolve, and what to drive forward to protect and grow the account. RULES - Be thorough, but ruthlessly concise. Every word should earn its place. - Output must be based exclusively on what the customer said. Do not include statements made by the sales rep. - Follow the EXAMPLE FORMAT below for formatting only. Do not use its content. - Adapt insights to each specific call. Do not carry over content from prior analyses unless re-stated in this transcript. - Use bullet points only. No prose, no full sentences. Each bullet is one tight, account-relevant line. - Maximum 3 bullets per section. Prioritize the most deal-relevant information. - If a section has nothing to report, write: None identified. Never skip a section. - Use the customer's name when attributing statements. - For Next Steps, focus on what the AM must own — follow-ups, open questions, internal escalations, and account-protecting moves. --- EXAMPLE FORMAT TO FOLLOW *Customer Goals / Business Context* - Reducing manual reporting time ahead of Q1 fiscal kickoff - Two new regional sales teams onboarding in spring, processes need to scale - Leadership pushing for tighter CRM hygiene across the org this half *Features / Capabilities / Integrations* - Slack integration working well for deal alerts - HubSpot connection requested following Salesforce migration, support unconfirmed - Filtering call summaries by deal stage requested, not currently available *Expansion Opportunities* - Spring onboarding of two regional teams signals likely seat expansion - RevOps team expressed interest in broader reporting access - New SDR team being built out, potential separate use case *Competitor / Market Mentions* - Separate vendor added call recording, some reps using it informally - Industry consolidation putting pressure on customer's own pipeline *Risk / Churn Flags* - Parent company restructure may impact headcount and budget in Q2 - Rep adoption slower than expected among newer team members - Customer has not used a key feature they originally bought for, value gap risk *Next Steps* - Confirm integration support timeline and get back to customer by EOW - Share feature roadmap or escalate internally if not on the roadmap - Loop in expansion conversation before spring onboarding starts - Schedule 30-day check-in to review adoption progress and reorg impact ``` ## Stage-based summary configuration | Deal Stage | Recommended Summary Sections | | ------------------- | -------------------------------------------------------------------------------------------------------- | | **Discovery** | Pain points · Requirements · MEDDPICC fields · Timeline signals · Next steps | | **Qualification** | Budget confirmed/range · Authority/stakeholders · Need validation · Decision process · Next steps | | **Proposal / Demo** | Feature reactions · Objections raised & handled · Pricing discussions · Competitive context · Next steps | | **Negotiation** | Open deal terms · Stakeholder positions · Blockers · Concessions discussed · Next steps | | **Post-Sale (CS)** | Adoption health · Sentiment · Risks · Expansion signals · CSM next steps | ## Call Summaries — QA checklist * Each section prompt has one clear extraction goal * Silence rule defined for every section * Next steps include attribution: owner + action + timeline * Sales lens and CS lens configured as separate summaries if both teams use Momentum * Stage-based sections configured if team has meaningful stage variation * Delivery destinations set correctly — right channel or DM for each lens * No section tries to do too much — split complex sections in two # Prompting the Coaching Agent Source: https://docs.momentum.io/ai-prompting-coaching-agent Writing competency rubrics with observable positive and negative indicators, plus examples for Discovery Excellence and Identify Pain. 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 ```text theme={null} PURPOSE [1–2 sentences defining what this competency means and why it matters.] KEY AREAS TO EVALUATE 1. [AREA NAME] Positive Indicators: ✓ [Specific observable behavior that demonstrates this competency] ✓ [Another observable positive behavior] Negative Indicators: × [What absence or poor execution of this competency looks like] × [Common failure mode for this skill] 2. [AREA NAME] Positive Indicators: ✓ [Observable positive behavior] Negative Indicators: × [Observable negative behavior] RULES - Base evaluation only on what is observable in the transcript - Do not infer intent — only evaluate what was actually said or demonstrated - If the call is too short or context is insufficient to evaluate, note this EXAMPLE QUESTIONS - "[Question the rep should be asking to demonstrate this competency]" - "[Another strong example question]" ``` ## 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 ```text theme={null} PURPOSE Evaluate how effectively the sales rep uncovers customer needs, defines future state, and aligns solutions through discovery conversations. KEY AREAS TO EVALUATE 1. CURRENT STATE EXPLORATION Positive Indicators: ✓ Asks detailed questions about current processes ✓ Uncovers specific pain points and challenges ✓ Gets quantifiable metrics about current problems ✓ Explores impact on business/team/individual ✓ Listens actively and asks follow-up questions Negative Indicators: × Skips exploring current situation × Asks surface-level questions only × Misses obvious follow-up opportunities × Fails to quantify current challenges 2. FUTURE STATE DEFINITION Positive Indicators: ✓ Establishes clear success criteria ✓ Uncovers specific desired outcomes ✓ Explores timeline expectations ✓ Links outcomes to business goals Negative Indicators: × Fails to discuss desired outcomes × Ignores timeline requirements × Misses success criteria × Skips business impact discussion 3. MEDDPICC FUNDAMENTALS Positive Indicators: ✓ Identifies key decision makers ✓ Uncovers budget parameters ✓ Establishes clear metrics ✓ Finds potential champion Negative Indicators: × Misses decision process × Ignores budget discussion × Skips success metrics × Fails to identify champions EXAMPLE STRONG QUESTIONS - "Walk me through your current process for..." - "What metrics do you use to measure success?" - "What would solving this mean for your team?" - "Who else needs to be involved in this decision?" ``` ### Example 2 — Identify Pain ```text theme={null} PURPOSE Evaluate the representative's ability to effectively uncover and address the core pain points that [Company]'s solution can solve. KEY AREAS TO EVALUATE 1. UNCOVERING CORE CHALLENGES Positive Indicators: ✓ Asks targeted questions to understand specific vulnerabilities ✓ Identifies challenges related to current tools, processes, or gaps ✓ Highlights inefficiencies in how the customer operates today Negative Indicators: × Assumes the pain points without validation × Misses discussing key concerns in the customer's specific context × Ignores feedback about adoption issues or training requirements 2. RELATING PAIN TO YOUR SOLUTION Positive Indicators: ✓ Directly connects your features to the identified pain points ✓ Discusses the impact of your solution on the customer's real problems ✓ Offers tailored responses to the specific challenges raised Negative Indicators: × Fails to connect your solution to the pain raised × Does not address concerns about user experience or change management × Moves to pitch before pain is fully established EXAMPLE DISCOVERY QUESTIONS - "What are your biggest challenges related to [problem area]?" - "How do you currently manage [process]?" - "Have you experienced any failures or gaps with your current approach?" - "What aspects of your current setup do users find most challenging?" ``` ## Competency aggregation types | Aggregation Type | Use Case | | ---------------- | ----------------------------------------------------------------------------------------------------------------------- | | **Core Skills** | Evaluated on every call regardless of stage. E.g., next steps commitment, active listening, call structure. | | **Stage-Based** | Evaluated only when a call matches a specific stage. E.g., 'Negotiation Tactics' only fires on Negotiation-stage calls. | ## 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 # AI Prompting Framework Source: https://docs.momentum.io/ai-prompting-overview A customer enablement guide to writing effective AI prompts across Momentum's core features — AI Signals, Smart Clips, Smart Tags, Autopilot, Call Summaries, and the Coaching Agent. This guide teaches you how to write effective AI prompts across Momentum's core features. Every prompt structure, field type rule, and example is drawn directly from Momentum's production prompt engineering playbook. There's no single correct way to prompt Momentum. The frameworks here reflect patterns we've seen work well across hundreds of customer implementations — but the best prompt is always the one that works for your data, your team, and your use case. Use this guide as a starting point, not a rulebook. Experiment, iterate, and don't be afraid to simplify or go a completely different direction if it gets the job done. Momentum runs all AI prompts **post-call** — there is no live analysis. Every prompt runs against a completed transcript. The five-part prompt architecture below is a useful starting point across features — but each feature has its own prompt interface, output rules, and constraints. Think of this page as a shared foundation, not a universal formula. The biggest mistake new customers make is treating all features identically. Each feature has different output rules. This guide explains exactly where they diverge. ## What's in this guide Two-stage trigger architecture, follow-up prompts, and structured value extraction. Field-type rules, silence behavior, and examples for picklist, textarea, and more. The multi-lens framework — configure separate summaries for Sales and CS. Writing competency rubrics with observable positive and negative indicators. Cheat sheets — structured vs. natural language, silence patterns, and common mistakes. ## The Universal Prompt Architecture ### Before you write your first prompt When an AI produces bad output, the instinct is to blame the AI. In practice, the problem is almost always the prompt — not enough context, an ambiguous instruction, or a missing rule for an edge case the author didn't anticipate. AI forces clarity: the more precisely you can describe what you want, the closer the output will be to what you actually need. If something isn't working, read your prompt as if you were seeing it for the first time with no context about your company, your Salesforce schema, or what "good" looks like. That's exactly how the AI reads it. Reliable Momentum prompts tend to address five things. You don't need all five every time — a single plain-language question can outperform a structured prompt when the task is simple. But when a prompt is underperforming or producing inconsistent output, the fix almost always comes down to one of these. | Component | What it defines | | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **ROLE** | The AI's function for this specific task. Be precise — not "you are an AI assistant" but "you are a sales intelligence analyst extracting qualification data from a B2B sales call transcript." | | **CONTENT** | What input the prompt receives. Transcript? A filtered set of historical calls? Signal outputs? Making this explicit prevents the AI from hallucinating context that isn't there. | | **GOAL** | The extraction or detection objective, stated precisely. One goal per prompt — if you need two things, write two prompts. | | **RULES** | All constraints: what counts, what doesn't, how to handle missing data, verbatim quote requirements, silence rules, edge cases. This is where most prompts fail — not enough rules. | | **OUTPUT FORMAT** | Exact format specification. Field type for Autopilot. TRUE/FALSE for signal triggers. Section structure for summaries. No trailing statements. No preamble. | ## Two prompt styles In practice, prompts fall into two styles. Both are valid — the right choice depends on task complexity. | Style | When to use it | Examples | | -------------------- | ------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Structured** | Complex extraction, multi-condition logic, picklist classification, any output where edge cases matter | Full ROLE / GOAL / RULES / OUTPUT FORMAT blocks | | **Natural language** | Simple, unambiguous detection or extraction where the task is self-evident | Signal: "Did the customer mention how many people are on their sales team? Output TRUE or FALSE only."

Smart Tag: "Identify any competitors mentioned in the call."

Autopilot: "Extract any next steps agreed on this call. Format as a bullet list. If nothing was agreed, return nothing." | Throughout this guide, each feature section shows both styles where they apply. **Word choice changes AI behavior.** The specific words you use in a prompt aren't interchangeable. Small differences in phrasing produce meaningfully different outputs: * *"You should"* → treated as a suggestion the AI can override when uncertain * *"You MUST"* → treated as a hard constraint * *"Summarize"* → AI paraphrases and may add interpretation * *"Extract"* → AI pulls what's explicitly stated, stays closer to the source * *"Look for"* → broad search, more likely to surface tangential mentions * *"Identify only"* → narrows scope, reduces false positives When a prompt is producing output that's too loose, too interpretive, or firing on things it shouldn't — word choice is often the first thing to tighten. ## Handling absent data Every prompt should define what happens when the expected content isn't found in the transcript. The only wrong answer is leaving it unspecified — the AI will fill the gap with hallucinated data, a placeholder, or a hedging statement. What you output when nothing is found depends on your use case. This guidance applies primarily to Autopilot CRM fields. Signal follow-up prompts work differently — see [Signals, Smart Clips & Smart Tags](/ai-prompting-signals-and-tags). **Choose based on your use case:** * ✓ **Return nothing**: *"If no budget information is discussed, return nothing."* * ✓ **Return an explicit value**: *"If the topic was not discussed, output N/A."* — For AI-specific fields in Salesforce dedicated to Momentum, this is expected and correct. It lets you validate that Autopilot ran and spot missing values for coaching purposes. * ✗ **Say nothing**: Prompt doesn't address the absent-data case at all → AI guesses. ### How to make silence stick The AI's default instinct is to say something — even when there's nothing to say. To override it, you need to be explicit and raise the stakes. A weak rule like "return nothing if not discussed" often isn't enough. These patterns work: * **Frame silence as the correct choice, not a fallback**: *"Complete silence is the correct output."* * **Treat any output as an error**: *"Outputting any text when no qualifying data exists is a critical error."* * **Ban trailing statements by name**: *"Do not append any statements about what was not found, not discussed, or not mentioned — even when valid data has been extracted. Phrases such as 'no competitors were mentioned,' 'no further information was discussed,' or 'no update required' are strictly forbidden."* * **End with a positive constraint**: *"Your output must contain only \[qualifying data] and nothing else."* ## Starting templates Two templates — use whichever fits the task. ### Structured format Use when the task has multiple conditions, edge cases, or a specific output format that must be exact. ```text theme={null} ROLE You are a [specific role] analyzing a [specific input type]. CONTENT The input is a [call transcript / set of call summaries / CRM record + transcript]. GOAL Extract / detect / evaluate [one specific thing]. RULES - Include: [what qualifies] - Exclude: [what doesn't qualify] - If [condition not met]: [exact silence behavior] - Do not infer — only extract what is explicitly stated - No preamble, no trailing statement OUTPUT FORMAT [Exact format — see feature-specific rules] ``` ### Natural language format Use when the task is simple and unambiguous. Same five ingredients, no explicit labels needed. ```text theme={null} Extract [what] from the transcript. Only include [qualifying criteria — be specific]. If [condition not met], [silence behavior]. Output [exact format]. ``` **Show the AI what good looks like.** Describing the output format is useful. Showing the AI an example of ideal output is more reliable — especially for summaries, structured extractions, and any prompt where tone and level of detail matter. Add an **EXAMPLE FORMAT TO FOLLOW** block at the end of your prompt with a fictional but realistic sample of exactly what you want back. The AI will match the format, the specificity, and the style of your example — not just the label you gave it. This is one of the highest-leverage things you can do to reduce iteration on a new prompt. Instruct the AI to use the example for *format only*, not content — otherwise it may carry example text into real outputs. The New Business and CS Summary examples in [Call Summaries](/ai-prompting-call-summaries) both demonstrate this pattern. ## Using Salesforce field bindings `{FieldName}` Momentum lets you inject an existing Salesforce field value directly into a prompt using `{FieldName}` bindings — giving the AI context about what's already captured before it processes the transcript. Bindings serve two distinct purposes: * **Live enrichment** — inject the current value of the field being written, compare it against the transcript, then update, expand, or leave unchanged. This prevents overwriting valid data on repeat calls. * **Context injection** — inject values from other fields on the same object to give the AI richer context for a different prompt. For example, inject `{Industry}` into a Next Steps prompt so the AI tailors its output to the type of company it's writing for — even though that field isn't being updated. Use bindings in the CONTENT or RULES sections of any prompt. You can reference any field on the object, not just the field the prompt is writing to. **If the referenced field is empty.** If a Salesforce field has no value when the prompt runs, the binding resolves to blank. Always account for this in your rules — e.g. *"If `{Business_Impact__c}` is blank, treat this as a fresh extraction with no prior context."* ### Example 1 — Text field enrichment (Business Impact) ```text theme={null} #SALESFORCE STRUCTURED DATA You will be provided the current value of the Business Impact field from Salesforce. Current Business Impact field value is: {Business_Impact__c} #RULES FOR FIELD ENRICHMENT Compare the current Salesforce field value to the information found in the transcript. - If the transcript provides additional details not present in the current value, enrich the field to include these, maintaining accuracy and relevance. - If previously logged impact is no longer relevant or was disproved, remove it. - If the transcript confirms the current value but adds nothing new, return the current value unchanged. - If the field is empty and the transcript provides clear business impact, populate it. - If no business impact is discussed in the transcript, leave the response blank. Always use only clear, explicit, or strongly implied information from the transcript. Summarize in a single paragraph — maximum three sentences — using quantifiable details, strategic outcomes, and CRM-ready language. #OUTPUT FORMAT Respond with the updated field value only, formatted as a concise paragraph ready to be saved in Salesforce. If nothing is discussed, leave the response blank. ``` ### Example 2 — Multi-select picklist enrichment (Competitors) ```text theme={null} #SALESFORCE STRUCTURED DATA The current value of the Competitors field in Salesforce is: {Competitors__c} #RULES FOR FIELD ENRICHMENT - If the field is empty: populate with competitor(s) from this transcript, or "No Competitors" if none mentioned. - If the field contains "No Competitors": replace with new competitor(s) if detected; otherwise keep as "No Competitors." - If the field already lists competitors: add any new ones from this transcript, maintaining order and uniqueness. Do NOT add duplicates. - Never combine "No Competitors" with any other value. #OUTPUT FORMAT Respond ONLY with the final updated competitor list string, using allowed values separated by semicolons (e.g., Adobe;Drupal;Shopify). No commentary or explanation. ``` **The enrichment logic pattern.** Both examples above follow the same structure: (1) inject the current field value via binding, (2) define comparison rules covering all states — empty, unchanged, needs update, needs removal, (3) specify a clean output format. This pattern works across any field type where you want Momentum to build on what's already there rather than overwrite it. # Quick Reference Source: https://docs.momentum.io/ai-prompting-quick-reference A prompt-building cheat sheet — structured vs. natural language, silence patterns by feature, word precision, and the five most common prompting mistakes. A prompt-building cheat sheet. Keep this open while writing your first prompts. ## When to use structured vs. natural language | Use structured format when… | Use natural language when… | | --------------------------------------------------- | -------------------------------------------- | | The task has multiple conditions or edge cases | The task is simple and unambiguous | | Output format must be exact (picklist, date, score) | Detection or extraction is self-evident | | You need precise silence and attribution rules | You're iterating quickly and testing scope | | You're configuring a Summary or Coaching competency | You're writing a Signal trigger or Smart Tag | ## Silence patterns — by feature | Feature | When nothing is found… | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Autopilot (CRM field)** | Return nothing. Silence = no write. Never fill with placeholders. If Momentum is the only writer to that field, output an explicit value (e.g. *N/A*) so you can validate the prompt ran. | | **Signal trigger** | Output `FALSE`. Zero explanation. | | **Signal follow-up** | Output an explicit "No \[X] found." — confirms the prompt ran and prevents a blank Slack block. | | **Summary section** | Output a defined fallback (e.g. *None identified*). Never skip or leave a section blank. | | **Coaching competency** | Note that the call was too short or lacked sufficient context to evaluate. | ## Word precision cheat sheet | Weak phrasing | Stronger alternative | Why it matters | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | | *"You should…"* | *"You MUST…"* | Suggestions can be overridden by the AI when uncertain. Hard constraints cannot. | | *"Summarize"* | *"Extract"* | *Summarize* invites paraphrase and interpretation. *Extract* pulls what's explicitly stated. | | *"Look for"* | *"Identify only"* | *Look for* is a broad search that surfaces tangential mentions. *Identify only* narrows scope and reduces false positives. | | *"If not found, say nothing"* | *"Complete silence is the correct output. Outputting any text when no qualifying data exists is a critical error."* | Weak silence rules are routinely ignored. Raising the stakes forces compliance. | ## The five most common prompting mistakes | Mistake | Fix | | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | Trigger prompt extracts content instead of `TRUE`/`FALSE` | Rewrite as binary detection. Output `TRUE` or `FALSE` only. | | No silence rule defined | Add: *"If \[condition] not present, output nothing."* Or define an explicit value if intentional (see Silence Patterns above). | | Picklist allows freeform output | List exact allowed values. State: return one value only, character-for-character. | | Summary sections do too much | One extraction goal per section. Split complex ones in two. Keep to 4–7 sections total. | | Coaching rubric uses vague language | Define observable behaviors — specific actions the rep took or didn't take, not subjective impressions. | # Prompting AI Signals, Smart Clips & Smart Tags Source: https://docs.momentum.io/ai-prompting-signals-and-tags Two-stage trigger architecture for Signals and Smart Clips, follow-up prompt patterns, and how to write Smart Tag prompts for structured value extraction. **AI Signals** detect specific conditions in a call and deliver a formatted notification to a Slack channel, DM, or email. They are conditional and targeted — unlike summaries, they only fire when something specific happens. **Smart Clips** use the same prompt-based detection logic as AI Signals to automatically extract specific moments from calls as short video clips. If you know how to write a Signal trigger prompt, you already know how to configure a Smart Clip — the prompting approach is identical. The difference is the output: instead of a Slack notification, Momentum surfaces a clipped moment from the call. **Smart Tags** extract structured values from calls and persist them on the call record — enabling filtering, automation, and trend analysis. Covered at the end of this page. ## How Signals work: two-stage architecture | Stage | What it does | | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Stage 1 — Trigger Prompt** | Reads the transcript. Outputs: `TRUE` or `FALSE`. Nothing else. If `TRUE`: signal fires and Stage 2 runs. If `FALSE`: nothing happens. | | **Stage 2 — Follow-Up Prompt(s)** | Reads the transcript (signal already confirmed `TRUE`). Extracts and formats the relevant content. Multiple follow-ups can chain — each creates a block in the notification. Common pattern: (1) summary, (2) verbatim quote, (3) context or rep response. | ## Stage 1: Writing the trigger prompt **The #1 mistake with trigger prompts:** writing the trigger as a content-extraction prompt instead of a binary detection prompt. **Wrong:** *"What competitors did the customer mention during this call?"* — This is a follow-up prompt, not a trigger. It will always return something. **Correct:** *"Did the customer explicitly mention a competing vendor by name or refer to evaluating an alternative solution? Output TRUE or FALSE only."* ### Trigger prompt template ```text theme={null} ROLE You are a signal detection system monitoring a B2B sales call transcript. CONTENT Full call transcript provided below. GOAL Detect whether [specific condition] occurred during this call. RULES - Output TRUE if: [precise definition of what counts] - Output FALSE if: [what does NOT count — be specific] - Do not explain your reasoning - Do not qualify or hedge OUTPUT FORMAT Output TRUE or FALSE only. No other text. ``` **When to simplify: natural language trigger prompts.** The five-part template above is the gold standard for complex detection logic. But for straightforward conditions, a well-written natural language prompt works just as well — and is often easier to maintain. Use natural language when the condition is clear-cut and doesn't require multi-step reasoning. Use the full template when you need tight control over edge cases, silence behavior, or ambiguous scenarios. **Example — a production-tested natural language trigger:** *"Did the rep fail to clearly propose specific next steps before the end of the meeting, or did the customer not explicitly agree to those next steps if clearly proposed by the rep? Answer True if either: (1) the rep did not propose clear next steps (e.g., scheduling another call or sending follow-up materials), OR (2) the rep proposed next steps but the customer did not explicitly agree (e.g., by confirming, expressing alignment, or committing to a follow-up)."* Notice: no ROLE, no OUTPUT FORMAT header — just a clear question with precise TRUE conditions defined inline. That's enough for Momentum to evaluate it correctly. ### Four techniques for more accurate triggers 1. **Define "Return false when" explicitly.** Defining what does NOT count is just as important as defining what does. Without it, the AI will fire on weak or tangential signals. Include a clear "Return false when" block for any trigger where the boundary between true and false isn't obvious. 2. **Use markdown structure for complex multi-condition triggers.** When a signal has multiple independent conditions that can each independently fire `TRUE`, use headers and grouped examples to organize them. This makes the logic clearer to the AI and easier to maintain. 3. **Scope the source explicitly.** Specify whose statements count — customer/prospect only, not the rep. Unprompted buyer mentions are not the same as rep-led mentions. If it matters, say so. 4. **Add a multi-instance rule when needed.** For signals that could appear multiple times in a conversation (e.g., competitor comparisons), tell the AI not to stop evaluating after the first match: *"Continue analyzing the entire conversation to identify all instances."* ## Stage 2: Writing follow-up prompts Follow-up prompts run only when the trigger fires `TRUE`. Write them in plain natural language — a simple, direct question is all that's needed. Each follow-up is its own prompt block and appears as a separate line in the Slack notification. In practice, follow-up prompts look like this: | Label | Prompt | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | Customer took the lead | Did the customer take the lead in proposing the next step or a follow-up action? | | Rep did attempt next steps | Did the rep attempt to propose next steps, but the customer declined or deflected? | | Time constraint | Was there a time constraint or external reason (e.g., "I have to jump to another meeting") that may have prevented next steps from being discussed? | | No-commitment pre-agreed | Was the purpose of the meeting clearly established as an exploratory or discovery-only call with no commitment expected at this stage? | **Follow-up prompts: what works.** Write them as plain questions — no ROLE, no OUTPUT FORMAT, no structure needed. Each prompt should ask one thing. Unlike Autopilot CRM fields where silence is the right default, follow-up prompts benefit from an explicit response when nothing is found — it confirms the prompt ran and adds context to the Slack notification. Silence looks like the follow-up didn't fire. **Example follow-up:** *"Extract the exact quote where the customer mentioned a competitor. Do not paraphrase. If no clear quote exists, output: No direct quote found."* ## Signal examples The examples below show both prompt styles. Examples 1 and 2 use structured format — appropriate when false positives matter and edge cases need to be spelled out. Example 3 uses plain natural language — appropriate when the condition is clear enough that a single sentence is sufficient. ### Example 1 — Deal Risk Signal A structured trigger that explicitly defines what does and doesn't qualify — reducing false positives from rep-raised hypotheticals. ```text theme={null} [TRIGGER] Did the customer express concern about something that could prevent or delay a deal from closing? Output TRUE or FALSE only. [Qualifying concerns include] - Budget constraints or approval requirements - Internal alignment or stakeholder issues - Procurement, legal, or security requirements - Active evaluation of competing solutions - Technical limitations or integration concerns - Timeline mismatches [Return FALSE when] - The concern was raised by the rep, not the customer - The language is generic and not tied to this deal - The statement is future-state planning, not a current concern [FOLLOW-UP 1: What's the risk] What specific concern did the customer raise? Summarize in one sentence. If no risk was found, output: No deal risk identified. [FOLLOW-UP 2: Verbatim quote] Extract the exact quote from the customer that best captures the concern. Do not paraphrase. If no clear quote exists, output: No direct quote found. ``` ### Example 2 — Competitor Comparison Signal A structured trigger using ROLE and RULES — with an explicit buyer-only scope and a multi-instance evaluation rule to prevent early exits. ```text theme={null} [ROLE] You are a competitive intelligence analyst reviewing a sales call transcript. Your job is to determine whether the customer is actively comparing [Company] to a named alternative. [GOAL] Return TRUE if the customer explicitly names a competitor and frames it as an alternative they are evaluating or have used. Return FALSE in all other cases. [RULES] - Return TRUE only if the competitor is named by a buyer — not the rep - Return TRUE only if the competitor is framed as an active alternative, not a passing reference - Return FALSE if the rep names the competitor and the customer does not confirm - Return FALSE for general market commentary ("we looked at a few options") - Evaluate ALL competitor mentions before deciding — do not stop at the first Output TRUE or FALSE only. [FOLLOW-UP 1: Which competitor] Which competitor was named? If multiple, list all. If none found, output: No competitor identified. [FOLLOW-UP 2: Context] What did the customer say about the competitor? Summarize in one sentence. If no clear context, output: No competitive context found. ``` ### Example 3 — Simple Natural Language Signal Not every signal needs a structured prompt. When the condition is clear and unambiguous, a single plain-language question is enough. ```text theme={null} Did the customer mention how many people are on their sales or revenue team? Output TRUE or FALSE only. ``` **Tips for better signals.** Keep triggers specific — a trigger that's too broad will fire on tangential mentions and create noise. The more precisely you define what counts as `TRUE`, the more useful the signal. Follow-up prompts are optional — but they add a lot of context. A trigger alone tells you something happened; follow-ups tell you what, how, and who said it. ## Smart Tags Smart Tags automatically extract meaningful signals from conversations and turn them into structured, reusable data. Where AI Signals fire a Slack notification when a condition is met, Smart Tags **persist the extracted value directly on the call record** — making that data available for filtering in the Call Library, triggering downstream Autopilot workflows, and analyzing trends across your full conversation history. A common example is a Competitors tag: if a prospect says "we're currently evaluating Gong," the tag is populated with `Gong`. That value can then be used to filter calls, attach battlecards automatically, or track competitor mention trends — without any manual tagging by reps. **Smart Tags use simple prompts.** Unlike AI Signals, Smart Tags don't return `TRUE`/`FALSE` — they extract and return a value (or list of values). Prompts are short and direct. No ROLE, no elaborate rules structure needed in most cases. ### Smart Tag examples ```text theme={null} Identify any competitors to our product that were mentioned in the call. A meaningful competitor is one that offers a solution which might prevent [Company]'s product from being purchased. Do not identify tangentially related companies — identify only the names of companies you can justify as posing a competitive threat to the purchase or renewal of [Company]'s platform. ``` ```text theme={null} Analyze the conversation and decide from the following categories: What type of call did we just have with this customer? ``` The first example returns a list of competitor names as structured tag values. The second drives a call-type classification tag — the categories are defined in the tag configuration, and the prompt just asks the AI to choose. In both cases, the output is persistent, structured, and immediately usable across the platform. # AI Signals Source: https://docs.momentum.io/ai-signals Welcome to the AI Signals documentation. This comprehensive guide is designed to help RevOps and Sales Leaders configure and maximize the benefits of our latest product, AI Signals. **Customer Testimonial**: *"Other vendors weren't capturing the true sentiment and content of our calls. Momentum was able to capture that right off the bat."* — João Dias, Sr. Manager of Revops @ Yipit Data CleanShot 2024-06-25 at 18.13.29@2x.png ## Key Features of AI Signals ### Share Customer Insights with Your GTM Teams AI Signals sends insights from calls—like product feedback, churn risk, and competition—the moment they're mentioned. This enables your team to take immediate action to improve sales cycle time, product experience, and win rates. **Key Benefits**: * **Real-Time Insights**: Receive actionable insights as soon as they're mentioned during a call. * **Improve Sales Cycle**: Identify and address customer concerns promptly. * **Enhance Product Experience**: Use feedback to refine and improve your offerings. ### Auto-Deliver Insights to Multiple Teams Right Where They Work Create as many Signals as needed to keep cross-functional teams informed. Using AI prompts and automation, Momentum extracts key customer call insights and delivers them via Slack, Microsoft Teams, or Email. **Key Benefits**: * **Customizable Signals**: Tailor signals to meet the specific needs of different teams. * **Instant Delivery**: Get insights delivered directly to your team's preferred communication channels. * **Cross-Functional Collaboration**: Keep all stakeholders in the loop with relevant information. ### Match Signals to Deal Conditions to Share Only Relevant Details Avoid overwhelming your teams with unnecessary information. Use our simple condition builder to identify and share high-value qualitative data from the calls and deals your teams care about. **Key Benefits**: * **Relevant Insights**: Share only the most pertinent information with your teams. * **Condition Builder**: Easily set conditions to filter valuable data. * **Focused Communication**: Ensure teams receive information that matters to them. ### Inform Your Product Roadmap and Marketing Efforts Create Signals that listen for key insights on product feedback, feature requests, competitors, and marketing campaigns, and auto-share them directly in Slack. **Key Benefits**: * **Product Improvement**: Gather feedback to enhance your product roadmap. * **Competitive Analysis**: Monitor and respond to competitor activities. * **Marketing Optimization**: Refine marketing strategies based on direct customer feedback. ## Use Cases ### Product Team Signals * **Feature Requests**: Automatically capture customer feature requests and route to product teams * **Bug Reports**: Identify and escalate product issues mentioned during calls * **User Experience Feedback**: Gather insights on product usability and satisfaction * **Integration Requirements**: Track customer needs for third-party integrations ### Sales Team Signals * **Competitive Intelligence**: Monitor competitor mentions and comparisons * **Objection Handling**: Identify common objections for sales training * **Deal Risk Indicators**: Flag potential deal risks for immediate attention * **Upsell Opportunities**: Detect expansion opportunities during customer calls ### Customer Success Signals * **Churn Risk**: Identify early warning signs of potential customer churn * **Support Issues**: Capture customer support concerns for immediate action * **Renewal Concerns**: Monitor customer satisfaction and renewal indicators * **Success Stories**: Collect customer success stories for marketing and sales enablement ### Marketing Team Signals * **Market Trends**: Track industry trends and market insights * **Brand Mentions**: Monitor brand perception and customer sentiment * **Campaign Feedback**: Gather feedback on marketing campaigns and messaging * **Competitive Intelligence**: Share competitive insights for strategic planning ## Getting Started To get started with AI Signals: 1. **Install Momentum AI** with your preferred call provider 2. **Configure your first signal** using our [step-by-step setup guide](/creating-ai-signals-workflows) 3. **Test in a safe environment** before routing to your team 4. **Monitor and optimize** based on team feedback ## How It Works AI Signals continuously monitors your sales calls for specific keywords, phrases, or patterns that you define. When a signal is triggered, Momentum automatically extracts the relevant context and delivers it to the appropriate team members via Slack, Microsoft Teams, or Email. This happens in real-time, ensuring your teams can act on insights immediately. For detailed setup instructions, see our [AI Signals Configuration Guide](/creating-ai-signals-workflows). ## Conclusion AI Signals transforms how your organization captures and acts on customer insights. By automating the detection and delivery of critical information, you can ensure that the right teams receive the right insights at the right time, leading to better decision-making and improved customer outcomes. # API Access Source: https://docs.momentum.io/api-access Enable and generate an API key to use Momentum's API. To use the Momentum API, your organization needs the API access feature enabled. Please contact the Momentum support team and request that API access be turned on for your workspace. Once API access is granted, you can create an API key: 1. Navigate to the **Integrations** page in your Momentum dashboard. 2. Select **Create API key**. 3. Copy the generated key and store it securely. Use this key as the `X-API-Key` header when making requests to the Momentum API. If you need to rotate or remove an API key, return to the Integrations page and manage your keys from there. ## Rate Limiting All API endpoints are rate limited to **100 requests per 15-minute window**. When the limit is exceeded, the API returns a `429 Rate limit exceeded` error. # Ingest a meeting from any source Source: https://docs.momentum.io/api-reference/meetings/ingest-a-meeting-from-any-source /api/openapi-spec.yaml post /v1/user-provided-meeting Ingests a meeting and optional transcript from any source into the Momentum system. # Remap a meeting with new salesforce objects Source: https://docs.momentum.io/api-reference/meetings/remap-a-meeting-with-new-salesforce-objects /api/openapi-spec.yaml post /v1/meeting/remap Associates a meeting with new salesforce objects and optionally triggers call summary and generates AI signals. # Retrieve a list of meetings Source: https://docs.momentum.io/api-reference/meetings/retrieve-a-list-of-meetings /api/openapi-spec.yaml get /v1/meetings # List all AI signal prompts Source: https://docs.momentum.io/api-reference/signals-v1/list-all-ai-signal-prompts /api/openapi-spec.yaml get /v1/signals/prompts Retrieves a list of all AI signal prompts configured for the organization, including their enabled status and context source type. # Retrieve signal executions Source: https://docs.momentum.io/api-reference/signals-v1/retrieve-signal-executions /api/openapi-spec.yaml get /v1/signals/{promptId}/executions Retrieves a paginated list of signal executions (triggered signals) for a specific prompt within a given time range. # List all signal v2 definitions Source: https://docs.momentum.io/api-reference/signals-v2/list-all-signal-v2-definitions /api/openapi-spec.yaml get /v2/signals Retrieves a list of all signal v2 definitions configured for the organization, including their enabled status and context source type. # Retrieve signal v2 executions Source: https://docs.momentum.io/api-reference/signals-v2/retrieve-signal-v2-executions /api/openapi-spec.yaml get /v2/signals/{definitionId}/executions Retrieves a paginated list of signal executions (triggered signals) for a specific signal definition within a given time range. # Retrieve a list of users Source: https://docs.momentum.io/api-reference/users/retrieve-a-list-of-users /api/openapi-spec.yaml get /v1/users Returns a paginated list of users in your organization with their profile, license, and integration status. # Automating Follow-Up Communications Source: https://docs.momentum.io/automating-follow-up-communications Use Email Follow-Up to craft personalized follow-up emails based on call insights. Maintain consistent communication with prospects and customers while reducing the time spent on drafting emails. Utilize follow-up emails after calls, and leverage notifications to remind reps to follow up with customers at the right time, reconnect on deals, or revive lost opportunities. ### Why Automating Follow-Up Communications Matters Effective follow-up communications are crucial for nurturing relationships with prospects and customers, moving deals through the pipeline, and reviving lost opportunities. However, drafting personalized follow-up emails can be time-consuming for sales reps. Automating this process ensures timely, consistent, and personalized communication, freeing up time for reps to focus on high-value activities. ### Key Features for Automating Follow-Up Communications 1. **Email Follow-Up** * **Personalized Emails:** Automatically generate follow-up emails based on insights from sales calls, ensuring each email is tailored to the specific conversation. * **Consistent Communication:** Maintain regular and relevant communication with prospects and customers, enhancing engagement and relationship building. * **Time Savings:** Reduce the time reps spend on drafting emails, allowing them to focus on selling. [Email Follow-Ups](/email-follow-ups) 2. **Scheduled Notifications** * **Timely Reminders:** Set up notifications to remind reps to follow up with customers at optimal times, ensuring no opportunity is missed. * **Reconnection Prompts:** Schedule reminders to reconnect with deals that have gone cold or to revive lost opportunities. * **Actionable Alerts:** Provide reps with actionable alerts that include context and suggested next steps, making follow-up easier and more effective. [Scheduled Notifications](/scheduled-notifications) ### Step-by-Step Guide to Automating Follow-Up Communications 1. **Setting Up Email Follow-Up** * Navigate to the Email Follow-Up section in the Momentum admin dashboard. * Configure the settings to automatically generate personalized follow-up emails based on call insights. * Customize email templates to match your brand's tone and style, ensuring consistency in communication. * Enable the feature to automatically draft follow-up emails after each sales call. Train your reps to review and send emails promptly. 2. **Implementing Scheduled Notifications** * Go to the Scheduled Notifications section in the Momentum admin dashboard. * Create notifications to remind reps to follow up with customers at specific intervals after calls. * Set criteria for notifications, such as follow-up reminders for deals that have gone cold or opportunities that need re-engagement. * Customize the notification messages to include relevant context and suggested actions for reps to take. 3. **Maintaining Continuous Engagement** * Ensure that follow-up emails are sent promptly after calls, providing customers with timely and relevant communication. * Use scheduled notifications to keep reps on track with follow-ups, ensuring that no opportunity is overlooked. * Regularly review the effectiveness of your follow-up communications and make adjustments as needed to improve engagement and outcomes. ### Benefits of Automating Follow-Up Communications * **Increased Productivity:** Save time on drafting emails and setting reminders, allowing reps to focus on higher-value activities. * **Enhanced Customer Engagement:** Maintain regular and personalized communication with prospects and customers, strengthening relationships and increasing engagement. * **Improved Follow-Up Rates:** Ensure timely follow-ups with automated reminders and emails, reducing the risk of missed opportunities. * **Consistent Messaging:** Use customizable templates to ensure that all follow-up communications are consistent and aligned with your brand's tone and style. * **Better Deal Management:** Keep deals moving through the pipeline with timely follow-ups and re-engagement efforts. ### Customer Testimonial *“Momentum has changed the sales management game for us all the while offering a seamless salesforce logging process to the reps. The tight integration with Slack as well as AI powered emails are must haves for our business. Glad to be a part of this rocketship!* — Sam Lee, Director of Revenue Operations @ Unit21 By leveraging Momentum's Email Follow-Up and Scheduled Notifications, you can automate follow-up communications, ensuring timely and personalized engagement with prospects and customers. For further assistance or to discuss custom workflows, please contact our support team. # The Autopilot Suite Source: https://docs.momentum.io/autopilot Automatically populate and update your CRM with key information from your historical conversational data. # The Autopilot Suite Momentum's Autopilot Suite is a collection of powerful AI tools designed to automatically populate and update your CRM with critical information from your sales conversations. By analyzing your [historical conversational data](/conversational-data-sources), the Autopilot Suite ensures your Salesforce data is always accurate, comprehensive, and up-to-date, freeing up your sales team to focus on selling. The suite consists of three distinct products, each tailored for different automation needs: **Real-time, Call-Based.** Triggers after each sales call to extract specific information and update Salesforce fields immediately. Best for capturing in-the-moment data. **Event-Based, Historical.** Triggers from a Salesforce event (like a stage change) and analyzes all [historical conversational data](/conversational-data-sources) to provide a comprehensive summary or update. **On-Demand, Bulk Process.** Triggers manually to run on a large set of records that match your defined criteria. Perfect for data cleanup, enrichment projects, and periodic health checks. ## How the Suite Works Each tool in the Autopilot Suite uses the same core engine. You define what information you need with a natural language **AI Prompt**, and the system analyzes your [historical conversational data](/conversational-data-sources) to find it. You then configure the specific **trigger** (a call ending, a record update, or a manual batch) and the **save behavior** (confirm, write if empty, or fully automatic). Data types and formatting of the output will automatically adapt to your CRM fields, giving you accurate extractions without the need for upkeep when you have a changing CRM. ### Core Features of the Suite * **Automated CRM Updates**: Keep Salesforce fields consistently updated without manual data entry. * **Custom AI Prompts**: Precisely define what information to extract from any conversation. * **Flexible Triggers**: Run automations in real-time, based on CRM events, or in bulk. * **Configurable Save Behavior**: Choose to write data automatically, require confirmation, or only fill empty fields. * **Analyzes Historical Conversational Data**: Extracts insights from your [historical conversational data](/conversational-data-sources). ## Common Use Cases for the Autopilot Suite * **Capture MEDDPICC Fields**: Automatically pull key sales qualification data from discovery calls. * **Identify Churn Risk**: Flag accounts that mention competitors or express dissatisfaction in check-in calls. * **Track Feature Requests**: Funnel product feedback directly from the customer's mouth to your product team. * **Enforce Sales Methodology**: Ensure reps consistently ask the right questions by automating data capture. * **Enrich Lead Data**: Run a batch job to populate the "Primary Pain Point" for all new leads from a recent marketing campaign. * **Prepare for Renewals**: Use a Retropilot trigger to summarize all key interactions 90 days before a renewal date. *** Ready to get started? Explore the configuration guides for each product to learn how to set them up. # Setting Up Autopilot Batch Source: https://docs.momentum.io/autopilot-batch-setup A guide to configuring Autopilot Batch to run on-demand extractions on a collection of Salesforce records. Triggers after each call/email to analyze its content in real-time. Triggers on a Salesforce event and analyzes all historical conversations. **You are here.** Triggers manually to run on a large set of records that match your defined criteria. # Setting Up Autopilot Batch Autopilot Batch, part of the Autopilot Suite, enables you to run AI extractions across a large set of Salesforce records **on-demand**. Unlike the other Autopilot tools, Batch jobs are manually triggered and run against a large set of Salesforce records that match your defined criteria. ## How Autopilot Batch Works Autopilot Batch finds all records matching your filter criteria, runs your AI prompt against the historical conversational data for each one, and then updates a field in Salesforce. ```mermaid theme={null} graph LR A(Run Batch) --> B{Find Records}; B --> C((For Each...
Analyze History)); C --> D[/Run AI Prompt/]; D --> E>Update Field]; ``` ## Use Cases for Autopilot Batch * **Quarterly Health Checks**: Run a batch job on all "Active" accounts to identify potential churn risks by summarizing recent support-related call snippets. * **Data Enrichment**: For all leads created last month from a specific campaign, run a batch to extract and populate the "Primary Pain Point" field. * **Competitive Analysis**: Identify all opportunities where a specific competitor is mentioned and extract the context for a competitive intelligence report. ## Step-by-Step Configuration ### Step 1: Access the Autopilot Batch Section 1. Log in to your [Momentum admin dashboard](https://app.momentum.io/admin/autopilot-extractions). 2. Navigate to the **Autopilot** section and select the **Batch** tab. 3. Click **"New Batch Extraction"** to begin. ### Step 2: Define the Target Records Create a filter to select the Salesforce records you want to process. The batch will run on all records that currently match these conditions when you trigger it. * **Object**: Select the Salesforce object (e.g., Opportunity, Account, Lead, Event). Autopilot Batch does not currently support Contact objects. Contact field extractions are available in Autopilot Classic. * **Field Conditions**: Add one or more conditions to build your list. * `Field`: e.g., `Status`, `CreatedDate`, `ARR__c`. * `Operator`: e.g., `equals`, `greater than`, `is not null`. * `Value`: The value to match. **Example Filter:** ```yaml theme={null} Object: Account Conditions: - Status: equals "Active" - ARR__c: greater than 50000 - LastActivityDate: within "Last 90 Days" ``` ### Step 3: Set the Time Window Define the period of [historical conversational data](/conversational-data-sources) that the AI should analyze for each record in the batch. ### Step 4: Write Your AI Prompt This prompt will be executed for each record in the batch, using its associated historical conversational data. **Example Prompts:** * **For an Account Health Check**: ```text theme={null} "Review all calls and emails for this account from the last 6 months. Summarize any mentions of product dissatisfaction, support issues, or churn risk. If none are found, state 'No risks identified'." ``` * **For Lead Data Enrichment**: ```text theme={null} "Analyze the initial discovery call for this lead. What is their primary business challenge? Respond with a single, concise sentence." ``` ### Step 5: Configure Save Behavior Choose how the extracted data is saved to Salesforce. Given the bulk nature of batch jobs, `Write if Empty` or `Automatic Write` are common choices after testing. * **Confirm to Write** * **Write if Empty** * **Automatic Write** **Handling Records with No Context:** You can configure what happens when no relevant [historical conversational data](/conversational-data-sources) is found for a record: * **Skip**: Nothing will be written to Salesforce (default behavior) * **Write Reason**: Write a message explaining why no data could be extracted * **Custom Text**: Write custom text that you specify This ensures fewer missed write-backs in edge cases and maintains data consistency even when context is missing. This setting still respects your "Write and apply the suggestions" configuration. Confirm to Write, Write if Empty, and Automatic Write settings will still apply. Autopilot automatically truncates extracted values to fit the target field's maximum length in Salesforce. ### Step 6: Preview and Test Before running the full batch, use the **Preview** feature to validate your configuration: 1. Click the **"Preview"** button in the editor wizard 2. Preview tests your prompt against a sample of matching records 3. Review the AI-generated results to ensure accuracy 4. Refine your prompt based on preview feedback 5. Iterate quickly until you're satisfied with the output quality The Preview feature enables rapid iteration and validation of prompts before committing to a full batch run. ### Step 7: Create and Run the Batch Job Once you've validated your configuration with Preview: * **Create Batch**: Set up the batch job with your configured settings * **Review Tasks**: Check the list of records that will be processed from the autopilot batch dashboard * **Run Batch**: Execute the extraction on all records that match your criteria * **Monitor Progress**: Track the batch job status from the autopilot batch dashboard * **Review Results**: Check completed extractions and any errors in the job report # Setting Up Autopilot Classic Source: https://docs.momentum.io/autopilot-classic-setup A guide to configuring the classic, real-time Autopilot to extract and update Salesforce data from your sales calls. **You are here.** Triggers after each call/email to analyze its content in real-time. Triggers on a Salesforce event and analyzes all historical conversations. Triggers manually to run on a large set of records that match your defined criteria. # Setting Up Autopilot Classic This guide provides step-by-step instructions for configuring Momentum's classic Autopilot feature to automatically extract and update Salesforce data from your sales calls. ## How Autopilot Works Autopilot triggers after a single call or email, analyzes its content, and updates a Salesforce field. ```mermaid theme={null} graph LR A(Call or Email) --> B{Autopilot Trigger}; B --> C((Analyze Content)); C --> D[/Run AI Prompt/]; D --> E>Update Field]; ``` ## Prerequisites Before configuring Autopilot, ensure you have: * [Momentum AI installed with your preferred call provider](/how-to-install-momentum) * Admin access to your Momentum Organization * Salesforce integration active * AI license seats assigned to team members ## Step-by-Step Configuration ### Step 1: Access the Autopilot Section 1. Log in to your [Momentum admin dashboard](https://app.momentum.io/admin/autopilot-extractions) 2. Navigate to the **Autopilot** section in the left sidebar 3. Click **"New Autopilot Extraction"** to begin the setup process ### Step 2: Select Salesforce Object and Field **Choose the Target Object:** * **Opportunity**: Extract data to Opportunity fields * **Account**: Extract data to Account fields * **Lead**: Extract data to Lead fields * **Event**: Extract data to Event fields * **Contact**: Extract data to Contact fields. Momentum monitors self-referential statements from call participants and uses that context to inform CRM field extraction for each individual Contact. * **Custom Objects**: Extract to other object fields by navigating from one of the default objects above **Select the Target Field:** * **Standard Fields**: Choose from standard Salesforce fields * **Custom Fields**: Select custom fields you've created * **Picklist Fields**: Automatically limit outputs for fields with predefined values * **Text Fields**: Automatically limit outputs for free-form text fields and their max length and formatting * **Number Fields**: Automatically limit outputs for numeric data * **Boolean Fields**: Automatically limit outputs for yes/no answers * **Lookup Fields**: For lookup fields pointing to Contacts, Autopilot can suggest one of the external attendees from the call as the value (e.g., for "Primary Contact" or "Decision Maker" fields) **Example Configuration:** ```yaml theme={null} Object: Opportunity Field: Pain_Points__c (Custom Text Field) ``` ### Step 3: Write Your AI Prompt The AI prompt is the instruction that tells Momentum what data to extract from calls. **Prompt Best Practices:** * **Be Specific**: Clearly define what information you want extracted * **Use Questions**: Frame prompts as questions the AI should answer * **Include Context**: Reference the field name and expected format * **Set Boundaries**: Define what should and shouldn't be included **Example Prompts:** **For Pain Points:** ```text theme={null} "What are the main pain points or challenges the customer mentioned during this call? Focus on business problems they're trying to solve. Return a concise list of 2-3 key pain points." ``` **For Budget Information:** ```text theme={null} "What is the customer's budget range or budget constraints mentioned in this call? Include specific amounts, ranges, or budget-related discussions. If no budget information is discussed, return 'Not discussed'." ``` **For Timeline:** ```text theme={null} "What is the customer's timeline or urgency for implementing a solution? Include specific dates, quarters, or urgency indicators mentioned. If no timeline is discussed, return 'Not discussed'." ``` **For Competitive Information:** ```text theme={null} "Which competitors did the customer mention during this call? List specific competitor names and any context about their current solutions or evaluation status." ``` ### Step 4: Configure Conditions Set conditions to determine when this extraction should run. You can use Salesforce field conditions, Smart Tag conditions, or both. #### Salesforce Field Conditions Filter extractions based on CRM data like opportunity stage, account attributes, or custom fields. **Example Conditions:** ```yaml theme={null} Opportunity Stage: Discovery, Qualification Account ARR: > $50,000 ``` #### Smart Tag Conditions (Optional) In addition to Salesforce field conditions, you can use [Smart Tags](/smart-tags) to trigger extractions based on what was actually said during the call. This ensures your automations only run when specific topics, keywords, or themes are detected. **Example Smart Tag Conditions:** ```yaml theme={null} Smart Tag: Competitor Mentions = "Competitor X" Smart Tag: Pricing Objection = True Smart Tag: Feature Request contains "integration" ``` **Use Cases:** * **Competitive intelligence**: Only run a competitive analysis extraction when a specific competitor is mentioned * **Objection handling**: Trigger follow-up workflows when pricing or security objections are detected * **Feature requests**: Route product feedback extractions only when feature requests are identified Smart Tag conditions evaluate the tags detected on the current call. Make sure your [Smart Tags are configured](/smart-tags#setting-up-a-smart-tag) in **Admin > Smart Tags** before using them as Autopilot conditions. ### Step 5: Configure Save Behavior Choose how the extracted data should be saved to Salesforce. **Save Options:** * **Confirm to Write**: Show extraction in Slack or web app for manual review before saving * **Write if Empty**: Only save if the field is currently empty, confirm to write otherwise * **Automatic Write**: Automatically save all extractions if new data is identified **Balancing Automation and Verification** While manual verification may seem like the safer approach, our extensive field experience has shown that requiring rep engagement often becomes the biggest roadblock to maintaining high-quality, consistent data. Sales reps are less likely to consistently review and approve extractions, which leads to gaps in data collection and outdated information. Instead, we strongly recommend pushing towards "Write If Empty" for most extractions after your initial testing period. This approach strikes the optimal balance between maintaining data integrity and maximizing the benefits of automation. For best results, we suggest a simple progression: begin with "Confirm to Write" during the first 1-2 weeks while you validate the extraction quality. Once you're confident in the results, transition to "Write If Empty" as your standard operating mode. For highly reliable extractions where the data changes frequently, you may eventually consider using "Automatic Write." Remember, focusing your energy on crafting precise, well-defined prompts will typically yield better results than relying on manual verification processes. Autopilot automatically truncates extracted values to fit the target field's maximum length in Salesforce. ### Step 6: Test Your Extraction 1. **Preview Your Extraction**: Click the "Preview" button before creating to test your prompt against past calls 2. **Review Sample Results**: Examine how your prompt performs on historical call data without affecting Salesforce or Slack 3. **Refine the Prompt**: Adjust the AI prompt based on preview results 4. **Create Live Extraction**: Once satisfied with preview results, create the extraction for production use Autopilot Configuration Interface ## Advanced Configuration ### Multiple Extractions for the Same Field You can create multiple extractions for the same field with different conditions: **Discovery Extraction:** * **Field**: Pain\_Points\_\_c * **Conditions**: Opportunity Stage = "Discovery" * **Prompt**: Focus on initial pain point discovery **Qualification Extraction:** * **Field**: Pain\_Points\_\_c * **Conditions**: Opportunity Stage = "Qualification" * **Prompt**: Focus on validated and prioritized pain points ### Include Historical Context with Lookback Autopilot Classic normally references only the incoming call, but Lookback gives the AI access to historical interactions so it can factor in prior conversations. **Configuration Modes:** * **Range Period**: Define a timeframe (e.g., last week, last 90 days, last quarter). Momentum pulls in relevant calls, emails, and texts from that window. * **Event Quantity**: Specify an exact number of recent interactions to include (e.g., last 10 touchpoints) regardless of when they happened. **Source of Data:** * Choose any combination of calls, emails, or SMS/text messages. **Example Lookback Configuration:** Example Lookback Configuration With the above configuration, when a new call triggers the extraction Momentum also considers relevant [historical conversational data](/conversational-data-sources) from the last quarter. Lookback is currently not configurable with Contact field extractions. ### Context-Aware Extractions Configure extractions that adapt based on call context: **Stage-Based Prompts:** * Use different prompts for different opportunity stages * Adjust extraction sensitivity based on deal maturity * Include stage-specific context in prompts **Account-Based Rules:** * Different extractions for enterprise vs. SMB accounts * Industry-specific prompts and conditions * ARR-based extraction rules ## Best Practices ### Prompt Engineering 1. **Start Simple**: Begin with basic prompts and add complexity 2. **Test Iteratively**: Refine prompts based on actual call data 3. **Use Examples**: Include examples in prompts when possible 4. **Be Specific**: Avoid vague language that could lead to inconsistent results 5. **Consider Context**: Account for different call types and stages ### Field Selection 1. **Prioritize High-Value Fields**: Focus on fields that impact forecasting and reporting 2. **Consider Data Quality**: Choose fields where manual entry is error-prone 3. **Start with Text Fields**: Text fields are easier to configure than picklists 4. **Validate Picklist Mappings**: Thoroughly test picklist field extractions ## Troubleshooting ### Common Issues **Extractions Not Running:** * Check Salesforce conditions are correctly configured * Verify calls are being recorded and processed * Ensure AI license seats are properly assigned **Incorrect Data Extraction:** * Review and refine AI prompts * Check that the right calls are being processed * Validate field mappings and conditions **Poor Data Quality:** * Improve prompt specificity and clarity * Add examples to prompts for better guidance * Consider using "Confirm to Write" for manual review * Review extraction logs for patterns * Refine prompts based on error analysis * Consider breaking complex extractions into simpler ones ## Support If you encounter issues during configuration, contact our support team: * **Slack**: Use your shared Momentum channel * **Email**: [support@momentum.io](mailto:support@momentum.io) # Best Practices Source: https://docs.momentum.io/best-practices [How to Write Effective AI Prompts for Momentum's Features](/how-to-write-effective-ai-prompts-for-momentum-features) # Call Ingestion Source: https://docs.momentum.io/call-ingestion Upload recordings or transcripts from any source into Momentum and get the same AI-powered insights as your live calls. ## Overview Call Ingestion lets you bring external meetings into Momentum — no integration required. You can either upload an audio or video recording, or upload a transcript directly if you don't have a recording. Either way, Momentum processes it the same way as a live call, giving you transcripts, summaries, AI insights, and Salesforce updates. Uploaded meetings appear in the **Recorded Calls** tab once processing is complete. ## Prerequisites The following feature settings must be enabled for your org: * **Call Intelligence** ## What You Can Upload **Recordings:** | Type | Extensions | | ----- | ----------------------- | | Video | `.mp4`, `.mov`, `.webm` | | Audio | `.m4a`, `.mp3`, `.wav` | **File size limit:** 2 GB per upload **Transcripts:** | Source | | ----------- | | Google Meet | | Zoom | **Daily limit:** 5 uploads per user per day ## How to Upload 1. Navigate to the **Call Library** in your Momentum dashboard. 2. Click **Upload Call Recording**. 3. Attach one of your files (either a Recording or a Transcript — not both): * **Recording** — select your audio or video file * **Transcript** — attach your transcript exported from Google Meet or Zoom 4. Fill in the required details: * **Title** — a name for the meeting; if left empty, Momentum will auto-generate one from attendees and date on submit * **Host** — the internal team member who led the call; auto-filled based on your account * **Attendees** — include at least one external participant (e.g., a customer or prospect) * **Meeting date** 5. Optionally provide a **Salesforce Account** or **Opportunity** to link the meeting directly. If not provided, Momentum will attempt to match it automatically based on attendees and meeting details. 6. Click **Submit**. Momentum will begin processing in the background. Once processing finishes, the meeting appears in your **Recorded Calls** tab with a full transcript, summary, and AI insights. Momentum requires at least one external attendee. Uploads with only internal participants cannot be processed. ## AI Agents and Salesforce Updates **Enable AI Agents** toggle must be enabled on your workspace to fully process the uploaded call — extracting insights and pushing updates into Salesforce based on your configured field mappings, exactly the same as your live calls. ## Checking Upload Status In the **Upload Call Recording** tab, click **View Upload Status** to navigate to a page listing all your uploads and their current status. | Status | What it means | | --------------- | ------------------------------------------------- | | **Pending** | Upload received, processing not yet started | | **In Progress** | Momentum is transcribing and analyzing the call | | **Completed** | The call is ready and visible in the Call Library | | **Failed** | Processing encountered an error | If an upload fails or the meeting status is **In Progress** for a long time, contact support with the recording details so we can investigate. # Summaries Source: https://docs.momentum.io/call-summaries ## Overview Momentum's Summaries product ensures you never miss an important update from your sales calls. Using advanced AI, Summaries transforms every call into actionable data within your CRM. CleanShot 2024-06-25 at 18.23.12@2x.png ### Key Benefits: * **Automated Note-Taking**: No more manual note-taking. Summaries automatically logs notes from every call into Salesforce. * **Instant Insights**: Receive shareable summaries directly in Slack, providing key insights to your team in real-time. * **Trend Identification**: Spot important trends such as churn and pipeline risks early and act on them without delay. * **Time Savings**: Save up to 10 hours of listening time per week, allowing sales managers to focus on coaching and strategy. *"We use Momentum to automate note-taking and call summaries across our company. It's fantastic—helping to deliver customer insight straight to our CEO and engineering team. I'm mindful of the tradeoff of giving my team more 'work about work.' With Momentum, we drive the insights we need, while saving our sellers a ton of time."* Aaron Bartel, VP of Revenue @ Harmonic ## Key Features ### Programmable Summaries * **Slack Integration**: Customizable summaries posted in Slack as per team requirements with fine-tuning options for where and how summaries are displayed. * **Salesforce Integration**: Automatic creation of notes in Salesforce with customization based on Salesforce object rules. * **Customization**: Fully customizable summaries focusing on areas of interest depending on the call type. ### High Degree of Refinement * Configurable behavior based on Salesforce object rules, such as opportunity stages or account ARR. * Suitable for companies of any size, from small teams (5 reps) to large enterprises (2500 reps). ### Smart Delivery * **Dynamic Routing**: Automatically deliver summaries to the right people based on deal ownership and team structure. * **Multi-Channel Delivery**: Send summaries to Slack channels, direct messages, or email. * **Action Buttons**: Include interactive Slack buttons to help your team take immediate action. ## Use Cases ### Cross-Functional Visibility * **Direct Delivery from Field to Management**: Provides executives with direct visibility into field operations, minimizing middle management layers. * **Enhanced Deal Handoff**: Collects unstructured context in CRM notes, aiding in smooth transitions between reps or during post-sale processes. ### Focused Capturing * **Refinement and Noise Reduction**: Summaries can be tailored to capture essential information, removing unnecessary details and reducing clutter. ### Multilingual Support * **Language Standardization**: Supports multiple languages, offering unparalleled visibility and standardization for global sales teams. ### Stage-Based Summaries Create different types of summaries for different deal stages: * **Discovery Calls**: Focus on pain points, requirements, and timeline * **Qualification Calls**: Emphasize budget, authority, and need validation * **Proposal Calls**: Highlight pricing discussions, objections, and next steps ### Team-Specific Delivery * **Rep + Manager**: Send summaries directly to the opportunity owner and their manager * **Account Teams**: Deliver to all stakeholders involved in a specific account * **Cross-Functional**: Route relevant insights to product, marketing, and customer success teams ## Getting Started To get started with Call Summaries: 1. **Install Momentum AI** with your preferred call provider 2. **Configure your first summary workflow** using our [step-by-step setup guide](/setting-up-call-summaries) 3. **Customize delivery settings** to match your team's workflow 4. **Monitor and optimize** based on team feedback ## How It Works Momentum automatically maps your team's calls to Salesforce objects based on attendee emails. When a call is recorded, Momentum analyzes the conversation and generates a summary based on your configured workflows. The summary is then delivered to the appropriate team members via Slack or email, and optionally saved as notes in Salesforce. For detailed setup instructions, see our [Call Summaries Configuration Guide](/setting-up-call-summaries). ## Conclusion Summaries is your ultimate tool for transforming how your sales team captures and utilizes call data. With automated note-taking, instant insights, and customizable summaries, you can significantly enhance your team's efficiency and decision-making capabilities. # Centralizing Deal Management Source: https://docs.momentum.io/centralizing-deal-management Manage deals more effectively by centralizing communication and updates in Deal Rooms. Reduce Slack fatigue and ensure all stakeholders are informed and engaged throughout the sales process. ### Why Centralizing Deal Management Matters Effective deal management is crucial for closing sales efficiently and maintaining clear communication among all stakeholders. Disjointed communication and scattered updates can lead to misunderstandings, unnecessary meetings, and delays. Centralizing deal management in Deal Rooms helps streamline the process, keeping everyone aligned and reducing the need for constant tool switching and status checks. ### Key Features for Centralizing Deal Management 1. **Deal Rooms** * **Centralized Communication:** Create dedicated Slack channels for each deal, consolidating all relevant information, communications, and updates in one place. * **Automatic Room Creation:** Set up automatic creation of Deal Rooms for deals that enter stages requiring collaboration between stakeholders. * **Automatic Invitations:** Automatically invite stakeholders to the Deal Room as the deal progresses, ensuring relevant parties are always informed and included. * **Integrated Notifications:** Configure notifications within Deal Rooms to remind the team of key events and actions needed. * **Scroll-Up History:** Provide a complete, easily accessible history of the deal, allowing anyone to scroll up and catch up on what's happened without switching tools. [Deal Rooms and Account Rooms](/how-to-create-a-deal-room-and-manage-opportunities) 2. **AI Signals** * **Insight Delivery:** AI Signals can capture and deliver critical insights about the opportunity to all stakeholders within a Deal Room. * **Real-Time Updates:** Ensure that all team members receive the latest information and insights about the deal as soon as they are available. [AI Signals](/ai-signals) 3. **Notifications** * **Aligned Updates:** Notifications can be set up to deliver critical updates directly into Deal Rooms. This ensures all team members are notified in sync about key events, keeping the entire team aligned. * **No One Left Behind:** By delivering notifications into Deal Rooms, all stakeholders are kept in the loop, ensuring that no one is left behind in the communication flow. * **Customizable Alerts:** Notifications can be customized to provide specific, actionable insights. This prevents information overload and allows team members to focus on what's most important. [Salesforce Notifications](/salesforce-notifications) ### Step-by-Step Guide to Centralizing Deal Management 1. **Setting Up Deal Rooms** * Navigate to the Deal Rooms section in the Momentum admin dashboard. * Configure the settings to automatically create Deal Rooms for opportunities that reach specific stages requiring cross-functional collaboration. * Invite relevant stakeholders from sales, support, product, and other teams to the Deal Rooms, ensuring that all necessary parties are included. 2. **Implementing AI Signals** * Go to the AI Signals section in the Momentum admin dashboard. * Set up AI Signals to capture key insights from sales calls and customer interactions, such as product feedback, competitor mentions, and potential objections. * Configure the delivery of these insights to the appropriate Deal Rooms, keeping all stakeholders informed in real-time. 3. **Configuring Notifications** * In the Deal Rooms, set up notifications to remind the team of important events and actions, such as upcoming meetings, deadlines, and follow-ups. * Customize the notification messages to provide clear instructions and context for the actions needed. 4. **Maintaining Continuous Engagement** * Encourage team members to regularly check the Deal Rooms for updates and new insights. * Use the scroll-up history feature to review past communications and updates, ensuring everyone stays on the same page. * Hold regular check-ins within the Deal Rooms to discuss progress, address issues, and plan next steps. ### Benefits of Centralizing Deal Management * **Improved Collaboration:** Centralize all deal-related communication and updates, making it easier for team members to collaborate and stay aligned. * **Enhanced Visibility:** Ensure all stakeholders have access to the latest information and insights, reducing the risk of misunderstandings and missed opportunities. * **Reduced Slack Fatigue:** Consolidate deal communications into dedicated Deal Rooms, reducing the clutter and noise in other Slack channels. * **Streamlined Processes:** Automate the creation of Deal Rooms and the delivery of notifications and insights, saving time and effort for your team. * **Better Decision-Making:** Leverage AI Signals to provide real-time insights and data, helping teams make informed decisions quickly. ### Customer Testimonial “*Momentum has added some really powerful visibility in regards to conversational insights, and efficiency gains for salesforce to slack bidirectional automation. Reps no longer need to fill things out, and I no longer need to ask reps for feedback on where things are at. For a fast moving startup, every moment saved is awesome”* — Aaron Dugca, Customer Success and Implementations Leader @ Rebuy Engine By leveraging Momentum's Deal Rooms and AI Signals, you can centralize deal management, improve collaboration, and ensure that all stakeholders stay informed and engaged throughout the sales process. For further assistance or to discuss custom workflows, please contact our support team. # Coaching Agent Source: https://docs.momentum.io/coaching-agent-overview Automatically evaluate and coach every sales call with objective, comprehensive competency assessments. ## Overview Momentum's Coaching Agent transforms how sales teams develop skills and improve performance by providing objective, comprehensive coaching evaluation for every single recorded call. Using advanced AI analysis, the platform evaluates sales competencies in real-time, delivering both quantitative scores and qualitative feedback to help sales representatives excel in their roles. Unlike traditional coaching methods that rely on managers reviewing a limited subset of calls, Coaching Agent provides complete coverage across your entire sales organization, ensuring every conversation contributes to skill development and performance improvement. ### Key Benefits * **Complete Coverage**: Evaluate every single call and every sales rep automatically - impossible to achieve with human coaching alone * **Objective & Fair Assessment**: Eliminate bias and subjectivity from coaching evaluations with consistent, AI-driven assessments * **Multi-Language Support**: Provide coaching across all languages, enabling global teams to receive consistent feedback * **Real-Time Feedback**: Get immediate coaching insights after each call, accelerating skill development * **Customizable Competencies**: Create dozens of competencies tailored to your sales methodology and process * **CRM Integration**: Automatically push coaching data to your CRM for reporting and performance tracking ## How Coaching Agent Works ### Competency-Based Evaluation Coaching Agent is built around the concept of **competencies** - specific skills and behaviors you want to assess for each sales representative. Each competency represents a particular aspect of sales excellence, such as discovery questioning, objection handling, or relationship building. Coaching Settings Page **Key Features:** * Create a comprehensive set of competencies using custom prompts * Access pre-built competencies for common sales skills * Apply CRM-based filters to evaluate competencies only on relevant calls * Track quantitative performance evolution for individuals and teams over time with comprehensive aggregated scoring ### Intelligent Call Filtering Momentum evaluates competencies based on sophisticated CRM conditions, ensuring assessments are contextually relevant: * **Stage-Based Assessment**: Evaluate discovery skills only on early-stage calls, negotiation skills on late-stage opportunities * **Deal Size Filtering**: Apply different competencies based on opportunity value * **Custom Field Conditions**: Use any CRM field to determine when specific competencies should be evaluated ### Dual Scoring System Each competency receives both quantitative and qualitative evaluation: **Quantitative Scores (0-2 Scale):** * **0**: Didn't exhibit the competency * **1**: Exhibited the competency at expected level * **2**: Excelled at the competency **Qualitative Assessment:** * Detailed feedback on what the rep did well * Specific suggestions for improvement * Context-aware coaching recommendations * Examples from the actual conversation ## Comprehensive Dashboards & Analytics The Coaching Analytics dashboard provides powerful insights into individual and team performance with intuitive visualizations and comparative analysis. Coaching Analytics Dashboard ### Quarterly Performance Analysis * **Time Period Selection**: Switch between Last Quarter and Current Quarter views to track progress * **Competency Trend Charts**: Visualize performance evolution over time with detailed graphs showing scores from March through June * **Individual Deep Dives**: Select specific team members to view their detailed competency performance * **Historical Comparison**: Track improvement patterns and identify skill development trends ### Team Performance Management * **Comprehensive Team View**: Compare all team members in a single interface with key metrics * **Performance Metrics**: View Total Calls, Talking Ratio percentages, and Skills Coverage for each team member * **Spider Graph Visualizations**: Individual spider graphs show each person's skill profile across all competencies * **Competency Filtering**: Filter analysis by specific competencies like Product Knowledge, Enterprise Value Articulation, Multi-Stakeholder Orchestration, and Change Management Navigation ### CRM Integration & Reporting * **Automated Data Push**: Send coaching scores and feedback directly to CRM fields * **Custom Report Building**: Create reports using Momentum's coaching data * **Programmable Integration**: Fully customize how coaching data flows into your systems * **Real-Time Updates**: Keep CRM records current with latest coaching assessments #### Automated CRM Integration Configure how coaching scores flow into your CRM system with dedicated object and field mapping for both overall meeting scores and individual competency evaluations. ## Our Coaching Philosophy The way Momentum works is that we attribute all coaching scoring and feedback to the call host - the person who scheduled and owns the meeting. This means even when multiple team members contribute to a call (like a Sales Engineer asking great discovery questions), all scores and feedback are assigned to the host. We designed it this way because the host is ultimately responsible for the overall call success - managing timing, flow, discovery depth, and ensuring the team works together effectively. Rather than fragmenting feedback across multiple participants, this approach provides comprehensive accountability and encourages hosts to leverage their entire team's strengths while taking ownership of the outcome. ## Getting Started Set up your competency framework with custom prompts and CRM-based filtering conditions. Learn how to maximize the impact of AI Coaching in your sales organization. Coaching Agent represents the future of sales development - providing the scale, objectivity, and comprehensive coverage that traditional coaching methods simply cannot match. By leveraging AI to evaluate every conversation, your team receives the consistent, actionable feedback needed to accelerate skill development and drive better sales outcomes. # Common Use Cases Source: https://docs.momentum.io/common-use-cases Welcome to the Common Use Cases section of the Momentum Product Documentation. Here, we provide detailed examples of how Momentum's products and features can be combined to address specific business challenges and improve overall efficiency. Explore the following use cases to learn how to maximize the benefits of Momentum for your team. ### 1. **Improving Data Hygiene** **Overview:** Ensure your CRM data is accurate and up-to-date by leveraging Momentum's Autopilot and Contact Automation features. Automate data capture and updates to reduce manual entry and maintain data integrity. [Improving Data Hygiene](/data-hygiene) ### 2. **Enhancing Sales Efficiency** * **Overview:** Streamline your sales processes by utilizing AI Signals, Autopilot, and Summaries. Automate administrative tasks and focus on selling by receiving real-time insights and automated call notes. [Enhancing Sales Efficiency](/enhancing-sales-efficiency) ### 3. **Gaining Customer Insights** * **Overview:** Capture and share valuable customer feedback and insights using AI Signals and Deal Rooms. Enhance product development and marketing strategies based on real-time data from customer interactions. [Gaining Customer Insights](/gaining-customer-insights) ### 4. **Managing Contract Renewals** * **Overview:** Proactively manage contract renewals and reduce last-minute scrambles with Scheduled Notifications. Keep your customer success teams informed about upcoming renewals and ensure timely follow-ups. [Managing Contract Renewals](/managing-contract-renewals) ### 5. **Optimizing Sales Playbooks** * **Overview:** Implement and refine your sales playbooks using Momentum's Autopilot and Deal Rooms. Ensure consistent execution of sales strategies and improve deal management by automating key processes. [Optimizing Sales Playbooks](/optimizing-sales-playbooks) ### 6. **Automating Follow-Up Communications** * **Overview:** Use Email Follow-Up to craft personalized follow-up emails based on call insights. Maintain consistent communication with prospects and customers while reducing the time spent on drafting emails. [Automating Follow-Up Communications](/automating-follow-up-communications) ### 7. **Centralizing Deal Management** * **Overview:** Manage deals more effectively by centralizing communication and updates in Deal Rooms. Reduce Slack fatigue and ensure all stakeholders are informed and engaged throughout the sales process. [Centralizing Deal Management](/centralizing-deal-management) ### 8. **Enhancing Reporting and Analysis** * **Overview:** Use Scheduled Reports to deliver key metrics and insights to your team regularly. Ensure everyone stays informed about sales performance and pipeline status without manually checking Salesforce. [Enhancing Reporting and Analysis](/enhancing-reporting-and-analysis) ### 9. Managing a Multi-Language and Cross-Cultural Team * **Overview**: Utilize Momentum's AI capabilities to manage a multi-language and cross-cultural team effectively. Ensure better visibility, consistency, and global understanding of the pipeline for leadership by leveraging AI-driven insights and tools. [Managing a Multi-Language and Cross-Cultural Team](/managing-a-multi-language-and-cross-cultural-team) # Coaching Agent Competencies Source: https://docs.momentum.io/configuring-coaching-agent-competencies Learn how to create and configure competencies for Coaching Agent evaluations. # Coaching Agent Competencies Competencies are the foundation of Momentum's Coaching Agent system. Each competency represents a specific skill or behavior you want to evaluate across your sales team. This guide walks you through creating, configuring, and managing competencies to ensure your coaching program aligns with your sales methodology and goals. ## Understanding Competencies A **competency** is a measurable skill or behavior that Momentum evaluates on sales calls. Examples include: * Discovery questioning techniques * Objection handling skills * Value proposition delivery * Closing effectiveness * Relationship building * Active listening * Negotiation skills Each competency is defined by: * **Competency Title**: Clear name identifying the skill being measured * **Prompt**: Detailed instructions that guide the AI evaluation process * **Aggregation Method**: Choice between Core Skills (continuous tracking) or Stage Based Skills (context-specific evaluation) * **Conditional Logic**: CRM-based filters that determine when the competency is evaluated ## Creating a New Competency ### Step 1: Access Competency Management 1. Navigate to **Admin Settings** in your Momentum dashboard 2. Select **Coaching Agent** from the configuration menu 3. Click **Competencies** to view your current competency library 4. Select **+ Create New Competency** Coaching Settings Page ### Step 2: Complete the Competency Form When creating a new competency, you'll see the competency creation dialog with several key sections: Create Competency Form **Competency Title** * Enter a clear, descriptive name (e.g., "Agenda Management," "Discovery Questioning") * Use specific titles that clearly indicate the skill being evaluated **Prompt** * Write detailed instructions for the AI on what to evaluate * Include specific behaviors, outcomes, and success criteria * Be explicit about what constitutes excellent vs. satisfactory performance ### Step 3: Choose Aggregation Method Select how this competency should be scored and tracked: **Core Skills** * Tracks essential sales skills that should be present in every call * Provides continuous scoring to show improvement over time * Best for fundamental competencies like active listening, communication clarity **Stage Based Skills** * Focuses on specific moments in the sales process * Only evaluates skills relevant to particular deal stages * Ideal for competencies like negotiation (late stage) or discovery (early stage) **Writing Effective Prompts** Based on the UI, your prompt should be comprehensive and include specific evaluation criteria. Here's an example from the interface: **Example: Agenda Management Competency** ``` Has the rep effectively managed the agenda of this meeting? Setting a clear expectation of what is going to end soon? What the timing of everything is and what is going to happen? ``` **Best Practices for Prompt Writing:** * **Be Specific**: Define exactly what behaviors or actions you want evaluated * **Include Multiple Criteria**: Ask several related questions to ensure comprehensive evaluation * **Use Clear Language**: Write prompts that leave little room for interpretation * **Focus on Observable Behaviors**: Evaluate what can be heard/seen in the conversation **Template Structure:** ``` [Main Question]: Has the rep effectively [specific skill/behavior]? [Supporting Questions]: - [Specific aspect 1 to evaluate] - [Specific aspect 2 to evaluate] - [Specific aspect 3 to evaluate] ``` #### Need Help with Competency Design? Our Customer Success team has developed proven prompt templates for common sales competencies including discovery questioning, objection handling, presentation skills, and relationship building. If you'd like assistance crafting effective prompts for your specific sales methodology, reach out to your CSM or support team for guidance and examples. ### Step 4: Configure Conditional Logic Use the conditional logic section to specify when this competency should be evaluated: **Adding Conditions** 1. Click **Select A Field** to choose a CRM field for filtering 2. Set the condition value (e.g., opportunity stage, deal amount, account type) 3. Use **Add Row** to include additional conditions within the same group 4. Toggle between **AND/OR** logic to refine your targeting **Creating Conditional Groups** * Use **Add Conditional Group** for complex filtering scenarios * Combine multiple groups with different logic operators * Create sophisticated rules like: "(Stage = Discovery OR Stage = Qualification) AND (Amount > \$50,000)" **Common Filtering Examples:** * **Discovery competencies**: Only evaluate when Opportunity Stage = "Discovery" or "Qualification" * **Enterprise skills**: Only assess when Account Type = "Enterprise" and Amount > \$100,000 * **Product-specific**: Evaluate different competencies based on Product Family or Solution Type The conditional logic ensures competencies are only scored on relevant calls, making your coaching data more meaningful and actionable. ### CRM Field Mapping Configuration Install the [Momentum Coaching package](https://api.momentum.io/integration/salesforce/install?package=coaching) to automatically create objects and fields for storing Coaching data in Salesforce For a sandbox environment, [Momentum Coaching sandbox package](https://api.momentum.io/integration/salesforce/install?package=coaching\&sandbox=1) Configure how competency and meeting scores are mapped to your CRM fields: **Meeting Score Mapping** Set up overall meeting evaluation scores to flow into designated CRM fields: Meeting Score Field Mapping **Competency Score Mapping**\ Configure individual competency scores to be written to specific CRM objects and fields: Competency Score Field Mapping ## Managing Your Competency Library ### Organizing Competencies **Use Categories Effectively** * Group related competencies together * Create categories that align with your sales process * Consider competency maturity levels (beginner, intermediate, advanced) **Naming Conventions** * Establish consistent naming patterns * Include target audience in names when relevant * Use descriptive names that team members will understand ### Monitoring Competency Performance **Regular Review Process** * Monitor competency scoring distributions * Look for competencies that consistently score too high or too low * Review qualitative feedback for relevance and usefulness **Refinement and Optimization** * Update prompts based on team feedback * Adjust CRM filters as your sales process evolves * Archive outdated competencies rather than deleting them **Team Feedback Integration** * Regularly collect feedback from sales reps and managers * Adjust competency criteria based on real-world application * Ensure competencies remain aligned with current sales strategies ## Best Practices for Competency Configuration ### Starting Your Competency Program 1. **Begin with Core Competencies**: Start with 5-7 fundamental competencies 2. **Align with Sales Process**: Map competencies to your existing sales methodology 3. **Get Team Input**: Involve sales managers in competency design 4. **Test Gradually**: Roll out competencies to a pilot group first ### Scaling Your Program 1. **Add Competencies Incrementally**: Introduce new competencies monthly 2. **Specialize by Role**: Create role-specific competencies for different team members 3. **Advanced Filtering**: Use sophisticated CRM filters for precise targeting 4. **Integration Focus**: Ensure coaching data flows effectively into your reporting systems ### Avoiding Common Pitfalls * **Don't Over-Engineer**: Keep prompts clear and focused * **Avoid Overlap**: Ensure competencies measure distinct skills * **Regular Maintenance**: Update competencies as your sales process evolves * **Team Buy-In**: Ensure the sales team understands and values the competencies By carefully configuring your competencies, you'll create a comprehensive coaching program that provides valuable insights while remaining practical and actionable for your sales team. Remember that competency design is iterative - start with solid fundamentals and refine based on results and feedback. The combination of thoughtful competency design and proper CRM integration ensures that your Coaching Agent implementation delivers maximum value to both individual representatives and the broader sales organization. # Configuring Zoom Groups for Momentum AI Source: https://docs.momentum.io/configuring-zoom-groups Momentum AI uses Zoom groups to control which meetings are recorded and analyzed. Follow these steps as a Zoom admin to create (or repurpose) a group, lock down the right recording settings, and add the reps you want Momentum to cover. ## Before You Start * You must be a Zoom Admin with access to group management. * Verify that the teammates you plan to add have **Licensed** Zoom seats. ## Create or Select a Zoom Group 1. In the Zoom web portal, open **User Management** and choose **Groups**. Zoom Groups navigation in the Zoom admin portal. 2. Use an existing group if it already contains the reps you want Momentum to analyze. Otherwise, click **Add Group**, name it, and save. Add Group dialog in Zoom. ## Configure Recording Defaults for the Group 1. Open your new (or existing) group and go to the **Recording** tab. Recording tab for a Zoom group. 2. Scroll to **Cloud recording** and switch it on. Enable **Create audio transcript**, lock that setting so users can’t disable it, and click **Save**. Cloud recording and audio transcript settings enabled. ## Add Licensed Users to the Group 1. Go back to **User Management** and select **Users**. Users list in the Zoom admin portal. 2. Check the box next to each licensed user whose calls should flow into Momentum, then click **Group**. Assign users to a Zoom group. 3. Pick the Zoom group you just configured and confirm with **Save**. Select the configured group in the assignment modal. That’s it! Momentum AI will start receiving the cloud recordings and transcripts for every hosted meeting from the users in this group. # Momentum Consent Link Injection by Conference Type Source: https://docs.momentum.io/consent-link-injection-by-conference-type ## Overview By default, Momentum will inject a custom consent link everytime a new meeting is created and set to be recorded, regardless of the conference provider. This would send any attendee joining a meeting to the consent page before sending them to the meeting room. When an organization admin turns off this setting for either Zoom or other providers, the consent link will no longer collected and attendees will be prompted to the meeting room immediately. Consent Link Injection Toggle ## Prerequisites * All the prerequisites listed in the recording consent page will have to be met. * You must be an organization admin or an editor to be able to have access to this setting. ## Step-By-Step Guide 1. Sign in to the [Momentum admin dashboard](https://app.momentum.io/admin/). 2. In the left navigation, go to **Settings → Recording Consent**. 3. Underneath the preview display, the toggle for enabling consent links for Zoom or other providers will show up. 4. Use the toggle to enable or disable consent link injection. x 5. Select **Save** to apply the change for the entire workspace. # Recording Consent Rejection Email Notification Source: https://docs.momentum.io/consent-rejection-email-notifications ### Overview When a participant rejects recording consent, the host of the meeting will receive an email notification from [support@momentum.io](mailto:support@momentum.io) If the consent is rejected by a **recognized participant**, the host will receive an email containing the following information: * Meeting details (title, meeting time, host name) * Salesforce Opportunity details (opportunity name, stage name) * Time of rejection * Email Address of Rejection * One line message stating the Momentum Bot was removed * Clear instruction on how to re-add the Momentum Bot manually Example Email Recognized Participant If the consent is rejected by an unrecognized participant, the host will receive an email containing the same information, except for the bot removal message and the instructions to re-add the bot manually. Example Email Not Recognized Participant ## Glossary ### Recognized Participant A **recognized participant** is defined as: 1. A participant whose email address is in the meeting's invitee list **OR** 2. A participant who shares the same email domain as the host of the meeting # Conversation Intelligence Source: https://docs.momentum.io/conversation-intelligence-overview ## Overview Momentum's Conversation Intelligence is a powerful call recording and management platform that transforms how your team captures, organizes, and shares customer conversations. Built specifically for sales and customer success teams, it provides a comprehensive solution for recording calls, building call libraries, creating playlists, and sharing insights with external stakeholders. Conversation Intelligence Call List ### Key Benefits * **Seamless Call Recording**: Automatically record and transcribe all your customer calls without disrupting your workflow * **Organized Call Library**: Build a searchable repository of all customer conversations with advanced filtering and tagging * **Curated Playlists**: Create targeted playlists of calls for training, coaching, and knowledge sharing * **External Sharing**: Share calls securely with external attendees and stakeholders * **AI Integration**: Seamlessly integrates with Momentum's AI analysis products for enhanced insights ## Key Features ### Call Recording & Management **Automatic Recording** * Records calls from Zoom, Google Meet, and other video conferencing platforms * Automatic transcription with high accuracy * No manual intervention required **Call Library** * Searchable database of all recorded calls * Advanced filtering by date, participants, crm details, and topics * Per-call and aggregate AI coaching * Full-text search across transcripts * Call metadata and analytics ### Playlist Creation **Curated Collections** * Create playlists for specific use cases (training, coaching, best practices) * Organize calls by deal stage, customer type, or sales methodology * Share playlists with team members for collaborative learning **Training & Coaching** * Build training playlists for new hires * Create coaching playlists highlighting specific techniques * Organize calls by performance metrics or outcomes Conversation Intelligence Call Playback ### External Sharing **Secure Sharing** * Share individual calls with external stakeholders * Control access permissions and viewing rights * Track who has viewed shared content * Expiring links and auth requirements for sensitive sharing **Stakeholder Collaboration** * Share calls with prospects during sales cycles * Provide free access to view calls to internal teams ### AI Integration **Enhanced Analysis** * Integrates seamlessly with Momentum's AI analysis products * Automatic call summarization and insight extraction * AI coaching based on customizable competencies * Competitive intelligence and objection tracking **Workflow Automation** * Automatic tagging and categorization of calls * Integration with CRM systems for deal context * Automated alerting for important call moments ## Use Cases ### Sales Training & Enablement * Create playlists of successful discovery calls for new reps * Build collections of objection handling examples * Share best practice calls across the organization ### Customer Success * Record and share customer onboarding sessions * Create playlists of product feedback calls * Share customer success stories with prospects ### Deal Collaboration * Share prospect calls with internal stakeholders * Create playlists for complex deal reviews * Enable external sharing for multi-stakeholder deals ### Competitive Intelligence * Build playlists of competitive discussions * Track competitor mentions across calls * Share competitive insights with product and marketing teams ## Getting Started To get started with Conversation Intelligence: 1. **Enable the Module**: Contact your Momentum account manager to add Conversation Intelligence to your subscription 2. **Configure Recording**: Set up automatic recording for your preferred video conferencing platforms 3. **Build Your Library**: Start recording calls to build your initial call library 4. **Create Playlists**: Organize calls into playlists for different use cases 5. **Share Content**: Begin sharing calls and playlists with your team and external stakeholders ## Pricing Conversation Intelligence is available as an optional add-on module with additional cost. Contact your Momentum account manager for pricing details and to enable the module for your organization. ## Integration with AI Analysis Conversation Intelligence works seamlessly with Momentum's AI analysis products: * **Call Summaries**: Automatic summarization of all recorded calls * **Autopilot**: Extract CRM data from recorded conversations * **AI Signals**: Real-time alerts for important call moments This integration provides a complete solution for capturing, organizing, analyzing, and sharing customer conversations across your organization. # Conversational Data Sources Source: https://docs.momentum.io/conversational-data-sources The more data Momentum has, the smarter it gets. Learn about the conversational data sources Momentum can leverage. ## Overview Momentum analyzes more than just calls. By connecting to your calls, emails, text messages, and documents, Momentum gives you a complete picture of every customer relationship — so features like Account Briefs, Autopilot, and Deep Research have the full story, not just the latest conversation. ## Conversational Data Sources ### Calls Recorded meetings and phone calls from supported integrations. Calls are Momentum's primary data source and are covered in detail on the [Conversation Intelligence](/conversation-intelligence-overview) page. ### Emails & Text Messages Emails and text messages are imported from **Salesforce Tasks**. When your team logs emails or SMS conversations to Salesforce, Momentum automatically picks them up. To set up email and text message ingestion, reach out to our team via your shared Slack channel or at [support@momentum.io](mailto:support@momentum.io). ### Documents Documents uploaded to Salesforce records — such as on-site visit summaries, meeting write-ups, or executive briefing notes. **Requirements:** * Stored as a Salesforce ContentDocument linked to an Account or Opportunity * `.docx` format, 1 MB or smaller ## How It All Works Together The more conversational data sources you connect, the more context Momentum has to work with. An Account Brief can reference a pricing discussion from an email, a follow-up commitment from a text message, and competitive intel from a visit report — all in a single view. # Creating AI Signals Workflows Source: https://docs.momentum.io/creating-ai-signals-workflows Complete guide to create and configure AI Signals workflows for automated customer insight delivery. # Creating AI Signals Workflows This guide walks you through the technical setup process for Momentum's AI Signals feature. AI Signals automatically detect and share key insights from sales calls with relevant teams in real-time. AI Signals Admin Interface ## Prerequisites Before setting up AI Signals, ensure you have: * [Momentum AI installed with your preferred call provider](/how-to-install-momentum) * Admin access to your Momentum Organization * Slack workspace or Microsoft Teams configured * Salesforce integration active ## Step-by-Step Setup ### Step 1: Access the AI Signals Section 1. Log in to your [Momentum admin dashboard](https://app.momentum.io/admin/ai-signals) 2. Navigate to the **AI Signals** section in the left sidebar 3. Click **"New AI Signal"** to begin the setup process ### Step 2: Configure Signal Detection Rules The first section involves setting up rules to determine which calls should trigger this signal. **Configure Call Detection:** * **Trigger Prompt**: Write an AI prompt that defines what to listen for * **Trigger Conditions**: Set specific CRM conditions to filter calls (e.g., "Stage = Discovery") **Example Configuration:** ```yaml theme={null} Signal Name: "Enterprise Security Concerns" Trigger Prompt: "Listen for any mentions of security requirements, compliance needs, or enterprise security concerns during this call. Focus on specific security features, certifications, or compliance standards mentioned." Stage: Proposal Account ARR: > $100,000 ``` #### Smart Tag Conditions (Optional) In addition to CRM-based trigger conditions, you can use [Smart Tags](/smart-tags) to trigger signals based on what was actually said during the call. This allows you to fire signals only when specific topics, keywords, or themes are detected. **Example Smart Tag Conditions:** ```yaml theme={null} Smart Tag: Competitor Mentions = "Competitor X" Smart Tag: Pricing Objection = True Smart Tag: Security Concerns is not empty ``` **Use Cases:** * **Competitor alerts**: Trigger a signal to sales leadership only when a specific competitor is mentioned * **Objection routing**: Send pricing objection signals to enablement when the "Pricing Objection" tag is detected * **Feature request capture**: Route signals to product teams only when feature requests are identified in the conversation Smart Tag conditions evaluate the tags detected on the current call. Make sure your [Smart Tags are configured](/smart-tags#setting-up-a-smart-tag) in **Admin > Smart Tags** before using them as signal conditions. ### Step 3: Define the Signal Content The second section allows you to specify how to format the signal. * **Output Format**: Specify how the signal should be formatted * **Follow Up Prompt**: Write additional prompts that will summarize and include specific insights with your signal * **Mention Users**: Automatically mention relevant team members **Example Signal:** ```yaml theme={null} Signal Name: "Enterprise Security Concerns" Output Format: "Security Concerns Identified: {opportunity.name}" Follow Up Prompt: "Summarize any security concerns brought up by the customer. Include quotes" Follow Up Prompt: "Summarize how the sales rep or sales engineer in the call handled any concerns brought up" ``` ### Step 4: Configure Delivery Settings The final section determines where and how signals are delivered. **Delivery Options:** * **Channel**: Send to a specific public or private channel * **Direct Message**: Send to individual users * **Email**: Send to email addresses * **Dynamic Delivery**: Route based on Salesforce object ownership **Example Delivery Configuration:** ```yaml theme={null} Primary: Product Team Channel (#product-feedback) Secondary: Direct Message to Opportunity Owner Escalation: Manager notification for opportunities with ARR over $100k ``` AI Signals Configuration Interface ### Step 5: Test and Validate 1. **Create a Test Signal**: Set up a signal with broad criteria for testing 2. **Schedule a Test Call**: Have a team member conduct a call that should trigger the signal 3. **Review Output**: Check that the signal appears in the correct location 4. **Adjust Settings**: Fine-tune detection and delivery based on results ## Advanced Configuration ### Multiple Signal Workflows You can create multiple signal workflows for different use cases: **Product Feedback Signal:** * **Rules**: All calls with product discussions * **Content**: Listen for feature requests and feedback * **Delivery**: Product team channel + opportunity owner **Churn Risk Signal:** * **Rules**: Customer success calls + renewal discussions * **Content**: Listen for dissatisfaction indicators * **Delivery**: Customer success team + account manager **Competitive Intelligence Signal:** * **Rules**: Sales calls in competitive deals * **Content**: Listen for competitor mentions and comparisons * **Delivery**: Sales leadership + marketing team ### Cross-Functional Signal Routing Set up signals that automatically route to different teams: **Product Team Signals:** * Feature requests * Bug reports * User experience feedback * Integration requirements **Marketing Team Signals:** * Competitive intelligence * Market trends * Brand mentions * Campaign feedback **Customer Success Signals:** * Churn risk indicators * Upsell opportunities * Support issues * Renewal concerns ## Best Practices ### Signal Design 1. **Be Specific**: Create focused signals rather than broad ones 2. **Use Clear Language**: Write detection prompts that are unambiguous 3. **Test Thoroughly**: Validate signals in test channels before directing them to your team 4. **Iterate**: Continuously improve based on team feedback 5. **Avoid Noise**: Ensure signals provide actionable insights ### Delivery Optimization 1. **Right Audience**: Send signals to the team that can act on them 2. **Escalation Rules**: Set up automatic escalation for critical signals 3. **Mention Strategy**: Mention relevant team members when appropriate ## Troubleshooting ### Common Issues **Signals Not Triggering:** * Check detection rules are correctly configured * Verify calls are being processed * Ensure detection prompts are clear and specific **False Positives:** * Refine detection prompts to be more specific * Add additional filtering conditions * Review and adjust signal criteria **Delivery Problems:** * Verify Slack permissions and channel access * Check user permissions in Momentum * Confirm delivery settings are properly configured ### Performance Optimization **For High-Volume Teams:** * Use specific detection rules to reduce noise * Consider separate signal workflows for different team segments **For Large Organizations:** * Create team-specific signal workflows * Use dynamic delivery to route to appropriate channels ## Monitoring and Analytics ### Regular Reviews 1. **Weekly**: Check signal accuracy and relevance 2. **Monthly**: Review signal performance and team feedback 3. **Quarterly**: Assess overall AI Signals ROI and optimization opportunities ## Support If you encounter issues during setup, contact our support team: * **Slack**: Use your shared Momentum channel * **Email**: [support@momentum.io](mailto:support@momentum.io) # Daily Call Reviews Source: https://docs.momentum.io/daily-call-reviews-configuration Configure daily email digests for reps and managers ## Overview Daily Call Reviews send personalized email digests every morning at **8:00 AM** in each recipient's local time zone. These emails help reps prepare for upcoming calls and keep managers connected to their team's activities. ### Two Features in One **Daily Call Review for Reps** * Sent to all call attendees (not just hosts) * Includes today's upcoming calls with context from previous meetings * Includes yesterday's call summaries with action items * Subject line: `Keep the momentum daily` **Daily Call Review for Managers** * Sent to team managers * Two separate emails that can be enabled independently: * **Team Focus** (Today's Upcoming): `Momentum Daily — Team Focus` * **Team Recap** (Yesterday's Recap): `Momentum Daily — Team Recap` * Shows a smartly prioritized list of team meetings based on deal stage, opportunity amount, and conversation topics Daily Call Review Email Example ## Prerequisites * [Momentum AI installed with your preferred call provider](/how-to-install-momentum) * Admin access for organization-wide settings * Call recordings and summaries enabled * Salesforce integration active (for contextual information) *** ## Daily Call Review for Reps ### Admin Configuration #### Enable the Feature 1. Log in to your [Momentum admin dashboard](https://app.momentum.io/admin/momentum-ai-settings) 2. Navigate to **Momentum AI Settings** → **Email** section 3. Toggle **Daily Call Review for Reps** to **ON** 4. Click **Save settings** **Important:** When enabled, all users automatically receive emails. Users must opt out if they don't want to receive them. #### Manage Exclusions (Optional) Use the toggle to switch between **Exclude** and **Include** modes: * **Exclude mode (default):** People on the list will never get emails. Add users via **Select users to exclude...** and save. * **Include mode:** Only people on the list will receive emails; the exclude list is ignored while this is on. Add users via **Select users to include...** and save. If a user turns off the feature for themselves, they are removed from the include list and automatically added to the exclude list. Remove someone from either list by clicking the **X** on their user block and saving. Daily Call Review Admin Settings For Reps ### User Configuration Users can opt out of Daily Call Reviews: 1. Navigate to [Momentum Settings](https://app.momentum.io/settings) 2. Locate the **Daily Meeting Review** card 3. Toggle **Daily Call Review Email** to **OFF** to stop receiving emails ### What Reps Receive **Today's Upcoming Calls:** * Meeting title, time, and participants * Context from previous calls with the same attendees * Associated action items from prior conversations * Salesforce details: Account, Opportunity, Amount, Stage * Direct link to call page **Yesterday's Calls:** * Meeting title and time * Compact summary (4 lines max) * Associated action items * Salesforce context * Direct link to call page *** ## Daily Call Review for Managers **Note:** This feature may require a feature flag. Contact [support@momentum.io](mailto:support@momentum.io) if you don't see it. ### Admin Configuration #### Enable Email Types 1. Log in to your [Momentum admin dashboard](https://app.momentum.io/admin/momentum-ai-settings) 2. Navigate to **Momentum AI Settings** → **Email** section 3. Locate **Daily Call Review for Managers** Toggle on the email types you want to enable: **Yesterday's Recap:** * Subject: `Momentum Daily — Team Recap` * Summaries of yesterday's meetings for direct reports **Today's Upcoming:** * Subject: `Momentum Daily — Team Focus` * Prep notes for today's meetings with context from previous calls Click **Save settings** to apply. **Important:** When enabled, all managers automatically receive emails. Managers must opt out if they don't want to receive them. #### Manage Exclusions (Optional) Use the toggle to choose how you target manager emails: * **Exclude mode (default):** Managers on the list never receive either email type. Add them via **Select users to exclude...** and save. * **Include mode:** Only managers on the list receive the emails, and the exclude list is disabled while this is on. Add them via **Select users to include...** and save. When a manager turns off the feature in their personal settings, they are removed from the include list and added to the exclude list. Remove someone from either list by clicking the **X** on their user block and saving. Daily Call Review Admin Settings For Managers ### Manager Configuration Managers can opt out or customize which emails they receive: 1. Navigate to [Momentum Settings](https://app.momentum.io/settings) 2. Locate the **Daily Meeting Review** card 3. Toggle **Email me a daily review of my team's meetings** to **OFF** to stop all manager emails **Or customize individual emails:** * Keep the master toggle **ON** * Toggle **Yesterday's Recap** or **Today's Upcoming** individually ### What Managers Receive Manager emails show a **smartly prioritized selection** of team meetings, filtered based on: * Opportunity stage and amount * Conversation topics and key moments * Deal importance and activity Daily Call Review Manager Email Example **Team Focus Email** (Today's Upcoming): * Subject: `Momentum Daily — Team Focus` * Prioritized list of today's scheduled meetings * Meeting title, time, and participants * Account and Opportunity (if mapped to Salesforce) * Context summary from previous calls (4 lines max) * Link to call page **Team Recap Email** (Yesterday's Recap): * Subject: `Momentum Daily — Team Recap` * Prioritized list of yesterday's completed meetings * Meeting title, date/time, and participants * Account and Opportunity (if mapped) * Compact summary (4 lines max) * Link to call page *** ## Troubleshooting ### Not Receiving Emails? Check in this order: 1. **Admin Settings:** Verify the feature is enabled in [admin dashboard](https://app.momentum.io/admin/momentum-ai-settings) 2. **Exclusion List:** Check if you're on the admin's exclusion list 3. **Personal Settings:** Verify your toggle is **ON** in [personal settings](https://app.momentum.io/settings) 4. **Wait for Next Email:** Emails send at 8:00 AM local time; changes apply to the next scheduled email ### Missing Salesforce Context? * Verify your [Salesforce integration](/salesforce-event-mapping) is active * Check that calls are mapped to Salesforce objects * Ensure attendee emails match Salesforce Contact or Lead emails ### Manager Sub-Toggles Disabled? * Admin must enable the corresponding email type * Contact your admin to enable it * If the issue persists, contact [support@momentum.io](mailto:support@momentum.io) *** ## Best Practices ### For Admins **Rollout Strategy:** * Communicate the change before enabling (users receive emails automatically) * Start with one email type for managers before enabling both * Use exclusions sparingly (executives or specific roles only) **Monitoring:** * Track opt-out rates to gauge adoption * Gather feedback on email quality and relevance ### For Reps * Review emails every morning before calls * Click through for deeper context when needed * Follow up on action items from previous calls ### For Managers * Skim emails to identify coaching opportunities * Reference specific calls in 1-on-1s * Disable email types that aren't providing value *** ## Support Need help with Daily Call Reviews? * **Slack**: Use your shared Momentum channel * **Email**: [support@momentum.io](mailto:support@momentum.io) # Improving Data Hygiene Source: https://docs.momentum.io/data-hygiene Leverage Momentum's Autopilot, Contact Automation, Scheduled Notifications, and Scheduled Paths features to ensure your CRM data is accurate and up-to-date. Automate data capture and updates and proactively remind reps to update records, reducing manual entry and maintaining data integrity. ## Why Data Hygiene Matters Maintaining clean and accurate data in your CRM is crucial for effective decision-making, efficient sales processes, and reliable reporting. Poor data hygiene can lead to poor deal handoffs, wasted time, and misinformed strategies. By automating data capture and updates and ensuring timely reminders, you can significantly enhance the quality of your CRM data. ### Key Features for Improving Data Hygiene 1. **Autopilot** * **Automatic Data Capture:** Autopilot listens to calls and captures critical information automatically, ensuring that no important data is missed. * **Real-Time Updates:** Automatically updates CRM fields with the latest information from sales calls, reducing the need for manual data entry. * **Custom AI Prompts:** Create prompts tailored to your specific data requirements to ensure consistent and accurate data capture. [Autopilot](/autopilot) 2. **Contact Automation** * **Effortless Contact Capture:** Automatically adds participants from sales calls to your CRM as leads or contacts, ensuring comprehensive data coverage. * **Flexible Sync Options:** Sync attendees from calls as contacts or leads based on your Salesforce object preferences, either manually or automatically. * **Enhanced Multi-Threading:** Capture all stakeholders involved in a deal, improving multi-threading and ensuring no key contact is missed. [Contact Automation](/contact-automation) 3. **Scheduled Notifications** * **Automated Reminders:** Set up scheduled notifications to remind sales reps to update out-of-date records. * **Native in Slack:** Scheduled notifications are native in Slack, lowering the friction for reps to update their deals and ensuring the job gets done. * **Batch Processing:** Scheduled notifications are grouped by record type, allowing reps to review and update similar records simultaneously. This batch processing reduces administrative overhead and makes it easier for reps to maintain CRM accuracy. [Scheduled Notifications](/scheduled-notifications) 4. **Scheduled Paths** * **Proactive Follow-Ups:** Use scheduled paths to send follow-up reminders about a specific event for a deal at predetermined times, ensuring individual records are kept up-to-date. * **Individual vs. Batch Processing:** Scheduled Paths deliver reminders for a single record at the exact time needed, based on a specific date field in that record. This is in contrast to Scheduled Notifications, which handle multiple records and deliver reminders in a batch on a regularly scheduled cadence. * **Targeted Interventions:** Set conditions to trigger reminders for specific records that require updates, helping maintain data accuracy. [Salesforce Notifications](/salesforce-notifications) ### Step-by-Step Guide to Improving Data Hygiene 1. **Setting Up Autopilot** * Navigate to the Autopilot section in the Momentum admin dashboard. * Configure AI prompts to capture the specific data fields you need from sales calls. * Enable Autopilot Extractions to start automatically capturing and updating CRM data. 2. **Configuring Contact Automation** * Go to the Contact Automation section in the Momentum admin dashboard. * Create a new contact automation workflow by specifying the contact types and conditions for syncing attendees from calls. * Set up Slack notifications to alert your team when new contacts are added, ensuring they can review and enrich the data if necessary. 3. **Implementing Scheduled Notifications** * Navigate to the Scheduled Notifications section in the Momentum admin dashboard. * Create a new scheduled notification to remind reps to update records that have not been modified within a specified period. * Customize the notification message to include relevant details and useful action buttons for the reps to manage things from Slack. 4. **Setting Up Scheduled Paths** * Go to the Salesforce Notifications section in the Momentum admin dashboard. * Define conditions to trigger a notification for an event and conditions that require rep review and updates. * Schedule these paths to ensure regular reminders are sent to reps to maintain data hygiene. 5. **Monitoring and Refining** * Regularly monitor the data being captured and updated in your CRM to ensure it meets your quality standards. * Adjust AI prompts, contact automation workflows, and notification schedules as needed to improve accuracy and relevance. ### Benefits of Improved Data Hygiene * **Increased Efficiency:** Reduce the time spent on manual data entry, allowing your sales team to focus on selling. * **Better Decision-Making:** Rely on accurate and up-to-date data to make informed business decisions. * **Enhanced Reporting:** Improve the reliability of your reports and forecasts with clean and consistent CRM data. * **Stronger Multi-Threading:** Ensure all relevant stakeholders are captured and tracked, enhancing your sales strategy and relationship management. * **Proactive Management:** Maintain up-to-date records with automated reminders to reduce the challenges faced by your sales managers. ### Customer Testimonial *“As a Series A company, we are working to nail our GTM motion and scale it as we grow. Momentum helps us build repeatable processes while also savin rep and management time with automations and actionable insights.”* — Alex Mitchell, Head of Sales @ Fleet By following these steps and leveraging Momentum's powerful features, you can ensure that your CRM data is always accurate, up-to-date, and ready to support your business goals. For further assistance or to discuss custom workflows, please contact our support team. # Deep Research Source: https://docs.momentum.io/deep-research ## Overview Momentum's Deep Research is a foundational product that enables a unique kind of structured analysis over your conversational data. Chat with Deep Research to execute 'research plans' that surface information from conversations, then aggregate, normalize, and correlate this information into actionable insights that you can trace right back to the conversations they were derived from. ### Key Capabilities * **Natural Language Research**: Ask questions in plain English and Deep Research generates a structured plan to answer them * **Conversation Intelligence**: Automatically extract insights from [historical conversational data](/conversational-data-sources) linked to your CRM records * **Traceable Results**: Findings refer back to the specific customer quotes they originated from * **Scheduled Automation**: Set up recurring reports delivered to email or Slack * **Export & Share**: Download datasets as CSV or generate polished brief reports ## Use Cases Deep Research excels at answering complex questions that require analyzing patterns across many deals. Here are common use cases: ### Closed-Lost Analysis Understand why deals are being lost by analyzing closed-lost opportunities from the past 90 days. **Example prompts:** * "What are the top reasons deals were lost?" * "Which competitors are mentioned most frequently in lost deals?" * "What objections came up most often in lost deals?" Deep Research will search through all [historical conversational data](/conversational-data-sources) associated with your closed-lost opportunities, extract the relevant information, and present normalized findings you can act on. ### Open Pipeline Risk Assessment Identify deals at risk in your current pipeline before they slip. **Example prompts:** * "Which open deals have gone quiet in the last 30 days?" * "Are there any deals where the champion has left or gone silent?" * "Which deals have pricing objections that haven't been addressed?" ### Competitive Intelligence Aggregate competitive mentions across your pipeline. **Example prompts:** * "How often is \[Competitor] mentioned in our deals?" * "What features are prospects comparing us against competitors on?" * "Which deals have active competitive evaluations?" ### Win Pattern Analysis Discover what's working in your won deals. **Example prompts:** * "What messaging resonated most in won deals?" * "Which stakeholders were involved in deals we won?" ### Scheduled Reports Turn any Deep Research analysis into a recurring report. Once you've completed a research session with valuable insights, you can schedule it to run automatically and deliver updated findings on a regular cadence. **Frequency options:** * Daily * Weekly * Bi-weekly * Monthly * Quarterly Scheduled reports re-run your research plan against fresh data, so you always see the latest insights without manual effort. ## Getting Started ### Provisioning Deep Research is a seat-based product. Before users can access Deep Research, an organization administrator must provision them. **To provision users:** 1. Navigate to your organization settings 2. Navigate to the Deep Research section 3. Add users you want to grant access to 4. Users will see Deep Research available in their Momentum workspace Your organization has a set number of Deep Research seats based on your subscription. Contact your account manager if you need additional seats. Provisioning Deep Research users ### Creating Your First Session 1. Configure a Research Setup Deep Research setup 2. **Define your Salesforce filter** to specify which records to analyze (e.g., "Closed-Lost Opportunities from the last 90 days") CRM filters in Deep Research 3. (Optionally) Tell Deep Research about specific Salesforce fields you want to reference Adding CRM fields 4. Submit a prompt Submitting a prompt Deep Research will generate a research plan outlining the steps it will take to answer your question. Review the plan, then approve it to begin execution. ### CRM Filtering Every Deep Research session is anchored to a Salesforce filter that defines your analysis scope. Filters use standard Salesforce query logic. **Common filter patterns:** | Use Case | Filter Example | | ------------------------ | ----------------------------------------------------------------- | | Closed-Lost (90 days) | `IsClosed = true AND IsWon = false AND CloseDate >= LAST_90_DAYS` | | Open Pipeline | `IsClosed = false` | | Won Deals (This Quarter) | `IsClosed = true AND IsWon = true AND CloseDate = THIS_QUARTER` | | Enterprise Segment | `Amount >= 100000 AND IsClosed = false` | You can also add custom Salesforce fields to your dataset for richer analysis. Deep Research automatically pulls standard Opportunity fields like Name, Amount, CloseDate, StageName, and more. ## Getting the Most Out of Deep Research ### Prompting The quality of your results depends on asking clear, specific questions. Here are tips for effective prompting: **Be specific about what you're looking for:** * Instead of: "Why are we losing deals?" * Try: "What objections or concerns did prospects raise in deals we lost?" **Specify the output you want:** * "List the top 5 reasons deals were lost, with the percentage of deals each reason appeared in" * "Categorize each deal by the primary competitor mentioned" **Ask follow-up questions:** After your initial analysis, drill deeper with follow-ups: * "Of the deals lost to pricing, what specific pricing concerns were raised?" * "Show me the deals where \[Competitor X] was mentioned" **Use starter templates:** Deep Research offers pre-built starter templates for common analyses like Closed-Lost Analysis and Open Pipeline Risk. These are a great way to get started quickly. Starter prompt templates ### Creating a new plan Your first prompt will always trigger Deep Research to create a research plan. After that point, it's up to you whether or not Deep Research should continue to perform research, or if it should use the data at hand to answer your question. Create new plan option When you select 'Create New Plan', Deep Research will *build* on your existing results and fetch more information to add to the dataset. In this way, you can conduct analysis in a step-by-step fashion, creating consecutive research plans as you better understand your data. When 'Create New Plan' is not selected, Deep Research will only look at the active dataset to answer your question. This is much faster then proposing and running a research plan, and is useful for re-interpreting results, or fetching more details for specific rows in the dataset. ### Diving Deep Deep Research plans consist of several operation types that work together: * **Research Each Row**: Searches conversations linked to each record and extracts specific information using AI * **Transform Rows**: Derives new insights by combining existing columns * **Normalize**: Standardizes free-text responses into consistent categories for easier analysis * **Get Column Info**: Analyzes a column to show distributions, counts, and patterns As your plan executes, you'll see progress updates in real-time. Once complete, you can: * **Create a brief**: Generate a polished report summarizing key insights * **Export to CSV**: Download the full dataset for further analysis * **Schedule the report**: Set up recurring delivery of this analysis * **Share the session**: Collaborate with teammates by sharing your research session Share a session ## Understanding Credits Deep Research uses a credit system to manage usage. Your organization has a monthly credit budget, and different operations consume different amounts of credits. **Credit consumption by operation:** | Operation | Credit Cost | | ----------------- | --------------------- | | Research Each Row | 1 credit per row | | Transform Rows | 1 credit per 100 rows | | Normalize | 1 credit per 20 rows | | Get Column Info | Free | | Fetch Information | Free | ## Pricing Deep Research is available as an add-on module. Contact your Momentum account manager for pricing details and to enable the module for your organization. Your subscription includes: * A set number of user seats * A monthly credit allocation * Access to all Deep Research features including scheduled reports Additional seats and credits can be added to your subscription as needed. # Email Follow-Ups Source: https://docs.momentum.io/email-follow-ups Welcome to the documentation for our Email Follow-Up product. Momentum leverages advanced AI to craft personalized follow-up emails based on customer calls, ensuring they align with your communication style and brand guidelines. This tool helps create highly contextual, meaningful interactions while saving 90% of your time and effort on email writing. By automating email drafts and incorporating relevant links from your knowledge base, Momentum drastically reduces administrative tasks and maintains a tight cadence with your customers. Email Follow Up 1 ## Setting Up Email Follow-Up ### Step 1: Organization-Level Settings **Login to the Web Application:** 1. Navigate to the Email Follow-Up settings in your armin dashboard. **Set Communication Guidelines:** 1. Define the tone and style for follow-up emails. 2. Upload example emails that represent your brand's communication style. Email Follow Up 2 **Add Relevant Links:** 1. Provide links that your team's emails usually include such as security portal URLs or product pages. 2. Save these settings to be used in all follow-up emails. CleanShot 2024-06-22 at 08.33.12@2x.png ### Step 2: Individual-Level Settings **Access Individual Settings:** 1. Sales reps and customer support reps can customize their settings. 2. Navigate to the "Momentum Home" app in [https://app.momentum.io](https://app.momentum.io) and find the Email Follow-Up product. 3. Click on the Configure link on the top right of your list of emails. **Customize Personal Communication Style:** 1. Upload example emails that reflect personal communication preferences. 2. Adjust tone and style settings to match individual preferences. **Add Relevant Links:** 1. Provide relevant links only to them and not the rest of the team such as their own calendar booking link, or pricing sheet. 2. Save these settings to be used in their own follow-up emails. **Save and Test:** 1. Save individual settings. 2. Wait for your first email to ensure settings are applied correctly. CleanShot 2024-06-22 at 08.36.24@2x.png ## Best Practices **Maintain Consistency:** Ensure that your follow-up emails maintain a consistent tone and style that aligns with both your brand and individual communication preferences. **Timely Follow-Ups:** Schedule follow-ups promptly to maintain engagement and show customers that their time is valued. **Use Relevant Links:** Always include pertinent links such as your calendar booking link or security portal to make it easier for customers to take the next step. **Review and Edit Your Drafts:** Before sending, review the AI-generated emails to ensure accuracy and relevance. Utilize tools like Grammarly for grammar and spelling checks. ## Advanced Settings **Email Generation in Slack:** Leverage Slack for real-time email generation and modifications. Your perfect follow-up email will be written and shown to you for any edits right in Slack and can be sent with the click of a button via Gmail. **Batch Mode Interaction:** Utilize the web application to handle emails in batch mode. Review and edit multiple emails at once to streamline your workflow. **Automated Expiry:** Understand that emails not handled after a certain time will expire automatically to maintain relevance. ## **Contact Support** If you encounter any issues not covered in this documentation, please contact our support team at [support@momentum.io](mailto:support@momentum.io). By following these guidelines and utilizing the advanced features of our Email Follow-Up product, your sales and customer support teams can enhance their efficiency and maintain a consistent, professional communication style with your customers. For further assistance or to explore more features, book a call with our support team. Happy emailing! # Email Follow-Ups Configuration Source: https://docs.momentum.io/email-follow-ups-configuration ## Overview This guide walks you through the technical setup process for Momentum's Email Follow-Ups feature. Email Follow-Ups automatically generate personalized follow-up emails based on your sales calls, saving your team 90% of their email writing time. ## Prerequisites Before setting up Email Follow-Ups, ensure you have: * [Momentum AI installed with your preferred call provider](/how-to-install-momentum) * Admin access to your Momentum Organization * Slack workspace configured * Salesforce integration active ## Step-by-Step Setup ### Step 1: Organization-Level Settings **Access the Email Follow-Up Settings:** 1. Log in to your [Momentum admin dashboard](https://app.momentum.io/admin/email-follow-up-config) 2. Navigate to the **Email Follow-Up** section in the left sidebar **Set Communication Guidelines:** 1. **Define Tone and Style**: Set the overall tone for follow-up emails 2. **Upload Example Emails**: Provide sample emails that represent your brand's communication style 3. **Configure Common Links**: Add frequently used links with names and URLs that can be included in emails **Example Relevant Links:** 1. **Security Portal URLs**: Add links to your security portal or compliance documentation 2. **Product Pages**: Include links to relevant product pages and resources 3. **Calendar Booking**: Add team calendar booking links 4. **Pricing Sheets**: Include links to pricing documentation ### Step 2: Individual-Level Settings Individual-level settings allow users to customize their email follow-ups beyond the organization-wide defaults. This personalization ensures that each team member's emails reflect their unique communication style while maintaining brand consistency. **Key Customization Options:** * **Personal Writing Style**: Override default tone and formality settings to match your individual voice * **Custom Email Examples**: Create and save your own email examples * **Personalized Links**: Add your own frequently used resources and calendar links These individual settings complement (but don't replace) organization-wide guidelines, giving users flexibility while maintaining brand standards. **Access Individual Settings:** 1. Navigate to the [Momentum Home app](https://app.momentum.io) 2. Find the Email Follow-Ups product section 3. Click **"Configure"** in the top right of your email list **Customize Personal Communication Style:** 1. **Upload Personal Examples**: Provide emails that reflect your personal communication preferences 2. **Adjust Tone Settings**: Customize the tone to match your individual style 3. **Set Writing Preferences**: Configure how formal or casual your emails should be **Add Personal Links:** 1. **Personal Calendar**: Add your individual calendar booking link 2. **Personal Resources**: Include links specific to your role or territory 3. **Custom Templates**: Upload any personal email templates you use ## Best Practices ### Email Content 1. **Keep It Concise**: Focus on key points from the call 2. **Include Next Steps**: Always include clear next steps 3. **Personalize**: Reference specific points from the conversation 4. **Add Value**: Include relevant resources or information ### Timing and Frequency 1. **Send Promptly**: Send follow-ups within 2-4 hours of the call 2. **Avoid Spam**: Don't send too many emails to the same contact 3. **Respect Time Zones**: Consider recipient time zones when scheduling ### Quality Control 1. **Review Before Sending**: Always review emails before sending 2. **Test Templates**: Test new templates with a small group first 3. **Monitor Performance**: Track open rates and response rates 4. **Iterate**: Continuously improve based on results ### Regular Reviews 1. **Weekly**: Check email quality and team adoption 2. **Monthly**: Review performance metrics and adjust templates 3. **Quarterly**: Assess overall Email Follow-Ups ROI ## Support If you encounter issues during setup, contact our support team: * **Slack**: Use your shared Momentum channel * **Email**: [support@momentum.io](mailto:support@momentum.io) * **Documentation**: Review our [Email Follow-Ups best practices](/email-follow-ups) # Ensuring Employee Consent and Privacy Source: https://docs.momentum.io/employee-and-customer-consent In the age of artificial intelligence, employee efficiency, and effectiveness have seen significant advancements. However, with these advancements come concerns about privacy and consent. At Momentum, we believe in leveraging AI to enhance employee efficiency and effectiveness without compromising their privacy. This article outlines our approach to ensuring employee consent and how we support our customers in utilizing AI responsibly for performance management. ## Active Consent Process Our commitment to privacy begins with an active consent process. Employees are required to undergo an installation procedure that grants access to their calendars and calls. This process includes a clear disclosure of data handling procedures, ensuring that employees are fully aware of how their data will be used. By obtaining explicit consent, we respect employees' autonomy and foster a culture of transparency. ## Real-time Control Momentum empowers employees by providing them with real-time control over data collection during calls. Employees can pause or stop data collection at any point, allowing them to manage which calls (or parts of their calls) will be analyzed. This feature ensures that employees feel secure and in control, reinforcing our commitment to their privacy. ## Customizable Consent Disclaimer To further enhance transparency, Momentum offers a customizable consent disclaimer feature. This allows hosts to tailor the recording disclaimers displayed during calls, setting clear expectations regarding data recording and processing. By providing this customization, we ensure that all parties involved are fully informed about the data collection process. ## Disclaimers on Analysis Momentum recognizes the importance of proper data use. We allow organizations to include disclaimers in each analysis, specifying that the data should not be utilized for performance management. This additional layer of protection ensures that data is used responsibly and ethically, aligning with our customers' preferences not to rely solely on AI for performance evaluations. ## Transcription-Only Data Storage Data security is paramount at Momentum. We have implemented a transcription-only data storage policy, where only the transcriptions of calls are retained, and audio recordings are discarded after processing. This approach minimizes the storage of sensitive data, further enhancing data security and privacy. # Conclusion Momentum's approach to utilizing AI for performance management is rooted in the principles of consent, transparency, and security. By ensuring active consent, providing real-time control, offering customizable disclaimers, and implementing stringent data storage policies, we respect employees' privacy while enhancing their performance. If you are interested in learning more about our security protocols and integrations, please visit our [Security Portal](https://security.momentum.io/). To discuss further or if you have any questions, feel free to reach out. Let's work together to create a secure and efficient performance management system that respects employee privacy. ## Call to Action Learn more about how Momentum can help your organization enhance performance management while ensuring employee consent and privacy. Book a demo with us today! Thank you for trusting Momentum as your partner in responsible AI-driven performance management. By following these practices, Momentum not only enhances performance management but also builds trust with employees, ensuring that their privacy and consent are always prioritized. # Enablement Videos Source: https://docs.momentum.io/enablement-videos Step-by-step video walkthroughs for configuring and getting the most out of Momentum. A collection of enablement videos to help you configure and optimize Momentum. Each video links to a step-by-step guide. 4:18 7:55 9:28 7:57 8:09 8:51 8:42 2:19 ## Best of Momentum Explore the best of what Momentum has to offer. # Enhancing Reporting and Analysis Source: https://docs.momentum.io/enhancing-reporting-and-analysis Utilize Autopilot to consistently and reliably extract data across the entire sales and customer success teams. Use Scheduled Reports to deliver key metrics and insights to your team regularly. Ensure everyone stays informed about sales performance and pipeline status without manually checking Salesforce. Leverage these tools to review data at scale, integrate dashboards into the team's workflows, and keep data up-to-date. ### Why Enhancing Reporting and Analysis Matters Consistent and accurate reporting is vital for understanding sales performance, tracking pipeline status, and making informed decisions. Manual data input and report generation can be time-consuming and prone to errors. By automating these processes, you can ensure that your leadership team has access to the latest insights and metrics, helping them make strategic decisions based on accurate, up-to-date data. This not only improves efficiency but also boosts confidence in data-driven decisions. ### Key Features for Enhancing Reporting and Analysis 1. **Scheduled Reports** * **Automated Delivery:** Set up scheduled reports to automatically deliver key metrics and Salesforce insights to your team at regular intervals. * **Customizable Content:** Tailor the content of scheduled reports to include the most relevant data for your team's needs, such as sales performance, pipeline status, and deal progress. * **Integration with Workflows:** Integrate these reports into your team's workflows by delivering them directly to Slack channels or individual users, ensuring timely and easy access to critical information. * **Collaborative Discussions:** Deliver Salesforce data right in Slack, where the team engages most with it. Team members can use threads to collaborate and converse about the data, fostering a collaborative environment for analysis and decision-making. [Scheduled Reports](/scheduled-reports) 2. **Autopilot** * **Reliable Data Extraction:** Use Autopilot to automatically extract data from sales calls and interactions, ensuring that all relevant information is captured consistently across the team. * **Context-Aware Prompts:** Configure Autopilot with prompts that adapt based on the stage of the opportunity and the type of call, ensuring that the right data is captured at the right time. * **Consistent Data Quality:** Maintain high data quality and consistency across all reps, reducing discrepancies and ensuring accurate reporting. [Autopilot](/autopilot) ### Step-by-Step Guide to Enhancing Reporting and Analysis 1. **Setting Up Scheduled Reports** * Navigate to the Scheduled Reports section in the Momentum admin dashboard. * Create a new scheduled report by selecting the Salesforce report you'd like to update and deliver. * Choose the Slack channels or individual users who should receive the scheduled reports. * Encourage team members to review the reports regularly and use the insights to inform their activities and decisions. * Foster collaboration by encouraging team members to discuss the data in report threads, share insights, ask questions, and coordinate actions directly in Slack. 2. **Implementing Autopilot for Data Extraction** * Go to the Autopilot section in the Momentum admin dashboard. * Configure Autopilot with prompts that capture the necessary data fields for your reports, ensuring consistency across all reps. * Set up context-aware prompts that adjust based on the opportunity stage and call type, ensuring accurate and relevant data capture. * Monitor the data extracted by Autopilot to ensure high quality and consistency, making adjustments as needed to improve accuracy. 3. **Maintaining Continuous Improvement** * Regularly review the effectiveness of your scheduled reports and the data captured by Autopilot. * Adjust the content and frequency of reports based on feedback from your team and evolving business needs. * Use the insights gained from reports to identify trends, address issues, and continuously improve your sales strategies and performance. ### Benefits of Enhancing Reporting and Analysis * **Timely Access to Insights:** Ensure your team has access to the latest metrics and insights without manually checking Salesforce, enabling timely and informed decision-making. * **Improved Data Quality:** Maintain high data quality and consistency across all reps with reliable and automated data extraction. * **Streamlined Workflows:** Integrate reports directly into your team's workflows, reducing the need for manual report generation and review. * **Collaborative Analysis:** Foster a collaborative environment by delivering reports in Slack, allowing team members to discuss and analyze data in threads. * **Better Strategic Planning:** Use the insights gained from regular reports to inform strategic planning, identify trends, and address potential issues proactively. * **Enhanced Team Performance:** Keep your team focused on high-value activities by providing them with the critical information they need to succeed. ### Customer Testimonial *“Momentum has been an amazing game changer for me. Not only has it opened my mind to what is possible with automation and AI, but it has accelerated my ability to help the team perform at a higher level. From the automation of notes into our CRM, to detailed call feedback reviews, to insights learned across calls, this platform is amazing and the team is even better. Good, smart, intelligent and strategic individuals who make all the difference. Could not recommend working with Momentum more.”* — Jonathan Kvarfordt, Head of GTM Revenue Enablement Product Marketing @ Simetrik By leveraging Momentum's Scheduled Reports and Autopilot, you can enhance your reporting and analysis processes, ensuring timely and accurate insights for your team. For further assistance or to discuss custom workflows, please contact our support team. # Enhancing Sales Efficiency Source: https://docs.momentum.io/enhancing-sales-efficiency **Momentum has allowed our team to be more productive while staying lean. Their AI solution has helped us reduce churn over 2023 by allowing all stake holders to see calls in real time and collaborate for a solution. Their support and customer success is second to none.** Streamline your sales processes by utilizing AI Signals, Autopilot, and Summaries. Automate administrative tasks and focus on selling by receiving real-time insights and automated call notes. ### Why Sales Efficiency Matters Sales efficiency is critical for maximizing productivity, reducing sales cycle times, and increasing revenue. Inefficient sales processes can lead to wasted time, missed opportunities, and decreased morale among sales teams. By automating routine tasks and providing real-time insights, Momentum helps sales teams focus on what they do best—selling. ### Key Features for Enhancing Sales Efficiency 1. **AI Signals** * **Real-Time Insights:** AI Signals captures key information from sales and customer success calls—such as product feedback, churn risk, and competitive mentions—and shares it with key stakeholders instantly. * **Customizable Alerts:** Tailor signals to your specific needs and include specialized summarized, ensuring that your team receives the most relevant and actionable insights. * **Cross-Functional Collaboration:** Distribute insights across teams and to leadership to keep everyone informed and aligned. [AI Signals](/ai-signals) 2. **Autopilot** * **Automatic Data Capture:** Autopilot listens to calls and automatically updates CRM fields, reducing the need for manual data entry. * **Streamlined Processes:** Capture essential information in real-time, ensuring that your CRM is always up-to-date and accurate. * **Custom AI Prompts:** Create prompts to guide reps on what information to capture during calls, ensuring consistency and completeness. [Autopilot](/autopilot) 3. **Summaries** * **Automated Note-Taking:** Summaries automatically generate detailed notes from sales calls, saving reps time and ensuring that key information is recorded. * **Instant Insights:** Summaries provide actionable insights from calls, which can be shared directly with the team in Slack or CRM. * **Configurable Workflows:** Customize summaries to focus on specific aspects of calls, such as objections, next steps, or competitor analysis. [Summaries](/call-summaries) ### Step-by-Step Guide to Enhancing Sales Efficiency 1. **Implementing AI Signals** * Navigate to the AI Signals section in the Momentum admin dashboard. * Set up signals to capture and share the most relevant insights from sales calls. * Configure delivery channels to ensure that the right teams receive timely alerts. 2. **Setting Up Autopilot** * Go to the Autopilot section in the Momentum admin dashboard. * Configure AI prompts to capture critical data fields during sales calls. * Enable Autopilot Extractions to automatically update CRM records in real-time. 3. **Utilizing Summaries** * Navigate to the Summaries section in the Momentum admin dashboard. * Set up summary workflows to capture and highlight key information from sales calls. * Customize the content and delivery of summaries to align with your team's needs. 4. **Monitoring and Refining Processes** * Regularly review the data and insights captured by AI Signals, Autopilot, and Summaries to ensure they meet your team's needs. * Adjust configurations and prompts as necessary to improve accuracy and relevance. * Use Momentum's reporting features to track the impact on sales efficiency and identify areas for further improvement. ### Benefits of Enhanced Sales Efficiency * **Increased Productivity:** Reduce the time spent on administrative tasks, allowing sales reps to focus on selling. * **Shorter Sales Cycles:** Streamlined processes and real-time insights help move deals through the pipeline faster. * **Improved Accuracy:** Automated data capture and note-taking ensure that key information is recorded accurately and consistently. * **Better Collaboration:** Share insights across teams to ensure everyone is informed and working towards the same goals. * **Higher Revenue:** More efficient sales processes lead to increased revenue and better overall performance. ### Customer Testimonial *“Momentum has allowed our team to be more productive while staying lean. Their AI solution has helped us reduce churn over 2023 by allowing all stake holders to see calls in real time and collaborate for a solution. Their support and customer success is second to none.”* — Alex Cartens, Director of RevOps @ Chowly By leveraging Momentum's powerful features, you can streamline your sales processes, enhance productivity, and focus on driving revenue. For further assistance or to discuss custom workflows, please contact our support team. # Exclusion Lists Source: https://docs.momentum.io/exclusion-lists Momentum’s **Exclusion List** feature gives you precise control over which data gets analyzed across your revenue communications. Whether you're syncing call recordings from tools like Gong, Clari Copilot, or Chorus, or relying on Momentum's native call recording, Exclusion Lists help ensure your reporting and AI workflows remain focused on the right conversations. ## What is an Exclusion List? An **Exclusion List** is a configurable set of criteria that tells Momentum to skip processing certain emails or calls. You can exclude: * Specific email addresses * Entire email domains (e.g. `@vendor.com`) * CRM accounts based on your own business logic This is useful for ignoring sensitive conversations, vendor meetings, or accounts that have opted out of recording or analysis. ## Types of Exclusions Momentum supports three main types of exclusions: ### 1. **Email Exclusion List** Prevent analysis of calls and messages to related to specific email addresses. **Examples:** * `legal@yourcompany.com` * `it@vendor.com` ### 2. **Email Domain Blocklist** Skip processing for all calls or emails associated with a given domain. **Examples:** * `@yourinvestors.com` (to avoid recording board meetings) * `@partner.org` (to avoid partner back-and-forth emails) ### 3. **Conditional Exclusions (Advanced)** For CRM-integrated workflows, you can define structured conditions to exclude conversations based on business-specific rules. This is especially useful for handling scenarios like: * Accounts that have opted out of call recording * Customers located in a certain region * Internal testing accounts **Example: Opt-out of Call Recording** If accounts in your CRM have a field that captures them explicitly opting out of call recording, you can codify that preference in Momentum using a condition like: ```json theme={null} { "_neq": { "Account?.Opt_Out_of_Call_Recording__c": true } } ``` This ensures that any meeting tied to an account where the custom field `Opt_Out_of_Call_Recording__c` is set to `true` will be excluded from recording and downstream analysis. > 🔐 Use conditional logic to align your conversation analysis with customer preferences, privacy needs, or internal segmentation strategies. ## How Exclusion Lists Work Exclusions are applied across the following inputs: * Calls pushed into Momentum from CI tools like Gong, Clari Copilot, and Chorus * Calls recorded natively by Momentum (when no CI tool is in use) * Emails or Cases flowing into Momentum through your CRM If a contact, domain, or account matches your exclusion list, Momentum will: * Ignore that conversation for any AI analysis * Exclude it from Autopilot workflows * Skip applying AI Signals or triggers * Not surface the conversation in reporting or deal rooms ## Managing Exclusion Lists in the UI You can configure Exclusion Lists directly in the Momentum dashboard. Navigate to: **Settings → Security → Exclusion Lists** From here, you can: * Add individual emails or domains * Paste in a list of entries * Define conditional logic using the advanced editor CleanShot 2025-03-27 at 17.37.162x.png > ⚠️ Note: The previous names Email Blocklist and Email Domain Blocklist are now updated to Email Exclusion List and Email Domain Exclusion List for clarity. ## Best Practices * **Exclude sensitive attendees** to avoid the recording of meetings that should be kept private. * **Block known vendors** that don't impact pipeline to keep reporting focused. * **Use conditional logic** to align analysis with your compliance requirements. # Executive Briefs Source: https://docs.momentum.io/executive-briefs Welcome to the Executive Briefs documentation. This guide is designed to help RevOps and Sales Leaders configure and maximize the benefits of our Executive Briefs product. ## Key Features of Executive Briefs ### Comprehensive Call Analysis Executive Briefs allow you to collectively analyze weeks' worth of calls, drawing insights that leadership seeks. This includes aggregating account details and providing bullet-point updates on progress made over many days. **Key Benefits** : * **Aggregate Insights**: Compile data from multiple calls to provide a clear picture of sales performance and customer feedback. * **Leadership Focus**: Tailor insights to what matters most to executives, such as pitch effectiveness, customer reception, and pricing feedback. ### Customizable Filtering and Targeting Use Momentum's condition builder to filter and focus on specific subsets of calls, such as all calls from the East Coast commercial team or the enterprise team in EMEA. **Key Benefits** : * **Precision Filtering**: Use Salesforce fields to narrow down the calls you want to analyze. * **Tailored Insights**: Program custom prompts to extract the exact insights your stakeholders are looking for. ### Scheduled Delivery Schedule Executive Briefs to be delivered on a set cadence, such as weekly every Friday morning right before your leadership team call. **Key Benefits** : * **Consistent Updates**: Ensure leadership receives timely updates without manual effort. * **Automated Workflow**: Set it once and have insights delivered automatically. ### Stakeholder-Specific Insights Deliver refined insights that are targeted to specific stakeholders, such as CMOs, CFOs, CPOs, CEOs, or any layer of leadership within sales, from first-level managers to CROs. **Key Benefits** : * **Personalized Briefs**: Customize the content to match the interests of different executives. * **Enhanced Observability**: Increase visibility into organizational performance tailored to each leader's focus. ## Getting Started with Executive Briefs ### Step 1: Integration Setup 1. **Install Momentum AI with your preferred call provider:** [Momentum Installation Guide](/how-to-install-momentum) 2. **Log in to access the Executive Briefs dashboard:** * Once logged in, navigate to the Executive Briefs section. ### Step 2: Configure Your Executive Brief 1. **Create a New Brief:** * Navigate to the **Executive Briefs** section and click on "Create New Brief." 2. **Set Delivery Time:** * Choose the date and time for a weekly or custom cadence. For example, you might set the brief to be delivered every Friday at 13:00. 3. **Define Criteria for the Brief:** * **Title:** Enter a title for your brief, such as "Weekly Sales Review." * **Description:** Provide a brief overview of what the brief will cover. * **Guidelines:** (Optional) Add any specific instructions or guidelines for the brief. 4. **Add Sections:** * Create as many sections as needed. For each section, provide examples of content that can be used as guidance by the AI model. Examples might include: * **Our Pitch:** "How are the reps pitching the product?" * **Pricing:** "What are the highlights of pricing conversations?" * **Competition:** "What are the discussions around competition and which competitors are mentioned?" * **Recommendations:** "What actionable recommendations can be derived from the calls?" * **Red Flags:** "Identify any red flags or noteworthy findings that could impact the sales process." 5. **Reorder and Preview:** * Sections can be re-ordered or deleted as needed. Preview the end result to ensure the brief contains the insights you need. * The preview will run on a small group of calls and execute quickly, allowing you to make adjustments before the final brief is generated. ### Step 3: Apply Filters 1. **Set Filters:** * Use Momentum's condition builder to filter down subsets of calls. You can filter by Salesforce fields to focus on specific teams or regions. For example: * **Opportunity Amount > 100000** * **Opportunity Owner's Manager = "John Doe"** ### Step 4: Choose Delivery Destination 1. **Select Destination:** * Send the brief via Email, Slack (channel or DM), or Microsoft Teams channel. ### Step 5: Generate and Schedule Briefs 1. **Run Preview:** * Run a preview to review the brief's content based on a small subset of calls. 2. **Save and Schedule:** * Once satisfied with the preview, save the brief. The final generation will run through all the calls that meet the criteria, which can be hundreds or thousands. * The brief will be delivered on the chosen cadence, such as next Friday morning. ## Monitoring and Analyzing Executive Briefs ### Regular Monitoring * **Check Regularly**: Stay updated on the insights delivered by Executive Briefs. * **Analyze Data**: Look for patterns or recurring issues that need attention. * **Adjust Settings**: Refine your briefs based on the analysis to improve their relevance and impact. * **Act on Insights**: Use the insights to make informed decisions and drive business growth. ### Share Feedback * Encourage your team to provide feedback on the usefulness of the briefs to continuously improve the system. ## Conclusion Executive Briefs is a powerful tool that provides unparalleled visibility and insights from your sales calls. By delivering tailored, actionable insights directly to leadership, it helps improve decision-making and organizational performance. Ready to take your sales insights to the next level? [Get Started with Executive Briefs](https://www.momentum.io/get-started) today! For any questions or support, feel free to reach out to our customer service team at [support@momentum.io](mailto:support@momentum.io) # Gaining Customer Insights Source: https://docs.momentum.io/gaining-customer-insights Capture and share valuable customer feedback and insights using AI Signals and Deal Rooms. Enhance product development and marketing strategies based on real-time data from customer interactions. ### Why Customer Insights Matter Understanding customer needs, preferences, and feedback is crucial for developing successful products, crafting effective marketing strategies, and maintaining strong customer relationships. However, in many organizations, valuable insights often get lost or delayed due to slow communication channels and hierarchical barriers. Momentum's AI Signals and Deal Rooms can cut through these layers, ensuring that vital information reaches the right teams quickly and efficiently. ### Key Features for Gaining Customer Insights 1. **AI Signals** * **Real-Time Data Flow:** AI Signals captures key insights from sales calls—such as product feedback, customer pain points, and competitive mentions—and shares them instantly across the organization. * **Customizable Signals:** Tailor signals to detect specific types of feedback and insights, ensuring that each team receives the most relevant information. * **Cross-Functional Collaboration:** Automatically distribute insights to marketing, product development, and leadership teams, fostering collaboration and informed decision-making. [AI Signals](/ai-signals) 2. **Deal Rooms and Account Rooms** * **Centralized Information Hub:** Create dedicated Slack channels for each deal, consolidating all relevant information, communications, and updates in one place. * **Automated Alerts:** Use AI Signals and Salesforce Notifications to automatically update Deal Rooms and Account Rooms with relevant insights, ensuring that all stakeholders are informed in real time. * **Transparency and Accountability:** Maintain a clear record of customer interactions and feedback, making it easier to track and act on important information. [Deal Rooms and Account Rooms](/how-to-create-a-deal-room-and-manage-opportunities) ### Step-by-Step Guide to Gaining Customer Insights 1. **Implementing AI Signals** * Navigate to the AI Signals section in the Momentum admin dashboard. * Set up signals to capture specific types of feedback and insights from customer interactions. * Configure delivery channels to ensure that marketing, product, and leadership teams receive timely alerts. 2. **Setting Up Deal Rooms** * Go to the Deal Rooms section in the Momentum admin dashboard. * Configure Deal Rooms and Account Rooms to be automatically created for key accounts and opportunities, inviting relevant stakeholders from across the organization. * Use AI Signals and Notifications to automatically update Deal Rooms with new insights, feedback, and alerts. Account Rooms and Deal Rooms will be available as an option for any notification you can build with Momentum. 3. **Monitoring and Acting on Insights** * Regularly review the insights captured by AI Signals to identify trends and recurring issues. * Share relevant insights with product development teams to inform feature enhancements and new product ideas. * Provide marketing teams with data-driven insights to refine messaging and positioning strategies. * Alert leadership to significant feedback and potential churn risks, enabling proactive management and swift action. ### Benefits of Gaining Customer Insights * **Enhanced Product Development:** Direct feedback from customers helps product teams prioritize features and improvements that matter most to users. * **Improved Marketing Strategies:** Real-time insights enable marketing teams to craft more effective messaging and positioning based on actual customer experiences and needs. * **Proactive Customer Management:** Quickly identify and address potential churn risks, improving customer satisfaction and retention. * **Faster Decision-Making:** Delivering insights directly to top leadership cuts through layers of management, enabling faster, more informed decision-making. * **Cross-Functional Collaboration:** Ensure all relevant teams are aligned and working together based on the same up-to-date information. ### Customer Testimonial *“Momentum has given us the ability to capture real time insights at a transactional level within our business. We can now better understand customer interactions with our sales org.”* — Navin Persaud, Head of Revenue Operations @ 1Password By leveraging Momentum's AI Signals and Deal Rooms, you can ensure that valuable customer insights flow freely throughout your organization, driving better product decisions, more effective marketing, and proactive customer management. For further assistance or to discuss custom workflows, please contact our support team. # Getting Started with Momentum Source: https://docs.momentum.io/getting-started-with-momentum-ai A brief introduction to Momentum. Momentum is a powerful tool that transforms your sales calls and emails into valuable sources of customer intelligence. This intelligence is key in driving revenue, accelerating sales cycles, and establishing go-to-market (GTM) observability across your entire team. ## What Sets Us Apart We seamlessly integrate with your existing tools, such as Zoom, Gong, Chorus, Google Meet, and more, leveraging AI and automation to extract and synthesize data at scale. This means your reps don't need to log into an additional platform. Companies like Zscaler, Ramp, and 1Password use Momentum to capture forecast and churn risk, autofill Salesforce fields, share product signals, and deliver instant insights to their preferred destination (e.g., Slack, Notion, Drive, etc.). ## Navigating Our Docs Our documentation is divided into several sections, each dedicated to a specific aspect or feature of Momentum. Here's a quick overview: Install Momentum in minutes. Take a look at Momentum's product offerings. Explore how to leverage Momentum for your use cases. Learn how we protect your data with our security and privacy measures. ### Configuration & Setup Guides: Configure automated call summaries and delivery workflows. Set up automated CRM field population from sales calls. Trigger historical analysis based on Salesforce events. Run on-demand, bulk extractions on CRM records. Configure automated customer insight detection and delivery. Configure automated email follow-ups for your team. Set up notifications and integrations with Salesforce. Configure scheduled notifications and alerts. Set up automated reporting schedules. Learn how to create and manage deal rooms. ### Other pages of interest: Learn about Momentum's POC process. Optimize your success with Momentum by following best practices. # Deal Rooms and Account Rooms Source: https://docs.momentum.io/how-to-create-a-deal-room-and-manage-opportunities Welcome to the comprehensive guide on setting up and managing Deal Rooms and Account Rooms with Momentum. Our platform is designed to streamline your sales processes, automate workflows, and ensure seamless communication within your team—all within Slack. This documentation will guide you through the key features and provide step-by-step instructions to get you started. ## Introduction to Deal Rooms and Account Rooms Deal Rooms and Account Rooms are specialized Slack spaces tailored to enhance your sales enablement efforts. These rooms consolidate all necessary information, communication, and updates in one place, reducing Slack fatigue and preventing deals from going stale. By leveraging our platform, you can maximize your team's efficiency and ensure every stage of your opportunity is managed effectively. ### Key Features and Benefits * **Improve Visibility**: Ensure that the right stakeholders are involved and engaged with deal progress directly within Slack. * **Automate Sales Motions**: Centralize processes and communications to drive efficiency and reduce manual updates. * **Capture Everything in Slack**: Maintain a log of all interactions and updates, enhancing transparency and improving handoffs. * **Lower Administrative Burden**: Simplify CRM updates by integrating them into your Slack workflow. * **Seamless Transition to Account Rooms**: Post-deal, transition seamlessly to Account Rooms for ongoing management and monitoring. ## Getting Started with Deal Rooms ### Creating Your First Deal Room ### Automated Creation 1. **Set Criteria**: * Define triggers for automatic Deal Room creation. For example, set Momentum to create a Deal Room when an opportunity moves to stage 2 and exceeds \$50,000. In certain cases, you may instead need to [configure an advanced self-managed Salesforce Flow](/user-managed-salesforce-flows). 2. **Auto-Invite Champions**: * Momentum will automatically invite relevant collaborators and stakeholders needed to close the deal. Untitled You can find the automations for creating deal rooms or inviting stakeholders in the advanced section of your Momentum admin dashboard. These automations, also known as recipes, can be customized with your own settings before their creation. ### Manual Creation 1. **Find Momentum in Slack**: * Use the Slack search bar to find the Momentum user. 2. **Start a Deal Room**: * From the Momentum Slack app Home, select the deal you want to focus on and click the "Start Deal Room" button. Untitled Congratulations! You now have a brand-new Deal Room setup. Remember, if the opportunity has a different owner in Salesforce, both you and the owner will be invited to the new Deal Room channel. ### Managing Your Opportunity 1. **Update Deal**: * Click the "Update Deal" button from the top message in your Deal Room to update key opportunity fields in Salesforce, such as stage, close date, amount, or next steps. Untitled * The top message in your Deal Room is always up-to-date and pinned for easy access. 2. **Capture Files and Highlights**: * **Automatically Capture Files**: Momentum uploads files and images directly to the Salesforce opportunity from the channel. Look for the 💾 reaction indicating successful capture. * **Message Highlights**: Highlight important messages by reacting with the ☝️ emoji. Momentum will store these highlights as Chatter comments in Salesforce, confirmed with a ✅ reaction. Untitled ### Inviting Teammates Momentum Deal Rooms and Account Rooms are essentially Slack channels and function in the same way. Channel members can manually invite users as they would in a regular channel, by '@' mentioning them. In Slack, an option to click a button to invite them will be provided. Feel free to invite individuals who are relevant to a deal. 1. **Dynamic Invitations**: * Configure Deal Rooms to dynamically invite users based on record updates. Automatically bring in legal teams, solutions engineers, or any other stakeholders as needed. ## Transitioning to Account Rooms Once a deal is closed, upgrade your Deal Room to an Account Room. This ensures a smooth handoff to your Customer Success Manager (CSM) while keeping the sales team engaged for potential expansions or mitigating churn risks. You can configure account room workflows in the advanced section of your Momentum admin dashboard. These appear as "recipes" that can be activated and modified. You can specify what particular stages or Salesforce conditions should trigger the conversion from opportunity/deal room to account room. ## Archiving Deal Rooms and Account Rooms As you work through new opportunities and acquire successful customers, deal rooms and account rooms will begin to accumulate in your Slack. It's crucial to archive these channels when deals or accounts are lost. Doing so minimizes communication and reduces Slack fatigue for your team. Momentum provides recipes in the advanced section of your admin dashboard for setting up auto-archiving. However, any individual in a channel or a Slack admin can manually archive, depending on your Slack instance settings and the progress of the deal. ## Advanced Use Case: Send **AI Summaries and Signals to Rooms** Leverage our AI to summarize calls and highlight key signals into your deal rooms and account rooms to keep your team informed. You can direct any type of AI or regular notifications into your deal, rooms to improve visibility, and reduce noise on other channels. ## Advanced Use Case: Setup Playbook To Enable Your Team With The Right Next Step Momentum Playbook enables you to deliver links, next steps, and milestones to your team. This becomes particularly useful whenever a deal enters a specific stage, and a deal room is created for it. Utilizing this playbook significantly reduces the effort needed to compose these notifications and manage your sales playbook throughout your organization. Playbook can be found in the Slack automation section of your admin dashboard. CleanShot 2024-06-22 at 09.03.53@2x.png ## Conclusion By following this guide, you're well on your way to mastering Deal Rooms and Account Rooms in Momentum. These tools are designed to centralize your sales efforts, automate workflows, and ensure seamless communication across your team. # Momentum Installation Guide Source: https://docs.momentum.io/how-to-install-momentum Install Momentum in minutes. ## System Requirements Before you begin the installation process, ensure that your environment meets the following requirements: * Access to a Slack (or Microsoft Teams) administrator instance. * Ability to authorize Momentum in Salesforce as an admin. * If utilizing Momentum AI, the ability to configure Momentum access to your call recording technology (Gong, Chorus, Clari Copilot, Dialpad, or Zoom). If you'd like an overview of how Momentum accesses your systems and the permissions granted, please review our Permissions and Access Overview document: Explore how Momentum seamlessly integrates with your existing systems. ## Momentum Platform Installation Guide ### Step 1: Install the Momentum App in Slack or Microsoft Teams #### Step 1A: Install the Momentum App in Slack 1. Navigate to the Slack App Directory. 2. Search for "Momentum" and click on the app. 3. Click the "Add to Slack" button. 4. Follow the prompts to authorize Momentum within your Slack workspace. Pro-tip: you can directly navigate to this page to install our app: [https://api.momentum.io/slack/install](https://api.momentum.io/slack/install). #### Step 1B: Install the Momentum App in Microsoft Teams Please follow these instructions for [Integrating Microsoft Teams with Momentum AI](/momentum-ai-microsoft-teams-integration) ### Step 2: Install the Salesforce Managed Package 1. Install the Momentum package in your Salesforce instance using one of the URLs below: * [Production Instance installer](https://api.momentum.io/integration/salesforce/install) * [Sandbox Instance installer](https://api.momentum.io/integration/salesforce/install?sandbox=1) Make sure to select "Install for All Users" Momentum Package for Salesforce ### Step 3: Authorize Momentum in Salesforce #### Step 3A: Authorize Momentum in Salesforce (using Slack) 1. Open the Momentum app within Slack. 2. Click the "Authorize Salesforce" button within the app. 3. Sign in to your Salesforce account as an admin. 4. Follow the prompts to authorize Momentum's access to your Salesforce instance. Momentum Installation #### Step 3B: Authorize Momentum in Salesforce (using Microsoft Teams) 1. Open the Momentum admin dashboard [https://app.momentum.io](https://app.momentum.io) 2. Click the "Connect Salesforce" button at the top of the page Connect Salesforce 3. Sign in to your Salesforce account as an admin. 4. Follow the prompts to authorize Momentum's access to your Salesforce instance. ### Step 4: Provisioning Your Momentum Instance 1. Once authorization in Salesforce is complete, Momentum will automatically provision an instance for your organization. 2. Check your email inbox for a message containing your Momentum admin dashboard login credentials. 3. Navigate to the Momentum admin dashboard URL provided in the email. 4. Enter your credentials to log in. If you intend to use the Momentum Admin dashboard often, you should bookmark our admin dashboard's website: [https://app.momentum.io](https://app.momentum.io). Congratulations! You are now ready to leverage features like [deal rooms](/how-to-create-a-deal-room-and-manage-opportunities) and [scheduled notifications](/scheduled-notifications). To proceed with Momentum AI and the analysis of your team calls for data extraction, please continue to the next section of the installation guide. ## Setting Up Momentum AI for Call Recording and Analysis Momentum offers three flexible integration options for analyzing your team's calls, depending on your existing technology and preferences. ### 1. Momentum Bot Joining as an Attendee If you do not have native call recording or pre-existing call recording technology, Momentum can join your calls as an attendee. Momentum will join your calls as a note-taker, providing recording disclosure and automatically transcribing the conversation. This setup is simple, easy to implement, and suitable for both short-term and long-term use, leveraging your team's calendar to identify and join scheduled calls without requiring additional administrative privileges. Importantly, videos will not be stored anywhere; Momentum will only use its access to transcribe the calls and utilize the data for workflows and extractions. For detailed instructions, follow this guide: ### 2. Native Integration with Google Meet and Zoom This method leverages the native "record" features of Google Meet and Zoom, allowing Momentum to access and transcribe calls without joining as an attendee. To use this setup, you will need specific admin access to Google Meet and Zoom, as well as the appropriate licenses and storage capacity within these tools. Once enabled, Momentum can seamlessly integrate with these platforms, automatically accessing and transcribing recorded calls. This option provides a streamlined, integrated solution without needing additional bot participation. For detailed instructions, follow these guides: ### 3. Integration with Pre-Existing Call Recording Technology (Gong, Chorus, etc.) If your organization already uses call recording technologies like Gong or Chorus, Momentum can integrate directly with these platforms. This means Momentum can access recorded calls from your Gong or Chorus account without changing your existing recording workflow. The installation is minimal and straightforward, as long as you have admin access to Gong, Chorus, or similar platforms. This integration maximizes the use of your existing infrastructure and provides a robust solution for call recording and transcription. For detailed instructions, follow these guides: Congratulations, your setup is complete! ## Need More Help? If you encounter any issues not covered in this guide, don't hesitate to contact our support team at [support@momentum.io](mailto:support@momentum.io) for further assistance. We're here to help you get the most out of your Momentum experience. # How to manage your calls in the Momentum Webapp Source: https://docs.momentum.io/how-to-manage-your-calls-in-the-momentum-webapp Have complete control over your calls and recording settings in the Momentum Webapp! ##### Go to [app.momentum.io](https://app.momentum.io) ### 1. Introduction From accessing current calls to recording settings, this guide will walk you through the necessary steps for effective call management. ![Introduction][image1] ### 2. Today's calls Click on the Today's calls tab to review the external calls that have been synced from your Google calendar. ![Today's calls][image2] ### 3. Enable Recording On this page, you can select for calls to be recorded. ![Enable Recording][image3] ### 4. Confirm recording settings Confirm action ![Confirm recording settings][image4] ### 5. Skip Recording You can select to skip recording for calls that should not be recorded. ![Skip Recording][image5] ### 6. Confirm skip recording Confirm action ![Confirm skip recording][image6] ### 7. Record ongoing call You can record an ongoing call if you had an adhoc meeting start and your calendar was not synced ahead of time. ![Record ongoing call][image7] ### 8. Provide call details You will need to provide some details for Momentum to be able to identify the correct call to record and process. ![Provide call details][image8] ### 9. Post call actions After you have completed your external calls for the day, you can review your calls and manage them if necessary. ![Post call actions][image9] ### 10. Make Call Private If you need your call to be private to the rest of the organization, you can secure your call by selecting "Make Private" ![Make Call Private][image10] ### 11. Private call access This will ensure that only you and the attendees of the meeting will be able to view the call within the organization. ![Private call access][image11] ### 12. Deleting calls Remove unwanted calls, calls that have been recorded by mistake or by client request by clicking on "Delete". ![Deleting calls][image12] ### 13. Confirm deletion and field revert You will be prompted if you also would like to revert all Salesforce fields if the call has been analyzed and insights have been pushed directly in. ![Confirm deletion and field revert][image13] This guide covered essential steps in call management within the Momentum Webapp. We hope you found the video easy to follow. Thank you for choosing Momentum! [image1]: images/how-to-guides/how-to-manage-your-calls-in-the-momentum-webapp/image1.png [image2]: images/how-to-guides/how-to-manage-your-calls-in-the-momentum-webapp/image2.png [image3]: images/how-to-guides/how-to-manage-your-calls-in-the-momentum-webapp/image3.png [image4]: images/how-to-guides/how-to-manage-your-calls-in-the-momentum-webapp/image4.png [image5]: images/how-to-guides/how-to-manage-your-calls-in-the-momentum-webapp/image5.png [image6]: images/how-to-guides/how-to-manage-your-calls-in-the-momentum-webapp/image6.png [image7]: images/how-to-guides/how-to-manage-your-calls-in-the-momentum-webapp/image7.png [image8]: images/how-to-guides/how-to-manage-your-calls-in-the-momentum-webapp/image8.png [image9]: images/how-to-guides/how-to-manage-your-calls-in-the-momentum-webapp/image9.png [image10]: images/how-to-guides/how-to-manage-your-calls-in-the-momentum-webapp/image10.png [image11]: images/how-to-guides/how-to-manage-your-calls-in-the-momentum-webapp/image11.png [image12]: images/how-to-guides/how-to-manage-your-calls-in-the-momentum-webapp/image12.png [image13]: images/how-to-guides/how-to-manage-your-calls-in-the-momentum-webapp/image13.png # How to review your call in Momentum Webap Source: https://docs.momentum.io/how-to-review-your-call-in-momentum-webapp ##### Go to [app.momentum.io](https://app.momentum.io) ### 1. Introduction This guide will walk you through how to access your past call to rewatch it, review the transcript and add comments for your colleague's calls ![Introduction][image1] ### 2. Select a Call Start by selecting the call that you would like to review by clicking on the "View" option. ![Select a Call][image2] ### 3. Watching the video You can watch the video by clicking on play. ![Watching the video][image3] ### 4. Review Summary of call Select the "Summary" tab to read the key highlights of the call. ![Review Summary of call][image4] ### 5. Review Transcript of call Select the "Transcript" tab to read or follow along the conversation in the call. ![Review Transcript of call][image5] ### 6. Add a comment If you would like to add comments to a call for your colleague or yourself, you can click on the speech bubble icon. ![Add a comment][image6] ### 7. Write your comment A pop up window will appear for you to add comments. ![Write your comment][image7] ### 8. Submit your comment Once you are ready with your comments, you can click on the "Submit" button. ![Submit your comment][image8] ### 9. View comments You can review all comments provided on a call by clicking on the "Comments" tabs. ![View comments][image9] ### 10. Jump to a comment timestamp You can jump back to the specific point on the call by clicking on the timestamp. ![Jump to a comment timestamp][image10] The guide covered the steps to review a call in the Momentum Webapp. Thank you for choosing Momentum! [image1]: images/how-to-guides/how-to-review-your-call-in-momentum-webapp/image1.png [image2]: images/how-to-guides/how-to-review-your-call-in-momentum-webapp/image2.png [image3]: images/how-to-guides/how-to-review-your-call-in-momentum-webapp/image3.png [image4]: images/how-to-guides/how-to-review-your-call-in-momentum-webapp/image4.png [image5]: images/how-to-guides/how-to-review-your-call-in-momentum-webapp/image5.png [image6]: images/how-to-guides/how-to-review-your-call-in-momentum-webapp/image6.png [image7]: images/how-to-guides/how-to-review-your-call-in-momentum-webapp/image7.png [image8]: images/how-to-guides/how-to-review-your-call-in-momentum-webapp/image8.png [image9]: images/how-to-guides/how-to-review-your-call-in-momentum-webapp/image9.png [image10]: images/how-to-guides/how-to-review-your-call-in-momentum-webapp/image10.png # How to share a call in Momentum Webapp Source: https://docs.momentum.io/how-to-share-a-call-in-momentum-webapp Call sharing can be easy and painless with just a few little clicks. This guide will walk you through the steps of sharing a full call or generate a clip to share internally within your Organization or externally. ##### Go to [app.momentum.io](https://app.momentum.io) ### 1. Select the call Go to the appropriate tab to locate the call that you would like to share. Click "View" to view the call. ![Select the call][image1] ### 2. Access Share settings In the call summary screen, click on the "Share" button on the top right to select the settings for sharing the call ![Access Share settings][image2] ### 3. Sharing Full Video Select the "Full Video" tab if you are planning to share out the full video ![Sharing Full Video][image3] ### 4. Set link expiry (full video) Select from the drop down the link expiry for your shared call ![Set link expiry (full video)][image4] ### 5. Enable protected sharing (full video) Click on "Protected Sharing" if you would like to include a password for access to the link. ![Enable protected sharing (full video)][image5] ### 6. Set access code (full video) Input your desired access code for call protection. ![Set access code (full video)][image6] ### 7. Generate link to share Generate a shareable link by clicking the button. ![Generate link to share][image7] ### 8. Confirm link generation (full video) Confirm the link generation process. ![Confirm link generation (full video)][image8] ### 9. Copy share link (full video) A link will be generated. You can click on the "copy link" button to copy and share the link together with the access code. ![Copy share link (full video)][image9] ### 10. Disable share link (full video) If you have generated this by mistake or would like to change any of the settings, you can click on the "Disable shared link" to start again. ![Disable share link (full video)][image10] ### 11. Confirm disabling link (full video) Confirm the action to disable the shared link. ![Confirm disabling link (full video)][image11] ### 12. Share a clip If you would like to share a clip instead, go back to the top tab and select the "Share a clip" tab ![Share a clip][image12] ### 13. Adjust clip via timeline You can select the start and end of the clip by adjusting the front and end of the video timeline. ![Adjust clip via timeline][image13] ### 14. Adjust clip via timestamp You can also adjust the clip by using a specific start and end timestamp. ![Adjust clip via timestamp][image14] ### 15. Set link expiry (clip) Select from the drop down the link expiry for your shared call ![Set link expiry (clip)][image15] ### 16. Enable protected sharing (clip) Click on "Protected Sharing" if you would like to include a password for access to the link. ![Enable protected sharing (clip)][image16] ### 17. Set access code (clip) Input your desired access code for call protection. ![Set access code (clip)][image17] ### 18. Generate clip to share Generate a shareable clip by clicking the button. ![Generate clip to share][image18] ### 19. Confirm clip generation Confirm the clip generation process. ![Confirm clip generation][image19] ### 20. Copy share link (clip) A link will be generated. You can click on the "copy link" button to copy and share the link together with the access code. ![Copy share link (clip)][image20] ### 21. Disable or delete shared link If you have generated this by mistake or would like to change any of the settings, or select a different section of the video to make a clip you can click on the "Disable shared link" or "Delete clip" to start again. ![Disable or delete shared link][image21] ### 22. Confirm disable/delete (clip) Confirm the action to disable/delete the shared link or clip. ![Confirm disable/delete (clip)][image22] We hope you found this video simple to follow! Thank you for choosing Momentum! [image1]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image1.png [image2]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image2.png [image3]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image3.png [image4]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image4.png [image5]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image5.png [image6]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image6.png [image7]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image7.png [image8]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image8.png [image9]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image9.png [image10]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image10.png [image11]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image11.png [image12]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image12.png [image13]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image13.png [image14]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image14.png [image15]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image15.png [image16]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image16.png [image17]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image17.png [image18]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image18.png [image19]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image19.png [image20]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image20.png [image21]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image21.png [image22]: images/how-to-guides/how-to-share-a-call-in-momentum-webapp/image22.png # Ingest Meetings from Unsupported Sources Source: https://docs.momentum.io/ingesting-meetings-from-unsupported-sources If you use a meeting platform we don’t yet support natively, you can still bring those meetings into Momentum using the [user-provided-meeting endpoint](/api-reference/ingest-a-meeting-from-any-source). ## Prerequisite * Follow the steps in [API Access](/api-access) to obtain an API key, then include it as `X-API-Key` in requests. ## Support If you encounter issues, contact our support team: * Slack: Use your shared Momentum channel * Email: [support@momentum.io](mailto:support@momentum.io) # Installation without Call Recording Technology Source: https://docs.momentum.io/installation-without-call-recording-technology If you wish to use Momentum without integrating with specific video call technologies (such as Zoom, Google Meet, Gong, or Chorus), you can still benefit from its powerful insights and data analysis. This setup is ideal for teams that want to leverage Momentum's capabilities using recall. ## Assign AI License Seats To Your Team Members To add users to the AI license Seats setting in Momentum: 1. Log in to the Momentum Admin: Visit the [Momentum admin](https://app.momentum.io/admin/team) page and log in with your credentials 2. In the **Team** section, find or invite the users you'd like to assign AI licenses to 3. Click **Assign AI License** option in the users's record assign-ai-license-to-user ## Authorize Google Calendar Access For Each AI License User Momentum will need all AI license holders to connect their Google Calendars. When you grant them an AI license, please have your users click on the **Authorize Google Calendar** button delivered via Slack. This allows Momentum to read meeting data from calendars. Congratulations, your setup is complete! ## **Troubleshooting** If you have any questions or need assistance troubleshooting any issues, please contact our support team at [support@momentum.io](mailto:support@momentum.io). # Managing a Multi-Language and Cross-Cultural Team Source: https://docs.momentum.io/managing-a-multi-language-and-cross-cultural-team Utilize Momentum's AI capabilities to manage a multi-language and cross-cultural team effectively. Ensure better visibility, consistency, and global understanding of the pipeline for leadership by leveraging AI-driven insights and tools. ### Why Managing a Multi-Language and Cross-Cultural Team Matters In today's globalized world, sales teams often span multiple countries and languages. Managing such teams requires tools that can provide consistent and accurate visibility into the pipeline, regardless of language or cultural differences. AI-driven insights help bridge these gaps, ensuring that leadership has a comprehensive understanding of the sales pipeline, while maintaining consistency in communication and reporting across the team. ### Key Features for Managing a Multi-Language and Cross-Cultural Team 1. **AI Signals** * **Language Translation:** Automatically translate call insights and notes into multiple languages, ensuring that all team members and leadership can understand the critical information. * **Cultural Nuance Detection:** AI can detect and interpret cultural nuances in communication, providing more accurate and contextually relevant insights. * **Consistent Reporting:** Standardize the reporting format across different languages, providing a uniform view of the pipeline for leadership. [AI Signals](/ai-signals) 2. **Summaries** * **Multi-Language Summaries:** Generate call summaries in multiple languages, regardless of the original language of the call, making it easier for cross-cultural teams to access and understand the information. * **Global Visibility:** Ensure that leadership has visibility into all calls and interactions, regardless of the language spoken during the calls. * **Language-Aware Data Capture:** Momentum AI can listen to calls in any language and centralize the data captured into the CRM, translating it into English, or any other preferred language, for easy understanding and analysis. * **Focus on Key Insights:** Highlight critical insights such as customer sentiment, potential churn, and opportunities for expansion, with summaries tailored to different cultural contexts. [Summaries](/call-summaries) 3. **Autopilot** * **Consistent Data Capture:** Ensure that data is captured consistently across all languages and regions, maintaining high data quality and integrity. * **Context-Aware Prompts:** Adapt prompts based on the language and cultural context, ensuring relevant and accurate data capture. [Autopilot](/autopilot) ### Step-by-Step Guide to Managing a Multi-Language and Cross-Cultural Team 1. **Setting Up AI Signals** * Navigate to the AI Signals section in the Momentum admin dashboard. * Configure AI Signals to automatically translate call insights into the necessary languages. * Set up cultural nuance detection to provide contextually relevant insights. 2. **Implementing Multi-Language Summaries** * Go to the Summaries section in the Momentum admin dashboard. * Configure summaries to be generated in multiple languages, based on the participants of the call. * Ensure that summaries highlight key insights and are tailored to the cultural context of the team members. 3. **Using Autopilot for Consistent Data Capture** * Set up Autopilot with prompts that are contextually aware and adapted to different languages and regions. * Ensure that data is captured consistently across all team members, maintaining high data quality and integrity. ### Benefits of Managing a Multi-Language and Cross-Cultural Team * **Enhanced Global Visibility:** Provide leadership with a clear and comprehensive view of the global pipeline, regardless of language and cultural differences. * **Consistent Communication:** Standardize communication and reporting across different languages and regions, ensuring consistency and accuracy. * **Improved Collaboration:** Facilitate better collaboration among cross-cultural teams by providing translated and culturally relevant insights. * **Better Decision-Making:** Equip leadership with the necessary insights to make informed decisions, taking into account the performance and challenges of each region. * **Increased Efficiency:** Automate data capture and reporting processes, reducing the manual effort required to manage a multi-language and cross-cultural team. ### Customer Testimonial *“We did a Momentum trial after trying 3-4 other vendors, and our reps immediately fell in love with it. They said the call summaries were the best they'd seen.”* *“Momentum is able to do an accurate high-level summary for calls conducted in Chinese (Mandarin), covering most of the key points discussed. We're impressed by the translation and accuracy, especially by how Momentum can identify 'confusion from clients' and my response clarification.'"* — João Dias, Sr. Manager of Revops @ Yipit Data [Read the case study with YipitData →](https://www.momentum.io/customer/yipitdata) By leveraging Momentum's AI-driven tools, you can effectively manage a multi-language and cross-cultural team, ensuring better visibility, consistency, and global understanding of the pipeline for leadership. For further assistance or to discuss custom workflows, please contact our support team. ### Supported Languages Momentum supports the following languages for translation and insights: * Afrikaans * Albanian * Amharic * Arabic * Armenian * Assamese * Asturian * Azerbaijani * Bashkir * Basque * Belarusian * Bengali * Bosnian * Breton * Bulgarian * Burmese * Castilian * Catalan * Cebuano * Chinese * Croatian * Czech * Danish * Dutch * English * Estonian * Faroese * Finnish * Flemish * French * Western Frisian * Fulah * Gaelic * Galician * Ganda * Georgian * German * Greek * Gujarati * Haitian * Haitian Creole * Hausa * Hawaiian * Hebrew * Hindi * Hungarian * Icelandic * Igbo * Iloko * Indonesian * Irish * Italian * Japanese * Javanese * Kannada * Kazakh * Khmer * Korean * Lao * Latin * Latvian * Letzeburgesch * Lingala * Lithuanian * Luxembourgish * Macedonian * Malagasy * Malay * Malayalam * Maltese * Maori * Marathi * Moldavian * Moldovan * Mongolian * Myanmar * Nepali * Norwegian * Nynorsk * Occitan * Oriya * Panjabi * Pashto * Persian * Polish * Portuguese * Punjabi * Pushto * Romanian * Russian * Sanskrit * Serbian * Shona * Sindhi * Sinhala * Sinhalese * Slovak * Slovenian * Somali * Spanish * Sundanese * Swahili * Swati * Swedish * Tagalog * Tajik * Tamil * Tatar * Telugu * Thai * Tibetan * Tswana * Turkish * Turkmen * Ukrainian * Urdu * Uzbek * Valencian * Vietnamese * Welsh * Wolof * Xhosa * Yiddish * Yoruba * Zulu # Managing Contract Renewals Source: https://docs.momentum.io/managing-contract-renewals Proactively manage contract renewals and reduce last-minute scrambles with Notifications, Account Rooms, and Summaries. Keep your sales and customer success teams informed about upcoming renewals and ensure timely follow-ups. Maintain visibility for sales reps while allowing CSM and Customer Support teams to take over. Ensure seamless transitions and continuous engagement with detailed summaries focusing on customer sentiment and expansion/churn insights. ### Why Managing Contract Renewals Matters Effective management of contract renewals is essential for maintaining strong customer relationships, ensuring continuous revenue streams, and minimizing churn. Poor renewal processes can lead to missed expansions, last-minute rushes, and lost contracts. By proactively managing renewals with Momentum's features, you can ensure timely follow-ups, seamless handoffs, and continuous visibility for all relevant teams. ### Key Features for Managing Contract Renewals 1. **Salesforce Notifications with Scheduled Paths** * **Automated Reminders:** Set up notifications using our scheduled paths feature to alert your team about upcoming contract renewals well in advance. * **Customizable Alerts:** Configure notifications based on specific criteria, such as renewal dates, contract value, and customer tier, ensuring timely and relevant reminders. * **Consistent Follow-Ups:** Ensure no contract renewal is overlooked by automating the reminder process and keeping your team on track. [Salesforce Notifications](/salesforce-notifications) 2. **Account Rooms** * **Centralized Account Management:** Create dedicated Slack channels for each account, consolidating all relevant information, communications, and updates. * **Seamless Handoffs:** Transition management of accounts to CSM and Customer Support teams while keeping sales reps connected to deals with minimum overhead. * **Continuous Visibility:** Maintain total visibility for sales reps, ensuring they stay informed about account status and can re-engage when necessary. [Deal Rooms and Account Rooms](/how-to-create-a-deal-room-and-manage-opportunities) 3. **Summaries** * **Automated Note-Taking:** Summaries automatically generate detailed notes from customer interactions, saving time and ensuring comprehensive documentation. * **Custom Prompts:** Create custom prompts for summaries to refine CSM notes, focusing on customer sentiment, expansion opportunities, and churn risks. * **Informed Decision-Making:** Use insights from summaries to guide renewal discussions, identify upsell opportunities, and address potential churn early. [Summaries](/call-summaries) ### Step-by-Step Guide to Managing Contract Renewals 1. **Setting Up Notifications with Scheduled Paths** * Navigate to the Salesforce Notifications section in the Momentum admin dashboard. * Create a new notification for any new contract created or opportunity closed-won. * Establish one or many scheduled path delivery for this notification, based on the contract end date. * Customize the notification message to include relevant information and actionable instructions for your team. * Schedule the notifications to be sent at intervals (e.g., 30 days, 14 days, 7 days before the renewal date) to ensure timely follow-ups. 2. **Creating and Using Account Rooms** * Go to the Account Rooms section in the Momentum admin dashboard. * Create an Account Room for each key account, inviting relevant stakeholders from the Customer Success, Customer Support, and Sales teams. * Use Account Rooms to centralize all account-related information, making it easy for teams to access and update as needed. * Set up automated updates using AI Signals to keep Account Rooms informed about any significant changes or feedback from the customer. 3. **Utilizing Summaries in Account Rooms** * Navigate to the Summaries section in the Momentum admin dashboard. * Set up summary workflows to capture detailed notes from customer success calls. * Customize the summary prompt to focus on key success areas such as customer sentiment, expansion opportunities, and churn risks. * Deliver these summaries within Account Rooms to keep all stakeholders informed and aligned on the latest customer feedback and renewal status. 4. **Maintaining Continuous Engagement** * Ensure sales reps remain part of the Account Rooms to maintain visibility into the account status and potential upsell opportunities. * Use the data and insights gathered in Account Rooms and Summaries to inform and guide renewal discussions, ensuring that the customer feels valued and understood. * Regularly review the status of upcoming renewals and take proactive steps to address any potential issues before they become critical. ### Benefits of Managing Contract Renewals * **Reduced Last-Minute Scrambles:** Automated reminders ensure that renewals are managed proactively, reducing the risk of last-minute rushes. * **Improved Customer Satisfaction:** Timely follow-ups and well-managed renewals contribute to a positive customer experience, increasing satisfaction and loyalty. * **Seamless Transitions:** Account Rooms enable smooth handoffs between sales, CSM, and Customer Support teams, ensuring continuity and comprehensive account management. * **Enhanced Sales Visibility:** Sales reps stay connected to deals with minimal overhead, maintaining awareness of account status and opportunities for upselling or cross-selling. * **Increased Renewal Rates:** Proactive management and timely follow-ups lead to higher renewal rates, ensuring continuous revenue and customer retention. * **Focused Insights:** Custom prompts in summaries provide detailed insights into customer sentiment and potential churn risks, enabling informed decision-making. ### Customer Testimonial *“Momentum's ability to combine Salesforce automation with AI-generated recommendations for our CRM has enhanced productivity for all our revenue-generating teams across the board. We've been able to get more revenue out of each customer interaction thanks to the automated notifications we're able to send to our teams in Slack.”* — Austin Reece, Head of GTM Strategy Operation @ Rebuy Engine *** By leveraging Momentum's Notifications, Account Rooms, and Summaries, you can ensure proactive and efficient management of contract renewals, enhancing customer satisfaction and retention. For further assistance or to discuss custom workflows, please contact our support team. # Manually Invite Momentum Recording Bot to External Meetings Source: https://docs.momentum.io/manually-invite-momentum-bot ## Overview Some organizations restrict blanket recording of externally hosted calls due to privacy or consent policies. As a result, users may not have an AI seat assigned for customer-hosted calls. To address this, Momentum supports manual invitation of the recording bot to external meetings, bypassing the usual AI license checks. ## How It Works * **Admin Control:**\ In the Momentum AI Settings page, admins can toggle the Manually Invite Momentum Recording Bot setting. * **User Experience:**\ When enabled, users see an Invite button in the Call Library, allowing them to manually invite the Momentum bot to an ongoing external meeting. * **License Bypass:**\ If the setting is enabled, users can invite the bot even if they do not have an AI license for externally hosted meetings. ## Steps to Use **Admin Setup** PREREQUISITE : You must be at least an Organization Admin to have access to this setting. 1. Go to the Momentum AI Settings page in the Admin dashboard. 2. Toggle Manually Invite Momentum Recording Bot to enable manual invitations. Setting **User Action** 1. Navigate to the Call Library. 2. Click the Invite button. Invite Tab 3. Enter the meeting link, title, and participant email addresses. Invite Modal 4. Press Join Call and the Momentum bot will request to join your meeting. 5. Admit the Momentum bot to start recording and analyzing your meetings Meeting Screenshot # Integrating Aircall with Momentum AI Source: https://docs.momentum.io/momentum-ai-aircall-integration Momentum connects to your Aircall account to automatically ingest call recordings and metadata into Momentum's Call Library. These calls are processed like any other source in Momentum: summarized, analyzed, and made searchable. ## Prerequisites You'll need Aircall administrator access and a Momentum admin account. Ensure users exist in both systems with matching work emails. * Momentum workspace permissions to install and manage integrations. * Calls must have recordings available and accessible in Aircall. * Salesforce integration recommended: One of the following Aircall Salesforce packages should be installed for optimal call attribution: * Aircall for Sales Engagement (V4) – Recommended. Includes Aircall Voice custom object (`aircall2gp__Aircall_Voice__c`) for reliable call mapping. * Aircall CTI (V3) – Logs calls to Tasks with custom Aircall fields(`aircall__CallId__c`, `aircall__Call_Recording__c`). ## Aircall - Salesforce Configuration Proper Salesforce configuration ensures accurate mapping between Aircall calls and Salesforce records. ### For Aircall Sales Engagement (V4) Users The Sales Engagement package creates an Aircall Voice custom object (`aircall2gp__Aircall_Voice__c`) with direct lookup relationships to Contact, Lead, and Account records. **Required Setup:** 1. Install the Aircall for Sales Engagement package from AppExchange 2. Ensure Field-Level Security grants Read access to the Aircall Voice object and its relationship fields 3. Verify the package's Permission Set is assigned to relevant users ### For Aircall CTI (V3) Users The CTI package logs calls to standard Task records with custom Aircall fields. **Required Setup:** 1. Install the Aircall CTI package from AppExchange 2. Configure Field-Level Security for custom Task fields: * Navigate to **Setup → Permission Sets → \[Aircall Permission Set] → Object Settings → Task** * Enable **Read** and **Edit** access for: * `aircall__CallId__c` (Call ID) * `aircall__Call_Recording__c` (Call Recording) 3. Ensure the **Type** field is visible on the Task object (calls won't log if not configured) 4. Reference: [Aircall Field-Level Security Guide](https://support.aircall.io/en-gb/articles/10375396313885) ### Aircall Dashboard Settings (All Versions) 1. Go to **Integrations & API → Salesforce** in your Aircall Dashboard 2. Verify call logging is enabled for desired call types (inbound, outbound, missed) 3. Ensure call types are set to **"completed"** or **"in progress"** (not "do nothing") If call types are set to "do nothing", Tasks records won't be created in Salesforce, and Momentum won't be able to map calls to accounts. ## Generate your Aircall API Credentials 1. Sign in to your Aircall Dashboard with an administrator account. 2. Navigate to **Integrations & API**. 3. Select **API keys**. 4. Click **Generate an API key** (a popup window will appear). 5. Enter a key name and copy the **API ID** and **API Token**. Make sure to copy and store your API Credentials immediately after generation, as you won't be able to retrieve it later. aircall-generate-api-credentials ## Add API Credentials to Momentum 1. Copy the [generated API Credentials](#generate-your-aircall-api-credentials) from Aircall. 2. Switch to your Momentum admin dashboard. 3. Find the Aircall integration tile, paste the API ID and API Token and save. aircall-add-api-key-to-momentum.png Your integration is now successfully completed! ## Where to Find Calls * Open the Call Library in Momentum to browse and search Aircall calls. ## Assign AI License Seats To add users to the AI license seats setting in Momentum: 1. Log in to the [Momentum admin](https://app.momentum.io/admin/team) page. 2. In the Team section, invite or locate users to license. 3. Click **Assign AI License** for each user. 4. Enable **Aircall calls** to sync calls of the user. assign-ai-license-to-user aircall-assign-dialer-call-import-license ## Troubleshooting If you encounter issues, contact our support team: * Slack: Use your shared Momentum channel * Email: [support@momentum.io](mailto:support@momentum.io) ## FAQs You'll need to update the credentials in Momentum's integration settings to maintain the connection. By default, ingestion starts after connection. Contact Momentum support for historical backfill requests. Salesforce integration is strongly recommended. While calls are ingested directly from Aircall's API, Momentum uses Salesforce records (Tasks or Aircall Voice objects) to map calls to the correct accounts, contacts, and opportunities. Without Salesforce, calls will still appear in your Call Library but won't be attributed to CRM records. Check that your Aircall integration settings have call types set to "completed" or "in progress", and ensure the Type field is visible on the Task object. # Integrating Amazon Connect with Momentum AI Source: https://docs.momentum.io/momentum-ai-amazon-connect-integration Momentum connects directly to your Amazon Connect instance to automatically ingest call recordings and metadata into Momentum's Call Library. These calls are processed like any other source in Momentum: transcribed, summarized, analyzed, and made searchable. ## How the Integration Works Momentum integrates with Amazon Connect through **direct AWS access** to your Connect instance: * Momentum calls the Amazon Connect API (`SearchContacts` → `DescribeContact`) on a recurring schedule to discover new voice calls. * Recording audio is downloaded from your Connect **recording S3 bucket** using the AWS credentials you provide. * Transcripts are generated by Momentum from that audio. Momentum ingests Amazon Connect calls **directly from AWS** — not through Salesforce. If your Amazon Connect instance is wired to Salesforce via Salesforce Voice (Service Cloud Voice), see [Using Amazon Connect with Salesforce Voice](#using-amazon-connect-with-salesforce-voice-service-cloud-voice) below. ## Prerequisites You'll need AWS administrator (IAM) access to your Amazon Connect account and a Momentum admin account. Ensure your Amazon Connect agents have work emails that match their Momentum users. * An active AWS account with an Amazon Connect instance. * Call recording enabled on the instance, with an S3 bucket configured for recordings. * Admin access to AWS IAM to create a programmatic user and policy. * Momentum workspace permissions to install and manage integrations. ## Amazon Connect - AWS Configuration ### Step 1: Create an IAM User 1. Go to **AWS Console → IAM → Users → Create user**. 2. User name: `momentum-connect-integration` (or any descriptive name). 3. Do **not** enable console access — this user only needs programmatic access. 4. Click **Next**. ### Step 2: Attach a Read-Only Policy On the **Set permissions** page: 1. Select **Attach policies directly**. 2. Click **Create policy** (opens in a new tab). 3. Switch to the **JSON** tab and paste this policy: ```json theme={null} { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "connect:SearchContacts", "connect:DescribeContact", "connect:SearchUsers", "connect:GetContactAttributes", "connect:ListUsers", "connect:DescribeUser" ], "Resource": [ "arn:aws:connect:*:*:instance/YOUR_INSTANCE_ID", "arn:aws:connect:*:*:instance/YOUR_INSTANCE_ID/*" ] } ] } ``` 4. Replace `YOUR_INSTANCE_ID` with your Amazon Connect instance ID (see [Step 4](#step-4-find-your-instance-id-and-region)). 5. Name the policy `MomentumConnectReadOnly` and click **Create policy**. 6. Return to the **Create user** tab, refresh the policy list, attach `MomentumConnectReadOnly`, then click **Next → Create user**. This policy is **read-only** — Momentum cannot modify your Amazon Connect instance. ### Step 3: Generate Access Keys 1. Open the newly created user and go to the **Security credentials** tab. 2. Under **Access keys**, click **Create access key**. 3. Select **Third-party service** as the use case and acknowledge the notice. 4. Click **Create access key**. 5. **Save both values** — the secret key is only shown once: * **Access key ID** (starts with `AKIA...`) * **Secret access key** Store your access keys securely immediately after generation. The secret access key cannot be retrieved later. ### Step 4: Find Your Instance ID and Region 1. Go to **AWS Console → Amazon Connect** and click your instance alias. 2. The **Instance ID** appears in the URL: `https://console.aws.amazon.com/connect/home?region=us-east-1#/instance/INSTANCE_ID/overview` * Example: `12345678-1234-1234-1234-123456789012` 3. The **Region** is also in the URL (for example, `us-east-1`). The **Instance ARN** on the instance overview page contains both: `arn:aws:connect:us-east-1:123456789:instance/12345678-...` ### Step 5: Confirm Call Recording Is Enabled 1. Open your Amazon Connect instance and go to **Data storage** settings. 2. Verify that **Call recordings** is enabled with an S3 bucket configured. 3. In your **contact flows**, ensure a "Set recording and analytics behavior" block is included with **Agent and Customer** recording enabled. ## Add Credentials to Momentum 1. Log in to Momentum as an org admin and go to **Admin → Integrations**. 2. Find the **Amazon Connect** integration tile and enter: * **Access Key ID** — from [Step 3](#step-3-generate-access-keys) * **Secret Access Key** — from [Step 3](#step-3-generate-access-keys) * **Region** — from [Step 4](#step-4-find-your-instance-id-and-region) (for example, `us-east-1`) * **Instance ID** — from [Step 4](#step-4-find-your-instance-id-and-region) 3. Click **Save**. Your integration is now complete! ## Where to Find Calls Open the **Call Library** in Momentum to browse and search Amazon Connect calls. Calls typically appear within 15 minutes of completion. ## Assign AI License Seats To enable Amazon Connect call sync for users: 1. Log in to the [Momentum admin](https://app.momentum.io/admin/team) page. 2. In the **Team** section, invite or locate users to license. 3. Click **Assign AI License** for each user. 4. Enable **Amazon Connect calls** to sync that user's calls. assign-ai-license-to-user ## Using Amazon Connect with Salesforce Voice (Service Cloud Voice) If your Amazon Connect instance is connected to Salesforce through **Salesforce Voice (Service Cloud Voice / SCV)**, Momentum still ingests the calls **directly from Amazon Connect (API + S3)** — not through Salesforce. The SCV setup is fully supported, as long as Momentum has the direct AWS access described above. When SCV is in use, Momentum can *optionally* use the Salesforce **`VoiceCall`** object to improve CRM linking: * Momentum matches `VoiceCall.VendorCallKey` (the Amazon Connect contact ID) to resolve the related Contact, Lead, Account, or Case. * The matched `VoiceCall` record can also serve as the write-back target for Momentum's insights. * If no matching `VoiceCall` record is found, Momentum falls back to standard Salesforce Task and Contact matching. A configuration where call recordings are reachable **only** inside Salesforce (via SCV) — with no direct Amazon Connect API and S3 access — is **not supported**. Momentum must be able to read recordings directly from your Amazon Connect instance. ## Troubleshooting If you encounter issues, contact our support team: * Slack: Use your shared Momentum channel * Email: [support@momentum.io](mailto:support@momentum.io) ## FAQs Yes. Amazon Connect + Salesforce works, including when Amazon Connect is wired to Salesforce through Salesforce Voice (Service Cloud Voice). Momentum ingests the calls directly from Amazon Connect (API + the recording S3 bucket), and can optionally use the Salesforce `VoiceCall` object to sharpen CRM linking. Momentum does not ingest calls, recordings, or transcripts *through* Salesforce Voice, so direct AWS access is always required. No. Recording audio is always downloaded directly from your Amazon Connect S3 bucket using the AWS credentials you provide. Salesforce is used only for CRM linking and write-back, never as the source of the call or its recording. Yes. The `MomentumConnectReadOnly` IAM policy grants read-only Amazon Connect permissions. Momentum cannot modify your Amazon Connect instance. You can rotate or revoke the access keys at any time from AWS IAM. By default, ingestion starts after connection. Contact Momentum support for historical backfill requests. Create a new access key pair in AWS IAM, update the credentials in Momentum's Amazon Connect integration settings, then delete the old key pair. # Integrating Attention with Momentum AI Source: https://docs.momentum.io/momentum-ai-attention-integration Momentum AI integrates with Attention to give you seamless access to your team's calls. There's no need to change how your calls are recorded or reconfigure your video platforms. Momentum works with your existing setup. ## Connect Attention to Momentum To establish a connection between Attention and Momentum, you'll need to generate an API key from Attention and add it to your Momentum admin dashboard. ### Generate Your Attention API Key 1. Sign into your Attention account and navigate to **Settings**. 2. Locate the **API Access** section. 3. Click **Generate API Key** and follow the instructions. ### Add API Key to Momentum 1. Copy the generated API key from Attention. 2. Switch to your Momentum admin dashboard. 3. Find the Attention integration and paste the API key. Your integration is now successfully completed! ## Assign AI License Seats To Your Team Members To add users to the AI license seats setting in Momentum: 1. Visit the [Momentum admin](https://app.momentum.io/admin/team) page and log in with your credentials. 2. In the Team section, find or invite the users you'd like to assign AI licenses to. 3. Click **Assign AI License** in the user's record. assign-ai-license-to-user ## Troubleshooting Momentum's Attention integration requires two systems to communicate, and errors can occur in the event of miscommunication. For assistance troubleshooting Momentum's Attention integration, don't hesitate to contact our team via our shared Slack channel or at [support@momentum.io](mailto:support@momentum.io). # Integrating Chorus with Momentum AI Source: https://docs.momentum.io/momentum-ai-chorus-integration Momentum AI integrates with Chorus to give you seamless access to your team's calls. There's no need to change how your calls are recorded or reconfigure Zoom or other video platforms. Momentum works with your existing setup. ## Connect Chorus to Momentum To establish a connection between Chorus and Momentum, you'll need to generate an API key from Chorus and add it to your Momentum admin dashboard. ### Generate Your Chorus API Key 1. Sign into your Chorus account and navigate to **Settings**. 2. Go to the **Personal Settings** page. 3. Scroll down to the **API Access** section. 4. Click **Generate API token** and follow the instructions. chorus-generate-api-token ### Add API Key to Momentum 1. Copy the generated API key from Chorus. 2. Switch to your Momentum admin dashboard. 3. Find the Chorus integration and paste the API key. chorus-add-api-key-to-momentum.png Your integration is now successfully completed! **API Limitation:** The Chorus public API doesn't support downloading video recordings from calls. Momentum can only retrieve call metadata through the API. **Importing Video Recordings:** To download the recordings, Chorus requires a username and password instead of the API key. Please create a Chorus User (service account) and securely share the credentials with your Momentum Account Manager. **Required Permissions:** Ensure the service account has **"All recordings"** selected for **"Download Recording Content"** in Chorus recording permissions. chorus-recordings-permissions ## Data Access for All Your Teams Your teams must have access to data within Chorus to provide Momentum with access to all the right calls. This access allows you to determine which call recordings Momentum can analyze. To modify data access, follow these steps: 1. In Chorus, navigate to **Settings** and select **Teams and Data Access.** 2. If data access isn't already activated, click on **Activate Data Access**. 3. Scroll down and select the team whose access you want to change. 4. On the selected team's page, scroll down to the **Data Access** section. 5. Click on **Selected Teams** and make the necessary additions or removals. 6. Save your changes, and you're done! You can also manage a team's access to the **Manager's data** by selecting **Yes** or **No** in the **Data Access** section. ## Assign AI License Seats To Your Team Members To add users to the AI license seats setting in Momentum: 1. Visit the [Momentum admin](https://app.momentum.io/admin/team) page and log in with your credentials. 2. In the Team section, find or invite the users you'd like to assign AI licenses to. 3. Click **Assign AI License** in the user's record. assign-ai-license-to-user ## Troubleshooting Momentum's Chorus integration requires two systems to communicate, and errors can occur in the event of miscommunication. For assistance troubleshooting Momentum's Chorus integration, don't hesitate to contact our team via our shared Slack channel or at [support@momentum.io](mailto:support@momentum.io). # Integrating Clari Copilot with Momentum AI Source: https://docs.momentum.io/momentum-ai-clari-copilot-integration Momentum AI's integration with Clari Copilot simplifies accessing your team's calls. With this integration, Momentum will access all calls in your Clari Copilot without altering how your team's calls are recorded or reconfigure Zoom or other video callers to incorporate Momentum. ## Connect Clari Copilot to Momentum To establish a connection between Clari Copilot and Momentum, you’ll need an organization administrator to generate an API key and password from Clari Copilot and add it to your Momentum admin dashboard. ### Generate Your Clari Copilot API Key and API Password 1. Sign into your Clari Copilot console. 2. Navigate to **Workspace Settings → Integrations → Clari Copilot API** (sometimes listed under "Others"). 3. Click "Generate" to obtain your API Key and API Password. ### Add API Key and API Password to Momentum 1. Copy the generated API Key and API Password from Clari Copilot. 2. Switch to your Momentum admin integrations dashboard and find the Clari Copilot integration. 3. Paste your API Key and API Password and click on "Save". clari-copilot-add-api-key-to-momentum Only one API Key may be used for this integration per organization. If the Clari integration is already connected, you may delete the API Key to disconnect the integration at any time. ## Assign AI License Seats To Your Team Members To add users to the AI license Seats setting in Momentum: 1. Log in to the Momentum Admin: Visit the [Momentum admin](https://app.momentum.io/admin/team) page and log in with your credentials 2. In the Team section, find or invite the users you'd like to assign AI licenses to 3. Click Assign AI License option in the users's record assign-ai-license-to-user ## Troubleshooting Momentum's Clari Copilot integration requires two systems to communicate, and errors can occur in the event of miscommunication. For assistance troubleshooting Momentum's Clari Copilot integration, don't hesitate to contact our team via our shared Slack channel or at [support@momentum.io](mailto:support@momentum.io). # Integrating CloudTalk with Momentum AI Source: https://docs.momentum.io/momentum-ai-cloudtalk-integration Momentum AI's integration with CloudTalk enables you to automatically capture and analyze your CloudTalk calls directly within the Momentum platform. Once connected, all your CloudTalk conversations will be available for playback and can be processed through Momentum's AI workflows—including automated coaching insights, action item extraction, and CRM updates. ## Generate Your CloudTalk API Credentials Copy Your CloudTalk API ID and Key 1. Sign in to the CloudTalk Dashboard with an administrator account. 2. In the left navigation, go to **Account → Settings → API Keys**. 3. Click **Add API Key**. 4. Copy the generated **API ID** and **API Key**. ## Connect CloudTalk in Momentum In your Momentum dashboard, you can find CloudTalk and paste the previously copied API Id and Key. cloudtalk-add-api-key-to-momentum.png That's all! Your integration is now successfully completed. ## Ensure CloudTalk Call Access In CloudTalk, head to **Account → Settings → General → Visibility of calls and recordings** and confirm recording is enabled for all calls you want Momentum to analyze. ## Assign AI License Seats To Your Team Members To add users to the AI license Seats setting in Momentum: 1. Log in to the Momentum Admin: Visit the [Momentum admin](https://app.momentum.io/admin/team) page and log in with your credentials 2. In the Team section, find or invite the users you'd like to assign AI licenses to 3. Click Assign AI License option in the users's record 4. Enable **CloudTalk calls** to sync calls of the user. assign-ai-license-to-user cloudtalk-assign-dialer-call-import-license ## Troubleshooting Momentum's CloudTalk Integration requires two systems to communicate, and errors can occur in the event of miscommunication. For assistance troubleshooting Momentum's CloudTalk Integration, don't hesitate to contact our team via our shared Slack channel or at [support@momentum.io](mailto:support@momentum.io). # Integrating Dialpad with Momentum AI Source: https://docs.momentum.io/momentum-ai-dialpad-integration Momentum connects to your Dialpad account to automatically ingest call recordings and metadata into Momentum's Call Library. These calls are processed like any other source in Momentum: summarized, analyzed, and made searchable. ## Prerequisites You'll need Dialpad administrator access and a Momentum admin account. Ensure users exist in both systems with matching work emails. * Momentum workspace permissions to install and manage integrations. * Calls must have recordings enabled in Dialpad. * **Dialpad plan requirements**: API access is typically available on Dialpad Pro or Enterprise plans. ## Dialpad Configuration ### Required API Scopes Your Dialpad API key must have the following additional scopes enabled: | Scope | Purpose | | ------------------- | --------------------------------------------------- | | `Recordings export` | Required. Access to download call recordings | | `List calls` | Required. Access to retrieve call data and metadata | If the required scopes are not enabled, Momentum will not be able to retrieve call data or recordings. ### Enable Automatic Call Recording Ensure that **Automatic Call Recording** is turned on in Dialpad Office Settings for all users whose calls should be synced to Momentum. 1. In Dialpad Admin Portal, navigate to **Office Settings** 2. Enable **Automatic Call Recording** for desired users. ## Generate your Dialpad API Key 1. Sign in to your Dialpad Admin Portal with an administrator account. 2. Navigate to **Admin Settings → My Company → Authentication → API Keys**. 3. Click **Add Key**. 4. Select the [required additional scopes](#required-api-scopes): * **Recordings export** * **List calls** 5. Click **Save**, then copy the **API Key**. Store your API key securely immediately after generation. You may not be able to view it again after leaving the page. ## Add API Key to Momentum 1. Copy the generated API key from Dialpad. 2. Switch to your Momentum admin dashboard. 3. Find the Dialpad integration tile and paste the **API Key**. dialpad-add-api-key-to-momentum.png Your integration is now complete! ## Where to Find Calls Open the **Call Library** in Momentum to browse and search Dialpad calls. ## Assign AI License Seats To enable Dialpad call sync for users: 1. Log in to the [Momentum admin](https://app.momentum.io/admin/team) page. 2. In the **Team** section, invite or locate users to license. 3. Click **Assign AI License** for each user. 4. Enable **Dialpad calls** to sync that user's calls. assign-ai-license-to-user dialpad-assign-dialer-call-import-license ## Troubleshooting * Calls may be missing if: * Automatic Call Recording is not enabled for that user. * The call does not have external contact information associated with it. * The API key is missing the required scopes (`Recordings export`, `List calls`). * Allow up to 15 minutes for the next sync cycle. If you encounter issues, contact our support team: * Slack: Use your shared Momentum channel * Email: [support@momentum.io](mailto:support@momentum.io) ## FAQs By default, ingestion starts after connection. Contact Momentum support for historical backfill requests. Every 15 minutes, subject to Dialpad API rate limits. You'll need to update the API key in Momentum's integration settings to maintain the connection. API access is typically available on Dialpad Pro and Enterprise plans. Contact Dialpad support to confirm API availability for your specific plan. # Integrating Gong with Momentum AI Source: https://docs.momentum.io/momentum-ai-gong-integration Momentum AI's integration with Gong simplifies accessing your team's Gong calls. With a single click in our official Gong app, you can integrate Momentum with Gong and enable immediate transcription. There's no need to alter how your team's calls are recorded, or reconfigure Zoom or other video callers to incorporate Momentum. ## Authorize Momentum in Gong.io The steps are very simple. From any Slack channel, as an administrator, type `*/configure*` in Slack to display the "**Configure Integrations with Momentum**" command. That will open Momentum Integrations Slack menu. configure-integrations Click on "Authorize" to open a new browser tab. This will allow you to complete the authentication flow on [Gong.io](http://gong.io/). gong-authorize-integration Please note that you need to be at least **Gong Technical Administrator** to authorize Momentum access to your account. To find out the **Gong Technical Administrator,** you can go to [**https://app.gong.io/my-settings**](https://app.gong.io/my-settings) as shown: gong-settings ## Assign AI License Seats To Your Team Members To add users to the AI license Seats setting in Momentum: 1. Log in to the Momentum Admin: Visit the [Momentum admin](https://app.momentum.io/admin/team) page and log in with your credentials 2. In the Team section, find or invite the users you'd like to assign AI licenses to 3. Click Assign AI License option in the users's record assign-ai-license-to-user ## Troubleshooting Momentum's Gong Integration requires two systems to communicate, and errors can occur in the event of miscommunication. For assistance troubleshooting Momentum's Gong Integration, don't hesitate to contact our team via our shared Slack channel or at [support@momentum.io](mailto:support@momentum.io). # Integrating Google Meet with Momentum AI Source: https://docs.momentum.io/momentum-ai-google-meet-integration Momentum AI's integration with Google Meet ensures seamless transcription and recording of your sales calls, transforming them into actionable data within your CRM. The Momentum bot will join your Google Meet calls so please ensure that your team allows the bot to join calls to ensure the recording happens. ## Assign AI License Seats To Your Team Members Once our support team confirms that your account is configured to pick up your Google Meet calls, we'll need you to add users to the AI license Seats setting in Momentum: 1. Log in to the Momentum Admin: Visit the [Momentum admin](https://app.momentum.io/admin/team) page and log in with your credentials 2. In the Team section, find or invite the users you'd like to assign AI licenses to 3. Click Assign AI License option in the users's record assign-ai-license-to-user ## Authorize Salesforce Access For Each AI License User Momentum will need all AI license holders to connect their Salesforce account. When you grant them an AI license, they will receive a Slack notification from Momentum with a message. Please have your users click on the 'Authorize Salesforce' button delivered via Slack. This allows Momentum to write into Salesforce on their behalf. ## Authorize Google Calendar Access For Each AI License User Momentum will also need all AI license holders to connect their Google Calendars. Please have your users click on the Authorize Google Calendar button delivered via Slack. This allows Momentum to read meeting data from calendars. **Important**: When authenticating with Google Calendar, ensure that the box that allows Momentum to see, edit, and share is checked. This allows Momentum to record calls and call participant information accurately. Next, check the box to grant access to see, edit, create, and delete Google Drive files. This allows Momentum to save transcripts from calls. google-momentum-access-permissions ## Troubleshooting Momentum's Google Meet Integration requires two systems to communicate, and errors can occur in the event of miscommunication. For assistance troubleshooting Momentum's Google Meet Integration, don't hesitate to contact our team via our shared Slack channel or at [support@momentum.io](mailto:support@momentum.io). # Integrating Microsoft Outlook with Momentum AI Source: https://docs.momentum.io/momentum-ai-microsoft-outlook-integration Momentum AI now supports Outlook. This early **beta release** enables automatic recording of external meetings for Outlook users just like with Google Calendar. ## Enable Outlook Support Outlook integration is currently available only to select organizations as part of our beta release. Please contact Momentum support if you would like access to the Outlook integration. ## Assign AI License Seats To Your Team Members Once your organization is approved for the Outlook beta release, we'll need you to add users to the AI license Seats setting in Momentum: 1. Log in to the [Momentum admin](https://app.momentum.io/admin/team) page and log in with your credentials 2. In the Team section, find or invite the users you’d like to assign AI licenses to 3. Click Assign AI License option in the user’s record assign-ai-license-to-user ## Connect Outlook Each Outlook user must authorize Momentum to read their calendar. From any Slack channel, type `/configure` and click **Authorize** for Outlook. This initiates an OAuth2 flow with Microsoft Graph and allows Momentum to: * Sync external-facing meetings every 2 minutes. * Capture all relevant meeting information for processing and recording. * Flag imported meetings for automatic recording. microsoft-outlook-access-permissions Users can return to `/configure` at any time to disconnect their Outlook if needed. ## Troubleshooting Because this integration is in beta, we’re still validating functionality and appreciate your feedback. If you run into issues or have questions, reach out to our team via your shared Slack channel or at [support@momentum.io](mailto:support@momentum.io). # Integrating Microsoft Teams with Momentum AI Source: https://docs.momentum.io/momentum-ai-microsoft-teams-integration ## Installing Momentum for Teams Only users with an email address in Active Directory/Microsoft Entra will be imported. The email address is used to match this user with accounts in other platforms such as Salesforce ### 1. Login in Momentum Connect the Microsoft Teams integration by navigating to the [My Integrations](https://app.momentum.io/my-integrations) screen and sign in to the Microsoft Teams integration. A user must take this step before installing our app in Teams The top of the Integrations page with two tabs: Connected and Browse Integrations. The Browse Integrations tab is selected A card depicting the Microsoft Teams logo and title. There is also a blue button with the title Sign in Depending on your organization’s settings in Microsoft Entra, you may be required to request permission to authorize Momentum. After receiving approval, you may be required to repeat this sign in step again. Once your login is completed, the Momentum App will be submitted to your organizations Teams App Marketplace. You will need a Teams Administrator to approve the app before installing it in your team ### 2. Approve the Momentum App You will need your Teams Administrator to complete this step. In the Teams Admin Center, navigate to **Teams apps > Manage apps** A portion of the sidebar navigation menu from the Teams admin console. The section Teams apps is open and the sub-menu item Manage apps is selected Search for `momentum` in the list of apps and open the application. On the main screen, click **Publish**. A section of the Manage apps screen with the All apps tab selected. The search bar contains the keyword Momentum and the Momentum app is the first item in the list. Once the app has been published, you will need to Grant Admin Consent. Navigate to the **Permissions** tab and click **Grant admin consent** in the yellow bar that appears Click on the Momentum app Click on the **Permissions** tab Under **Required Permissions** click **Grant admin consent** A page section with a row of tabs. The Permissions tab is selected. The section below is named Required permissions. This lists the permissions required to install Momentum as well as a call to action asking the user to Grant Admin consent Sign in and accept the requested permissions ### 3. Enable Direct Messaging Momentum must be installed for each user that will receive direct messages from the Momentum bot. Continuing from the previous step, select the **Users and Groups** tab Click on **Install App** or **Edit installs** users and groups tab detail the edit installs button will appear if the app is already installed for some users Select which users or groups you want to enable Momentum for, or enable for all users and click **Apply** edit installs detail ### 4A. Install Momentum as a Teams Admin For instructions on how to add Momentum to a Team as a Team Owner, proceed to [step 3B](#3b-install-momentum-as-a-team-owner) below Return to **Teams apps > Manage apps** Search for the Momentum app again and click on the checkbox to the left of it A list of applications including the Momentum app. The checkbox to the left of Momentum is selected Click **Add to team** Select which teams you’d like to install Momentum. You’ll need to repeat this step for each team. Team owners may also add Momentum through the Teams interface A page section titled "Add to a team". There is a search bar with the contents "team" and two search results, one named team2 and the other named team. Each result includes an Add button Once installed, the Momentum bot will post a message to the General channel of each installed Team Message posted to the Teams channel after a successful installation. The message is authored by the Momentum bot and reads "Momentum bot has been installed and is now syncing your data" ### 4B. Install Momentum as a Team Owner Once the Momentum Teams app has been approved by your administrator, any Team Owner can add Momentum to their Team. In the Chat tab, find the team you’d like to add Momentum to. In this example we’ll be adding this to Demo Team. A sidebar tab from the Teams user interface. There is a chat bubble with the label Chat below it Mouse over the team you want to configure and click on the three dot menu A list of Teams and channels with the Team named Demo Team selected. The accessory menu control is visible Select **Manage team** The expanded accessory menu for the selected Team. The menu item Manage team is highlighted Select the **Apps** tab. The manage Team screen for a team named Demo Team, as it appears on a larger screen. The Apps tab is highlighted On smaller screens, this may be a menu below the team name The manage Team screen for a team named Demo Team, as it appears on a smaller screen. The menu below the team name is expanded and the Apps menu item is selected On the Apps screen, click **+ Get more apps**. Momentum should appear in the **Built for your org** section. If it doesn’t appear there, you may need to click **See all** A page section named Built for your org. The Momentum app is present and includes a button with the label Open Click **Add** or **Open** You may be prompted to select a channel, this will set the first channel for messages to appear A modal dialog showing the Momentum logo and name. There is a search bar below allowing the user to search for a channel and one channel below named All Call Summaries Select a channel and click **Go** After a few seconds, Momentum will post a message to your channel confirming installation Message posted to the Teams channel after a successful installation. The message is authored by the Momentum bot and reads "Momentum bot has been installed and is now syncing your data" ## Required Permissions The Momentum Teams integration is in early preview and permissions listed below may be subject to change. Users may need to reauthorize to add or remove permissions as they change Permissions for Momentum are required to be approved in two places: Microsoft Entra Admin Enterprise Apps and Teams Admin Application permissions * `Channel.ReadBasic.All` - read lists of channels, so that admins may select a channel as a destination for notifications * `ChannelMessage.Send.Group` - post notifications to channels and messages * `Team.ReadBasic.All` - read lists of teams and their channels * `TeamMember.Read.All` * `TeamMember.Read.Group` * `User.Read.All` - read user details, including email addresses. Email addresses are used to correlate users across systems such as Zoom, Salesforce, etc. Delegated permissions * `AppCatalog.Submit` - upload the Momentum app to your Team * `Files.ReadWrite.All` - upload and attach files (e.g. video clips) to messages * `offline_access` - access the Microsoft Graph API to periodically synchronize lists of users and channels, post messages at any time # Integrating Orum with Momentum AI Source: https://docs.momentum.io/momentum-ai-orum-integration Momentum connects to your Orum account via webhooks to automatically ingest call recordings and metadata into Momentum's Call Library. These calls are processed like any other source in Momentum: summarized, analyzed, and made searchable. ## Prerequisites You'll need Orum administrator access and a Momentum admin account. Ensure users exist in both systems with matching work emails. * **Orum Webhooks add-on**: Your Orum plan must include the Webhooks add-on feature. This is required for the integration to work. [View Orum plan details](https://www.orum.com/pricing) to confirm your plan includes webhooks. * Momentum workspace permissions to install and manage integrations If you don't have the Webhooks add-on in your Orum plan, contact your Orum account representative to enable this feature before proceeding with the integration setup. ## Connect Orum to Momentum ### Step 1: Get Your Webhook Signing Key from Orum 1. Sign in to your Orum Admin Portal 2. Navigate to **Settings → System → Webhooks** 3. Locate or create your **Webhook Signing Key** 4. Copy the signing key value The webhook signing key is used to verify that webhook requests are genuinely from Orum. Keep this key secure and never share it publicly. ### Step 2: Add the Signing Key in Momentum 1. Log in to the [Momentum Admin Portal](https://app.momentum.io/admin) 2. Navigate to **Integrations** 3. Find **Orum** and click **Secret Keys** 4. Enter your webhook signing key and **Save** Once saved, Contact Momentum support who will provide you with a unique **Webhook URL** for your organization. Orum Secret Key Configuration ### Step 3: Configure Webhook URL in Orum 1. Return to your Orum Admin Portal 2. Navigate to **Settings → System → Webhooks** 3. Add a new webhook with the following settings: * **URL**: *(the webhook URL provided by Momentum)* 4. Save the webhook configuration 5. Optional: Use Orum's **Test** button to send a test event Orum's test events do not include the webhook signature header that Momentum uses to verify authenticity. As a result, test events will return an **Unauthorized** error. This is expected and does not indicate a problem with your configuration. To confirm the integration is working, make a real call in Orum. Your integration is now complete! ## Assign AI License Seats To enable Orum call sync for specific users: 1. Log in to the [Momentum admin](https://app.momentum.io/admin/team) page. 2. In the **Team** section, invite or locate users to license. 3. Click **Assign AI License** for each user. 4. Enable **Orum calls** to sync that user's calls. assign-ai-license-to-user orum-assign-dialer-call-import-license ## Troubleshooting * Calls may be missing if: * The webhook URL is not set correctly in Orum. Verify the URL in **Settings → System → Webhooks**. * The signing key in Momentum does not match the key configured in Orum. Re-enter the key in both systems. * The call event does not have prospect information(name or phone number) associated with it. * Calls are below the minimum duration threshold * Calls do not have recording links If you encounter issues, contact our support team: * Slack: Use your shared Momentum channel * Email: [support@momentum.io](mailto:support@momentum.io) ## FAQs Yes. Orum sends webhook events immediately once a call is ended. Calls typically appear in Momentum within a few minutes of completion. No. Orum's webhook integration only captures calls going forward from the time the webhook is configured. Calls without recordings, calls below the minimum duration threshold, and calls missing prospect details (no name or phone number) are automatically excluded. # Integrating Outreach with Momentum AI Source: https://docs.momentum.io/momentum-ai-outreach-integration Momentum connects to your Outreach account to automatically ingest call recordings and metadata into Momentum's Call Library. These calls are processed like any other source in Momentum: summarized, analyzed, and made searchable. ## Prerequisites You'll need Outreach administrator access and a Momentum admin account. Ensure users exist in both systems with matching work emails. * Momentum workspace permissions to install and manage integrations. * Outreach Voice enabled: Your Outreach account must have Voice/Dialer functionality enabled. ## Outreach Configuration ### Enable Call Recording To ensure Momentum can access your call recordings: 1. Sign in to your Outreach Admin Portal 2. Navigate to **Administration → Org Info → Voice** 3. Enable call recording for the desired users or teams 4. Ensure users have the appropriate voice recording permissions Only calls with recordings will be imported into Momentum. Calls without recordings, or calls in "ringing", "no\_answer", or "canceled" states are automatically excluded. ### Salesforce Sync for Prospects For optimal call attribution in Momentum, ensure your Outreach prospects are synced from Salesforce: * In Outreach, navigate to Administration → Integrations → CRM * Select your Salesforce integration * Verify that prospect sync is enabled ## Connect Outreach to Momentum Outreach uses OAuth 2.0 authentication. To connect: **From the Momentum web app:** 1. Click on your profile icon and select **Integrations**. 2. Find the Outreach integration from **Browse integrations** and click **Sign in**. **From Slack:** 1. Type `/configure` to open Momentum's Integrations menu. 2. Find the Outreach integration and click **Authorize**. **Complete the authorization:** 1. You'll be redirected to Outreach to authorize the connection. 2. Sign in with your Outreach account. 3. Review and approve the requested permissions. 4. When connected, the status will show as **Connected**. Your integration is now complete! Momentum requests read-only access to your Outreach calls, prospects, and users. No data is written back to Outreach. ## Where to Find Calls Open the **Call Library** in Momentum to browse and search Outreach calls. ## Assign AI License Seats To enable Outreach call sync for users: 1. Log in to the [Momentum admin](https://app.momentum.io/admin/team) page. 2. In the **Team** section, invite or locate users to license. 3. Click **Assign AI License** for each user. 4. Enable **Outreach calls** to sync that user's calls. assign-ai-license-to-user outreach-assign-dialer-call-import-license ## Troubleshooting * Calls may be missing if: * Call recording is not enabled for that user * The call state is "ringing", "no\_answer", or "canceled". * The call has no associated prospect * Allow up to 15 minutes for the next sync cycle. If you encounter issues, contact our support team: * Slack: Use your shared Momentum channel * Email: [support@momentum.io](mailto:support@momentum.io) ## FAQs By default, ingestion starts after connection. Contact Momentum support for historical backfill requests. Every 15 minutes. # Integrating RingCentral with Momentum AI Source: https://docs.momentum.io/momentum-ai-ringcentral-integration Momentum connects to your RingCentral account to automatically ingest call recordings and metadata into Momentum's Call Library. These calls are processed like any other source in Momentum: summarized, analyzed, and made searchable. ## Prerequisites You'll need RingCentral Super Admin access and a Momentum admin account. Ensure users exist in both systems with matching work emails. * Momentum workspace permissions to install and manage integrations. * **RingCentral plan requirements**: RingEX Advanced or higher is recommended. * **Super Admin authorization**: A RingCentral Super Admin must authorize the connection in Momentum to access company-wide call logs. * [RingCentral for Salesforce](#salesforce-integration) package installed in Salesforce with auto call logging enabled. * Calls must have automatic call recording enabled in RingCentral. ## RingCentral Configuration ### Enable Automatic Call Recording To ensure Momentum can access your call recordings: 1. Sign in to the [RingCentral Admin Portal](https://service.ringcentral.com/) with administrator credentials 2. Navigate to **Phone System** tab 3. Depending on your company settings layout: * **If New company settings layout is OFF:** * Navigate to **Auto-Receptionist → General Settings → Call Recording** * Toggle **Enable Automatic Call Recording** on * **If New company settings layout is ON:** * Navigate to **Company → Company Call Handling → Call recording** * Toggle **Enable Automatic Call Recording** on 4. Click **Save** The authorized user must be a **Super Admin** in RingCentral to access company-wide call logs. Momentum calls the `/account/~/call-log` endpoint, which requires the `ReadCompanyCallLog` user permission that only Super Admins have. ## Salesforce Add-on: RingCentral Package When you're using RingCentral for Salesforce add-on, ensure proper setup for optimal call attribution: ### Prerequisites * RingCentral for Salesforce is available for **RingEX Advanced and Ultra** customers * [Install the RingCentral for Salesforce package](https://www.ringcentral.com/apps/salesforce) ### Setup Steps 1. Install the RingCentral for Salesforce package 2. Enable auto-logging calls as Tasks in Salesforce 3. Verify Task page layout: * Ensure RingCentral custom fields are visible: **CALL\_UNIQUE\_ID**`(rcsfl__CALL_UNIQUE_ID__c)` and **Call Recording**`(rcsfl__Call_Recording__c)` * Adjust field-level security for all RingCentral users if needed ### Resources * [Admin Guide (PDF)](https://assets.ringcentral.com/us/guide/rc-sfdc-admin-guide.pdf) * [RingCentral Integrations Portal](https://integrations.ringcentral.com/) - To check your connection status ## Connect RingCentral to Momentum RingCentral uses OAuth 2.0 authentication. To connect: **From the Momentum web app:** 1. Click on your profile icon and select **Integrations**. 2. Find the RingCentral integration from **Browse integrations** and click **Sign in**. **From Slack:** 1. Type `/configure` to open Momentum's Integrations menu. 2. Find the RingCentral integration and click **Authorize**. **Complete the authorization:** 1. You'll be redirected to RingCentral to authorize the connection. 2. Sign in with your RingCentral Super Admin account. 3. Review and approve the requested permissions (`ReadCallLog`, `ReadCallRecording`, `ReadAccounts`). 4. When connected, the status will show as **Connected**. Your integration is now complete! Momentum requests read-only access to your RingCentral call logs and recordings. No data is written back to RingCentral. ## Where to Find Calls Open the **Call Library** in Momentum to browse and search RingCentral calls. ## Assign AI License Seats To enable RingCentral call sync for users: 1. Log in to the [Momentum admin](https://app.momentum.io/admin/team) page. 2. In the **Team** section, invite or locate users to license. 3. Click **Assign AI License** for each user. 4. Enable **RingCentral calls** to sync that user's calls. assign-ai-license-to-user ringcentral-assign-dialer-call-import-license ## Troubleshooting * Calls not appearing: * Authorizing user must be a Super Admin in RingCentral (for company-wide call log access) * Automatic call recording not enabled: Enable via Admin Portal ([see steps above](#enable-automatic-call-recording)) * Check that your RingCentral plan is RingEX Advanced or higher If you encounter issues, contact our support team: * Slack: Use your shared Momentum channel * Email: [support@momentum.io](mailto:support@momentum.io) ## FAQs Simply follow the connection steps again. Your existing call history in Momentum will remain intact. RingEX Advanced and Ultra plans include full API access. RingEX Core may have limited recording capabilities and is not recommended. RingCentral's API permission model requires **Super Admin** privileges to access company-wide call logs. Momentum calls the `/account/~/call-log` endpoint to retrieve call data across your entire organization, which requires the `ReadCompanyCallLog` user permission. Only users with the **Super Admin** role have this permission. Regular users can only access their own call logs, which would not provide Momentum with visibility into all organizational calls. Momentum supports RingCentral **RingEX**. Most RingCX customers can also connect because RingCX is typically deployed alongside RingEX. However, contact-center-specific features are **not** currently supported (queue-level analytics, contact-center routing, agent performance metrics, supervisor workflows, omnichannel interactions). # Integrating Salesloft Conversation Intelligence with Momentum AI Source: https://docs.momentum.io/momentum-ai-salesloft-ci-integration Momentum AI's Salesloft integration also supports Salesloft Conversation Intelligence(CI). With this integration, you can allow Momentum to access all your Salesloft Conversations, including video recordings. There's no need to alter how your team's calls are recorded or reconfigure Zoom or other video callers to incorporate Momentum. ## Prerequisites You'll need Salesloft administrator access and a Momentum admin account. Ensure users exist in both systems with matching work emails. * Salesloft account with API access to Conversations and recordings (where applicable). * Momentum workspace permissions to install and manage integrations. ## Connect Salesloft 1. In Slack, type `/configure` to open Momentum's Integrations menu. 2. Select Salesloft and click **Authorize**. 3. Sign in to Salesloft and approve the requested scopes. 4. When connected, the status will show as Active. If your organization restricts app installs, your Salesloft admin may need to approve the Momentum app. ## What Gets Synced * Source: Salesloft Conversations ([API docs](https://developers.salesloft.com/docs/api/conversations-find-all/)) * Frequency: every 15 minutes * Content: call recording (if available) and metadata (e.g., call ID, timestamps, user/owner, and related references) ## Where to Find Calls * Open the Call Library in Momentum to browse, search, and play Salesloft CI calls. * Standard processing applies: AI summaries, key moments, trackers/extractions, and full-text search. ## Sync Timing and Limitations * Allow up to 15 minutes from availability in Salesloft to appearance in Momentum. * Salesloft permissions limit what Momentum can retrieve; restricted users/calls are not synced. ## Assign AI License Seats 1. Log in to the [Momentum admin](https://app.momentum.io/admin/team) page. 2. In Team, invite or locate users to license. 3. Click **Assign AI License** for each user. assign-ai-license-to-user salesloft-ci-assign-video-source-license ## Security and Access * Read-only: Momentum retrieves Salesloft Conversations and recordings; it does not write back to Salesloft. * To ingest Salesloft Conversations, Momentum requires the `conversations:read` scope and appropriate permissions to import corresponding recordings (where applicable). * Access is governed by your Salesloft and Momentum permissions. * You can disconnect anytime in Momentum Settings > Integrations; you may also revoke access in Salesloft. ## Need Help? If you have questions about setup, permissions, or backfills, contact Momentum Support and include: * Your workspace name * The Salesloft Conversation ID(s) * A brief description of the issue and when it occurred # Integrating Salesloft with Momentum AI Source: https://docs.momentum.io/momentum-ai-salesloft-integration Momentum connects to your Salesloft account to automatically ingest Dialer/Cold-call recordings and metadata into Momentum's Call Library. These calls are processed like any other source in Momentum: summarized, analyzed, and made searchable. ## Prerequisites You'll need Salesloft administrator access and a Momentum admin account. Ensure users exist in both systems with matching work emails. * Salesloft account with API access to Call Activities and recordings. * Momentum workspace permissions to install and manage integrations. * Calls must have a recording available and accessible in Salesloft for audio processing. ## Connect Salesloft 1. In Slack, type `/configure` to open Momentum's Integrations menu. 2. Select Salesloft and click **Authorize**. 3. Sign in to Salesloft and approve the requested scopes. 4. When connected, the status will show as Active. If your organization restricts app installs, your Salesloft admin may need to approve the Momentum app. ## What Gets Synced * Source: Salesloft Activities > Calls ([API docs](https://developers.salesloft.com/docs/api/activities-calls-index)) * Frequency: every 15 minutes * Filters: excludes calls with dispositions “No Answer”, “Not in Service”, “Voicemail Full”, and “Wrong Number” * Content: call recording (if available) and metadata (e.g., call ID, timestamps, disposition, user/owner, and related references) ## Where to Find Calls * Open the Call Library in Momentum to browse, search, and play Salesloft calls. * Standard processing applies: AI summaries, key moments, trackers/extractions, and full-text search. ## Sync Timing and Limitations * Allow up to 15 minutes from availability in Salesloft to appearance in Momentum. * Recording must exist and be accessible in Salesloft for audio to process. * Only supported dispositions are ingested; other dispositions are ignored. * Salesloft permissions limit what Momentum can retrieve; restricted users/calls are not synced. ## Assign AI License Seats 1. Log in to the [Momentum admin](https://app.momentum.io/admin/team) page. 2. In Team, invite or locate users to license. 3. Click **Assign AI License** for each user. assign-ai-license-to-user salesloft-assign-dialer-call-import-license ## Security and Access * Read-only: Momentum retrieves Salesloft Call Activities and recordings; it does not write back to Salesloft. * To ingest Salesloft Call Activities, Momentum requires the `calls:read` scope and appropriate permissions to import corresponding audio recordings. * Access is governed by your Salesloft and Momentum permissions. * You can disconnect anytime in Momentum Settings > Integrations; you may also revoke access in Salesloft. ## Troubleshooting * **A call isn't showing up:** * Confirm the call's disposition is NOT one of: “No Answer”, “Not in Service”, “Voicemail Full”, or “Wrong Number”. * Verify a recording exists and is accessible in Salesloft. * Allow up to 15 minutes for the next sync cycle. * Check that the Salesloft connection is Active in Momentum. * **Audio won't play:** * Ensure the recording link in Salesloft is valid and not restricted. * **Still stuck?** Contact support via your shared Slack channel or email [support@momentum.io](mailto:support@momentum.io) with the Salesloft call ID and timestamp so we can investigate. ## FAQs * **Does Momentum write to Salesloft?** No, the integration is read-only. * **Can we change which dispositions are ingested?** We exclude calls with the following dispositions: “No Answer”, “Not in Service”, “Voicemail Full” and “Wrong Number”. * **Do you support historical backfill?** By default, ingestion starts after connection. For backfill, contact Momentum. * **How often are calls imported?** Every 15 minutes. ## Disconnecting the Integration * In Slack: type `/configure`, select the Momentum app, and click **Log Out** next to Salesloft. * Optionally contact Momentum to confirm the disconnect completed as expected. ## Need Help? If you have questions about setup, permissions, or backfills, contact Momentum Support and include: * Your workspace name * The Salesloft Call ID(s) * A brief description of the issue and when it occurred # Momentum AI Settings Source: https://docs.momentum.io/momentum-ai-settings Momentum AI Settings govern how Momentum CI preprocesses calls before transcription and post-processes them after insights are generated. Configure these options to make sure call enrichment follows your Salesforce data model and governance policies. Use the **Momentum Call Salesforce Mapping** setting to control how Momentum AI associates calls with Salesforce records. The latest update introduces an option to ignore partner or internal account types when other attendees are present, preventing misattribution of calls. ### Why this setting matters * **Problem**: Calls could get mapped to partner accounts even when customers, prospects, or stakeholders joined the meeting, skewing reporting and engagement metrics. * **Solution**: A new configuration reads the Salesforce `Account.Type` picklist and lets admins choose which types to ignore when additional attendees are present. Momentum then maps the call to the most relevant customer-facing account. ### Open the Settings Page 1. **Navigate to Momentum AI Settings**: Go to `Settings > Momentum AI`. 2. Select **Momentum Call Salesforce Mapping**. ### Configure "Ignore account types when extra attendees are present" 1. In the settings page, locate **Ignore account types when extra attendees are present** and check the box to enable it. 2. Select one or more account types (for example, *Partner*) from the dynamically loaded list pulled from the Salesforce `Account.Type` picklist. 3. Click **Save**. If any selected "ignored" account types are present alongside other account types, Momentum skips the ignored ones and maps the call to the remaining attendees. When every attendee belongs to an ignored account type, the call will not be mapped to any accounts. Ensure the Momentum integration user has read access to the `Account.Type` field; otherwise the list of account types will appear empty. After saving, resync a recent call to spot-check that the call record now associates with the expected customer or prospect account. This targeted control keeps Momentum call records focused on the customer or prospect you care about, improving reporting accuracy and follow-up workflows. The **Summary Disclaimer** setting allows admins to add a custom disclaimer message that appears at the top of all Slack call summaries. This helps organizations communicate important context about how AI-generated summaries should be used. ### Why this setting matters * **Compliance**: Notify recipients that summaries are AI-generated and may require verification. * **Usage Guidelines**: Clarify that summaries should not be used for performance management or other specific purposes. * **Transparency**: Set clear expectations about the nature and limitations of automated call analysis. ### Open the Settings Page 1. **Navigate to Momentum AI Settings**: Go to `Settings > Momentum AI > Summary`. 2. Locate the **Summary Disclaimer** field. ### Configure Summary Disclaimer 1. Enter your custom disclaimer text. 2. Click **Save**. When configured, the disclaimer text appears at the top of every Slack call summary, ensuring all recipients see the message before reviewing the summary content. Leave the field empty to disable the summary disclaimer. No disclaimer will be shown if no text is specified. **Example Disclaimer:** ```text theme={null} This summary was generated by AI and is intended for informational purposes only. Please verify critical details and do not use this content for performance evaluations. ``` The **Bot Kicked Disclaimer** setting allows admins to customize the message displayed when the Momentum recording bot is removed from a call by a participant. This disclaimer appears in both **Slack summaries** and **Salesforce notes**. ### Why this setting matters * **Context for Stakeholders**: When a bot is kicked from a call, stakeholders receiving the Slack summary or reviewing Salesforce notes need to understand why only partial information may be available. * **Custom Messaging**: Tailor the notification to match your organization's tone and provide relevant next steps. * **Visibility**: Ensure teams are aware across both Slack and Salesforce when recordings are incomplete due to bot removal. ### Open the Settings Page 1. **Navigate to Momentum AI Settings**: Go to `Settings > Momentum AI > Summary`. 2. Locate the **Bot Kicked Disclaimer** field. ### Configure Bot Kicked Disclaimer 1. Enter your custom message text. 2. Click **Save**. When the Momentum bot is removed from a meeting, this disclaimer will be included in both the Slack summary and the Salesforce notes generated for that call. Leave the field empty to disable the bot kicked disclaimer. No message will be shown in Slack summaries or Salesforce notes if no text is specified. **Example Disclaimer:** ```text theme={null} Note: The recording bot was removed from this call. The summary below may be incomplete. ``` # Integrating Vonage Contact Center with Momentum AI Source: https://docs.momentum.io/momentum-ai-vonage-integration Momentum connects to your Vonage Contact Center (VCC) account to automatically ingest call recordings and metadata into Momentum's Call Library. These calls are processed like any other source in Momentum: summarized, analyzed, and made searchable. ## Prerequisites You'll need Vonage Contact Center administrator access and a Momentum admin account. Ensure users exist in both systems with matching work emails. * Momentum workspace permissions to install and manage integrations. * Calls must have recordings enabled and accessible in Vonage Contact Center. * **Vonage Contact Center region**: Know your VCC region (NAM, EMEA, or APAC) — this determines the API endpoints used. ## Vonage Contact Center Configuration ### Required API Scopes Your Vonage Contact Center API credentials must have the following scopes enabled in the VCC Admin Portal: | Scope | Purpose | | ----------------------------------------------------------------- | --------------------------------------------------------------------------- | | `stats - View Insights stats` | Required. Access to Insights Stats API for retrieving call/interaction data | | `interaction-content:read - Read or download interaction content` | Required. Access to recordings and transcripts | | `users:read - Read VCC user details, settings and presence` | Required. Enables automatic user sync between Vonage and Momentum | vonage-vcc-required-scopes If the required scopes are not enabled, Momentum will not be able to retrieve call data or recordings. Contact your Vonage administrator to verify scope configuration. ### Regional Endpoints Vonage Contact Center uses region-specific endpoints. Momentum will use the appropriate endpoints based on your configured region: | Region | Authentication Endpoint | API Endpoint | | -------------------------------- | ----------------------------------------------- | -------------------------------- | | NAM (North America) | `https://nam.cc.vonage.com/Auth/connect/token` | `https://nam.api.cc.vonage.com` | | EMEA (Europe/Middle East/Africa) | `https://emea.cc.vonage.com/Auth/connect/token` | `https://emea.api.cc.vonage.com` | | APAC (Asia Pacific) | `https://apac.cc.vonage.com/Auth/connect/token` | `https://apac.api.cc.vonage.com` | EMEA is the default region. If your VCC account is provisioned in a different region, ensure you specify the correct region when configuring the integration or inform the support team and they will help you to configure. ## Generate your Vonage API Credentials 1. Sign in to your Vonage Contact Center Admin Portal with an administrator account. 2. Navigate to **Admin → API Credentials**. 3. Click **Create API Credentials** or locate existing credentials. 4. Select the [required scopes](#required-api-scopes). 5. Click **Create**. 6. Copy the **Client ID** and **Client Secret**. Store your API credentials securely immediately after generation. The Client credentials may not be retrievable later. ## Add API Credentials to Momentum 1. Copy the generated API credentials from Vonage Contact Center. 2. Switch to your Momentum admin dashboard. 3. Find the Vonage integration tile and enter: * **Client ID** * **Client Secret** vonage-add-api-key-to-momentum.png Your integration is now complete! ## Where to Find Calls Open the **Call Library** in Momentum to browse and search Vonage calls. ## Assign AI License Seats To enable Vonage call sync for users: 1. Log in to the [Momentum admin](https://app.momentum.io/admin/team) page. 2. In the **Team** section, invite or locate users to license. 3. Click **Assign AI License** for each user. 4. Enable **Vonage calls** to sync that user's calls. assign-ai-license-to-user vonage-assign-dialer-call-import-license ## Troubleshooting If you encounter issues, contact our support team: * Slack: Use your shared Momentum channel * Email: [support@momentum.io](mailto:support@momentum.io) ## FAQs By default, ingestion starts after connection. Contact Momentum support for historical backfill requests. You'll need to update the credentials in Momentum's integration settings to maintain the connection. Your region is determined by where your Vonage Contact Center account was provisioned. If you're unsure, contact your Vonage administrator or check your VCC Admin Portal URL — it typically contains the region prefix (nam, emea, or apac). # Integrating Zoom with Momentum AI Source: https://docs.momentum.io/momentum-ai-zoom-integration Momentum is a powerful tool to analyze your calls and better work your deals. If you already have a call recording tool or use video conferencing software like Zoom, the setup is easy! By integrating with Zoom, Momentum enables sharing recorded meetings from Zoom to Momentum AI. This streamlines the process of recording meetings in Zoom and accessing them in Momentum. ## Requirements **Zoom License:** To integrate Momentum AI with Zoom, you must have a Zoom Business, Education, or Enterprise license. This license provides access to advanced features and functionalities that are necessary for our product to work. ## **Administrator steps to setup Momentum's integration with Zoom** Momentum for Zoom needs to be installed only once for a company, by a Zoom Administrator *Things to Note:* *We recommend you check with IT or an admin to make sure you have the right access to install the Momentum app in Zoom.‍* ## **Authorize Momentum's Zoom Integration** Setting up Momentum's Zoom Integration establishes the connection between Momentum AI and Zoom. *Things to Note: When you set up* Momentum's Zoom Integration\*, only recorded meetings and transcripts will be available to Momentum. This will apply to past and future calls.\* To set up Momentum's Zoom Integration, follow these steps: Click on this link to access the 👉 [**Momentum App for Zoom**](https://api.momentum.io/oauth/zoom/auth) You can also copy the following URL and paste it in your browser: [https://api.momentum.io/oauth/zoom/auth](https://api.momentum.io/oauth/zoom/auth) * Login to the Momentum admin if you aren't logged-in already. Once completed you'll be taken to the Zoom Marketplace * In Zoom's login page, enter your Zoom credentials to continue. * Review the Authorize page, then click **Allow**. zoom-momentum-access-permissions You are done. Congratulations! Now every recorded call hosted by one of your team members will be received by Momentum AI and analyzed. To successfully leverage Momentum for Zoom, you must also make sure your organization has these key features of Zoom enabled: * Cloud Recordings in Zoom * Audio Transcripts in Zoom ## **Enable Cloud Recording in Zoom** Turning on cloud recording allows Momentum to capture your Zoom video and audio recordings successfully. To turn on Cloud Recording in Zoom, follow these steps: 1. Go to your [Zoom Account Settings](https://zoom.us/account/setting) page to do this at the account level (this will apply to all your Zoom users), or instead [go to a specific Zoom User Group](https://zoom.us/account/group#/) settings page (to apply the same only for a subset of your Zoom users). 2. Enable Cloud Recording. zoom-enable-cloud-recording ## **Enable Audio Transcripts in Zoom** The Audio Transcript settings allow Momentum to access the transcript associated with your Zoom recordings. To turn on the Audio Transcript, follow these steps: 1. Open the same Zoom Settings page for either your account (to set this up globally), or group (for a subset of your users). 2. Scroll to the *Advanced cloud recording* settings and check the box that sits next to the Create audio transcript option: zoom-enable-audio-transcript *Things to Note: Cloud recording and audio transcripts are only available for Business, Education, or Enterprise account in Zoom. If you're using Zoom Pro, please reach out to our team.* As a Zoom Administrator, **your work is done**! Thanks for supporting your team in their journey to leveraging AI to close more deals.‍ *** ## **Final Step: Adding AI License Seats** To add users to the AI license Seats setting in Momentum: 1. Log in to the Momentum Admin: Visit the [Momentum admin](https://app.momentum.io/admin/team) page and log in with your credentials 2. In the Team section, find or invite the users you'd like to assign AI licenses to 3. Click Assign AI License option in the users's record assign-ai-license-to-user ## **Individual Team Members Will Now Start Seeing Zoom Record Their Calls!** Once your admins have enabled Momentum's Zoom Integration and cloud recordings, it's time for your team to start capturing some calls! Momentum will automatically manage the recording of sessions so that end-users can capture a meeting in Zoom. This will warn every attendee and lead to a video and transcript of the session generated by Zoom after the call completes. ## **Uninstalling the Momentum app from your Zoom organization** If you want to remove the Momentum app from your Zoom account, you can do so by following a few simple steps. First, you need to go to the [**https://marketplace.zoom.us/user/dashboard/installed-apps**](https://marketplace.zoom.us/user/dashboard/installed-apps) link. Once you are there, you should be able to see a list of all the apps that you have installed in your Zoom account. Look for the Momentum app and click on it, in the **Manage app** section. You should then see an option to remove the app from your account. Simply click on it, and the app will be removed from your account. It's that easy! zoom-uninstall-momentum-app Transcripts and data collected from Zoom are stored until the organization requests that this data be removed or if a customer has decided to terminate Momentum. This allows Momentum users to query for insights on their Sales calls regardless of how long ago they happened. ## **Troubleshooting** Momentum's Zoom Integration requires two systems to communicate, and an error can occur in the event of miscommunication. For assistance troubleshooting Momentum's Zoom Integration errors, please contact our team via our shared Slack channel or [support@momentum.io](mailto:support@momentum.io).‍ # Call Remapping Source: https://docs.momentum.io/momentum-ci-call-remapping Learn how to link and remap meetings to the correct Salesforce records using Momentum's enhanced remapping experience. # Overview Momentum's Call Remapping feature allows you to link meetings to the correct Salesforce records when automatic mapping doesn't match your needs. We've enhanced the Meeting Remap experience to make it faster, clearer, and more flexible. ## What's New ### Cleaner UI See clearer mapping details with name, ID, and ARR displayed together, along with more descriptive field placeholders and consistent styling throughout the modal. * **Clear record details**: View name, Salesforce ID, and ARR at a glance * **Descriptive placeholders**: Easily understand what each field expects * **Consistent styling**: A polished, unified interface throughout the remapping modal Call Remapping Overview ### Improved Search Quickly find Accounts, Opportunities, and Leads by name or Salesforce ID. You can now paste a full Salesforce ID to instantly match the correct record. * **Search by name**: Type any part of the Account, Opportunity, or Lead name to filter results * **Search by Salesforce ID**: Paste a full Salesforce ID to instantly locate the exact record * **Fast matching**: Results appear as you type for quick selection Improved Search ### More Flexible Remapping Remap meetings to a Lead without requiring an Account, and get clearer confirmation messages when remapping or unmapping records. * **Lead-only remapping**: Link a meeting directly to a Lead without needing an associated Account * **Clear confirmations**: Receive explicit confirmation messages when remapping or unmapping records * **Flexible workflows**: Support for various sales processes and CRM structures #### Salesforce Data Model An Opportunity is always a child of an Account in Salesforce—it can't exist standalone. When you map a meeting to an Opportunity, we need the parent Account (or a Lead) to properly anchor the relationship. **Why we require Account or Lead:** * **Opportunities are transient**: They get closed (won/lost) and may be deleted, but the Account relationship persists * **Attribution & Reporting**: Account/Lead is the primary entity for tracking customer engagement; Opportunity is secondary * **Data integrity**: If an Opportunity is deleted, the meeting would lose its CRM context entirely without an Account/Lead fallback **Valid mapping combinations:** | Mapping | Supported | | --------------------- | -------------------- | | Account only | ✓ | | Lead only | ✓ | | Account + Opportunity | ✓ | | Lead + Opportunity | ✓ | | Opportunity only | ✗ (no anchor entity) | Flexible Remapping ### Better Feedback Success notifications now explicitly list the selected Account and Opportunity, so you always know exactly what was mapped. * **Detailed success messages**: See the specific Account and Opportunity names in confirmation notifications * **Clear status updates**: Know exactly which records were linked after each action Cleaner UI ## How to Remap a Call There are two ways to access the **Remap Salesforce Object** option: ### Option 1: From the Call Library Table 1. Navigate to the **Call Library** in your Momentum dashboard. 2. Find the call you want to remap in the table. 3. Click the **three vertical dots** (⋮) on the call row. 4. Select **Remap Salesforce Object** from the menu. Call Library Remap ### Option 2: From the Call Details Page 1. Navigate to the **Call Library** and click on a call row to open the call details page. 2. In the upper right corner, click the **three horizontal dots** (⋯). 3. Select **Remap Salesforce Object** from the menu. Call Library Remap ### Complete the Remapping Once the remapping modal opens: 1. **Search for records**: Use the search bar to find the correct Account, Opportunity, or Lead by name or Salesforce ID. 2. **Select the record**: Click on the desired record from the search results. 3. **Confirm the mapping**: Click **Apply Changes** to complete the remapping. ## Use Cases * **Incorrect automatic mapping**: When Momentum maps a call to the wrong Account or Opportunity, use remapping to correct it. * **New deals**: Link calls to newly created Opportunities that weren't available during the original meeting. * **Lead qualification calls**: Map discovery calls directly to Leads before an Account or Opportunity exists. * **Multi-deal accounts**: Ensure calls are associated with the correct Opportunity when an Account has multiple active deals. # Recording Google Calendar Events Source: https://docs.momentum.io/momentum-ci-google-calendar-events Momentum lets each user decide how the recorder treats their Google Calendar meetings. Two independent preferences control the behaviour so people who handle sensitive conversations can opt out without impacting teammates who still want full coverage. * **Record private Google Calendar events** – If disabled, meetings whose Google Calendar visibility is "Private" are skipped. * **Automatically record Google Calendar events** – If disabled, Momentum won't auto-join your Google Calendar meetings at all; you'll need to enable recording case by case (for example, via the meeting detail page). ## Requirements * Google Calendar integration, because both settings rely on Google's event metadata. * Momentum's native recorder must be enabled for the user; uploads from external CI systems ignore these toggles. ## Manage your preferences 1. Open the Momentum web app and choose **Settings** from the profile menu in the lower-left corner. 2. In **Recording Settings**, you'll see both toggles: * **Record private Google Calendar events** – leave on to capture private events, turn off to skip them. * **Automatically record Google Calendar events** – leave on so Momentum auto-joins your events, turn off to opt in manually. 3. Changes take effect immediately, and you can re-enable either toggle at any time. ## How Momentum evaluates events When the recorder prepares to join, Momentum pulls the Google Calendar event and applies the toggles in this order: 1. If **Automatically record Google Calendar events** is off, Momentum does not join, regardless of privacy. * Internally we log the skip as `AUTO_RECORD_DISABLED`. 2. If auto-record is on and the event is marked Private while **Record private Google Calendar events** is off, Momentum skips the meeting and logs `PRIVATE_MEETING`. 3. Otherwise, Momentum behaves normally and records the meeting. Renaming an event to include the word "Private" doesn't influence the decision—only Google's visibility flag matters. ## Known behaviors * Decisions are made with the data available at join time. If visibility changes afterwards, the recorder may still join or stay based on the earlier state. * Preferences are per user; each attendee controls their own toggles. * If Google Calendar visibility can't be determined (for example, due to an API error), Momentum defaults to joining as though both toggles were enabled. # Momentum CI Licensing Source: https://docs.momentum.io/momentum-ci-licensing An explanation of the different user seat types for Momentum CI, including Viewer, CI, and AI seats. # Momentum CI Licensing Explained Momentum offers a flexible and powerful licensing model designed to give your entire organization visibility into customer conversations while providing advanced capabilities to the users who need them most. Our model is built on three distinct seat types. **Cost**: Free and Unlimited **Permissions**: * View any call, clip, or playlist they are given access to. * Receive shared content. Viewer seats are designed to promote widespread learning and collaboration. Anyone in your company can be a viewer at no cost. **Cost**: Paid (Per User) **Permissions**: * Everything a Viewer can do, plus... * Have their own calls recorded by Momentum. * Create clips and playlists. * Search the entire call library. CI seats are for the users who are actively having their conversations recorded, such as your sales reps and customer success managers. **Cost**: Paid (Per User, Add-on) **Permissions**: * Everything a CI Seat holder can do, plus... * Access to all Momentum AI features on recorded calls (Summaries, Autopilot, Signals, etc.). * Ability to configure AI-powered workflows. AI seats unlock the full power of Momentum's analysis on your recorded conversations. This is typically assigned to users who need to leverage AI for automation and deep insights. ## How the Seats Work Together * A user with a **CI Seat** can have their calls recorded. * If that same user also has an **AI Seat**, all of Momentum's AI features can be run on those recordings. * Anyone in the organization can be a **Viewer** for free to watch the recordings and clips that are shared with them. This model allows you to provide recording and AI capabilities to your key customer-facing team members while ensuring that the valuable insights generated can be shared freely across your entire company without incurring extra costs. # Nested Folders Source: https://docs.momentum.io/momentum-ci-nested-folders Organize your Momentum Call Library with nested folder hierarchies, breadcrumbs, and shared navigation. # Call Organization with Folders Momentum's folder system helps you organize your calls, recordings, and snippets into logical collections. Whether you're organizing by project, client, team, or any other structure that works for you, folders provide a flexible way to keep your content organized and easily accessible. Keep your Call Library aligned with the way your team works by building folder structures that mirror your customer journeys or internal processes. Nested folders help you stay organized no matter how fast your library grows. ## Key Capabilities * **Hierarchical Organization**: Create sub-folders inside any folder to group recordings by customer, region, team, or project. * **Multi-Folder Assignment**: Add calls to multiple folders simultaneously for cross-project visibility. * **Flexible Management**: Drag and drop folders to rearrange hierarchies so you can move an entire customer folder under a new parent without touching every call. * **Comprehensive Storage**: Store everything in one place—folders, call recordings, and snippets. Item counts include nested folders so you always know what lives inside. * **Effortless Navigation**: Navigate effortlessly with breadcrumbs. The header trail shows exactly where you are and lets you jump back up a level in one click. * **Team Alignment**: Keep everyone aligned. Folder breadcrumbs, search results, and organization are shared, so teammates see the same structure you do. * **Search & Filter**: Filter calls by specific folders to quickly find relevant content. ## Getting Started ### Creating Your First Folders 1. Open the `Calls → Folders` tab. 2. Click `New Folder` to create your top-level folders. 3. Choose a descriptive name that reflects the folder's purpose. 4. Open any folder and use `New Folder` again to create sub-folders. ### Organizing Your Structure 4. **Drag and Drop**: Drag a folder into another folder to nest it, or click `More → Move` to choose the destination from a list. 5. **Navigation**: Use the sidebar or breadcrumb trail to move between levels. Searching within a folder focuses on the current level—clear the search to see everything again. ### Adding Calls to Folders * **From Call Details**: When viewing a specific call, use the action menu to `Manage Folders` * **Multiple Folders**: Add the same call to multiple folders for cross-project visibility * **Folder Management Modal**: Select one or more folders where you want to add the call ## Managing Folder Content ### Moving Folders and Content * **Individual Folders**: Select any folder and use the move action to relocate it within your hierarchy * **Snippet Management**: Move clips between folders independently of their parent calls * **Validation**: The system prevents moving folders into their own children to avoid circular references ### Folder Hierarchy Examples **Project-Based Structure:** ``` Sales Team ├── Q1 2024 Prospects │ ├── Enterprise Deals │ └── Mid-Market Opportunities ├── Q2 2024 Prospects └── Client Onboarding ├── Completed └── In Progress ``` **Client-Based Structure:** ``` Clients ├── Technology Sector │ ├── Client A - Implementation │ └── Client B - Discovery ├── Healthcare Sector └── Financial Services ``` ## Best Practices and Tips ### Organizational Strategy * **Purpose-Driven Structure**: Organize folders around how you actually work * **Consistent Naming**: Use clear, consistent naming conventions like "Client - Project" or "Team - Quarter" * **Balanced Depth**: While unlimited nesting is supported, keep your structure to 2-3 levels deep for optimal usability * **Regular Maintenance**: Periodically review and reorganize as your needs evolve ### Folder Management * **Rename or Delete**: Access folder options from the `More` menu. Deleting a folder removes any sub-folders and snippets it contains, but the underlying calls stay in the Call Library. * **Break Down Clutter**: If a folder feels cluttered, break it down by creating sub-folders and moving items into them. * **Breadcrumb Navigation**: Breadcrumbs always start with `All folders`—click it to jump back to the top level. * **Search Functionality**: Use the search box in folder pickers to quickly find specific folders in large hierarchies. ### Multi-Folder Strategy * **Cross-Project Calls**: Add calls to multiple folders when they serve multiple purposes * **Topic Tagging**: Use folders as topic tags for better discoverability * **Team Sharing**: Share relevant calls across team folders * **Archive Strategy**: Create archive folders for completed projects ## Quick Reference | Action | How To | | ------------------ | ------------------------------------------- | | Create Folder | Call Library → Folders → New Folder | | Add Call to Folder | Call Menu → Manage Folders → Select Folders | | Remove from Folder | Folder Management Modal → Remove Icon | | Move Folder | Folder Menu → Move → Select Destination | | Move Snippet | Snippet Menu → Move → Select Destination | | Search Folders | Use search box in folder picker | | Navigate Hierarchy | Click breadcrumbs or folder names | # Momentum ci overview Source: https://docs.momentum.io/momentum-ci-overview # Setting Up Momentum CI Source: https://docs.momentum.io/momentum-ci-setup A step-by-step guide to configuring Momentum's Conversation Intelligence (CI) for native call recording and analysis. # Setting Up Momentum CI This guide will walk you through the process of setting up Momentum CI to start recording, transcribing, and analyzing your sales calls. ## Prerequisites * Admin access to your Momentum Organization. * Admin access to your video conferencing platform (e.g., Zoom). ## Step 1: Enable Momentum CI First, ensure that Momentum CI is enabled for your organization. If you don't see the "Call Library" or "CI Settings" in your admin dashboard, please contact your Momentum account manager or support to have it activated. ## Step 2: Configure Your Recording Method Momentum provides two primary methods for recording your meetings: ### Option A: Native Zoom Recording (Recommended) Using the native Zoom integration is the most seamless way to record high-quality video and audio. 1. **Navigate to CI Settings**: In your Momentum admin dashboard, go to `Settings > CI Settings`. 2. **Connect Zoom**: Click "Connect" next to the Zoom integration option. You will be prompted to authorize Momentum to access your Zoom account. 3. **Enable Native Recorder**: Once connected, toggle on the "Use Zoom native recorder" option. This allows Momentum to directly manage and pull recordings from Zoom's cloud. 4. **Assign CI Seats**: Ensure that the users you want to record have been assigned a "CI Seat" in your user management settings. Only users with a CI seat and a connected Zoom account will have their meetings recorded. ### Option B: Momentum Recording Bot For other platforms or for users without a direct Zoom integration, the Momentum Recording Bot can join your calls to capture the conversation. 1. **Enable Bot**: In `Settings > CI Settings`, toggle on the "Use Momentum recording bot" option. 2. **Configure Bot Behavior**: * **Bot Name**: You can customize the name the bot uses when it joins meetings (e.g., "Momentum Notetaker"). * **Auto-Join**: Configure the bot to automatically join scheduled meetings for users with a CI seat. ## Step 3: Configure Recording Consent It's crucial to manage recording consent in accordance with your company's policies and local regulations. 1. **Navigate to Consent Settings**: Go to `Settings > Recording Consent`. 2. **Customize Consent Page**: You can customize the landing page that attendees see when they are notified that the call is being recorded. 3. **Enable In-Meeting Consent**: For platforms that support it, you can enable a pop-up that asks for consent directly within the meeting interface. Once these steps are complete, Momentum CI will begin recording meetings for your assigned users. The recordings will automatically appear in your new **Call Library** shortly after each meeting ends. # Upcoming Calls Source: https://docs.momentum.io/momentum-ci-upcoming-calls ## Overview The Upcoming Calls tab introduces a streamlined, at-a-glance view of all scheduled, in progress and processed meetings. Designed to help users manage their daily communication more effectively, the tab separates in-progress meetings from upcoming meetings, highlights important call states, and provides direct controls for AI Recording and privacy management. This feature ensures Momentum users can easily monitor, manage, and control meetings from a unified interface, without having to switch between tools or dashboards. Upcoming Calls ## Key Features ### 1. Dedicated Tab for Calls A new tab, “Upcoming Calls”, is now available in the Momentum web app. It lists: * In-progress meetings (highlighted and displayed at the top) * Meetings scheduled for the next seven days. * Meetings that have already been processed. This layout prioritizes visibility of ongoing calls and helps users prepare for upcoming ones at a glance. Each meeting entry shows all the necessary information : * Meeting Date & Time * Meeting Title * Salesforce Details * AI Recording Toggle * Privacy Control Button Updated Calls Page ### 2. AI Recording Management Each meeting row includes a toggle switch for the Momentum AI Recording feature: * **Toggle ON/OFF**: Enables or disables automatic recording and transcription by Momentum. * **Info icon**: Appears when recording is disabled, showing: * The call’s recording status * The reason recording is unavailable (e.g. Missing Cross-Source Information, No User License Found, or Disabled by User). Upcoming Calls No License Upcoming Calls Recording Disabled * **Reactivation**: Users can re-enable recording only if it was manually disabled. Calls with disabled recordings with a valid skip reason, such as missing info or licensing issues, cannot be re-enabled. This ensures users maintain full control over recording privacy at ease while respecting system constraints. ### 3. Privacy Controls A secondary action button allows users to mark a meeting as private: * Converts a public meeting (visible to the entire organization) into a private meeting (visible only to the host and attendees). * Once made private, the action cannot be undone. * The column updates to show a greyed-out “Private” label to indicate restricted visibility. Upcoming Calls Privacy Column # Using Momentum CI Source: https://docs.momentum.io/momentum-ci-usage Learn how to use the Momentum Call Library to find, analyze, clip, and share your sales conversations. # Using the Momentum CI Platform Once your setup is complete, you can begin to leverage the full power of the Momentum CI platform. This guide covers the key features you'll use day-to-day. ## The Call Library The Call Library is your central hub for all recorded conversations. * **Accessing the Library**: Navigate to the `Call Library` tab in your Momentum dashboard. * **Viewing Calls**: You'll see a list of all recent recordings. Click on any call to open the playback page, which includes the video, a searchable transcript, and AI-powered insights. ### Team Calls * Gives managers visibility into meetings across their full reporting hierarchy including direct reports, their reports, and deeper levels. * Meetings are sorted newest first, paginating automatically as you scroll. ## Searching for Calls The search functionality is one of the most powerful features of Momentum CI. You can find calls based on: * **Call Details**: Search by participant name, meeting title, or date. * **Transcript Keywords**: Search for specific words or phrases mentioned during the conversation. * **CRM Data**: This is where Momentum CI shines. You can search using any data from your connected Salesforce instance. For example: * `Find all calls for Opportunity "Project X"` * `Show me calls with Accounts in the "Technology" industry` * `Search for calls where the deal stage is "Negotiation"` Search results display the total number of matches and surface highlighted transcript snippets, enabling faster review and access to the most relevant moments. Advanced search results showing match count and transcript snippets ## Creating Clips and Organizing with Folders Clipping allows you to isolate key moments from a call for coaching or sharing, while folders help you organize your content effectively. 1. **Create a Clip**: On the call playback page, highlight a section of the transcript. A "Create Clip" button will appear. Click it and give your clip a descriptive name. 2. **Organize with Folders**: Folders are collections of calls, clips, and other content that help you stay organized. You can create new folders from the "Folders" tab or add content to existing folders. 3. **Use Cases for Folders**: * **Coaching**: Create a folder with clips of a rep's best discovery questions. * **Onboarding**: Build a folder with perfect objection handling examples for new hires. * **Competitive Intelligence**: Compile a folder with clips of every time a specific competitor is mentioned. * **Project Organization**: Group all calls and clips related to a specific deal or customer. * **Team Structure**: Organize content by sales rep, team, or territory. ## Managing Folders Folders provide a flexible way to organize your calls, recordings, and snippets into logical collections. ### Creating and Using Folders 1. **Access Folders**: Navigate to the `Folders` tab in your Call Library. 2. **Create New Folders**: Click `New Folder` and give it a descriptive name. 3. **Add Content to Folders**: Use the `Manage Folders` option from any call or clip's action menu. 4. **Nested Organization**: Create sub-folders within existing folders for hierarchical organization. ### Folder Benefits * **Multi-Folder Assignment**: Add calls to multiple folders for cross-project visibility. * **Hierarchical Structure**: Create nested folder structures that mirror your organizational needs. * **Search and Filter**: Filter calls by specific folders to quickly find relevant content. * **Team Collaboration**: Share folder structures with your team for consistent organization. ### Moving Content Between Folders * **Drag and Drop**: Easily move folders and reorganize your structure. * **Folder Actions**: Use the `Move` option from folder menus to relocate entire folder hierarchies. * **Snippet Management**: Move clips between folders independently of their parent calls. ## Sharing Content Momentum makes it easy to share insights securely. 1. **Sharing Options**: On any call, clip, or folder, click the `Share` button. 2. **Share with Individuals**: You can share directly with another Momentum user via email. 3. **Share with a Public Link**: Generate a secure link to share with anyone, even people outside your organization (like a customer). 4. **Track View Counts**: When you share content, Momentum will show you who has viewed it and how many times, giving you insight into engagement. Remember, sharing with internal colleagues is always free, as Viewer seats do not incur any cost. # Momentum Credits Source: https://docs.momentum.io/momentum-credits A fair, predictable way to price high-volume workloads. ## At a Glance * **Included & unlimited:** Real-time, call-triggered workflows (Autopilot Classic, Summaries, AI Signals, Call Recording) are **not** metered. * **Metered with credits:** High-volume workflows that can reprocess large historical datasets. * **One credit = one record run.** Think "one deal or account processed once." * **Credits are pooled** across your seats and **refresh monthly**. No rollover. * **If you hit zero:** We **pause** high-volume jobs and **notify admins**. No auto-charges. ## Why Credits Exist Credits make costs predictable when you run big, non-call jobs (e.g., backfills or retro analyses). They act as clear guardrails so you can scale without surprise bills and without limiting the day-to-day, call-bound workflows your team relies on. ## What Uses Credits These product areas can consume credits because they operate at large scale and/or on historical data: * **Retropilot**: Re-analyzes past calls when a Salesforce event occurs (e.g., an opportunity changes stage). * **Autopilot Batch**: On-demand or scheduled backfill jobs across many CRM records. * **Executive Briefs**: Scheduled rollups digesting insights across a wide set of deals or accounts. * **Deep Research**: Ad-hoc lookups over a large corpus (e.g., enterprise-segment accounts or deals). **Not metered:** AI Signals, Summaries, and other workflows triggered by live calls aren't ever metered or paused. ## How Credits Are Allocated * **Account-level pool:** All seats share a single monthly pool of credits. * **Per-seat allocation:** Your plan specifies a per-seat amount that rolls into the pool. *Example:* 150 credits/seat × 10 seats = **1,500 credits/month**. * **Monthly refresh:** Credits reset on the first day of your billing month. * **No rollover:** Unused credits expire at the monthly reset. ## How Credits Are Counted **Simple rule:** *one credit = one processing run per record (deal or account).* Examples: * **Retropilot:** 1 credit per opportunity (or account) analyzed when the trigger fires. * **Autopilot Batch:** A batch that reviews 500 opportunities uses **500 credits**. * **Executive Briefs:** A digest that processes 350 opportunities uses **350 credits**. * **Deep Research:** Querying 1,000 enterprise-segment deals uses **1,000 credits**. We intentionally abstract technical costs so you can plan usage with a clear, human-readable unit. ## What Happens at Zero Credits When your monthly pool is fully consumed: 1. The next high-volume workflow is **auto-paused**. 2. **Admins are notified** in-app and can adjust/plan next steps. 3. Workflows **resume automatically** at the next monthly refresh **or** when credits are added. **No surprise bills:** Momentum's standard policy is to pause and notify rather than auto-charge. ## Buying More Credits * You can purchase additional **credit bundles** at any time. * Talk to your CSM if you anticipate a spike (e.g., a large backfill) so we can size the bundle appropriately. * During onboarding, some plans include **generous exploration allowances**. Ask your CSM for details. ## Controls & Best Practices * **Toggle high-volume workflows** (Retropilot, Autopilot Batch, Executive Briefs, Deep Research) on/off to manage spend. * **Use scheduling windows** for batches and briefs to align with your operating cadence. * **Get a usage report:** Your CSM can provide current credit consumption on request. ## FAQ **Do call-based features use credits?** No. Real-time, call-triggered workflows are unlimited and not metered. **Can I allocate credits per team or per rep?** Credits live in an account-level pool. Use workflow toggles and scheduling to control where usage happens. **When do credits refresh?** On the first day of your billing month. Unused credits do not roll over. **What if a job is paused at zero?** Start it again after your monthly refresh or add a credit bundle to resume sooner. **How do I plan a large backfill?** Estimate records × 1 credit per record, then ask your CSM to size a temporary bundle. ## See Also * **[Setting Up Retropilot](/retropilot-setup)**: Configure triggers for historical analysis. * **[Setting Up Autopilot Batch](/autopilot-batch-setup)**: Run on-demand and scheduled backfills. * **[Executive Briefs](/executive-briefs)**: Learn about scheduled insights digests for leadership. For any questions about credits or your plan, contact your Momentum CSM or reach out to [support@momentum.io](mailto:support@momentum.io). # Momentum Deletion Settings Source: https://docs.momentum.io/momentum-deletion-settings Control who can delete meetings and meeting clips across your workspace. These policies are configured under **Settings > Security** and take effect immediately for all users. Users who do not have permission to delete under the current policy will not see the delete option. Controls who can delete call recordings from your organization's Call Library. | Policy | Who Can Delete | | ----------------------------- | ----------------------------------------- | | **Admins Only** | Organization Admins only. | | **Host and Admins** (Default) | The meeting host and Organization Admins. | To configure, go to **Settings > Security**, select your preferred option from the **Meeting Deletion Policy** dropdown, and click **Save**. For strict data retention requirements, use **Admins Only** to prevent recordings from being removed without admin approval. Controls who can delete meeting clips — short highlights created from call recordings. This is managed separately from meeting deletion. | Policy | Who Can Delete | | ---------------------------------------- | ------------------------------------------------------------ | | **Admins Only** | Organization Admins only. | | **Host and Admins** | The meeting host and Organization Admins. | | **Creators, Host, and Admins** (Default) | The clip creator, the meeting host, and Organization Admins. | To configure, go to **Settings > Security**, select your preferred option from the **MeetingClip Deletion Policy** dropdown, and click **Save**. The default **Creators, Host, and Admins** provides a good balance — clip creators can manage their own content while admins retain full oversight. # Momentum Permissions and Access Overview Source: https://docs.momentum.io/momentum-permissions-overview ## Introduction Integrating Momentum with various systems ensures seamless workflow and enhanced productivity. This overview provides detailed steps on how Momentum accesses each system, ensuring a smooth installation process. ## Systems and Access Methods Momentum integrates with the following systems using specific access methods: #### CRM & Revenue Operations Platforms * Salesforce #### Team Collaboration Platforms * Microsoft Teams * Slack #### Calendar & Scheduling Platforms * Google Calendar * Microsoft Outlook Calendar #### Call Dialers & Recorders * Aircall * CloudTalk * Dialpad * Orum * Outreach * RingCentral * Salesloft * Vonage * Zoom #### Conversation & Revenue Intelligence Platforms * Attention * Chorus by ZoomInfo * Clari * Clari Copilot * Gong * Salesloft CI ## Momentum Permissions Overview Momentum installation is straightforward and involves three key steps. Here's a breakdown of the necessary system accesses and permissions needed: ### Step 1: Installing the Momentum Slack App **Permissions Required**: * Slack system administrator permissions **Installation Process**: * Click the provided link to install Momentum in Slack. **What does the installation do?** * Momentum will access specific Slack permissions, such as posting messages or inviting participants to channels. The app will appear as a Slack app for your team to interact with but won't proactively contact team members. **Why is this necessary?** * Momentum's primary interactions and workflows are built on top of Slack. This integration ensures team members can efficiently use Momentum to update deals and receive notifications and call notes. **Warnings and Considerations**: * Momentum will not read messages or history from channels it's not invited to. It doesn't need access to every channel in your organization. * Momentum will not impersonate Slack users. Some operations such as creating new channels will operate with the same level of permissions as a Workspace Member. Limiting access to these features will result in loss of functionality. ### Step 2: Granting Momentum Access to Salesforce **Permissions Required:** * Any user with the Customize Application permission may install Momentum **Installation Process:** * Authentication and installation takes place via OAuth. There's no need to change your Salesforce configuration or install a new package. **What does the installation do?** * Momentum is a highly flexible tool purposefully designed to agentically improve your specific deal cycle. As such, there are different permission configurations based on the use case. **Permission Requirements by Product:**
| Permission | Installation | CI, Summary Agents, and Signal Agents | CRM Agents | CRM Agents (Advanced) | | ---------------------------- | :----------: | :-----------------------------------: | :--------: | :-------------------: | | **Installation Permissions** | | | | | | Customize Application | ✅ | ✅ | ✅ | ✅ | | **Read Access to Objects** | | | | | | Account | | ✅ | ✅ | ✅ | | Lead | | ✅ | ✅ | ✅ | | Opportunity | | ✅ | ✅ | ✅ | | Contact | | ✅ | ✅ | ✅ | | OpportunityContactRole | | ✅ | ✅ | ✅ | | Event | | ✅ | ✅ | ✅ | | Task | | ✅ | ✅ | ✅ | | User | | ✅ | ✅ | ✅ | | **Edit Access** | | | | | | Fields Momentum updates | | | ✅ | ✅ | | **System Permissions** | | | | | | Send Outbound Messages | | | | ✅ | | Manage Flows | | | | ✅ | | View All Data | | | | ✅ | | Modify Metadata | | | | ✅ | | View Setup and Configuration | | | | ✅ | | Run Reports | | | | ✅ |
**Notes:** * **Installation:** Basic OAuth installation only requires Customize Application permission * **CI, Summary Agents, and Signal Agents:** Requires read access to core Salesforce objects * **CRM Agents:** Adds edit permissions for fields that Momentum will update * **CRM Agents (Advanced):** Includes Notifications + Retropilot features using event-based architecture with flows and outbound messages. Required by Momentum to monitor Salesforce system limits and usage. **Why is this necessary?** * Salesforce integration allows Momentum to read and update CRM data, ensuring your deal information stays current and accurate across all systems. **Warnings and Considerations:** * Permission levels vary based on the Momentum features you plan to use. Advanced features require additional Salesforce permissions for optimal functionality. ### Step 3 (Optional): Granting Momentum Access to Video Conferencing or Call Recording Tools **Permissions Required**: * Video conferencing administrator permissions **Installation Process**: * Review the documentation for your specific call recording tool. **What does the installation do?** * This step allows Momentum AI to collect customer call data, including titles, attendees, transcripts, and video recordings. **Why is this necessary?** * To analyze customer calls, connect those calls with CRM objects, and update the CRM accordingly, Momentum needs to record and transcribe the calls. Calendar details help detect new meetings and their attendees, while call transcripts provide the content for analysis. **Warnings and Considerations**: * Depending on your tools, this step may require only administrator access (for Zoom, Gong, Dialpad, and Copilot), or individual reps' calendar access. These permissions allow Momentum to read calendar events and meetings. ### Specific Requirements for Call Recording Tools: * **Attention**: Requires an Attention API Key. * **Aircall**: Requires an Aircall Integration Token. * **Chorus by ZoomInfo**: Requires an API Key and a service account to import video recordings (if applicable). * **Clari Copilot**: Requires a Clari Copilot Integration Token. * **CloudTalk**: Requires a CloudTalk Integration Token. * **Dialpad**: Requires a Dialpad Integration Token. * **Gong**: Requires a Gong Technical Administrator account. * **Google Meet**: Requires a Google Workspace admin. * **Orum**: Requires Orum administrator access and the Webhooks add-on enabled on your Orum plan. * **Outreach**: Requires an Outreach Organization Administrator account. * **RingCentral**: Requires RingCentral Super Admin access with automatic call recording enabled. * **Salesloft**: Requires a Salesloft Organization Administrator account. * **Zoom**: Requires a Zoom Business One license and a Zoom Administrator. * **Vonage Contact Center**: Requires API credentials with the necessary scopes and Vonage admin access. ## Conclusion By following these steps, you'll ensure that Momentum integrates seamlessly with your existing systems, providing your team with enhanced capabilities for managing customer interactions and workflows. If you have any questions or require further assistance, our support team is here to help. # Momentum's Proof of Concept (POC) Process Source: https://docs.momentum.io/momentum-proof-of-concept-poc-process ## Overview At Momentum, our Proof of Concept (POC) process is designed to be straightforward, efficient, and minimally disruptive to your team. This document outlines the key stages, goals, common concerns, and overall process to provide a clear understanding of how we operate. ## Key Stages of the POC The Momentum POC spans two weeks and involves three key meetings: 1. **Installation Meeting (45 minutes)** Objective: Set up the initial system and integrate Momentum with your existing tools. Activities: * Installation of the Momentum application. * Initial configuration and setup of call extractions. 2. **Check-In Meeting (30 minutes)** Objective: Review prompts and extractions to ensure alignment with your needs. Activities: * Discuss initial findings from Momentum's AI extractions. * Adjust prompts and workflows as necessary. 3. **Go/No-Go Session (30 minutes)** Objective: Evaluate the results of the POC and decide on the next steps. Activities: * Review the impact and effectiveness of the POC. * Make a go/no-go decision based on the outcomes. ## Goals and Success Metrics The primary objectives of our POC process are: * **Prove the quality of Momentum's AI extractions:** Demonstrate the accuracy and relevance of the data extracted by our AI. * **Showcase our team's support:** Provide a taste of how our team operates and supports customers. * **Reduce administrative workload:** Highlight the impact of our workflows in minimizing your team's day-to-day administrative tasks. * **Improve pipeline visibility:** Illustrate how our product enhances the visibility of your sales pipeline. ## Common Questions and Concerns We understand that stakeholders may have concerns about the POC process. Here are some common questions and our responses: **Will the POC take too much of my time?** No, the POC is designed to be efficient, requiring only three short meetings over two weeks. **Will I need to distract my team during the POC?** No, the POC can run with minimal involvement from your team. Reps can engage with Momentum notes and field extractions, but it is not mandatory. **Do I need to connect Momentum to production environments?** Yes, but Momentum ensures data privacy and security with industry-standard certifications and practices. **Does Momentum offer data privacy assurances and hold certifications?** Yes, Momentum adheres to strict data privacy standards and holds the necessary certifications to ensure your data is secure. **Do I need to run this through infosec and procurement?** It is advisable to consult with your infosec and procurement teams, but our process is designed to be straightforward and compliant with standard security protocols. We're happy to setup agreements if needed for a POC to be put in place. ## Process Overview Throughout the POC, you will be assigned a dedicated Solutions Architect who will manage the process and implement the necessary prompts and workflows. Our goal is to deliver value to you while handling the majority of the workload, ensuring the POC is approachable and efficient. You will have access to our admin panel, allowing you to review or change any configurations as needed. However, our team will take the lead in managing the process to ensure a seamless experience. **Steps Involved:** 1. **Assigning Solutions Architect:** A dedicated Solutions Architect from Momentum will be assigned to oversee the POC. 2. **Initial Setup:** Your Momentum Solutions Architect will guide you through the installation and handle the initial configuration. 3. **Ongoing Management:** The Solutions Architect will design and manage the prompts and workflows for your initial setup, ensuring they deliver value. 4. **Review and Adjust:** You will have the opportunity to review and adjust configurations as needed. 5. **Final Evaluation:** At the end of the POC, a go/no-go decision will be made based on the outcomes. ## Conclusion Momentum's POC process is designed to be simple, efficient, and minimally disruptive. We handle most of the workload, allowing you to focus on evaluating our product's value to your organization. Ready to get started? Contact us today to schedule your POC and experience the benefits of Momentum firsthand. # Security and Privacy Source: https://docs.momentum.io/momentum-security At Momentum, we take the security and privacy of your data very seriously. Our robust security measures ensure that your information is protected at every stage. Below is a brief overview of our security practices and a link to our comprehensive security portal for more detailed information. Please visit our [Security Portal](https://security.momentum.io/). This portal provides comprehensive details on how we safeguard your data and maintain your privacy. ### Data Encryption We use advanced encryption methods to protect your data both in transit and at rest. This ensures that your sensitive information is secure from unauthorized access and breaches. ### User Access Controls Momentum allows you to set up and manage user roles and permissions, ensuring that only authorized personnel have access to critical data. This helps maintain the integrity and confidentiality of your information. Users can setup MFA and SSO for their own administrators and end users to access Momentum. ### Privacy Policies We adhere to strict privacy policies that govern how we handle your data. Our policies are designed to protect your personal information and provide transparency on how it is used. You can manage your data privacy settings and request data deletion in accordance with our policies. As part of our contract, we review and establish DPAs with all of our customers and vendors. ### Security Certifications and Compliance Momentum complies with industry-standard security certifications and regulations to ensure your data is handled with the highest level of security. Our practices are regularly audited to maintain compliance with these standards. ### Security Portal For more detailed information about our security measures, including our encryption practices, user access controls, privacy policies, and compliance certifications, please visit our [Security Portal](https://security.momentum.io/). # Onboarding Checklist Source: https://docs.momentum.io/onboarding-checklist Track and complete new-org setup from a single, centralized page. ## Overview The Onboarding Checklist is a dedicated page in the Momentum admin app that brings every new-org setup step into one shareable view. Instead of bouncing between the admin app, the user web app, and multiple integrations pages, Org Admins and Editors can see the status of every required integration, invite their team, and activate starter workflows from a single location. This page is designed to: * Give new customers one shareable URL they can return to during setup. * Provide a clear, at-a-glance view of what is connected and what still needs attention. * Enable self-serve configuration for the most common onboarding tasks. ## Prerequisites To use the Onboarding Checklist, you must be signed in as an **Organization Admin** or **Editor**. See [User Roles and Permissions](/user-roles-and-permissions) for details on these roles. ## Accessing the Onboarding Checklist 1. Sign in to the Momentum admin app at [app.momentum.io](https://app.momentum.io). 2. Open the **Settings** tab in the left-hand navigation. 3. Select **Onboarding Checklist**. You'll be redirected to the `/admin/onboarding` route. The resulting URL can be shared directly with other Org Admins or Editors so they can pick up setup where you left off. Onboarding Checklist ## Checklist Steps The Onboarding Checklist surfaces each setup step as a card, along with its current status. Steps can be completed in any order, and the checklist will update automatically as integrations are authorized or users are invited. ### Service Account Configure a dedicated service account for org-level integrations. Using a service account keeps org-wide connections stable and independent of any single user's credentials or license. ### Salesforce Connection Connect your Salesforce instance so that Momentum can sync CRM data, map calls to opportunities, and power deal-focused workflows. For deeper detail on authorizing Salesforce, see [Step 3 of the Installation Guide](/how-to-install-momentum#step-3-authorize-momentum-in-salesforce). ### Calendar Connect a calendar provider so Momentum can track scheduled meetings, join calls as needed, and associate recordings with the right events. Available options: * Google Calendar * Microsoft Outlook Calendar — see [Microsoft Outlook Integration](/momentum-ai-microsoft-outlook-integration) * Google Drive ### Calling Platform Connect your video conferencing and dialer tools so Momentum can ingest calls from the platforms your team already uses. **Video conferencing and conversation intelligence** * Zoom — see [Zoom Integration](/momentum-ai-zoom-integration) * Gong — see [Gong Integration](/momentum-ai-gong-integration) * Clari Copilot — see [Clari Copilot Integration](/momentum-ai-clari-copilot-integration) * Chorus — see [Chorus Integration](/momentum-ai-chorus-integration) **Dialers** * Dialpad — see [Dialpad Integration](/momentum-ai-dialpad-integration) * Aircall — see [Aircall Integration](/momentum-ai-aircall-integration) * CloudTalk — see [CloudTalk Integration](/momentum-ai-cloudtalk-integration) * Orum — see [Orum Integration](/momentum-ai-orum-integration) * Vonage — see [Vonage Integration](/momentum-ai-vonage-integration) * RingCentral — see [RingCentral Integration](/momentum-ai-ringcentral-integration) ### Messaging Platform Connect the messaging tool your team uses to receive call summaries, signals, and other Momentum notifications. Available options: * Slack * Microsoft Teams — see [Microsoft Teams Integration](/momentum-ai-microsoft-teams-integration) * Email (via Microsoft Outlook) — see [Microsoft Outlook Integration](/momentum-ai-microsoft-outlook-integration) ### Invite Users Invite teammates to Momentum directly from the checklist by sending email invitations. You can also manage previously invited users from this step. For an overview of which role to assign, see [User Roles and Permissions](/user-roles-and-permissions). ### Activate Workflows Enable templated workflows so your team starts receiving value immediately after setup. The checklist includes starter templates for: * **AI Meeting Summary** — see [Setting Up Call Summaries](/setting-up-call-summaries). * **Deal Risk Smart Clips** — see [Signals, Clips & Tags](/ai-prompting-signals-and-tags). Workflows can be toggled on or off directly from the Onboarding Checklist, and the full configuration for each workflow remains available on its dedicated page. ## Need More Help? If a step is blocked, missing, or behaving unexpectedly, contact our support team at [support@momentum.io](mailto:support@momentum.io) and we'll help you finish setup. # Optimizing Sales Playbooks Source: https://docs.momentum.io/optimizing-sales-playbooks Implement and refine your sales playbooks using Momentum's Autopilot and Deal Rooms. Ensure consistent execution of sales strategies and improve deal management by automating key processes. Utilize the Playbook product within Deal Rooms to guide your team through each stage of the sales process, ensuring that Autopilot focuses on capturing the right fields at the right stage and type of call for each deal. ### Why Optimizing Sales Playbooks Matters A well-optimized sales playbook is essential for ensuring that your sales team executes strategies consistently and effectively. It provides a structured approach to sales, helping reps navigate through various stages of the sales cycle with clear guidance and actionable steps. By leveraging automation and centralized management, Momentum enables you to implement and refine your sales playbooks, ensuring that every deal is handled with precision and consistency. ### Key Features for Optimizing Sales Playbooks 1. **Autopilot** * **Automatic Data Capture:** Autopilot listens to calls and automatically captures relevant information, ensuring that key fields are updated in your CRM. * **Context-Aware Prompts:** Configure Autopilot to focus on the most important fields based on the stage of the opportunity and the type of call, ensuring that the right information is captured at the right time. * **Consistent Execution:** By automating data capture, Autopilot ensures that your sales playbook is followed consistently across all deals. [Autopilot](/autopilot) 2. **Deal Rooms** * **Centralized Deal Management:** Create Deal Rooms for each opportunity, consolidating all relevant information, communications, and updates in one place. * **Playbook Integration:** Utilize the Playbook product within Deal Rooms to guide your team through each stage of the sales process, providing clear instructions and next steps. * **Automatic Invites:** Set up automatic invites to bring the right stakeholders into each deal. By aligning with your sales playbook, this improves collaboration across your organization and ensures everyone is on the same page. [Deal Rooms and Account Rooms](/how-to-create-a-deal-room-and-manage-opportunities) ### Step-by-Step Guide to Optimizing Sales Playbooks 1. **Setting Up Autopilot** * Navigate to the Autopilot section in the Momentum admin dashboard. * Configure AI prompts to capture the specific data fields required for each stage of the sales cycle. * Set up context-aware prompts that adjust based on the opportunity stage and type of call, ensuring that the most relevant information is captured. 2. **Creating and Using Deal Rooms** * Go to the Deal Rooms section in the Momentum admin dashboard. * Create a Deal Room for each key opportunity, inviting relevant stakeholders from the sales, support, and management teams. * Use Deal Rooms to centralize all deal-related information, making it easy for teams to access and update as needed. * Integrate the Playbook product within Deal Rooms to provide clear guidance and next steps for each stage of the sales process. 3. **Utilizing the Playbook Product** * Within each Deal Room, configure the Playbook product to outline the steps and actions required for each stage of the sales cycle. * Ensure that the Playbook provides clear instructions on the key fields to capture, the questions to ask, and the actions to take during each type of call. * Regularly review and update the Playbook to reflect best practices and new strategies, ensuring continuous improvement. 4. **Monitoring and Refining Processes** * Regularly review the data and insights captured by Autopilot to ensure they align with your sales playbook. * Adjust AI prompts and playbook instructions as necessary to improve accuracy and relevance. * Use Momentum's reporting features to track the effectiveness of your sales playbook and identify areas for further optimization. ### Benefits of Optimizing Sales Playbooks * **Consistent Execution:** Ensure that your sales team follows a structured approach, leading to more predictable and successful outcomes. * **Improved Deal Management:** Centralized Deal Rooms and automated updates keep all stakeholders informed and aligned, improving overall deal management. * **Increased Efficiency:** Automate key processes and reduce the time spent on manual data entry, allowing sales reps to focus on selling. * **Enhanced Training:** Use the Playbook product to provide clear guidance and training for new and existing reps, ensuring everyone follows best practices. * **Better Decision-Making:** Leverage data captured by Autopilot to make informed decisions and continuously refine your sales strategies. ### Customer Testimonial *“Momentum has seriously amped up our business effectiveness. As someone deeply entrenched in account management, harnessing Momentum's AI for sticking to our sales playbook has been superb. It's like having a forward-thinking sidekick that notches up both workflow execution and automation.”* — Michael Wilde, Enterprise Account Executive @ Honeycomb By leveraging Momentum's Autopilot and Deal Rooms, you can ensure that your sales playbooks are implemented and executed effectively, leading to improved sales efficiency and better deal management. For further assistance or to discuss custom workflows, please contact our support team. # Recording Consent Source: https://docs.momentum.io/recording-consent ## Overview Momentum keeps everyone informed whenever a sales call will be recorded. When Momentum is set to record a meeting, it automatically updates the calendar event with a link to a recording consent page. Attendees who click this link see your recording disclaimer and a button that redirects them to the scheduled Zoom, Google Meet, Microsoft Teams, or Webex meeting. By proceeding through the consent page, participants acknowledge that the call will be recorded. Recording Consent Automatic Calendar Updates ### Prerequisites * Each user of the Recording Consent feature must be authenticated with a supported calendar provider (Google Calendar or Microsoft Outlook). This is required for Momentum to update calendar events with the recording consent link. * An AI license is required to use this feature. ### Key Benefits * Automatic calendar updates ensure that invitees receive notice of recording. * Works seamlessly with Zoom, Google Meet, Microsoft Teams, and Webex. * Helps your team stay compliant with recording consent requirements. ### Customizing the Consent Page Recording Consent Automatic Calendar Updates Admins can tailor the messaging and logo shown on the consent screen. Head to **Settings → Recording Consent** in the Momentum admin dashboard to update the text that attendees see and upload your company logo. To enable recording consent links in your calendar events, reach out to your Momentum representative. ### How It Works When an organization has the Momentum consent screen enabled, meeting participants will be directed to the consent collection page prior to joining the meeting. Recording Consent Page * If the participants gives consent, they may click the "Yes, join meeting" button to be redirected to the call immediately. * If the participant wishes to reject consent, they may click the "Reject Consent" button, which will prompt up a pop-up window asking the participant to provide their email. Email Verification Page The Momentum Bot, if present, will be removed from the call if and only if the user is a **recognized participant**. A recognized participant is defined as: 1. A participant whose email address is in the meeting's invitee list **OR** 2. A participant who shares the same email domain as the host of the meeting Before leaving the call, the Momentum Bot will send a message in call chat indicating that it is leaving the call due to consent rejection. The host of the meeting will also be notified of the consent denial through email. Chat Message # Recording Consent Report Source: https://docs.momentum.io/recording-consent-report Recording Consent Page ## Overview The Recording Consent Report lets Organization Admins see how many participants accepted or rejected recording consent per meeting. It displays the meeting ID, title (with an “Untitled Meeting” fallback), and acceptance/rejection counts. Admins can opt to either see all meetings in a set date range (up to 31 days) or view a specific meeting by providing the meeting ID. The report also supports the option of exporting the results as a CSV. ### Prerequisites * You must be an Organizaton Admin * The organization must have the Momentum meeting recording consent page enabled * When selecting a date range, the range must be less than 31 days ### Step-by-Step 1. Sign in to the [Momentum admin dashboard](https://app.momentum.io/admin/). 2. In the left navigation, go to **Debug Console → Meeting Consent Report**. 3. Pick a date range (max 31 days). * (Optional) Enter a specific Meeting ID. If a Meeting ID is provided, it will disregard the set date range and prioritize searching the specified meeting. 4. Click Request New Report. The table populates with the matching rows. 5. Click Refresh List if you adjust filters and want to re-run. 6. Click Download to export the current table as CSV. # Setting Up Retropilot Source: https://docs.momentum.io/retropilot-setup A guide to configuring Retropilot to trigger extractions based on Salesforce events and historical call/email data. Triggers after each call/email to analyze its content in real-time. **You are here.** Triggers on a Salesforce event and analyzes all historical conversations. Triggers manually to run on a large set of records that match your defined criteria. # Setting Up Retropilot Retropilot, part of the Autopilot Suite, allows you to trigger powerful AI extractions based on **Salesforce events**. Unlike the real-time Autopilot, Retropilot analyzes all [historical conversational data](/conversational-data-sources) within a specified timeframe to provide comprehensive insights right when a key moment occurs in your CRM. ## How Retropilot Works Retropilot operates on a simple but powerful flow: a Salesforce event triggers an AI analysis of historical conversational data, which then results in an update to a Salesforce field. ```mermaid theme={null} graph LR A(Salesforce Event) --> B{Retropilot Trigger}; B --> C((Analyze
History)); C --> D[/Run AI Prompt/]; D --> E>Update Field]; ``` ## Use Cases for Retropilot * **New Opportunity Stage**: When an opportunity moves to "Proposal," automatically summarize all previous call notes related to budget and timeline. * **Account Ownership Change**: When a new account owner is assigned, generate a summary of the customer's key pain points and historical issues. * **Pre-Renewal Analysis**: 90 days before a renewal date, compile a list of all mentioned competitors and feature requests from the past year. ## Step-by-Step Configuration ### Step 1: Access the Retropilot Section 1. Log in to your [Momentum admin dashboard](https://app.momentum.io/admin/autopilot-extractions). 2. Navigate to the **Autopilot** section and select the **Retropilot** tab. 3. Click **"New Retropilot Extraction"** to begin. ### Step 2: Define the Salesforce Trigger Event This is the core of Retropilot. You'll define the specific Salesforce event that initiates the extraction. In certain cases, you may instead need to [configure an advanced self-managed Salesforce Flow](/user-managed-salesforce-flows). * **Object**: Select the Salesforce object (e.g., Opportunity, Account, Case). * **Trigger Action**: * `On Create`: Runs when a new record of the selected object is created. * `On Update`: Runs when a record is modified. * `On Create & Update`: Runs for both creation and modification. Retropilot Configuration Interface To prevent the trigger from firing on every small change, you must specify field conditions when using `On Update`. * **Field**: Choose the field to monitor (e.g., `StageName`, `OwnerId`). * **Condition**: * `Changes to`: Triggers only when the field's value changes *to* a specific value (e.g., StageName changes to "Closed Won"). This is the recommended and most precise way to control triggers. * `Is`: Triggers if the field has a certain value after the update. Use with caution as this can fire on unrelated record updates. **Example Trigger:** ```yaml theme={null} Object: Opportunity Trigger Action: On Update Field: StageName Condition: Changes to "Negotiation" ``` ### Step 3: Set the Time Window Define the period of [historical conversational data](/conversational-data-sources) that Retropilot should analyze. This can be anything from the last 7 days to the entire history of the record. ### Step 4: Write Your AI Prompt This prompt will guide the AI in its analysis of the historical conversational data. Make sure your prompt is clear about what you want summarized or extracted. **Example Prompts:** * **For a "Negotiation" Stage Trigger**: ```text theme={null} "Review all calls and emails from the last 90 days for this opportunity. Summarize all discussions related to budget, key decision-makers, and final blockers. List the key contacts involved." ``` * **For a "New Owner" Trigger**: ```text theme={null} "Analyze all historical call data for this account. Provide a summary of the top 3 pain points mentioned and any outstanding support tickets or unresolved issues." ``` ### Step 5: Configure Save Behavior Choose how the extracted data is saved to Salesforce, just like a regular Autopilot extraction. * **Confirm to Write**: Requires manual approval in Slack. * **Write if Empty**: Only writes if the target field is blank. * **Automatic Write**: Always writes the new value. **Handling Records with No Context:** You can configure what happens when no relevant [historical conversational data](/conversational-data-sources) is found for a record: * **Skip**: Nothing will be written to Salesforce (default behavior) * **Write Reason**: Write a message explaining why no data could be extracted * **Custom Text**: Write custom text that you specify This ensures fewer missed write-backs and maintains data consistency even when context is missing. This setting still respects your save behavior configuration. Confirm to Write, Write if Empty, and Automatic Write settings will still apply. Retropilot automatically truncates extracted values to fit the target field's maximum length in Salesforce. Retropilot Configuration Interface ### Step 6: Test and Activate * **Preview**: Test your Retropilot configuration against existing Salesforce records that meet your trigger criteria to see what the output would look like. * **Activate**: Once you're confident, activate the Retropilot rule to have it run automatically based on your trigger. Retropilot Configuration Interface # Salesforce Event Mapping Source: https://docs.momentum.io/salesforce-event-mapping Users can now toggle the option to map their calls to Salesforce Event records. Momentum admins can now control whether Momentum call logs are written to Salesforce Event records. Use this toggle if you need Events for reporting or automation, or leave it off if you prefer to rely on Tasks, Calls, or third-party logging. Here are the steps to start mapping calls to Salesforce events ## Prerequisites * You must be an **admin** user to view or change this organization-wide setting. * Your Salesforce integration must already be connected in Momentum. ## Enable or disable the Salesforce Event toggle 1. Sign in to the [Momentum admin dashboard](https://app.momentum.io/admin/). 2. In the left navigation, go to **Settings → Momentum AI**. Salesforce Mapping Home Screen 3. Scroll down until you see the **Momentum Call Salesforce Mapping** section. 4. Use the toggle to enable or disable Event mapping. Salesforce Mapping Section 5. Select **Save** to apply the change for the entire workspace. ## What happens after you toggle the setting * **When enabled:** Upcoming calls that Momentum processes can be mapped to Event records, allowing you to run autopilot classic workflows on Event related fields * **When disabled:** Event mapping is unavailable, but Momentum continues to log any other Salesforce records you configure (Opportunities, Accounts, Contacts, Leads) * Changes apply prospectively. Calls logged before enabling the toggle will not automatically backfill into Events. # Salesforce Notifications Source: https://docs.momentum.io/salesforce-notifications Welcome to Salesforce Notifications by Momentum! Stay on top of your sales process with real-time Slack notifications and alerts. Whether it's sending reports, pipeline updates, or Closed Won messages, Momentum is the easiest and fastest way to create seamless notifications between Salesforce and Slack. ### Key Features: * **Smart Slack Notifications**: Receive automatic notifications directly in Slack, triggered by customer call insights and Salesforce updates. * **Customizable Workflows**: Use pre-built notification workflows or create your own to match your sales process. ### Customer Testimonial: *"It's a joy partnering with the Momentum team! We use Momentum automations for core notification workflows, and our Enterprise sales team uses the impressive Momentum AI features every day."* — Catherine Hsieh Director, Sales Strategy & Operations @ Jasper ## Getting Started ### Install Momentum To begin using Salesforce Notifications, you first need to install the Momentum app. Follow the instructions in the [Momentum Installation Guide](/how-to-install-momentum) to set up the app and configure the necessary permissions. ### Set Up Your First Notification **Step 1: Set Object and Record Criteria** First, specify which Salesforce object and records you want to monitor. * **Select the Salesforce Object**: Choose the object you wish to monitor, such as Contacts, Accounts, or Opportunities. Any object, custom or standard, is supported. * **Define the Record Criteria**: Specify the criteria that a record must meet to trigger a notification. This could be based on changes to a specific field, or a combination of fields reaching certain values. Any non-formula field that can be accessed through a lookup to the root record can be used as criteria. In certain cases, you may instead need to [configure an advanced self-managed Salesforce Flow](/user-managed-salesforce-flows). Untitled **Step 2: Customize Your Notification** Once you've identified the records to monitor, the next step is customizing how you receive notifications. * **Customize the Message**: Tailor the notification message to include relevant information. You can leverage details such as the record's name, the specific change made, and who made the change. Take full advantage of rich text editing, such as bolding, embedded links, or emojis. * **Include Record Details**: Include CRM fields directly into the message or as an add-on at the bottom of your Slack message. * **Include Options for Action**: Give users the fields they need to update directly from Slack. Define fields with predefined values, or links to the records directly as part of the message. Untitled **Step 3: Set Your Destination** The final step involves specifying where the notifications should be sent. Notifications can be sent to a variety of locations, including Slack channels, DMs, Deal Rooms, and more. Be sure to take advantage of active user lookup to send to the relevant Salesforce users. That's it! You've just configured your first notification. 🎉 Untitled ## Advanced Use Case: Scheduled Path for Notifications As your notification strategy matures, you may want to set up a schedule for your notifications to be delivered on a specific date derived from a date field in the record. This allows you to trigger notifications based on an event but deliver them at a later time that makes more sense for your workflow. ### Example: Reminder for Account Executives to Qualify an Opportunity **Scenario**: You want to remind account executives to qualify an opportunity multiple days after the initial meeting has taken place. The scheduled paths feature allow you to deliver the same notification multiple times at specific intervals after an event should have been handled. If the rep updates the opportunity and qualifies or disqualifies it, further scheduled path deliveries will not execute. CleanShot 2024-06-22 at 07.50.57@2x.png CleanShot 2024-06-22 at 07.55.08@2x.png ## Advanced Use Case: Conditional Delivery Conditional delivery allows you to send notifications to multiple destinations with specific conditions applied to each destination. This is useful when you need to deliver notifications differently based on certain criteria. ### Example: Close-Won Notification **Scenario**: You want to send a Close-Won notification to both your Customer Success team in a public Slack channel and your Chief Revenue Officer (CRO). However, the CRO should only receive notifications if the deal meets a minimum ARR threshold. CleanShot 2024-06-22 at 07.56.52@2x.png ## Advanced Use Case: Action Buttons with Pre-Set Values Action buttons in Slack notifications allow users to update Salesforce records can have preset values records will always receive, streamlining the process for your team and ensuring consistency. Pro tip: enable your sales reps to take alternative actions on record by using different Update Object buttons with different set of preset values. Use colors to help visualize these actions. ### Example: Update Multiple Fields with Preset Values **Scenario**: You want your reps to update Salesforce records efficiently. By using action buttons in Slack, reps can apply predefined changes to multiple fields without remembering the exact values or navigating Salesforce manually. CleanShot 2024-06-22 at 08.02.03@2x.png CleanShot 2024-06-22 at 07.58.28@2x.png ## FAQs ### What are Salesforce Notifications? Salesforce Notifications are real-time alerts and updates sent to Slack, triggered by specific actions or changes within your Salesforce environment. ### How do I customize notifications? You can customize notifications by selecting the Salesforce object and record criteria, tailoring the notification message, and setting the destination in Slack. ### Can I share customer insights with other teams? Yes, you can proactively share important customer insights with your product and marketing teams through Slack notifications. ## Security Your data security is our priority. Momentum adheres to strict security standards and practices to ensure your information is protected. For more details, refer to our [Security Overview](https://security.momentum.io/). ## Conclusion Thank you for choosing Salesforce Notifications by Momentum. We are excited to help you streamline your sales process and keep your team informed with real-time updates. If you have any questions or need assistance, feel free to contact our support team at [support@momentum.io](mailto:support@momentum.io). Ready to get started? Configure your first notification now and see the difference it makes! # Scheduled Notifications Source: https://docs.momentum.io/scheduled-notifications Welcome to Momentum's Scheduled Notifications. This feature is designed to help you stay ahead of your contract renewals and pipeline management by delivering timely alerts directly to your team. No more last-minute scrambles—just proactive engagement and seamless renewals. CleanShot 2024-06-25 at 18.16.47@2x.png ### Key Benefits * **Reduces Last-Minute Scrambles**: Your team will always be prepared for renewals. * **Enhances Customer Relationships**: Shows clients that you are proactive and attentive. * **Streamlines Processes**: Makes your renewal process seamless and efficient. ## Primary Use Cases ### Sales Pipeline Management * **Pipeline Updates**: Remind reps to keep their pipeline current. * **Renewal Alerts**: Notify customer success teams about accounts nearing renewal. * **Managerial Insights**: Inform managers about deals that are out of date or not meeting specific criteria. ### CRM Integration * **Batch Updates**: Update Salesforce records directly from Slack. * **Custom Objects & Fields**: Manage any types of records, including custom objects and fields, via Slack messages and pagination. ## Integration ### Salesforce and Slack Integration * **Slack Native Interface**: Seamlessly integrates with Slack to provide a user-friendly interface. * **First-Class CRM Updates**: Update Salesforce without leaving Slack, ensuring your CRM remains up-to-date. * **Real-Time Notifications**: Receive alerts at the right time to ensure proactive management. ## Getting Started with Scheduled Notifications 1. **Install Momentum** To begin using Salesforce Scheduled Notifications, you first need to install the Momentum app. Follow the instructions in the [Momentum Installation Guide](/how-to-install-momentum) to set up the app and configure the necessary permissions. **Create a New Scheduled Notification**: * In the Momentum administrator, go to the Scheduled Notifications section. * Click the button to create a new notification. **Setup Salesforce Rules**: * The first section involves setting up Salesforce rules. * Here, you can specify which records will trigger the notification based on criteria such as using a Reconnect Date field to begin a process of reconnecting with your lost Opps. Combine multiple filters using logical operators (AND/OR) to refine your triggers. CleanShot 2024-06-22 at 07.36.10@2x.png **Configure the Notification's Content**: * The second section involves configuring the content of the notification. * Customize the message to include relevant Salesforce fields and action buttons. This ensures that the notification is informative and actionable, allowing users to understand the importance of the records and make necessary updates directly from Slack. CleanShot 2024-06-22 at 07.38.21@2x.png **Set the Delivery Channel**: * The final section involves configuring the delivery location for this specific notification workflow. * Choose where the notification should be sent, such as specific Slack channels, group DMs, or any other Momentum component. Set up automatic delivery to ensure timely insights. * Pro-tip: Split the records of your Scheduled Notification between a group of users who can be traced from your records using their Salesforce ID. This allows you to deliver the right records to the right person and nobody else. CleanShot 2024-06-22 at 07.38.47@2x.png By following these steps, you can effectively set up and utilize scheduled notifications to keep your team informed and proactive in managing important records. ## Conclusion Momentum's Scheduled Notifications is your key to efficient pipeline management and improved CRM data hygiene. By leveraging automated alerts and seamless integration with Salesforce and Slack, you can ensure your team stays ahead of the game, improving retention rates and customer loyalty. Ready to take the next step? # Scheduled Reports Source: https://docs.momentum.io/scheduled-reports Scheduled Reports by Momentum allows you to deliver Salesforce reports on a specific cadence directly into your Slack channels or to specific users. This feature ensures that your team stays updated with important data without the need to constantly check Salesforce manually. CleanShot 2024-06-25 at 18.18.37@2x.png ### Key Features: * **Automated Delivery**: Schedule reports to be delivered at regular intervals (daily, weekly, monthly) to keep your team informed. * **Slack Integration**: Receive reports as convenient tables in Slack, making it easy to review key metrics quickly. * **Direct Links**: Each report includes a link back to Salesforce for in-depth analysis and detailed review. ### Getting Started ### Set Up Your First Scheduled Report **Step 1**: Select the Report * **Choose a Salesforce Report**: Navigate to the Scheduled Reports section in the Momentum administrator and select the report you want to schedule. This can be any standard or custom report in your Salesforce instance. **Step 2**: Define the Schedule * **Set the Cadence**: Determine how often you want the report to be delivered (e.g., daily, weekly, monthly). * **Choose the Time**: Specify the exact time of day the report should be sent to ensure it aligns with your team's workflow. * **Select Days**: For monthly reports, choose which day of the month the report should be sent. **Step 3**: Customize the Notification * **Customize the Message**: Tailor the notification message to include relevant information. You can leverage details such as the report name, the specific metrics included, and any additional context for the team. * **Include Report Details**: Render the report as a convenient table in Slack for quick review. Include a link back to Salesforce for in-depth analysis. **Step 4**: Set Your Destination * **Select Slack Channels or Users**: Choose the Slack channels or individual users who should receive the report. * **Pin Messages**: Optionally, pin the report message in Slack for easy access. That's it! You've just configured your first scheduled report. 🎉 ### Example Use Case: Monthly SDR Meeting Report **Scenario**: You want to keep your sales development team updated with a monthly meeting report. This report includes metrics such as meeting counts by SDR, lead sources, and qualification tasks. CleanShot 2024-06-22 at 08.11.19@2x.png ### FAQs **What are Scheduled Reports?** Scheduled Reports are automated deliveries of Salesforce reports to Slack, helping teams stay updated with important data without manual effort. **How do I customize the report delivery?** You can customize the report delivery by selecting the Salesforce report, defining the schedule, and configuring the Slack channels or users who will receive it. **Can I include additional context in the Slack message?** Yes, you can add a personalized message to provide context or instructions for your team along with the report. # Setting Up Call Summaries Source: https://docs.momentum.io/setting-up-call-summaries Step-by-step guide to configure and set up call summaries in Momentum. # Setting Up Call Summaries This guide walks you through the technical setup process for Momentum's Call Summaries feature. Call Summaries automatically generate detailed notes from sales calls and deliver them to your team via Slack, Microsoft Teams, or Salesforce. Slack Summaries Notification ## Prerequisites Before setting up Call Summaries, ensure you have: * [Momentum AI installed with your preferred call provider](/how-to-install-momentum) * Admin access to your Momentum Organization * Slack workspace configured * Salesforce integration active ## Step-by-Step Setup ### Step 1: Access the Summaries Section 1. Log in to your [Momentum admin dashboard](https://app.momentum.io/admin/notifications/ai-summary) 2. Navigate to the **Summaries** section in the left sidebar 3. Click **"New AI Call Notification"** to begin the setup process ### Step 2: Configure Salesforce Rules The first section involves setting up Salesforce rules to determine which calls will be processed by this summary workflow. **Configure Call Detection Rules:** * **Object Type**: Select the Salesforce object (Opportunity, Account, Lead) this summary should apply to * **CRM Conditions**: Set specific CRM conditions to filter calls to be summarized **Example Configuration:** ```yaml theme={null} Object: Opportunity Stage: Discovery, Qualification Opportunity > Account > ARR: < $100,000 ``` Call Summary Configuration Interface ### Step 3: Configure Summary Content The second section allows you to customize what content appears in your summaries. **Enable/Disable Features:** * **Follow-up Emails**: Include email follow-up suggestions * **Autopilot**: Display extracted CRM data * **Action Items**: List next steps and commitments * **Action Buttons**: Include Slack buttons to assist your team in taking action * **Condensed Summary**: Provide a brief overview with full details in the Slack thread **Custom Prompt Configuration:** * **Default Prompt**: Use Momentum's standard summary format * **Custom Prompt**: Write your own AI prompt for specialized summaries **Example Custom Prompt:** ```text theme={null} Create a concise summary of this sales call focusing on: 1. Customer pain points and challenges 2. Product interest and requirements 3. Budget and timeline discussions 4. Next steps and action items 5. Competitive mentions or concerns ``` ### Step 4: Configure Delivery Settings The final section determines where and how summaries are delivered. **Delivery Options:** * **Slack Channels, DMs, Group DMs**: Send to a specific channel or individuals * **Microsoft Teams**: Public channel messages or personal chats (choose a user via dropdown, Active User Lookup, or internal meeting attendees) * **Dynamic Lookups**: Route based on Salesforce object ownership * **Email**: Send to somebody's inbox **Advanced Delivery Settings:** * **Active User Lookup**: Automatically find and notify Salesforce users * **Pinning**: Pin important summaries to channels * **Conditional Delivery**: Add additional conditions for individual delivery destinations **Example Delivery Configuration:** ```yaml theme={null} Primary: Direct Message to Opportunity Owner Secondary: Slack Channel #sales-calls Salesforce: Create note on Opportunity Manager: Include rep's manager if Opportunity Amount is over $50k ``` Call Summary Delivery Configuration ### Step 5: Test and Validate 1. **Create a Test Summary**: Set up a summary workflow with broad criteria for testing 2. **Schedule a Test Call**: Have a team member conduct a test call 3. **Review Output**: Check that the summary appears in the correct location 4. **Adjust Settings**: Fine-tune content and delivery based on results ## Advanced Configuration ### Multiple Summary Workflows You can create multiple summary workflows for different use cases: **Discovery Summary Workflow:** * **Rules**: Opportunity Stage = "Discovery" * **Content**: Focus on pain points, requirements, timeline * **Delivery**: Rep + Manager DM **Proposal Summary Workflow:** * **Rules**: Opportunity Stage = "Proposal" * **Content**: Focus on pricing, objections, next steps * **Delivery**: Sales channel + Salesforce note ## Troubleshooting ### Common Issues **Summaries Not Appearing:** * Check Salesforce rules are correctly configured * Verify call recording integration is working * Verify that one of the attendees has a Momentum AI seat * Ensure delivery settings are properly configured * Make sure call lasts longer than 5 minutes **Incorrect Content:** * Review and refine custom prompts * Check that the right calls are being processed * Validate Salesforce field mappings **Delivery Problems:** * Verify that Momentum has channel access * Check Salesforce conditions match * [**Microsoft Teams DMs not appearing**](/momentum-ai-microsoft-teams-integration#4-install-momentum-for-an-individual-user): Reauthorize the Teams integration (My Integrations), then have a Teams admin open the Momentum app in Teams admin center and click **Publish Update** (wait \~10 minutes for version **1.0.1** to show). If a user is missing from the DM dropdown, have them send a message to the Momentum bot once; they will then appear and can receive call summary DMs. ## Best Practices 1. **Start Simple**: Begin with basic summary workflows and add complexity gradually 2. **Test Thoroughly**: Always test new configurations with sample calls 3. **Monitor Usage**: Regularly review summary quality and team adoption 4. **Iterate**: Continuously improve prompts and delivery based on feedback 5. **Document**: Keep records of successful configurations for team reference ## Support If you encounter issues during setup, contact our support team: * **Slack**: Use your shared Momentum channel * **Email**: [support@momentum.io](mailto:support@momentum.io) # Slack Commands & Shortcuts Source: https://docs.momentum.io/slack-commands-and-shortcuts Complete reference guide for all Momentum commands, shortcuts, and interactions available in Slack # Using Momentum in Slack Momentum integrates deeply with Slack to help you manage deals, track opportunities, and stay connected with your sales workflow. This guide covers all available commands, shortcuts, and interactions. ## Slash Commands Slash commands are typed directly in Slack's message input field. ### /momentum-cheat-sheet Opens a quick reference modal showing all available emojis, inline updates, and slash commands. ``` /momentum-cheat-sheet ``` **Use this when:** You need a quick reminder of available commands and emoji reactions. *** ### /momentum-link-connect-channel Links a Slack Connect channel to a Salesforce opportunity. This is useful when you have external channels with customers or partners that should be associated with a deal. ``` /momentum-link-connect-channel ``` **Use this when:** You want to connect a Slack Connect channel to track conversations with external stakeholders. **Requirements:** Salesforce integration must be connected. *** ### /momentum-make-account-room Converts an existing Slack channel into an Account Room linked to a Salesforce account. Account Rooms centralize all communications related to a specific customer account. ``` /momentum-make-account-room ``` **Use this when:** You want to associate an existing channel with a Salesforce account for better organization and tracking. **Requirements:** Salesforce integration must be connected. *** ### /momentum-rename-dealroom Opens a modal to rename an existing dealroom. You can also convert the dealroom to an Account Room from this modal. ``` /momentum-rename-dealroom ``` **Use this when:** You need to update the name of a dealroom or convert it to an Account Room. *** ### /ask-momentum-channel Creates a new Ask Momentum channel where you can query deal information and get AI-powered insights. ``` /ask-momentum-channel ``` **Use this when:** You want to set up a dedicated channel for querying Momentum's AI assistant about your deals and accounts. *** ### /momentum-sfdc-report Generates a Salesforce report and uploads it as a CSV file directly in Slack. ``` /momentum-sfdc-report ``` **Use this when:** You need to quickly export Salesforce report data without leaving Slack. **Requirements:** Salesforce integration must be connected. *** ### /momentum-sfdc-dashboard Opens a modal to browse and view your Salesforce dashboards directly within Slack. ``` /momentum-sfdc-dashboard ``` **Use this when:** You want to check dashboard metrics without switching to Salesforce. **Requirements:** Salesforce integration must be connected. *** ## Global Shortcuts Access global shortcuts by clicking the lightning bolt icon in Slack's message composer or by using the keyboard shortcut `Cmd + /` (Mac) or `Ctrl + /` (Windows/Linux). ### Configure Integrations Opens the "Your Integrations" modal where you can manage your connected services: * **Salesforce** - Connect or disconnect your Salesforce account * **Google Calendar** - Link your calendar for meeting sync * **Outreach** - Connect your Outreach account for sequence management **Use this when:** You need to set up or manage your integration connections. *** ### Search Knowledge Base Opens a modal to search Momentum's knowledge base filtered by opportunity stage. Find relevant content, battle cards, and resources for your deals. **Use this when:** You need quick access to sales enablement content relevant to a specific deal stage. *** ## Emoji Reactions React to messages with these emojis to trigger Momentum actions. These work in dealrooms and other Momentum-enabled channels. | Emoji | Action | | ------------------ | --------------------------------- | | ✅ / 👍 (`+1`) | Positive reaction captured | | 👆 (`point_up`) | Capture message as deal highlight | | 📞 (`telephone`) | Log as call note | | 📁 (`file_folder`) | Capture file | Emoji reactions are a quick way to capture important information without interrupting your workflow. Simply react to any message to save it to the associated deal. *** ## App Home Click on the Momentum app in your Slack sidebar to access the App Home. Here you can: ### Tabs * **Opportunities** - View and manage your pipeline * **Tasks** - See and update your tasks * **Calendar** - View upcoming meetings (requires Google Calendar integration) ### Features * **Filter** - Narrow down results by owner, stage, or custom fields * **Sort** - Reorder your view by different criteria * **Pagination** - Navigate through large lists ### Quick Actions From the App Home, you can: * View opportunities in Salesforce * Request updates on deals *** ## Dealroom Actions When inside a dealroom channel, you have access to these actions through message buttons and the channel header: ### Channel Management | Action | Description | | ---------------------- | --------------------------------------------------- | | **Invite to Dealroom** | Add team members to the dealroom | | **Archive Dealroom** | Archive the dealroom when a deal is closed | | **Rename Dealroom** | Change the dealroom name or convert to Account Room | ### Deal Actions | Action | Description | | ---------------------- | ------------------------------------------- | | **Create Dealroom** | Create a new dealroom from an opportunity | | **Manage Opportunity** | Update opportunity fields directly in Slack | | **Request Update** | Send an update request to the deal owner | ### Task & Meeting Actions | Action | Description | | ------------------------ | ----------------------------------------------------- | | **Create Task** | Create a follow-up task from a meeting | | **Edit Task** | Update task status, assignee, due date, or completion | | **AI Email Draft** | Generate an AI-powered follow-up email | | **Sync Data Insights** | Sync call insights to Salesforce | | **Manage Data Insights** | Edit or review captured insights | | **Complete Milestone** | Mark deal milestones as achieved | | **Manage Milestones** | Update or revert milestone status | *** ## Bot Mentions Mention the Momentum bot (`@Momentum`) in any channel to interact with Ask Momentum. You can ask questions about: * Deal status and history * Account information * Pipeline metrics * Meeting summaries * And more ``` @Momentum What's the status of the Acme deal? ``` *** ## Integration Requirements Some features require specific integrations to be connected: | Feature | Required Integration | | ---------------------- | -------------------- | | Opportunity management | Salesforce | | Dashboard viewing | Salesforce | | Report generation | Salesforce | | Calendar view | Google Calendar | | Sequence selection | Outreach | Use the **Configure Integrations** shortcut to connect your accounts and unlock all features. *** ## Tips & Best Practices Instead of copying and pasting information, simply react to messages with the appropriate emoji to save them to your deal automatically. Create separate dealrooms for each opportunity to keep conversations organized and ensure all context is captured in the right place. Make it a habit to review your App Home each morning to see your tasks, upcoming meetings, and pipeline at a glance. If you forget a command or emoji, the cheat sheet is always one command away. *** ## Troubleshooting ### Command not working? 1. **Check your integrations** - Use the Configure Integrations shortcut to ensure your accounts are connected 2. **Verify permissions** - Some commands require specific user permissions in your organization 3. **Check the channel** - Some commands only work in dealrooms or specific channel types ### Need help? Contact your Momentum administrator or reach out to support for assistance. # Smart Clips Source: https://docs.momentum.io/smart-clips Automatically capture and share the strongest call moments with Momentum Call Intelligence. ## Overview Smart Clips automatically packages the most important moments from every analyzed call into short, shareable highlights. The feature is available to every workspace that has Call Intelligence and can be configured by admins to deliver those clips directly into the right Slack destinations. Smart Clips are designed to help revenue teams: * Capture consistent feedback themes (wins, risks, objections, pain points) without manual clipping. * Share the decisive moments from calls with managers, enablement, and executives in real time. * Keep stakeholders aligned by routing highlights to the Slack channels or individuals that need them most. ## Prerequisites * Call Intelligence is enabled and actively analyzing calls. * Your workspace Slack app is connected in `Admin > Integrations`. ## Create a Smart Clip Workflow 1. Go to `Admin > Smart Clips` and select **Create Smart Clip**. 2. Choose the prompt that tells Momentum what to capture. Prompts can target themes such as: * Positive feedback or customer praise. * Negative feedback, objections, or escalations. * Pain points or deal blockers you want the team to track. 3. Pick the delivery cadence. You can fire Smart Clips after every qualifying call or only when the prompt finds matching content. 4. Select the Slack destination: * **Slack Channel** to notify a broader audience (for example, `#wins`, `#cs-escalations`, or `#product-feedback`). * **Slack User** for direct alerts to an individual manager, rep, or executive. 5. Save the workflow. The next time a call matches the prompt, Momentum generates the clip and posts a playable video card into Slack with context and a link back to the Call Library. ## Managing Smart Clips * **Edit or pause** a workflow from the Smart Clips list if priorities change. * **Duplicate** a workflow to experiment with different prompts or destinations without starting over. * **Trace delivery** by following the Slack link back into the Call Library, where you can download or add the clip to playlists if you want to reuse it elsewhere. ## Prompt Best Practices * Include the outcome you want, such as “Capture a 60-second clip where the customer describes their biggest pain point.” * Reference speaker roles to focus on customer statements (e.g., “Highlight when the prospect shares negative feedback about the onboarding experience.”). * Avoid stacking too many requirements; create separate workflows for different use cases (wins vs. risks) so stakeholders only receive the clips that matter to them. ## FAQs **Do we need to enable Smart Clips?**\ No additional toggle is required. Once you create a workflow, Smart Clips start generating for newly analyzed calls that match your prompt. **Do Smart Clips still show up in the Call Library?**\ Yes. Every Smart Clip is stored alongside the full recording in the Call Library so you can review, download, or add it to playlists. **Can we still create clips manually?**\ Yes. Manual clipping continues to work exactly the same way. Smart Clips simply adds AI-generated highlights alongside the clips your team creates. **What if a clip misses the context we need?**\ Open the full call recording to expand the range around the Smart Clip, or adjust the prompt to request more or less context. # Smart Quarantine Source: https://docs.momentum.io/smart-quarantine Automatically detect and pause processing of meetings containing sensitive content before summaries and insights are shared across your organization. ## Overview Smart Quarantine automatically screens meeting transcripts for sensitive content before Momentum generates and distributes AI summaries, action items, and insights. When a meeting is flagged, processing is paused and the meeting host is notified via Slack to decide what happens next. This ensures that confidential discussions — such as personnel matters, legal proceedings, or non-public financial information — are never inadvertently shared across your organization through Momentum's automated workflows. ### Prerequisites * Smart Quarantine must be enabled for your organization by your Momentum representative. * Meeting hosts must have Slack connected to Momentum to receive quarantine notifications and take action. * An AI license is required to use this feature. ### Key Benefits * **Prevent accidental exposure** of sensitive meeting content before it reaches summaries, CRM syncs, or team feeds * **AI-powered detection** goes beyond keyword matching to understand context, intent, and confidentiality * **Zero manual effort** — meetings are automatically screened without any action required from reps or hosts * **Host stays in control** — flagged meetings are paused until the host explicitly chooses how to proceed ## What Gets Flagged Momentum's AI evaluates meeting transcripts for sensitive content across the following categories: | Category | Examples | | ------------------------------------ | ----------------------------------------------------------------------------------- | | **M\&A and Restructuring** | Non-public acquisition targets, restructuring plans, layoff discussions | | **Personnel Matters** | Terminations, PIPs, disciplinary actions, performance reviews for named individuals | | **Legal Proceedings** | Active litigation, regulatory investigations, legal threats | | **Non-Public Financial Information** | Material inside information, undisclosed financial results | | **HR Investigations** | Harassment complaints, misconduct investigations, ethics complaints | | **Medical / Health Discussions** | Health information about specific individuals | | **Personal Conversations** | Unintentional personal or family recordings | | **Job Interviews** | Candidate evaluations, offer discussions, rejection conversations | Smart Quarantine uses contextual understanding — not simple keyword matching. A sales rep mentioning a competitor's recent acquisition in a deal call will not trigger quarantine. An executive discussing confidential acquisition targets with non-public details will. The AI considers participant roles, meeting context, and whether the information discussed is likely non-public before flagging. ### What Does NOT Get Flagged Routine business conversations are not flagged, including: * Standard sales calls, competitive analysis, and market positioning * General company financial performance discussed in earnings calls or QBRs * Contract terms, compliance training, and policy briefings * Routine team meetings such as standups, sprint planning, and project updates * Public information about acquisitions or financial matters ## How It Works ### 1. Automatic Screening After a meeting is imported and the transcript processing begins, Momentum's AI analyzes the full conversation for sensitive content. This happens automatically — no configuration or manual action is needed from your team. Only meetings where the AI has **high confidence** that sensitive content is present are flagged. Ambiguous or low-confidence signals are not flagged, ensuring minimal disruption to your normal workflow. ### 2. Processing Is Paused When a meeting is flagged, all downstream processing is immediately paused. This means: * No AI summary or action items are generated * The meeting is not indexed in the Call Library * No data is synced to your CRM * No Autopilot or AI Signal workflows are triggered The meeting remains in this paused state until the host takes action. ### 3. Host Is Notified via Slack The meeting host receives a Slack direct message explaining that the meeting has been flagged. The notification includes: * The **meeting title** * A brief **reason** explaining why the meeting was flagged * Three action buttons to resolve the quarantine Smart Quarantine Slack Notification The host can choose one of three options directly from the Slack notification: | Action | What Happens | | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Approve Processing** | Transcript processing resumes normally. The meeting is summarized, indexed, and shared across your organization as usual. | | **Keep Private** | Processing resumes, but the meeting's visibility is restricted to the host and attendees only. The broader organization will not see this meeting in the Call Library or receive any related notifications. | | **Delete Meeting** | The meeting and all associated data are permanently deleted. Any previously synced data in Salesforce is reverted. | There is no timeout on quarantine notifications. The meeting will remain paused until the host responds, so hosts can take action at their convenience. ## Best Practices 1. **Educate meeting hosts** — Let your team know that they may receive quarantine notifications via Slack and what each action means 2. **Connect Slack** — Ensure all meeting hosts have Slack connected to Momentum so they can receive and respond to notifications promptly 3. **Review flagged meetings** — When a meeting is flagged, hosts should review the stated reason before choosing an action 4. **Use "Keep Private" for legitimate but sensitive calls** — If a meeting contains sensitive content that still needs to be documented, "Keep Private" lets processing continue with restricted access rather than deleting the record entirely # Smart Tags Source: https://docs.momentum.io/smart-tags Automatically extract and structure meaningful signals from your conversations for powerful filtering and automation. ## Overview Smart Tags automatically classify calls based on your prompts. They eliminate manual tagging and provide the foundation for intelligent automation across the Momentum platform. Smart Tags enable revenue teams to: * **Easily identify important calls** by filtering based on automatically detected themes like competitor mentions, objections, or feature requests * **Automate workflows with infinite flexibility** by triggering actions when specific tags or combinations of tags are detected * **Analyze trends** by correlating tags across calls at scale ## How Smart Tags Work When a conversation is analyzed, Momentum's AI evaluates which of your configured Smart Tags apply and tags the conversation accordingly. Each tag includes the relevant context from the transcript, so you can always verify why a tag was applied. **Example**: If a prospect mentions "we're currently evaluating Competitor X," a competitors Smart Tag automatically tags the conversation with a "Competitor X" tag. That data can then be used to: * Filter calls in the Call Library to review all conversations where "Competitor X" emerged as a competitor * Trigger Autopilot or AI Signal workflows (e.g., notify sales enablement or attach a battlecard) ## Smart Tag Types Create Smart Tags that match your specific business needs: | Type | Description | Example Use Case | | ------------------ | ------------------------------------------------------------- | ------------------------------------ | | **Boolean** | Yes/no detection | "Demo Requested", "Budget Confirmed" | | **Picklist** | Single selection from predefined or AI-discovered keywords | "Primary Objection Type" | | **Multi-Picklist** | Multiple selections from predefined or AI-discovered keywords | "Competitors Discussed" | | **String** | Free-form text extraction with multiple values allowed | "Specific Feature Requested" | The type dictates how the tag can be used for filtering and automation. For example, a Boolean tag can trigger an action when true, while a Picklist tag can trigger different actions based on the selected value. ## Key Features ### Meaningful Detection Smart Tags go beyond simple keyword matching: * **Contextual Understanding**: Momentum analyzes meaning and intent, not just exact phrases * **Evidence Capture**: Every tag includes supporting quotes from the transcript for verification * **Dynamic Discovery**: Optionally allow Momentum to detect new values beyond your predefined keywords ### Call Library Filtering Find the calls you need instantly: * **Multi-Tag Filtering**: Combine multiple Smart Tags to narrow results * **Keyword-Specific Search**: Filter by specific tag values (e.g., a particular competitor name) * **Cross-Reference**: Combine with other filters like date range, owner, and deal stage ## Use Cases ### Competitive Intelligence Track competitor mentions and understand win/loss drivers. **Example Tag**: *Competitors Discussed* (Multi-picklist) * Keywords: "Competitor X", "Competitor Y", "Competitor Z" * Allow others: Yes (to discover new competitors) Filter calls to review positioning battles, analyze win/loss patterns by competitor, and build training playlists of successful competitive calls. ### Enablement and Coaching - Objection Handling Identify and categorize common objections to improve coaching. **Example Tag**: *Primary Objection* (Picklist) * Keywords: Pricing, Timeline, Competition, Internal Buy-in, Technical Concerns Build coaching materials around specific objection types and track objection frequency trends over time. ### Product Feedback Capture feature requests and product insights from customer conversations. **Example Tag**: *Feature Request* (Multi-picklist) * Keywords: Reporting, Integrations, Mobile App, API, Automation * Allow others: Yes Route product feedback to your product team and prioritize roadmap based on customer demand. ### Deal Risk Indicators Identify calls that signal deal risk for proactive intervention. **Example Tag**: *Risk Indicator Detected* (Boolean) * Prompt: "Identify if the customer expressed concerns about budget, timeline, decision-making authority, or mentioned evaluating alternatives" ### Sales Methodology Adherence Ensure reps follow your sales process and identify coaching opportunities. **Example Tag**: *MEDDPICC Coverage* (Multi-picklist) * Keywords: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion, Competition ## Setting Up a Smart Tag Admins can create and configure Smart Tags to capture the signals that matter most to your organization. Smart Tag Wizard 1. Navigate to **Admin > Smart Tags** and select **Create Smart Tag** 2. Enter a **Title** for your tag (e.g., "Competitor Mentioned") 3. Select a **Data Type**: Boolean, Picklist, Multi-picklist, or String 4. Write your **Prompt**: Describe what Momentum should look for in the call 5. Add **Keywords** (for picklist types): Define expected values like competitor names or objection categories 6. Enable **Allow Others** (optional): Let Momentum discover new keywords not in your predefined list 7. Click **Save** Smart Tags apply to newly analyzed calls. Existing calls will not be retroactively tagged unless you run a backfill. Carefully craft your Smart Tag prompts to ensure accurate and consistent tagging. [Learn more about prompt writing best practices](/how-to-write-effective-ai-prompts-for-momentum-features). ## Using Smart Tags in Automations Once configured, Smart Tags can trigger automated workflows based on conversation content: * [Using Smart Tags in Autopilot Classic](/autopilot-classic-setup#smart-tag-conditions-optional) — Trigger Salesforce field extractions when specific tags are detected * [Using Smart Tags in AI Signals](/creating-ai-signals-workflows#smart-tag-conditions-optional) — Route signals to teams based on what was said during calls **Example**: When a competitor is mentioned on an early-stage deal and pricing objections arise, trigger an Autopilot extraction to check whether the rep addressed a key talking point. ## Best Practices 1. **Start Simple**: Begin with a few high-value tags before expanding 2. **Iterate on Prompts**: Refine your prompts based on initial results 3. **Use Specific Keywords**: For picklists, include known values to ensure consistent tagging 4. **Enable Discovery**: Use "Allow Others" to catch unexpected patterns 5. **Review Regularly**: Periodically review Smart Tag results and refine definitions 6. **Combine Tags**: Use multiple Smart Tags together for powerful, hyper-specific filtering ## FAQs **How are Smart Tags different from manual tagging?** Smart Tags are automatically detected by Momentum's AI based on what was actually said during the call. There's no need for reps to remember to tag calls—it happens automatically. **Can Smart Tags detect new keywords automatically?** Yes. When "Allow Others" is enabled, Smart Tags can identify new values and add them as selectable options—for example, discovering new competitor names that appear in conversations. **Where can I see Smart Tags on a call?** In the Call Library, you can filter calls using your configured Smart Tags. When viewing an individual call, you'll see all the Smart Tags that were applied to it along with the supporting evidence. **Do Smart Tags work with Autopilot Classic and AI Signals?** Yes. Smart Tags can be used as conditions in both Autopilot Classic workflows and AI Signals to trigger actions based on tagged keywords. # Understanding Our Products Source: https://docs.momentum.io/understanding-our-products Welcome to the Momentum Product Documentation. This index provides an overview of all the available documentation pages to help you navigate and find the information you need. Record, organize, and share customer calls. Turn calls into actionable CRM summaries. Auto-capture and update Salesforce data. Share key data across GTM. Send the right message. Automated and tailored call analysis. AI-powered account overviews with timelines and interactive Q\&A. Automatically evaluate and coach every sales call with objective competency assessments. # User Managed Salesforce Flows Source: https://docs.momentum.io/user-managed-salesforce-flows Configure Salesforce Flows and Outbound Messages for Momentum automations when integration permissions are restricted ## Overview Momentum integrates with Salesforce using Flows and Outbound Messages to trigger automated features including: * Retropilot executions * Salesforce notifications * Slack room automation This architecture enables Salesforce to notify Momentum when specific events occur, triggering the appropriate Momentum automations. **Example Use Case**: When an Opportunity moves to "Closed Won" stage, automatically trigger Retropilot to create a handoff document for the Customer Success team. ## When to Use This Guide This guide is designed for organizations where IT or Security teams restrict the Momentum-Salesforce integration user from creating Flows and Outbound Messages in production environments. In these scenarios, you'll need to collaborate with your Salesforce admin team to implement the configurations described below. ## Salesforce Configuration Requirements To enable Momentum workflows in environments with restricted integration permissions, your Salesforce administrator needs to configure two key components: 1. **Outbound Message**: Sends event notifications to Momentum 2. **Salesforce Flow Integration**: Triggers the Outbound Message when specific conditions are met If multiple Momentum workflows share the same trigger condition, a single Outbound Message can handle all of them. Just ensure the message includes all required fields for every workflow. ## Step 1: Create an Outbound Message The Outbound Message serves as the communication bridge between Salesforce and Momentum. Configure it with the following specifications: | **Field** | **Configuration** | | ------------------- | ----------------------------------------------------------------------------------- | | **Object** | Select the Salesforce object that triggers the automation (e.g., Opportunity) | | **Name** | Choose a descriptive name (e.g., "Momentum Opportunity Updates") | | **Unique Name** | System-generated unique identifier | | **Endpoint URL** | `https://salesforce-flow-event-receiver.momentum.io/salesforce/flow/event/receive` | | **User to Send As** | Select any user with appropriate permissions | | **Send Session ID** | ❌ Leave unchecked | | **Fields** | Include all fields required by your Momentum workflows (see workflow documentation) | #### Configuration Example The following example shows an Outbound Message configured for Opportunity events, including Record ID, Amount, and Stage fields: sfdc-edit-outbound-message.png The above example represents an Outbound Message that is triggering Momentum to perform an action on an Opportunity record, using not only its Record ID but also the Amount and Stage of the opportunity. ## Step 2: Integrate with Salesforce Flow After creating the Outbound Message, integrate it into your Salesforce automation using one of these approaches: #### Option A: Add to Existing Flow If your organization already has a Flow that triggers on your desired condition (e.g., Opportunity stage changes): 1. Open the existing Flow in Salesforce Flow Builder 2. Navigate to the appropriate decision path 3. Add an **Action** element 4. Select **Send Outbound Message** and choose your created message 5. Save and activate the Flow #### Option B: Create New Flow For new automations or dedicated Momentum integrations: 1. Create a new Record-Triggered Flow in Salesforce 2. Set the object and trigger conditions (e.g., Opportunity record updates) 3. Add Decision elements to check for specific criteria 4. Add Outbound Message actions for each relevant condition 5. Test, save, and activate the Flow Ensure your Flow's trigger conditions match exactly when you want Momentum automations to execute. #### Example Scenario * **Trigger**: Opportunity moves to "Closed Won" stage * **Required Momentum Actions**: * Create an Account Room * Send celebratory message to Sales Slack channel * Execute "Hand Off" Retropilot rule * Execute "Closed Won Reason" Retropilot rule * **Solution**: Create one Outbound Message with fields required for all four automations, then configure each Momentum workflow to use the same Outbound Message ID. ## Step 3: Connect the Flow to Momentum Workflows Once your Salesforce Outbound Message and Flow are configured: 1. **Access Momentum Admin Panel**: Log into your Momentum workspace as an administrator 2. **Create Workflow**: Navigate to the desired workflow type: * Retropilot automations * Salesforce notifications * Slack room automation 3. **Enter Outbound Message ID**: In the workflow configuration form, paste the Outbound Message ID from Salesforce. Please ensure the ID is 18 characters long. Retropilot Wizard - Outbound Message ID Configuration 4. **Configure Workflow Details**: Complete the remaining workflow settings: * Slack message templates * Retropilot extraction prompts * Notification preferences 5. **Save and Activate**: Save your workflow configuration ## Important Notes * **No Condition Configuration Required**: Since trigger conditions are handled by your Salesforce Flow, you don't need to configure additional conditions in Momentum * **Immediate Activation**: Once saved, your workflow will automatically process Outbound Messages from Salesforce * **Testing**: Trigger your Salesforce condition to verify the integration works correctly ## Troubleshooting If your automation isn't triggering: 1. **Verify Flow Activation**: Ensure your Salesforce Flow is active 2. **Check Outbound Message**: Confirm the endpoint URL is correct 3. **Review Field Mapping**: Verify all required fields are included in the Outbound Message 4. **Test Conditions**: Manually trigger the Salesforce condition and monitor Momentum logs # User Roles and Permissions Source: https://docs.momentum.io/user-roles-and-permissions Understanding different user types and their roles in Momentum ## Overview Momentum provides several different user types to ensure each user only interacts with the information essential to them. This guide covers how each user type interacts with Momentum and the information they can access. ## Quick Reference | Role | Primary Function | Key Permissions | Access Level | | ------------------ | --------------------- | -------------------------------------- | ------------ | | Default User | Basic access | View summaries, ask questions | Limited | | Organization Admin | Platform management | Full system access, license management | Highest | | Editor | Configuration support | Workflow setup, no license management | High | | User Admin | License management | User onboarding, license assignment | Medium | | Integration User | System automation | API access, backend tasks | System | ## Understanding Role Hierarchy Momentum's roles are designed with a clear hierarchy to maintain proper access control: 1. **Organization Admin** - Full system control 2. **Editor** - Configuration access 3. **User Admin** - User management 4. **Default User** - Basic access 5. **Integration User** - System-level access ## User Roles ### Default User The basic role assigned to all individuals when they first join Momentum. **Access and Interaction:** * Primary interaction through Slack * Can view summaries and ask questions about calls in Slack channels where they receive Momentum call notes * Access to relevant call insights based on team membership **Slack Configuration:** * Organization Admins and Editors determine content destinations * Content may be sent via: * Direct messages to call owners * Private Slack channels restricted to relevant team members * Customizable notification preferences **Use Case:** * Receive tailored AI insights for relevant customer interactions * Stay informed about important call outcomes * Collaborate with team members on call insights **Best Practices:** * Ensure you're added to relevant Slack channels * Set up appropriate notification preferences * Regularly review call summaries for your accounts ### Organization Admin Full owners and primary operators of the Momentum platform within the organization. **Permissions:** * Assign and manage user licenses * Access and view call data related to troubleshooting * Configure all Momentum workflows and settings * Manage organization-wide integrations * Set up and modify data pipelines * Configure security settings and access controls **Best Practices:** * Limit to 1-3 users for centralized control * Document configuration changes * Regularly review user access and permissions * Maintain an audit trail of system changes **Common Tasks:** * Onboarding new teams * Setting up custom workflows * Troubleshooting system issues * Managing integration configurations ### Editor Support role for platform configuration and setup. **Permissions:** * Configure workflows and data pipelines (similar to Organization Admins) * Modify notification settings * Set up custom reporting * Configure integration settings **Restrictions:** * Cannot view all call data * Cannot assign licenses * Cannot modify security settings * Cannot change organization-wide configurations **Use Case:** * Best suited for team members supporting tool owners with technical setup and workflow management * Ideal for department-level administrators * Perfect for technical team leads managing their team's Momentum setup ### User Admin License administrators focused on managing user onboarding and licensing. **Permissions:** * Assign licenses that enable users to record customer interactions * Manage user access levels * View license usage and allocation * Generate license reports **Use Case:** * Ideal for those who onboard new users and manage licensing * Does not require access to call data or advanced workflow configuration * Perfect for HR or IT personnel managing user access **Best Practices:** * Maintain an up-to-date user directory * Regularly review license allocation * Document license assignment procedures * Monitor license usage patterns ### Integration User System-level user accounts created by the organization to automate backend tasks. **Use Case:** * Poll call recorders for relevant call transcripts * Update Salesforce records after calls or emails * Automate data synchronization * Handle bulk data operations **Technical Details:** * Uses API keys for authentication * Runs automated processes * Operates on a schedule or event triggers * Handles system-to-system communication ## Role Comparison ### Access Levels * **Full Access:** Organization Admin * **Configuration Access:** Editor * **User Management:** User Admin * **Basic Access:** Default User * **System Access:** Integration User ### Common Scenarios 1. **New Team Setup:** * Organization Admin creates the team structure * Editor configures team-specific workflows * User Admin assigns licenses to team members * Default Users begin receiving call insights 2. **Integration Setup:** * Organization Admin approves the integration * Editor configures the integration settings * Integration User handles the data synchronization * Default Users receive integrated insights 3. **License Management:** * User Admin manages license allocation * Organization Admin approves major changes * Default Users are notified of access changes ## Best Practices 1. **Role Assignment:** * Start with minimal necessary permissions * Review and adjust roles as needed * Document role assignments * Regular access reviews 2. **Security:** * Use strong authentication * Regular password updates * Monitor access patterns * Report suspicious activity 3. **Maintenance:** * Regular role audits * Update documentation * Review permission changes * Monitor system usage