The Daily Loop
This is the Mission Control rhythm — the 5-step cycle that keeps customer issues moving from detection to resolution. It runs continuously, mostly automated, with your team stepping in where human judgment matters.
The 5 Steps
1. Issue Detected
Sailfish continuously monitors your application. Issues are detected through:
- Exception patterns and error spikes
- Customer reports from connected sources (Slack, Zendesk)
- Workflow conditions you've configured
- In-app bug reports from users
2. Impact Calculated
Within seconds of detection, Sailfish answers the critical questions:
- How many users are affected?
- Which users — including those who never reported it?
- How severe is the impact?
- Is it getting worse or stabilizing?
3. Triage Decision Made
Based on impact data, your team decides:
- Fix now — High-impact, create an engineering ticket immediately
- Monitor — Moderate impact, set up a workflow to alert if it worsens
- Defer — Low impact, log it and move on
Product owns prioritization. Sailfish provides the data to make it a 30-second decision, not a 30-minute meeting.
4. Action Triggered
Actions can be manual or automated:
- Automated — Workflows fire Slack alerts, create Jira tickets, or trigger auto-fix
- Manual — Engineer opens the issue, debugs with full context, ships a fix
- Proactive — Support reaches out to affected customers before they complain
5. Resolution + Feedback
The loop closes when:
- The fix is deployed
- Affected customers are notified (or proactively contacted)
- The issue stops recurring — Sailfish confirms it automatically
What "Good" Looks Like
| Signal | Healthy | Needs Attention |
|---|---|---|
| Issues detected daily | Yes — means telemetry is working | No issues = check instrumentation |
| Time from detection → triage | Minutes to hours | Days |
| Time from triage → resolution | Hours to days | Weeks |
| Customer outreach on high-impact issues | Proactive | Reactive or none |
| Workflows firing appropriately | Alerts for real issues | Too noisy or too quiet |