Health Settings

Configure the default grace period for manual health overrides, require a reason on every override, and choose which custom objects feed into AI Health.

The admin Health settings page controls three things: the grace period that holds a manual override before AI takes back over, the reason users must provide on every override, and the custom objects the AI considers when it calculates a customer’s health.

Accessing Health Settings

1. Navigate to Admin → Settings → Health. You need admin permissions to access this page.

2. The Health section exposes three 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
   • Additional Custom Objects for Health — Pick custom objects whose records should flow into AI Health alongside accounts, activities, and opportunities

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:

Days	When to use
7	Fast-moving accounts where you want the AI to revisit quickly
14	Two-week feedback cycles
30	Balanced default — enough room to act on the override, short enough to stay current
60	Slower-moving renewal cycles
90	Quarterly 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.

Additional Custom Objects for Health

By default the AI considers accounts, activities, and opportunities when it scores health. If you’ve modeled additional business state as Custom Objects — onboarding milestones, support tier records, escalation logs, expansion plays — you can tell AI Health to read those too.

1. Scroll to Additional Custom Objects for Health on the Health settings page.

2. Click Add Custom Object and pick a custom object type from the dropdown. Only custom objects with account as their parent entity appear in the list, because each record needs to attach to a specific account for health to use it.

3. Repeat for every custom object you want included. Each one shows up as a removable chip; click the × on a chip to drop it.

The next health calculation reads each linked custom-object record for the account and surfaces it to the AI alongside standard signals. Records appear in the Health rationale Stella generates for the account, so reviewers can see exactly which custom-object rows contributed.

Choose objects that genuinely move the health needle — onboarding-stage rows, support escalations, executive-sponsor changes. Adding low-signal objects (e.g., logging tables, audit trails) makes the AI noisier without improving accuracy.

You can change the list at any time. New selections take effect on the next scheduled health recompute for each account, or immediately if you trigger a manual recalculation.

Need Help?

Contact [e-mail] 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.