The operational problem
Urgent requests arrive incomplete.
Phone and chat messages omit vehicle facts, access conditions, authorization evidence, and details that affect timing. Repeated questions and premature promises create risk.
Closed-loop field service intelligence
Turn every request into a safe plan — and every completed job into the next customer’s answer.
One verified loop from customer inquiry to Mission Pack, Service Memory, and review-ready Growth Pack.
CasePilot keeps uncertainty and authorization visible before dispatch, helps qualified technicians arrive prepared, and converts sanitized completion facts into reusable operations and answer-engine content.
DEMO-VEHICLE-A-001Closed loop ready
Synthetic customer inquiry
“Vehicle A is a 2019 compact sedan. All smart keys are lost in Taipei underground parking. Can someone come now?”
Intake facts structured
Mission Pack gated
Service Memory verified
Growth Pack review-ready
Demo analysis mode. Deterministic, reproducible judge experience. Optional live GPT-5.6 analysis is supported when configured.
Built for
Locksmith dispatch and field teams
Customer service, dispatchers, field technicians, operations managers, and business owners — with no login required for this synthetic demo.
One compounding workflow
Capture → recover → authorize → serve → grow
Incomplete demand remains a recoverable LeadRecord. Owner-approved intake then produces three typed, auditable case artifacts: a Mission Pack, a verified Service Memory, and a human-reviewed Growth Pack.
The difference
Completion compounds — without auto-publishing
Content is grounded only in verified, privacy-safe completion facts. Authorization cannot be skipped, sensitive procedures stay excluded, and publication remains a separate human decision.
Executable evidence
73 contract checks, not just product claims.
The synthetic suite verifies safety, privacy, bilingual behavior, state gates, and grounded output. Separate zero-key tests exercise the optional Responses API request boundary without making a network call.
73/73 contract checks14 analysis fixtures0 network calls
Safety boundary
Operational clarity without exposing proprietary knowledge.
This independent Build Week project uses synthetic data and general workflow logic only. It contains no real customer records, pricing tables, production code, or model-specific security procedures.