Catch customer risk while there is still time.
Compass brings support, product usage, account, renewal, and warehouse context into the channels where customer teams already coordinate.
Brittany Chen
@compass Which accounts have rising ticket volume before renewal?
Turn scattered customer signals into earlier action.
Renewal risk, onboarding drop-off, support spikes, and account health stay in one thread while the team can still intervene.
Pylon
P1 tickets
Salesforce
42 days to renew
Segment
usage drop
Risk signals before the escalation
Spot the account that looks fine in CRM but is getting louder in support and quieter in product.
Support, usage, and account context together
Compass brings curated ticket, usage, CRM, renewal, and warehouse context into one answer path.
Curated context
WAU = users with a core workspace event in the trailing 7 days. Login-only activity is excluded.
with wau_events as (
select user_id,
date_trunc('week', event_time) as week
from product_events
where event_name in ('project_created',
'query_run', 'teammate_invited',
'shared_answer_viewed')
group by 1, 2
)
select week, count(*) as weekly_active_users
from wau_events
group by 1Faster renewal prep
CSMs can ask what changed for an account while the renewal plan is still being written.
Answers where customer teams coordinate
Compass answers in Slack or Teams with the definitions, permissions, and account context your data team has approved.
Mine the pattern behind churn risk
The next save motion is usually hiding in repeated tickets, stalled usage, and old account notes.
Reviewed guidance over hidden memory
Compass turns repeated risk patterns, playbook corrections, and data-team caveats into reviewed guidance for future customer questions.
PylonSalesforce
Google Docs
NotionTurn risk into the next save motion
Move from scattered warning signs to a renewal brief, account update, and recovery plan while there is still time to act.
MCP Servers for customer work
Compass can use customer MCP Servers as inputs and outputs: read support and account context, draft the brief, and write next steps back.
How customer teams adopt Compass
Pick one concrete customer workflow: review renewal risk for an upcoming cohort, or diagnose onboarding drop-off before it becomes an escalation. Then expand once the health signals and review loop are working.
Pick one renewal cohort
Data teams connect CRM, renewal dates, support tickets, product usage, and warehouse context for accounts renewing soon.
Answer risk questions in the channel
CSMs ask which accounts are getting louder in support, quieter in product, or showing signals that need intervention.
Review missing health signals
Data teams see where health scores, usage events, ticket tags, or account ownership data are missing and turn them into roadmap work.
Move renewal reviews into rollout
Customer teams can self-serve common renewal-risk questions while data teams keep definitions, access, and context under review.
