A sales enablement team wants Conversation Intelligence to detect when a prospect raises a pricing objection during a recorded call (phrases like 'that's more than we budgeted' or 'can you do better on price') and automatically surface a battlecard about pricing flexibility to the rep during the call. What should the team configure to extend Conversation Intelligence for this purpose?
Select an answer to reveal the explanation.
Short Explanation
The whole point is timing: the rep needs help while the prospect is still on the line, not a recap after the call is already over. That rules out anything that only works from a finished recording. What gets the job done is building a tracker specifically for pricing-objection language and tying it to a card that pops up live, so the moment the prospect pushes back on price, the rep sees flexibility talking points right then, not an email the next morning. Reaching for a tracker meant to catch competitor names doesn't help, because it's listening for a different vocabulary entirely and won't reliably catch budget complaints. And turning off an unrelated signal like sentiment scoring doesn't unlock anything here, those two features run side by side and touching one does nothing for the other. A purpose-built tracker wired to a real-time card is the only setup that actually delivers help at the moment it matters.
Full Explanation
The correct answer is D. Conversation Intelligence supports custom keyword trackers, and linking a pricing-objection tracker to a real-time card lets the rep see the relevant battlecard content the moment the prospect raises a price concern, while the call is still in progress and actionable. Option A is incorrect because reviewing the transcript after the call and emailing a battlecard afterward cannot influence how the rep handles the objection during that same conversation, which is the stated goal. Option B is incorrect because a competitor-mention tracker is scoped to competitor names and would not reliably fire on generic pricing-objection language, since trackers match the terms and phrases configured for their specific purpose. Option C is incorrect because sentiment analysis and keyword trackers are independent features that run concurrently in the same call; disabling sentiment analysis would not enable or improve keyword tracking and only removes an unrelated signal the team might still want. Building a purpose-built tracker tied to a live card is the extension point that actually connects detection to real-time guidance for the rep.