[Feature] Client Intelligence Sidebar #64

New Issue

2026-02-10T16:00:35Z

chihlasm commented

2026-02-10 16:00:35 +00:00

(Migrated from github.com)

Summary

When starting or during a session, show a sidebar with: previous sessions for this client, known configurations, recurring issues, and client-specific notes. Build a living client dossier from accumulated session data.

Why

MSPs manage dozens of clients; engineers often handle tickets for unfamiliar clients
Today they dig through PSA history or ask colleagues
ResolutionFlow already captures client_name on sessions — aggregating this is high value
Transforms from troubleshooting tool into client knowledge base

Unlocks

"This client had the same VPN issue 3 times in 6 months" — pattern detection
Client-specific configurations (e.g., "Acme uses Cisco, not Fortinet")
Handoff quality — new engineer sees full client history
Churn risk signals for MSP account managers

Implementation Notes

Client entity (could be lightweight: normalized name + optional metadata)
Aggregation query: sessions grouped by client_name
Sidebar in TreeNavigationPage showing:
- Session count for this client
- Recent sessions with outcomes
- Most common trees used
- Recurring issue alerts (see #60)
- Client notes (freeform, editable)
Depends on consistent client naming (or PSA integration for canonical names)

Relates To

#60 Recurring Issue Detection (subset of this)
#63 PSA Integration (canonical client names)

Sources

.claude/docs/ai/resolutionflow/10x/session-1.md — Massive Opportunity #3

Priority

Explore — medium-high effort, enormous value for MSPs with 30+ clients

## Summary When starting or during a session, show a sidebar with: previous sessions for this client, known configurations, recurring issues, and client-specific notes. Build a living client dossier from accumulated session data. ## Why - MSPs manage dozens of clients; engineers often handle tickets for unfamiliar clients - Today they dig through PSA history or ask colleagues - ResolutionFlow already captures `client_name` on sessions — aggregating this is high value - Transforms from troubleshooting tool into **client knowledge base** ## Unlocks - "This client had the same VPN issue 3 times in 6 months" — pattern detection - Client-specific configurations (e.g., "Acme uses Cisco, not Fortinet") - Handoff quality — new engineer sees full client history - Churn risk signals for MSP account managers ## Implementation Notes - Client entity (could be lightweight: normalized name + optional metadata) - Aggregation query: sessions grouped by client_name - Sidebar in TreeNavigationPage showing: - Session count for this client - Recent sessions with outcomes - Most common trees used - Recurring issue alerts (see #60) - Client notes (freeform, editable) - Depends on consistent client naming (or PSA integration for canonical names) ## Relates To - #60 Recurring Issue Detection (subset of this) - #63 PSA Integration (canonical client names) ## Sources - `.claude/docs/ai/resolutionflow/10x/session-1.md` — Massive Opportunity #3 ## Priority **Explore** — medium-high effort, enormous value for MSPs with 30+ clients

chihlasm commented

2026-03-21 15:26:34 +00:00

(Migrated from github.com)

Deferred — partially addressed by PSA ticket context pulling client info. Full client dossier is premature before validating core demand.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: chihlasm/resolutionflow#64