Predictive Intelligence combines operational data — reports, incidents, risks, SLA performance, monitoring, and automation history — into health scores, trend analysis, and forward-looking signals across your client portfolio. Open Dashboard → Predictive to review portfolio summaries and drill into per-client forecasts. Access is gated by the ai_predictive_intelligence plan feature, available on Professional and above.
Predictive Intelligence gives agency leaders a portfolio-level view of client health before problems surface in QBRs or escalation calls. Open Dashboard → Predictive to see overall confidence, executive overview narrative, forecast counts, and key metric cards for churn risk, SLA breaches, incident likelihood, and revenue trajectory.
Each client with sufficient operational history receives a health score, trend direction (improving, stable, declining, critical), and contributing factors drawn from recent activity. Portfolio views highlight clients flagged for attention so account owners can prioritize outreach.
Per-client predictive pages show historical windows (7 days, 30 days, 90 days, 12 months), trend comparisons, incident and risk forecasts, SLA breach probability, and actionable recommendations linked to relevant records. The module checks ai_predictive_intelligence at the plan level — API access via predictive.read scope requires the same feature.
Purpose
Reactive account management — learning about churn risk only when a client complains — is expensive and damages trust. Predictive Intelligence exists to shift portfolio reviews from backward-looking reporting to forward-looking intervention.
Health scores and early warning signals help operations leaders allocate attention across dozens or hundreds of clients. Rather than reviewing every account equally, teams can focus on declining trajectories, elevated churn probability, or SLA breach forecasts while maintaining lighter touch on stable and growing accounts.
Portfolio signals consolidate data that already lives in Clients, Reports, Risks, Incidents, Monitoring, and SLA modules. Predictive does not replace account owner judgment — it surfaces patterns that are easy to miss when reviewing clients individually.
Core Concepts
FAQ
Which plan includes Predictive Intelligence?
Professional, Business, and Enterprise plans include the ai_predictive_intelligence feature with health scores and portfolio forecasts. Workspaces without the feature should upgrade through Settings → Billing.
How often are forecasts updated?
Forecasts refresh automatically on a nightly schedule. You can trigger an immediate recalculation with the Refresh button on Dashboard → Predictive.
Should I share health scores directly with clients?
Predictive views are designed for internal portfolio management. Validate signals with account context before external conversations — scores reflect operational data, not client relationship quality alone.
What data improves forecast confidence?
Consistent report publishing, recorded incidents and risks, SLA policy assignment, monitoring signals, and automation execution history all increase data density and raise confidence labels.
What is the ai_predictive_intelligence feature flag?
It is the plan-level gate for Dashboard → Predictive, per-client predictive pages, manual refresh actions, and API endpoints requiring predictive.read scope. Diagnostics show feature status at Settings → Diagnostics.
Are predictions AI-generated black-box outputs?
No. Predictive views use transparent, rule-based models computed from your workspace data. Confidence labels indicate data sufficiency; contributing factors show which signals drive each score.
Need help?
Contact support@auroranexis.com for onboarding support, billing questions, or product guidance. Include your workspace name, the module you are working in, and a brief description of your goal so we can respond efficiently.
Health score — composite numeric signal reflecting operational activity, SLA adherence, incident volume, report cadence, and related factors for a single client.
Trend direction — whether a client's health is improving, stable, declining, or critical compared to prior windows.
Confidence label — Very High, High, Medium, or Low; indicates how much data supports the forecast.
Churn segment — likely churn, stable, or growing classification based on probability and health trajectory.
Portfolio signals — aggregated dashboard metrics highlighting at-risk clients, SLA breach forecasts, and incident likelihood across the portfolio.
SLA breach forecast — projected probability that open items will breach response targets.
Incident forecast — predicted incident likelihood and severity band for at-risk clients.
Historical window — rolling comparison period (7d, 30d, 90d, 12m) for trend analysis.
ai_predictive_intelligence — plan feature flag gating Dashboard → Predictive, per-client predictive pages, and predictive.read API scope.
Features
Portfolio dashboard with executive overview and overall confidence score.
Customer forecast cards segmenting likely churn, stable, and growing accounts.
Health scores and trend badges per client with contributing factors.
SLA breach forecast with per-client probability and open item counts.
Incident forecast highlighting at-risk clients with predicted severity.
Revenue forecast with recurring revenue trend and healthy vs declining account counts (when profitability data exists).
Per-client predictive detail with health history and linked recommendations.
Manual refresh for on-demand recalculation after bulk data changes.
API access via predictive.read scope for integrations (requires ai_predictive_intelligence).
Step-by-step usage
Confirm your plan includes ai_predictive_intelligence (Professional or above). Open Dashboard → Predictive.
Read the executive overview and note overall confidence — low confidence means insufficient historical data across the portfolio.
Review customer forecast cards. Identify clients in the likely churn segment for immediate account owner review.
Check SLA breach forecast for clients with elevated breach probability and open SLA-tracked items.
Review incident forecast for clients with high predicted severity — validate with recent monitoring and risk records.
Click a client name to open the per-client predictive detail page.
On the client page, compare historical windows to understand whether trends are new or sustained.
Follow linked recommendations to create risks, incidents, or client notes as follow-up actions.
Include predictive highlights in weekly portfolio standups and QBR preparation.
Use Refresh after importing historical data or closing a large batch of incidents to update scores immediately.
Best Practices
Treat scores as signals, not verdicts — validate with account owners before client conversations.
Ensure underlying data is current: stale reports, unrecorded incidents, and missing SLA assignments reduce forecast accuracy.
Review predictive insights weekly in portfolio standups; assign owners to flagged clients within 48 hours.
Use declining trends as prompts for internal review, not automatic client escalation.
Document interventions as risks or incidents so future forecasts reflect your response history.
Compare confidence labels before acting — Medium or Low confidence forecasts need more validation.
Pair predictive views with Monitoring and Clients modules for full operational context.
Verify ai_predictive_intelligence is enabled before building integrations against predictive.read API endpoints.
Examples
Marketing agency
Before a quarterly business review, the account manager opens the client's predictive detail page, notes 90-day trend comparisons, and documents improving report cadence alongside one elevated SLA breach forecast. The QBR deck includes both achievements and proactive items the agency is addressing, backed by health score history from Dashboard → Predictive.
AI automation agency
An automation agency newly upgraded to Professional enables ai_predictive_intelligence and opens Dashboard → Predictive. Initial confidence is Low because historical data is sparse. Over six weeks, consistent report publishing and incident recording raise confidence labels. The portfolio owner establishes a baseline health score review as part of the monthly operations cadence.
MSP
Every Monday, the operations lead opens Dashboard → Predictive and focuses on the likely churn segment. Three clients show declining health over 30 days. The lead assigns each to its account owner, who reviews per-client contributing factors — missed reports, open incidents, SLA warnings — and schedules internal check-ins before any client-facing outreach.
Consultancy
SLA forecast shows elevated breach probability for a client with four open incidents. The delivery lead reassigns capacity, resolves two items same-day, and creates a risk record documenting root cause. After Refresh on Dashboard → Predictive, breach probability drops and the intervention is auditable in the operational modules.
Enterprise deployment
An agency managing eighty clients cannot review every account weekly. The director uses portfolio signals on Dashboard → Predictive to identify twelve accounts in declining or critical trend bands. Account owners receive a prioritized list with health scores, contributing factors, and recommended actions — stable and growing segments receive lighter scheduled touchpoints.
Troubleshooting
Common predictive intelligence issues
Problem
Cause
Solution
Module locked or missing from navigation
Plan lacks ai_predictive_intelligence feature on current subscription
Upgrade to Professional via Settings → Billing or contact sales for Enterprise
All clients show unknown or low confidence
Insufficient historical activity across the portfolio
Ensure reports, incidents, monitoring data, and SLA assignments exist for active clients
Stale scores after major data changes
Forecasts refresh on nightly schedule by default
Click Refresh on Dashboard → Predictive after bulk imports or incident closures
Client missing from forecasts
New client without activity history or archived status
Confirm client status is active; allow time for data across at least one historical window
Revenue forecast empty
Profitability data unavailable on plan or not configured
Configure client revenue in profitability module; verify plan includes profitability feature
Health score differs between dashboard and client page
Scores recalculate on different refresh schedules
Use Refresh on both views for consistency after significant changes
API returns 403 on predictive endpoints
Plan missing ai_predictive_intelligence or API key lacks predictive.read scope
Verify plan tier and create a new API key with predictive.read scope in Settings → API