Fix Single-Threaded Relationships

An account that depends on one person on either side is one resignation away from risk. If your only champion leaves, or the one teammate who knows them moves on, the relationship resets just when it matters. FunnelStory flags these accounts from the conversations it already ingests, so you can widen coverage while it's easy — not after the champion's farewell email. Use this guide to find single-threaded and fading accounts, decide who to engage next, and keep new risks from slipping through.

How FunnelStory spots thin coverage

FunnelStory scores every account on two relationship risks, using only conversations the customer took part in — an email your team sent that nobody answered doesn't count as engagement:

Risk	Flagged when	Severity rises when
Single-Threaded	Too few of your team members, or too few customer contacts, have been engaged recently	The renewal is close, the contract is large, health is low, or the account is predicted to churn
Engagement Drop	Conversation volume or meeting attendance fell month over month	The drop is steep, or the account went dark with no conversations at all

Both also create needle movers — Single-Threaded Relationship and Relationship Drop — so they show up in the same queue as every other risk. Admins tune the thresholds under Configuration → Features → Relationship Map.

Step 1: Find the accounts

• Across your book — open Focus Areas → Revenue Review and read the Relationships column: it shows Single-threaded or Multi-threaded, plus an engagement-drop label when conversation has fallen. Sort by revenue so the largest thin accounts come first.
• As a queue — in Needle Movers, open the Single-Threaded Relationship and Relationship Drop type tabs. Each one has an owner and a status, so the work can be assigned and tracked like any other risk.
• On one account — the Relationship Intelligence panel at the top of Renewal → Dossier shows the account's coverage, engagement, and relationship scores, with the date range that was scored.

Work red severity first: those are single-threaded accounts renewing soon, worth a lot, or already predicted to churn.

Step 2: See who's engaged and who isn't

Open the account's Customer Relations tab. The relationship map is a grid of customer contacts across the top and your team down the side; a dot marks who has talked to whom in the selected window. Read it for:

• One column of dots — a single customer contact carries the relationship.
• One row of dots — a single person on your team does.
• Contacts nobody talks to — people who are on the account but have never been engaged.

Then open Renewal → Dossier and read the stakeholder profiles: each contact's role (Champion, Economic Buyer, Executive Sponsor, Power User, and so on), whether they're Active, Flat, or Dark, and what they care about.

Step 3: Pick who to engage next

Choose one or two people to add, not a list of ten. Good candidates, in order:

1. The economic buyer or executive sponsor, if nobody on your team talks to them. They decide the renewal.
2. An active power user in a team your champion doesn't cover. They already value the product.
3. A contact who went Dark after being active. A short check-in often recovers them — and tells you if something changed.

On your side, match the contact to the right teammate — an executive sponsor to your leadership, a technical contact to a solutions engineer — so coverage grows on both sides.

Step 4: Make the introduction

Ask your champion to introduce you; it's faster and warmer than cold outreach. Tie the ask to something the new contact cares about, from their stakeholder profile, and follow through with a meeting that has a clear purpose — a roadmap preview, an adoption review for their team, or a QBR.

Record the plan as a task under Adoption → Tasks with an owner and date, so the next person to open the account sees it.

Step 5: Catch the next one automatically

Relationship risk changes weekly. Put an agent on it so new cases reach the right person without anyone checking a report:

Detect	Investigate	Act
Needle Mover trigger on Single-Threaded Relationship, Relationship Drop, and Personnel Change risks	Read the account's relationship map history and stakeholder facts: who's still engaged, who held the role, and what they cared about	Post a Slack alert to the account team; draft an Action Card that names the next contact to engage and why

See Design an Agent: Detect, Investigate, Act for building it.

Measure it

Coverage should widen within weeks. Watch the Relationships column in Revenue Review move from Single-threaded to Multi-threaded, and the relationship needle movers resolve as the risk clears. If an account stays single-threaded after an introduction, check the map: meetings with the new contact have to happen, and be recorded, before they count.

Related

• Relationship Risk Configuration — thresholds and severity rules
• Relationship maps — reading the grid
• Account Dossier — stakeholder profiles
• Prepare for a Customer Call
• Prevent Churn with a Retention Outcome Agent