Notice when your champion moves on.
A familiar contact leaving can create a gap in the relationship. Bring the change to the account owner with the available evidence and people to research next.
One action: confirm who now owns the relationship.
06Churn detection
Catch relationship changes before the renewal conversation.
Lumnis surfaces customer changes that deserve an account-owner review, starting with the people and relationships your team depends on.
A relationship change, with a clear review action
Illustrative example
Customer account
Your champion changed roles.
Hearth Computing
Theo Lane
Former champion · left company
Role change · public profile · Sep 01
Amira Malik
Operations lead
Confirm who owns the account relationship now.
A role change alone does not establish churn.
Put it to work
See the change. Start the right conversation.
Refresh the context around a renewal.
Check whether roles and responsibilities still match your account plan. Use observed changes to guide a conversation with the customer, rather than treating last quarter’s contacts as current.
A better-informed account review before the next renewal discussion.
Evidence before action
An early review signal, not a churn verdict.
Lumnis connects a specific people change to an account review. The owner sees what changed, what remains uncertain, and the next question to resolve.
A role change alone does not establish dissatisfaction, renewal risk, or intent to leave.
Explore account intelligenceA few useful details.
What does Lumnis flag for an account review?
Lumnis surfaces changes in the people and relationships around your customer accounts, with supporting evidence and a suggested next step. The account owner can review these signals alongside CRM and renewal context.
What should the account owner do with a signal?
Verify the change, confirm who owns the relationship, and speak with the customer. Combine this context with account health and renewal information before drawing a conclusion.