Relationship Risk Configuration
Relationship Risk lets you control exactly when FunnelStory flags an account for coverage gaps or conversation drop-off. Admins can tune two independent risk models — Single-Threaded Risk and Engagement Drop — and retrigger the analysis at any time.
Navigate to Settings → Relationship Risk to open the configuration page.
Saving and retriggering
- Save Configuration — persists any threshold changes. Updated thresholds apply the next time the analysis runs or is manually retriggered.
- Retrigger Analysis — reruns the relationship risk computation immediately against all accounts using the current configuration. Use this after saving changes to see results right away.
Single-Threaded Risk
Controls when an account is flagged for having too few team members or contacts engaged.
| Setting | Description | Default |
|---|---|---|
| Min team threads | Minimum number of distinct team members who must have recent conversations to avoid a risk flag. | 2 |
| Contact coverage | Percentage of the account's total tracked users that must be covered as contacts. | 5% |
| Max contact threshold | Upper cap on required contacts, regardless of user count. Prevents unrealistic coverage requirements for very large accounts. | 5 |
| Low health score threshold | Prediction score below this value is considered low health. Accounts below this threshold with single-threaded coverage are escalated to a higher severity. | — |
| Renewal window — red | Days until renewal that triggers a red severity flag. | 90 days |
| Renewal window — amber | Days until renewal that triggers an amber severity flag. Must be greater than or equal to the red window. | 180 days |
| High-value contract (USD) | Contract amount above which a single-threaded account is automatically flagged red, regardless of other thresholds. | $50,000 |
How severity is determined
An account is flagged Single-Threaded when it has fewer active team members than Min team threads or fewer tracked contacts than the coverage requirement. Once flagged, severity escalates to red when any of the following apply:
- The renewal date falls within the Renewal window — red window.
- The contract value exceeds the High-value contract threshold.
- The health score is below the Low health score threshold.
Otherwise the flag is amber.
Engagement Drop
Controls when a month-over-month drop in conversation volume is flagged, and how severity is assigned.
| Setting | Description | Default |
|---|---|---|
| Minimum baseline conversations | Prior-month conversation count below this threshold skips flagging entirely. | 3 |
| Drop threshold | Month-over-month conversation drop percentage that triggers a flag. | 20% |
| Attendance drop threshold | Avg attendee count decrease (prior − current) that signals an attendance drop. | — |
| Sentiment drop threshold | Current avg sentiment below this value flags a sentiment drop. | −0.1 |
How severity is determined
When the prior month exceeds the minimum baseline, FunnelStory compares the current month's conversation count to the prior month. If the drop exceeds the Drop threshold, the account is flagged. Severity — green, amber, or red — is then assigned based on two quality signals:
- Attendance drop — average attendee count fell by more than the Attendance drop threshold.
- Sentiment drop — current average sentiment is below the Sentiment drop threshold.
| Quality signals | Severity |
|---|---|
| Went dark (zero conversations this month) | Red |
| Both attendance drop and sentiment drop | Red |
| Attendance drop only or sentiment drop only | Amber |
| Neither — volume drop only | Green |
Related
- Revenue Review — where Single-Threaded Risk and Engagement Drop flags surface in the account table.
- Relationship Maps — per-account visualization of team and contact coverage.
- Predictions Overview — health scores that feed into risk severity calculations.