Skip to content

For Customer Success

Check the events behind a health score before you act on it.

Your team defines account health, and engineering ships the product events it reads. Skene checks those events and fields, so a missing event is not read as low usage.

A real answer / Skene’s own workspace

Skene named five retention events missing from our own code.

Asked how to raise customer retention, Skene named the five events a health rule would read, from first_value to support_ticket_opened. None existed in Skene’s own code yet, which is the gap a health score would inherit.
Issues

See if tracking can answer it.

Ask a question. Skene names what is missing.

Ask a questionAuto
  • Marketing ops
  • Sales ops
  • CS ops
  • Product ops
  • RevOps / GTM ops
  • Data ops
The Agent page with the CS ops question set open, in Skene’s own skene-web workspace. Captured from the live app on 29 October 2026 and redrawn. The text is the app’s own.
AgentI want to increase retention with our customers

I want to increase retention with our customers

14 investigation steps

To answer this question we need the following events:

EventWhyParametersStatus
first_valueThis marks when an account reaches the product outcome, which is the key point to measure retention from.plantimestampNot found
feature_usedThis shows which parts of the product customers keep returning to after activation.featureplantimestampNot found
onboarding_step_completedThis identifies where customers stop during setup, which helps find early drop-off that hurts retention.steptimestampNot found
subscription_cancelledThis captures churn directly so you can measure how retention changes over time.plantimestampNot found
support_ticket_openedThis helps connect support issues to later churn or repeated use patterns.timestampNot found
Open coverage
A saved Agent answer in the same workspace. Captured from the live app on 29 October 2026 and redrawn. The text is the app’s own.

Review the missing event

Give engineering the event and the reason it matters.

  1. 01 / Skene

    Names the evidence gap

    support_ticket_opened is missing, so support issues cannot be tied to later churn.

  2. 02 / Coding agent

    Prepares the tracking change

    Follows the How to fix brief: add the event where tickets are created and send a timestamp.

  3. 03 / Engineering and Skene

    Review and check again

    Engineering reviews the change. Skene checks the evidence again once the event arrives.

  4. 04 / Customer Success

    Applies the health rule

    Scores the account only once the events its health rule reads are arriving.

Connect the sources your health rule reads.

Skene checks what the rule depends on.

Bring the account rule and connect the sources it needs. Skene maps the required events and fields, then checks each one, such as plan_tier and support_ticket_opened.

Customer Success owns the decision.

Keep account segments, thresholds and interventions in your existing workflow. Tracking that exists in the code does not show whether the account was active in the last 30 days.

Check the events behind one account health rule.

Skene lists the events and fields the rule reads and checks each one. Your first experiment is free, with no card.

Measure your first experiment free