Skip to main content
Service, CX & risk insights

Churn signals in customer conversations: spotting the risk early

When a cancellation request arrives the customer has already decided, but dissatisfaction shows in conversations weeks earlier. This guide covers a list of churn signals in conversations, why a signal is not a prediction, the fields, human review, the right next step and the profiling line.

October 5, 20266 min read

Short answer

Churn risk (a customer leaving) can be seen early in conversations, but as a signal, not a prediction. By the time a customer says "I want to cancel" it is already late; earlier signals are a repeated problem, an unresolved complaint, a competitor mention, sentences saying usage has dropped, and questions such as "when does my contract end?". Collect these signals as fields, have a person read each one, and choose the right next step.

The key rule: a signal is not a verdict on the customer. Using a conversation flagged by AI to give a customer a different price, restrict service or label them "risky" is wrong. A signal is for one thing only: quickly finding the conversation a person should look at.

Why early signals matter

For a business built on subscriptions, contracts or repeat purchases, keeping a customer is often cheaper than winning a new one. But a retention step only works while the problem can still be solved. When a cancellation request arrives, the customer has already decided. In conversations, dissatisfaction shows up weeks before the decision — nobody simply gathers it in one place.

A signal list

  1. A repeated problemThe customer writes about the same problem a second or third time: "again…", "I've already said many times…".
  2. An unresolved complaintAn earlier conversation went unanswered, or the customer says "nobody got back to me".
  3. A competitor mention"It's cheaper at X", "I'm thinking of switching to X".
  4. Doubt about value"I don't use this service much", "why am I paying this much?".
  5. A contract question"When does my contract end?", "what are the early cancellation terms?".
  6. Open intent"I want to cancel", "stop my subscription" — the latest signal.

A signal is not a prediction

A customer asking when their contract ends may simply be planning their budget. A customer mentioning a competitor may be negotiating on price. A signal raises the probability but does not decide the outcome. So write "conversations with a churn signal" in reports, not "customers at risk of churn". The difference is honest, and it protects the team from a wrong automated decision.

Setting up the fields

  • "Churn signal": the six values above plus "none". Multi-value, because a conversation can hold several signals.
  • "Topic of dissatisfaction": price, quality, service, technical problem, competitor offer, other.
  • "Problem resolved": yes / no / unclear — based on how the conversation ended.
  • Customer type: new or existing — usually CRM data rather than a field.

Human review: who looks

Every day or week, the list of conversations with a "churn signal" that ended with "problem not resolved" goes to a responsible person: an account manager, the support lead or a retention team. They read the conversation and answer one of three questions: is the signal real, is the problem still current, which step fits. AI's job is to shorten the list; the decision is a person's.

The right next step

  1. Solve the problemThe step that works most often. If a repeated problem is unsolved, a discount will not help.
  2. Get in touchThe responsible person writes or calls: acknowledges the problem, says what will be done and when.
  3. Show the valueFor value doubts: features the customer is not using, a better-fitting plan.
  4. An offerOnly for price topics and within company rules — not an automatic discount for every signal.

The aggregate view: a system problem

Beyond individual conversations, the overall distribution of signals reveals system problems. If most churn signals share one "topic of dissatisfaction" (say, slow technical support), that is an operations issue, not a retention team issue. The most valuable decision is often not a call to one customer but fixing the process that creates the signal. For that, apply complaint root cause analysis.

The profiling line

Building customer profiles from conversation signals and making automated decisions on them (different prices, refusing service, credit terms) carries serious legal and ethical risk. In the EU, Article 22 of the GDPR places specific restrictions on decisions based solely on automated processing that significantly affect a person; in Azerbaijan, the Law on Personal Data applies. Before planning any automated decision, consult a lawyer and build human review into the process.

Illustrative example

This is an illustrative example. A fitness club chain switches on a "churn signal" field in members' conversations. In the first month, the biggest signal group is "repeated problem", with the topic "no hot water in the showers", at one branch. Some of these members later ask "when does my contract end?".

Instead of offering each member a discount, the retention team passes the issue to the branch manager, the problem is fixed and members with the signal are told about it. Over the next two months the signal share at that branch is tracked.

Typical mistakes

  • Presenting a signal as a prediction.
  • Sending an automatic discount for every signal — customers learn that complaining pays.
  • Watching only the "I want to cancel" signal — it is already late.
  • Covering a system problem with individual retention steps.

Limits

  • Unhappy customers who never write do not appear in conversations.
  • AI may misread a signal; irony and emotional phrasing are difficult.
  • Knowing whether a customer actually left after a signal needs payment or contract data.

Churn signals in Vexvon

In Vexvon the company builds fields such as "churn signal", "topic of dissatisfaction" and "problem resolved" itself; AI picks from the customer's words and shows the evidence message. The panel's AI assistant can list customers matching a condition — for example, customers with a signal in the last two weeks whose problem is not resolved — and show each customer's full record. Vexvon does not predict churn; reviewing the list and deciding is the team's job. More: analytics and CRM.

Next step

Read the conversations of 20 customers who cancelled last month, from before they cancelled: which signals were visible, and when? That will sharpen the signal list for your business. On retention calls, see telecom churn retention calls; we can set up the fields together in a demo.

Further reading on this topic: negative customer feedback signals, sentiment vs customer satisfaction.

Live demo

Ready? Let's start

See Vexvon live in a 10-minute demo.

  • A scenario built for your business
  • A live sample call
  • A tour of the platform
Get a demoorBook a meeting

Your details are used only for the demo and to get in touch.