Relationship Maps show who matters structurally—not enough on whether the team actually engages those people. This initiative brings interaction frequency and recency into the CRUSH Relationship Map surface using governed Salesforce signals, with UX that preserves sharing and accessibility.
As someone working a Relationship Map, I want to see how recently and how often we've engaged each contact so that I can coach coverage with evidence—not guesswork—from inside CRUSH.
Jira SCRUM-97 sits under RM Governance & Coverage (SCRUM-132); it complements staleness alerting (SCRUM-102). Full taxonomy, rollup rules, and UI pattern are spelled out there.
Please authenticate to join the conversation.
Planned
Backlog
maps
About 2 months ago

Nick Campion
Get notified by email when there are changes.
Planned
Backlog
maps
About 2 months ago

Nick Campion
Get notified by email when there are changes.