Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.statisfy.com/llms.txt

Use this file to discover all available pages before exploring further.

When a user manually overrides an AI-calculated account health, two things happen: the override holds for a configurable grace period before the AI takes back over, and the user must provide a reason explaining why they overrode the AI. Both behaviors are controlled from the admin Health settings.

​
Accessing Health Settings

  1. Navigate to Admin → Settings → Health. You need admin permissions to access this page.
  2. The Health section exposes two related controls:
    • Default Grace Period (days) — How long a manual override is honored before the AI recalculates health
    • Override Reason Required — Always on; users cannot save an override without a reason

​
Default Grace Period

The grace period is the number of days a manual health override is locked in before AI-calculated health resumes. Statisfy ships with a default of 30 days. Available options:
DaysWhen to use
7Fast-moving accounts where you want the AI to revisit quickly
14Two-week feedback cycles
30Balanced default — enough room to act on the override, short enough to stay current
60Slower-moving renewal cycles
90Quarterly review cadences
Pick the value that matches your team’s review cadence. Once configured, this becomes the default that pre-fills the grace-period selector on every override modal — individual users can still pick a different grace period per override.
Changing the default does not retroactively change the grace period on overrides that have already been saved. The new default applies to overrides created from that point forward.

​
Mandatory Override Reason

Every manual health override now requires a non-empty reason. Whitespace-only reasons are rejected. This captures the rationale behind each override and feeds into Statisfy’s Customer Insights — the AI learns from your team’s collective context over time. What makes a good override reason:
  • Be specific about the signal you’re acting on (e.g., “Executive sponsor left; new buyer not yet onboarded”)
  • Reference the timeframe (e.g., “Through end of Q2 — renewal review”)
  • Avoid generic placeholders (“test”, “checking”, “n/a”)
Override reasons surface in the Customer Insights page over time. Concise, specific reasons make the AI’s calibration to your business more accurate.

​
How Overrides Work

  1. From an account detail page, click the Health badge and choose Override Health.
  2. Pick the new health value and an optional grace period (defaults to your tenant configuration).
  3. Enter an Override Reason — required, non-empty.
  4. Save. The override holds for the grace period, after which the AI-calculated health resumes.

​
Need Help?

Contact support@statisfy.com if you need a grace-period option outside the standard 7 / 14 / 30 / 60 / 90 day choices, or if you have questions about how override data feeds into Customer Insights.