SECURE SESSION
One link opens the right vehicle and the right photo job.
The vehicle, required captures, photo standard, and destination are already set. At the vehicle, the job is simple: Move to the dot. Then capture.
PLATFORM MODEL
Five simple pieces keep the whole photo job with the VIN.
Halo knows what the job needs, opens it for the right person, builds the finished photo set, shows the status, and sends the result through the agreed path.
- 01CAPTURE REQUEST
Defines the vehicle, the photo job, and where the finished set needs to go.
- 02SESSION
Opens the right job in a secure browser link for the person beside the vehicle.
- 03VEHICLE RECORD
Keeps the captures, finished photos, coverage, and status with the VIN.
- 04STATUS
Shows the team what happened and what still needs attention.
- 05DELIVERY
Sends the approved photo set through the agreed dealership system path.
API LIFECYCLE
Prove the dealership connection first. Add more automation later.
The founding POC focuses on the connection your rooftop needs today. APIs, webhooks, and other programmable connections remain later platform work.
- REQUESTFOUNDING POC SCOPE
A dealership workflow can ask for a configured guided observation.
- EVIDENCEFOUNDING POC SCOPE
The completed capture creates a VIN-linked record with selected output and context.
- STATUSFOUNDING POC SCOPE
Halo Flows and the Operations Board expose where the vehicle is in the workflow.
- WEBHOOKNEXT
A programmable response surface remains a staged platform direction, not a public endpoint.
ROUTING POLICY
Send the finished set only where you agreed it should go.
During the POC, we agree on one recipient or dealership system and prove that path together. We do not claim that every syndication platform is already connected.
EDGE STATES
See when a job is complete, syncing, or needs attention.
Vehicle work happens around glass, concrete, weather, weak signals, and busy people. Halo keeps the job status visible so no one has to guess whether the photos made it through.
- ONLINEFOUNDING POC SCOPE
The session has access to the configured task and can return state normally.
- DEGRADEDFUTURE DIRECTION
Weak field conditions should remain visible before a recipient relies on the record.
- OFFLINE-CONTINUINGFUTURE DIRECTION
Continuing without connection is an architectural boundary to validate by workflow.
- SYNCINGFUTURE DIRECTION
Queued state must reconcile before downstream delivery.
- COMPLETEFOUNDING POC SCOPE
A configured workflow can mark the record ready for routing.
- NEEDS REVIEWPOC MEASURE
Exceptions remain visible before teams publish or act on the evidence.
Provenance can make origin and change history inspectable.
C2PA and content credentials are useful interoperability context for origin and change history. They do not determine whether a depicted vehicle fact is true, and Halo does not present them here as a current production control.
Read the C2PA source noteTECHNICAL CONVERSATION
Show us every handoff between the phone and the live listing.
Bring the current capture process, editing steps, uploads, and one destination. We will show you what Halo can replace now and what still needs to be proven.
