Use the Adoption Dashboard to spot stagnant adoption and re-engage users or teams before it becomes a retention risk.
Identifying and Re-Engaging Low Adoption Users and Teams
Start here when: Adoption feels stagnant, leadership is asking why certain teams aren't using Spekit, or you want to proactively prevent churn before it becomes a problem.
Step 1: Sort User Activity and Team Activity Tables
Sort both tables by the lowest number of views, searches, and chats to immediately surface who isn't engaging. These are your re-engagement targets.
Step 2: Look for Patterns
Once you've identified low-engagement users or teams, ask:
- Are they only in the All Spekit Users default group? (Cross-reference with the Activation Dashboard)
- Do they have relevant content in their topics?
- Is an Expert assigned to their team?
- Are they accessing content in the right channel? (Check Where Content is Being Accessed)
Step 3: Take Action
| Scenario | Suggested Action |
|---|---|
| User has zero views and zero searches | Check Activation Dashboard — they may not have fully onboarded yet |
| Team has low views but high searches | Users are looking but not finding — audit topic content for that team |
| User views content but never marks as read | Send a reminder about the Mark as Read feature or check if required content is clearly flagged |
| Team has low external shares | Review whether Deal Room content is relevant and up to date for that team |
Best Practices
- Cross-reference low adoption in the Adoption Dashboard with activation data in the Activation Dashboard for a full picture, and tailor your outreach based on where each user is in their journey.
- Use the Dashboard Agent to ask "Which teams have had zero searches in the last 30 days?" for a fast re-engagement list — don't just look at views, since users who search but find nothing are also a priority.
- Set a monthly alert on Team Activity for "Results have changed" to track whether re-engagement efforts are working, and remember low adoption isn't always a content problem — sometimes it's an awareness or onboarding issue.