Fix hot prospects by implementing additive engagement scoring #519
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The hot prospects view was showing no results because the old scoring system used a priority-based approach where only the highest-priority signal counted. Email exchanges and Slack users weren't factoring into "hot" status. Changes: - Add migration 109_org_engagement_scoring.sql with additive scoring (0-100) - Slack users: 0-20 pts - Team members: 0-15 pts - Working groups: 0-15 pts - Recent activity: 0-15 pts - Email engagement: 0-15 pts - Event interest: 0-10 pts - Interest level: 0-10 pts - Low interest caps score at 20 - Update prospects.ts to use stored engagement_score - Hot prospects filter: score >= 30 - Convert 0-100 score to 1-5 display level for backwards compatibility - Show all contributing factors in engagement_reasons - Add refresh-scores endpoint for manual score updates - Add performance indexes for engagement_score queries - Update UI tooltip to show "Score: X/100" with all reasons 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Changes
compute_org_engagement_scorefunction with additive scoring:engagement_scorefor hot prospects filter (score >= 30), convert to 1-5 display level for backwards compatibilityPOST /api/admin/prospects/refresh-scoresendpointTest plan
🤖 Generated with Claude Code