Contact Support
Before You Reach Out
Generate a diagnostic bundle first. It speeds up every support interaction significantly:Support Channels
Live Chat
The fastest way to reach us for questions and active issues. Available on acmeagentsupply.com/support — click the chat widget in the bottom-right corner.GitHub Issues
github.com/CHE10X/acme-site/issues For bugs, installation issues, and feature requests. GitHub Issues requires a diagnostic bundle for support and bug reports — the evidence gate enforces this automatically.What to Include
Support requests that include diagnostics get resolved faster. Include:- Diagnostic bundle —
acme support bundleoutput - ACME CLI version —
acme --version - Operating environment — macOS / Linux / Docker / k8s
- What you were doing — the context around the issue
- What you expected vs. what happened — specific, concrete descriptions help
Evidence-First Support Policy
ACME operates on an evidence-first model. Support and bug tickets without diagnostic evidence cannot be triaged. When you open a GitHub Issue, the evidence gate checks for:- OCTriage output (paste the terminal output of
acme triage) - A proof bundle path from OCTriage or Agent911
Response Times
| Channel | Typical Response |
|---|---|
| Live Chat | Minutes during business hours |
| Within 1 business day | |
| GitHub Issues | Within 2 business days |
What Support Handles
| Topic | Who handles it |
|---|---|
| Installation and setup | Support |
| CLI issues and bugs | Support / GitHub |
| RadCheck interpretation | Support |
| Sentinel configuration | Support |
| Agent911 and snapshots | Support |
| Billing and account | chip.ernst@gmail.com |
| Feature requests | GitHub Issues |