City Operations

Service Requests (311)

Service requests ranked by risk and routed to close within SLA.

311 requests are worked in arrival order, so an arterial hazard waits behind cosmetic tickets.

Deploy via outcome brief

79 teams run this pack 28,203 runs / 30 days 91% auto-resolution

Expected outcome

311 requests are risk-ranked and routed to the right crew to close within SLA.

Hours saved / wk

FTEs freed

0.4

Monthly value

$10,000

Triggers

Sensor / telemetry anomaly

ready

Scheduled monitoring sweep

ready

Custom webhook (POST JSON)

ready

Integrations

Webhook / REST API

Ingest live signals from your systems

Slack / Teams (optional)

Escalate edge cases to a channel

Agent steps

2 credits / run

1
Perceive
Ingests incident, 311 and municipal-asset signals into a live World Model of the operation.
2
Classify
Tags the signal by type and severity against your ontology.
3
Decide
Applies your SOP rules to choose the dispatch or service response — or escalate when confidence is low.
4
Act
Drafts the dispatch or service response; a human approves the first runs, then it advances to assisted / autonomous.
5
Log decision
Every decision is written to the Decision Log with the full reasoning trail.

See it in action

State Transformation

A formal contract: what this pack converts, with explicit uncertainty bounds and verification criteria.

Initial state

Crew on Request observed but not yet reconciled

Target state

Service Requests (311): Request returned to a reconciled state with SLA issued (auto-resolved | assisted | escalated) and the record updated

Invariants (must hold)

Request identity resolved before any actionCrew classified by type & severity against the ontologySLA authorized by policy and fully reversible

Uncertainty bounds (max acceptable error)

max_severity_misclassification≤ 5.0%

max_routing_error≤ 2.0%

Verification: SLA recorded + downstream Request state advanced + append-only audit entry

Domain ontology — entities & states

The vocabulary this pack reasons over. Each entity has its own state machine.

Request4 states

observed→classified→in_review→resolved

Crew4 states

observed→classified→in_review→resolved

SLA4 states

observed→classified→in_review→resolved

Relations

· Request-emits-Crew
· Crew-routed-to-Owner
· Crew-resolves-into-SLA

Audit & explainability

Per-decision reasoning saved (input, rule applied, output)
Override button — marks the decision and re-trains the rule layer
Append-only ledger export for compliance / audit

Pricing

~7× ROI — you keep ~85% of the value this pack creates. Priced at the market median, never as a race to the bottom.

Pilot

Prove the ROI on one bottleneck.

$1,500/mo

Onboarding · included free

1 workflow deployment
Shadow + assisted run modes
White-glove setup call
Decision Log + audit export

Scale

Recommended

Run it as a continuous outcome.

$3,600/mo

Onboarding · included free

Up to 5 deployments
Autonomous mode (earned via self-grading)
Continuous SLA in the Outcome Console
Autopilot drift signals

Enterprise

Your operating model, contracted.

Custom

+ custom implementation

Unlimited deployments
Custom SLAs + integrations
Dedicated solutions engineer
SSO + compliance reviews

Talk to sales

Calculate my ROI

Drag the sliders. We'll email you a personalized report — no fluff, your numbers.

Onboarding is included free — self-serve or white-glove

Pick Self-serve and our onboarding assistant walks you through connecting Gmail/Outlook/Slack/ERP, or choose White-glove and a Centertron specialist joins you for a live go-live call — both at no extra cost, live in <48 hours. Either way, the pack runs in your audit trail with every decision logged.

Talk to sales