What needs immediate attention?
Operating view · Field-service command center
Command Center
Everything the office team needs to review, dispatch, and act on today.
Emergency work, follow-ups, owner attention, and recommended next actions in one operating view.
Today
Showing today across all service requests
Emergency requests
Select any top card to change this view
2 emergency requests need immediate action
Product foundation · Cal overview
Cal overview
Cal is the service-request triage and owner-visibility layer around a plumbing team’s existing intake and dispatch workflow. It structures incoming requests, identifies urgency and risk, surfaces what needs attention, supports the human decision, and turns the daily queue into a clear owner operating brief.
Cal product thesis
Can Cal turn a messy service request into a trusted, prioritized human decision—and then ensure the right request, risk signal, next action, and owner attention are clearly surfaced before dispatch?
Validation question
Can Cal turn a messy service request into a trusted, prioritized human decision—and then ensure the right request, risk signal, next action, and owner attention are clearly surfaced before dispatch?Product foundation · What Cal proves
Clarity before dispatch.
Built around the L.E. Isley & Sons Plumbing workflow, Cal demonstrates a reusable AtlasFlow pattern for field service: a messy request becomes AI triage, a structured job record, Operational Viewer visibility, human review, and a clear recommended next action.
Operating architecture · Decision path
AtlasFlow Decision Path
A service request can become prioritized, dispatch-ready work automatically: Request → Customer record → Cal AI → Command Center → Human decision
Automation path
Request
Customer record
Cal AI
Command Center
Human action
01 · Detect: a service request is captured—a call, form, text, or office note.
02 · Contextualize: Cal assembles the customer record, location, history, and open commitments.
03 · Prioritize: Cal determines urgency, why it matters, and the recommended next action.
04 · Surface: the request appears in Command Center with a clear reason and priority.
05 · Decide: Doug or dispatch reviews, approves, delegates, or completes the action.
What could create damage, delay, or customer exposure?
Why did Cal surface this request now?
What should Doug or dispatch do next?
Product foundation · Operator model
Operator model
This view shows how Cal routes plumbing service requests through intake, triage, review, and briefing so the office team can make informed decisions and take action.
