What FixControl is
FixControl is an operator control plane for inbound work. Customer reports come in over email, Slack, or Microsoft Teams. The intake agent classifies each one. You get a per-item dashboard with structured context, suggested next steps, and — when relevant — a draft reply or a draft patch.
You stay in control. By default, nothing is sent, applied, or merged without an explicit operator action. Opt-in automation exists — policy-scoped auto-replies and per-project auto-delivery of approved patches — but it is off by default, and when enabled every automatic action is written to the audit log.
What FixControl is not
- Not an autonomous AI agent. AI prepares the work; you approve.
- Not a generic ticketing system. The shape of an issue and the actions per kind are opinionated.
- Not a generic chatbot. Slack and Teams are governed action surfaces: they can answer ticket questions, route intake, collect approvals, and update cards, while every write/action follows project scope, permissions, capability health, outbox/retry, and audit. Channel messages also land as inbox rows so nothing is lost.
End-to-end flow
Channels Intake agent Operator review
│ │ │
▼ ▼ ▼
Inbox row ──────────► classified ─────────► convert / reply
│
▼
Issue detail
│
▼
Approve / Dry run / Run fix
│
▼
Plan approval ◄── you approve the plan
│
▼
Patch (PR or commit)
│
▼
Patch approval ◄── you approve the change
│
▼
ApplyYou see every step. You approve every meaningful gate — for risky work, the plan first, then the patch.
Three kinds of inbound work
| Kind | What it is | What you do |
|---|---|---|
| SUPPORT | A question, request for help, "how does X work" | Send a reply (you may use the AI draft, edited or as-is) |
| BUG | Something broken at the customer | Reproduce, fix, deploy — with the patch pipeline |
| FEATURE | A request for new functionality | Triage, scope, prioritise, then build |
The detail layout changes per kind. SUPPORT puts the draft reply on top. BUG puts Risks & Impact on top. FEATURE puts triage actions before any dev work.
Five-step tour
- Inbox. Every new inbound item. Use
j/kto navigate,Enterto open. - Convert to issue. Click when the row is actual work.
- Issue detail. Structured context: rationale, risks, sources, action items, draft reply (for SUPPORT).
- Action items. Concrete follow-up steps from the workflow agent. Different per kind.
- Send or execute. For SUPPORT, click Send in the Auto-reply panel. For BUG, click Approve or Run fix to start the patch pipeline.
Key concepts
- Plan before patch. For risky work the AI first drafts an execution plan that you approve — you steer before there's any code, not after. Only then comes the patch, with its own approval.
- Confidence ≠ Risk. Confidence is the model's self-rating; risk is an independent judgement on consequences. High confidence + high risk is a normal combination — read both.
- Suggested → Auto-drafted → Auto-sent. Three escalation levels. You start at suggested. Auto-* is opt-in per surface.
- Retry lineage. Patches that need revision link to their predecessor. After three revisions the chain pauses for human triage.
- Dry run. Always available next to Run fix. Runs the pipeline up to apply, without committing.
- Saved views. Per-user filter+sort+search bookmarks on every operator page.
Where to start
- Mostly customer questions? → Inbox.
- Mostly bugs and features? → Issues.
- Want to know how to approve a plan or patch? → Approvals.
- Knowing what FixControl integrates with? → Integrations.
- Setting up FixControl for a new organization? → Admin guide → Onboarding.