This page explains how BatteryArb handles onboarding, response expectations, API stability communication, and reliability references for evaluation, pilot, and production customers.
| Plan Stage | Support posture | Typical use | Target response window |
|---|---|---|---|
| Sandbox / Evaluation | Email support and self-serve docs | Technical diligence and initial validation | Within 2 business days |
| Pilot / Team | Evaluation support plus rollout guidance | One workflow, one market, or one team pilot | Within 1 business day |
| Enterprise / Production | Priority support and onboarding coordination | Production rollout, procurement, and security review | Coordinated during onboarding |
Core endpoint behavior is documented in OpenAPI. Material breaking changes should be communicated before rollout so buyers are not surprised during evaluation or production planning.
Most pilots start with buyer fit, technical validation, and one workflow definition, then move into a bounded evaluation period with agreed success criteria.
Health checks and public docs remain available for operational transparency. Serious incidents should be routed through direct support email and the contact path.
Use Contact for broad questions, Pilot for structured evaluation, and Docs/Quickstart for technical validation.