Review customer relationships that depend on one known person. Separate verified role access, recent contact and revenue exposure before choosing a relationship action.
A key account can receive frequent attention and still depend on one customer contact. The relationship is active, but every specification discussion, budget question and escalation goes through the same person. A dependency review asks what would happen if that person changed jobs, took leave or stopped responding.
Use existing account coverage measures to assess attention. This article concerns relationship breadth and continuity, not another definition of contact recency.
Choose a material customer decision or relationship scope. A small repeat-order account may reasonably have one purchasing contact. A multi-site account with a complex expansion proposal may need verified routes to several responsibilities. Apply a proportionate rule rather than insisting on a universal minimum number of people.
State whether the review concerns current service continuity, renewal or a specific expansion purchase. The same account can have an alternative route for routine orders and no alternative for a new category. Reporting one overall red flag would hide that distinction.
Do not infer dependency solely from an incomplete CRM. A missing contact record may indicate missing documentation rather than a weak relationship. Report evidence gaps separately from confirmed reliance.
Join authorized account IDs, contact IDs, verified role assignments and the relevant activity history. Keep the source and confirmation date for each role. The buying-group map provides the role structure for a purchase decision.
Count distinct people, not emails, meeting attendees or role assignments. One person occupying three roles still represents one departure point. Equally, three people attending the same operational meeting do not necessarily provide three independent routes to a budget decision.
Record whether an alternative contact has agreed to the relevant responsibility. A name discovered on a public website is an identified lead, not a verified substitute.
The accounts and annual invoiced revenue below are invented DEMO records. All three have recent customer contact.
| Account | Revenue | Relationship evidence | Review classification |
|---|---|---|---|
| DEMO-A | $200,000 | One person holds all confirmed buying roles | Confirmed dependency |
| DEMO-B | $150,000 | Budget owner and operational lead have independent verified routes | No dependency under this rule |
| DEMO-C | $50,000 | Contact records incomplete | Unknown |
The book totals $400,000. Confirmed dependency represents $200,000 / $400,000 = 50% of revenue. Unknown evidence represents another 12.5%. These categories describe the review population; neither is a predicted churn loss.
Classifying unknown accounts as resilient would understate uncertainty. Classifying every unknown as confirmed dependency would confuse a data-maintenance task with a relationship finding. Publish all three states and their basis.
Ask the account owner to describe the next practical step if the primary contact became unavailable tomorrow. Who could confirm an urgent order? Who could continue the expansion discussion? Where would an escalation go? Review the answers against customer-confirmed evidence.
For DEMO-A, the correct action may be to ask the existing contact to introduce the operational lead and procurement coordinator. It is not to bypass that person or contact an entire customer organization indiscriminately.
The customer-gap conversation remains a question about need. Additional contacts should clarify that need and the decision route, rather than multiply unsupported sales claims.
Small owner-managed businesses, centralized purchasing and customer communication preferences can legitimately produce a narrow contact structure. Record an accepted exception, its rationale and review date. Do not penalize an account owner for respecting a customer-approved route.
A confidentiality restriction may also prevent sharing personal details in a common report. Role IDs and a statement that an approved escalation route exists may be sufficient for the management view. Verify access to the underlying record separately.
Choose an introduction, documentation update, renewed role confirmation or accepted exception. Review completion using the confirmed relationship change, not merely the number of calls made. Apply the salesperson handover checklist when the internal owner changes too.
The completed customer-growth review shows how evidence can sit beside account priorities. Bring an authorized relationship sample to Covirage contact to agree the analytical view and review scope.
Not necessarily. Both may be users with no access to the budget or approval route. Review the responsibilities and alternative access they provide, not just the contact count.
It is a reporting exposure under a stated relationship rule. It does not provide a loss probability or prove that the customer would leave if the contact departed.
Coverage concerns whether the account received its required attention. Dependency concerns whether the relationship can continue through another verified route if one person becomes unavailable.