Operating Context
The operating context is how WisePilot understands your business funnel — automatically. It detects what data sources you have connected, computes performance baselines, and identifies where your funnel is underperforming. This context is then injected into every runner and workspace chat session, so the AI always knows what matters most for your business right now.
How It Works
Zero Configuration
You don’t need to set anything up. When you connect integrations (Google Analytics, HighLevel CRM, Google Ads, etc.), WisePilot automatically:
- Detects your funnel stages based on what’s connected
- Computes weekly baselines from your actual data
- Identifies constraints — which stage is underperforming
Auto-Detected Funnel
Your funnel is built from your connected integrations:
| Integration | Funnel Stages Added |
|---|
| HighLevel CRM | Revenue, Appointments |
| Google Analytics | Traffic (sessions) |
| Google Ads / Meta Ads | Ad Spend |
| Tracking Events | Leads (form submissions, CTA clicks) |
Weekly Baselines
Every Monday, WisePilot computes:
- 30-day and 90-day trailing averages for each funnel stage
- Current week vs previous week comparison
- Deviation from baseline — how far current performance is from normal
- Trend direction — improving, stable, or declining
New data sources start in a warming up state until there are at least 30 days of data, ensuring baselines are reliable before they influence AI decisions.
Constraint Detection
WisePilot walks your funnel from top (revenue) to bottom (traffic), looking for the first stage that’s significantly below its baseline. This becomes the primary constraint — the biggest bottleneck in your funnel.
- Warning — Performance 15%+ below baseline for 1+ weeks
- Critical — Performance 25%+ below baseline for 2+ weeks
- Healthy — All stages performing within normal range
Additional declining stages are tracked as secondary constraints.
What Runners See
When a runner executes, it receives your operating context as part of its system prompt:
- Which stage is constrained and by how much
- All funnel baselines with current values, deviations, and trends
- Stage-specific guidance (e.g., “Focus on booking flow and lead-to-appointment conversion”)
This means a content planner runner will naturally prioritize content that addresses your actual bottleneck, rather than producing generic recommendations.
Viewing Your Operating Context
Navigate to Settings > Operating to see:
Operating Profile Card
- Your detected vertical and funnel stages
- Data source badges showing where each metric comes from
- Auto-detected vs manually configured indicators
Baseline Dashboard
- Current performance for each funnel stage
- Baseline comparison with deviation percentages
- Trend indicators (improving, stable, declining)
- Warming-up status for new data sources
Overrides
While everything works automatically, you can optionally:
- Adjust thresholds — Change the sensitivity for individual stages (expand “Adjust thresholds” in the profile card)
- Disable stages — Exclude a stage from constraint detection
- Set a primary KPI — Tell the system what metric matters most to you
- Override vertical — If the auto-detected vertical isn’t right
Most users never need to change anything. The defaults work well for the vast majority of businesses.
How It Affects Prioritization
When a constraint is detected, it influences how work items and content opportunities are prioritized:
| Relevance | Priority Multiplier |
|---|
| Targets the primary constraint | 2x priority |
| Targets a secondary declining stage | 1.5x priority |
| Targets an adjacent stage | 1.2x priority |
| Targets an unrelated stage | 0.5x priority |
