Docs
For builders. And for evaluators.
The full documentation is at docs.fieldops-concept.example. Below is the page-level overview for product evaluators.
Setup guides
From signup to live in 8 to 12 days.
Customer + service area import
CSV format and template, or pull from your accounting integration. Service area + zoning configured.
Tech profiles + integrations
Configuring technician profiles, including skills and home-base addresses. Connecting accounting and CRM. Webhook verification.
Field team onboarding
Onboarding the field team — typically 30 minutes per technician. Live with sandbox jobs in parallel with production for a week.
Production cutover
Switch dispatcher routing to FieldOps as primary. Sandbox tenant stays alive for parallel-running tests.
API
REST. OAuth2. Webhooks.
REST API with OAuth2. Webhooks for job state changes. Rate limits at 100 requests per second per account, soft-cap, scaled up on request. Public docs include 47 endpoints with code examples in JavaScript, Python, and Ruby.
- AuthOAuth2 authorization code + client credentials
- VersioningURL-based (v1, v2). 12-month deprecation window on each major.
- WebhooksJob state, invoice state, tech presence. HMAC signed.
- SandboxEvery account ships with a parallel sandbox tenant.
- SDKsJavaScript + Python first-party. Ruby community-maintained.
Status & uptime
99.97% over the last 12 months.
Status page at status.fieldops-concept.example. Incident history goes back two years. We post incident postmortems within 5 business days of resolution, and we link the postmortem from the incident entry on the status page.
Outages happen. We write up the cause and the fix every time, and we link it from the status page. No “intermittent issues” hand-waving.