Global verdict
The status says whether revenue needs attention now or only monitoring without escalation.
Workflow demo
See CashFlowCanary in action, without real data.
This demo follows a fictional incident end to end: detection, incident report, AI intervention on a paid plan, recheck and intervention report.
Demonstration
The scenario shows each useful decision.
The cockpit should not only say red or green. It should explain what broke, what was attempted, why recovery is credible and what can be handed to the client.
-
09:42
Detection Payment rejects finalization
The checkout monitor gets a 503 error on order validation while the product page remains available.
- Checkout status KO
- Filtered HTML body
- Revenue impact linked to the plan
-
09:43
Incident The incident report is generated
The report lists affected monitors, likely cause, exact path and non-generic resolution leads.
- Exact description
- Proof without PII
- Agency logo when configured
-
09:46
AI intervention The agent fixes what the context allows
On a paid plan, the non-interactive AI applies a bounded action: checkout cache purge, targeted cache-rule disablement or restore of a known healthy configuration depending on diagnosis.
- Action logged
- No card data
- No customer data
-
09:52
Recheck The journey is replayed before closure
Product, cart, checkout, test payment and confirmation are checked again to avoid confusing temporary improvement with real recovery.
- Full control
- Before/after comparison
- Resolved only when every step passes
-
09:54
Handoff The intervention report details the actions
The resolution PDF keeps the client template and adds exact AI actions, timestamps, observed result and proof of recovery.
- Actions by monitor
- Verified result
- Clickable CTA when upsell applies
What the user should understand at a glance
Each cockpit zone has a clear operating role: prioritize, diagnose, act, then report back.
Monitored site
Product, cart, checkout, payment and confirmation stay separate to avoid vague diagnosis.
Open incident
The detail shows the exact symptom, opening time, proof and next action.
Channels
Email, Slack, Telegram and WhatsApp appear depending on plan and configuration, with masked destinations.
Reports
The incident report and intervention report keep the same design and content quality.
Plan and quotas
Cadence, history, exports and AI access explain why a paid plan protects better.
Read-only
A demo to understand usage, not to operate the real cockpit.
The page does not access customer accounts, trigger checks or contain personal information. It only illustrates the expected hierarchy in the client area.
- Fictitious data
- No access to any client store
- No persistent action
- No email, webhook, payment or account creation
