Frost & Sullivan On-Demand Webinar: Agents like AI but why? How to implement, build trust, and deliver results.

Watch Now!
×
Blog AI & ML She Said “I’m Done.”Your Analytics Said “No Cancellation Detected.”
Customers don't follow scripts when they're frustrated. Traditional speech analytics only finds the phrases you told it to look for. Deep Prompt reads the whole conversation and surfaces what actually matters.

She Said “I’m Done.”Your Analytics Said “No Cancellation Detected.”

Customers don’t follow scripts when they’re frustrated. Traditional speech analytics only finds the phrases you told it to look for. Deep Prompt reads the whole conversation and surfaces what actually matters.

June 11, 2026 5 minute read

Table of Contents

Keywords sometimes fail to answer what was said | SuccessKPI

The conversation

A customer said she was leaving, and the system did not pick it up.

A telecom provider has configured its speech analytics platform with a “Cancellation” topic, a list of keyphrases it expects customers to say when they want to cancel or leave. The system scans every call transcript for those phrases. If none are found, no alert fires.

Customer“Honestly, I’ve been with you guys for six years but this is the last straw. I’m looking at other providers right now.”
Agent“I understand your frustration. Let me look into the billing issue…”
Customer“Don’t bother with the script. I’ve already started the switch. I just need my final bill.”
Agent“I’m sorry to hear that. Let me pull up your account…”
CustomerI’m done. Just tell me what I owe.”
Keywords configured
cancel my accountcancel serviceterminate my planend my subscription
None found. NOT DETECTED.
What she actually said
“this is the last straw”“looking at other providers”“started the switch”“I’m done”
Clear churn intent. Zero keyword matches.

No alert. No supervisor notification. No retention workflow triggered. She churned quietly. The dashboard never recorded a cancellation event because to the system, a cancellation never happened.

Why this happens

Keywords only find what someone thought to look for.

Every platform works the same way: an analyst lists phrases they expect customers to say, then the system scans transcripts for matches. Found = flagged. Not found = invisible.

1
Define topic
Name + keyphrases
2
System scans
Every transcript
3
Match or miss
Found = flagged
4
Alert or nothing
No match = no signal
The assumption
Customers in distress will say what an analyst would expect. If you want to leave, you say “cancel.”
The reality
Real customers use indirect, emotional, colloquial language, especially when they are already decided. They do not announce intent. They express it.
What this means for coverage
Any customer who expresses churn intent without using the exact configured phrases is invisible to the system, and there is no signal that anything was missed.
The compounding problem
The more certain a customer is about leaving, the less likely they are to say it directly. The highest-risk calls are the ones most likely to go undetected.

Vendors have improved this over the years, but the constraint is structural: the system can only find what someone anticipated in advance.

Keyword detection coverage by conversation type
Each bar shows what percentage of conversations the system successfully detects. The remaining space is the coverage gap, calls where intent is expressed but no keyword fires.
Scripted language (greetings, holds, disclosures) ~90% detected
10% gap
Agents use predictable, scripted phrasing, easy to match.
Moderate variance (billing, transfers, complaints) ~67% detected
33% gap
Common topics, but customers phrase them inconsistently.
⚠ Highest-value conversations, lowest detection
High variance (churn intent, escalation, sentiment) ~40% detected
60% gap, invisible to the system
Customers in distress use indirect, colloquial, emotional language, not the formal phrases analysts configured. 6 in 10 churn-risk calls go undetected.

Estimates based on industry patterns. Actual coverage varies by configuration quality.

The red bar is where the highest-value conversations live, and where keyword detection is least effective. So what’s the alternative?

Enter Deep Prompt

Keywords answer what was said.
Deep Prompt answers why it was said.

Deep Prompt is SuccessKPI’s GenAI analytics capability. Instead of scanning for pre-defined phrases, it reads the full conversation and extracts structured answers: scores, summaries, reasons, and recommended actions. You describe what you want to understand in plain English. The AI does the rest.

KeywordsDeep Prompt
What it answers“Was this phrase said?”“What happened, why, and what should we do?”
Best forScripted, repeatable interactionsEmotional, indirect, or nuanced conversations
OutputYes / No flagScores, summaries, reasons, actions
Cost per conversationLow (no LLM tokens)Higher (LLM processing per conversation)
AutomationTopic triggers PlaybooksScore-based triggers via Playbook Builder™

Choosing the right tool

Both methods have a place. The question is knowing which to use when.

Keywords and Deep Prompt are not in competition. For high-volume, predictable tasks like greeting checks, disclosure flagging, or product mentions, keywords are fast, cheap, and reliable. For anything requiring context, judgment, or understanding intent, Deep Prompt is the right call. The practical question is always: does this business question need context, or just a match?

1
Speech & Text
High-volume, predictable detections. Configure once, run at scale, cost-efficient.
+
2
Deep Prompt
Complex, intent-driven analytics. Churn, coaching, compliance, root cause.
=
3
Complete Insight
Volume handled by keywords. Complexity handled by Deep Prompt. Both feed dashboards and Playbooks.
On cost: Deep Prompt processes each conversation with an LLM, so there is a per-call cost. Use it where the insight justifies it. Keywords handle volume. Deep Prompt handles complexity. That combination is also the most cost-efficient.

In practice

A simple rule of thumb.

🔍
Use Keywords When…
Target is a specific, predictable phrase
You need binary detection: said or not said
Language is consistent and formulaic
High volume, straightforward detection
Cost efficiency is the priority
🧠
Use Deep Prompt When…
Question requires analyzing context and intent
You need structured outputs: scores, summaries, flags
Language is unpredictable or emotional
You want to know why, not just what
Outputs should trigger Playbook automation
The bottom line: Keywords tell you whether a phrase was said. Deep Prompt tells you what was meant. Used together, they give you complete insight across every conversation.

Back to the scenario

Same call. Same transcript. Here is what Deep Prompt found.

The customer from our opening example, the one who said “I’m done” instead of “cancel my account”, went undetected by keyword scanning. When the same transcript was run through Deep Prompt:

9
Churn Risk Score

9 out of 10. Customer is actively switching to a competitor and requesting a final bill. Imminent departure.

Risk Signals

“I’m looking at other providers”, active competitor research. “Started the switch”, defection in progress. “I’m done”, explicit disengagement.

Recommended Action

Urgent retention outreach. Escalate to a retention specialist with billing resolution and loyalty offer. Standard scripts will not work.