/ to search
Documentation Tenant Settings

Tenant Settings

Prospect Intelligence

This page explains the Prospect Intelligence settings that live in Workspace Settings and what admins should expect after changing them.

Why this area exists

Prospect Intelligence is a tenant-wide scoring and flagging feature. The settings page lets the organization choose whether the feature is enabled and tune the thresholds behind its visible prospect outputs.

Confirmed settings shown in Workspace Settings:

  • Enable Prospect Intelligence
  • Major gift threshold
  • Use leadership annual giving
  • Leadership annual threshold
  • Lapsed after days
  • Second-gift window start
  • Second-gift window end
  • Planned giving relationship years
  • Planned giving consecutive years
  • Refresh Prospect Scores
  • Score freshness

What the setting area is for

This section exists to let the workspace define what counts as:

  • a major gift
  • a leadership annual donor
  • lapsed behavior
  • a second-gift follow-up window
  • a planned-giving style profile

These settings adjust thresholds only. They do not change the underlying donor records.

What changes after configuration

Changing the settings changes how future prospect calculations should be interpreted, but there is one critical operational detail:

  • saving the settings does not automatically refresh persisted prospect scores
  • admins must run Refresh Prospect Scores for visible saved outputs to catch up

That is one of the most important behavior details in this area.

Enablement and refresh behavior

When the feature is off:

  • the workspace should not rely on prospect scoring outputs

When the feature is on:

  • the threshold settings become meaningful
  • a refresh action is available
  • the score freshness message helps staff see whether scores have been refreshed yet
  • refreshed prospect score rows now persist a structured ask_optimization payload inside tenant_constituent_prospect_scores.explanation_factors_json

If there is no refresh timestamp, the page explicitly tells admins that the first set of scores still needs to be generated.

Persisted score payload notes

Each refreshed row in tenant_constituent_prospect_scores continues to store derived explanation data in explanation_factors_json.

That payload now also includes ask_optimization, which persists:

  • recommended_ask_anchor
  • recommended_ask_multiplier
  • confidence
  • reason_codes
  • strategy

This recommendation is based on existing first-party prospect score inputs and is intended for later reuse in public donation rendering and related runtime decisions.

In the current donation rendering pass, those persisted recommendations may be applied only for eligible logged-in donors and still fall back to the giving form baseline amounts whenever the runtime eligibility checks do not pass.

Operational notes

  • Workspace Settings saves Prospect Intelligence in simple mode.
  • The broader settings model contains more fields than this page currently exposes.
  • Make one threshold change at a time when possible so your team can understand what changed in the output.

Common mistakes

  • enabling the feature and assuming scores already exist
  • changing thresholds without running a refresh
  • adjusting many thresholds at once and losing the ability to interpret the change
  • treating score outputs as raw data instead of derived signals

What to test afterward

  • the score freshness message
  • a known major donor record
  • a known recently lapsed donor record
  • one donor who should fall inside or outside the second-gift window
  • any dashboard page or workflow where your staff uses prospect output

Related topics

Keep exploring

Related topics

Tenant Settings Ask Altrinum and AI Prospect Research Prospect Research Tutorial Prospect Research Prospect Research How-To