Remote inspection kit

Inspect claims, returns and repairs through your customer’s camera

Send a link. Your customer points their phone at the item, an AI guide walks them through every required view, and your inspector gets a sealed, verifiable evidence package back. No app to install and no inspector on the call.

  • Works in the phone’s browser
  • Evidence stays with the customer until shared
  • Open source, MIT
Case CLM-20418 · Vehicle damage claim6 of 7 steps confirmed
  • Photos, one per step7 files
  • Session recording4 min
  • Inspection reportPDF
  • Findings for your systemsJSON
  • Manifest and audit chainsealed
Evidence intactHashes, audit chain and case binding match
Example package
Ready-made checklists

Five templates for the inspections teams run most

Each template lists the views to collect and what the guide checks before it moves on. Change any step, or write your own.

Insurance: vehicle damage

Motor insurers, fleets, rental and leasing

  • Whole vehicle
  • Number plate
  • Damage in context
  • Damage close up
  • Dashboard
  • VIN plate
  • Registration document
motor-claim

Insurance: property damage

Home and contents insurers, loss adjusters, property managers

  • Property front
  • Affected room
  • Damage in context
  • Damage close up
  • Likely cause
  • Damaged items
property-damage

Warranty and returns

Support teams for appliances, electronics and equipment

  • Product overview
  • Serial or rating plate
  • The fault
  • General condition
  • Proof of purchase
warranty-check

Field service pre-visit

HVAC, solar, appliance and utility service teams

  • Equipment overview
  • Rating plate
  • Fault indicator
  • Connections
  • Access route
  • Safety check
field-service

Anything else

Product walkthroughs and controlled tests

  • Object overview
  • A useful detail
  • Visible condition
general-visual

Your own inspection

Pre-delivery checks, rental returns, site surveys: list the views, what the guide should confirm at each one and which are required.

Write a template
A report without its required views is marked incomplete.
An inspection, start to finish

About five minutes on your customer’s phone, with no inspector on the call

  1. Send a link

    Your inspector picks a checklist and a case reference in the console, then sends a link or QR code by SMS, email or chat.

  2. Customer consents

    The customer opens the link in their phone’s browser. Camera and microphone start only after they agree; recording and location are their choice.

  3. The guide walks each view

    An AI guide speaks each step, checks the live camera view and asks for a closer look, the torch or a steadier hand when a plate or serial is hard to read.

  4. Finish and seal

    Finish stops the camera and seals the package in the browser. Anything required that is missing is marked incomplete, so nothing is quietly skipped.

  5. Inspector verifies

    The customer shares the ZIP through your channel. Your console opens it, checks the seal and shows photos, findings and the transcript.

What your inspector receives

One sealed ZIP per inspection, ready to review

  • Photos of every step

    A still for each view the checklist asks for, with an optional continuous video recording of the session.

  • Step findings

    What the guide saw at each step, marked confirmed, unavailable or skipped, so reviewers know what to look at first.

  • Transcript

    The guided conversation in full, for context on anything the customer explained out loud.

  • PDF report

    A readable report for adjusters, support agents and technicians, ready to attach to the case.

  • JSON report

    The same findings as structured data, for your claims, ticketing or job-scheduling system.

  • Integrity seal

    File hashes, a tamper-evident audit chain and a case and session binding that the console checks on import.

Built for a human decision

Faster first passes, with your reviewer still in charge

The seal shows the package is untouched

  • No file was edited, added or removed after the package was created
  • The audit chain records each step in order
  • The package belongs to the case and session it names

It proves integrity, not identity: it does not show who created the package, establish legal authenticity or trusted time, or prove that a finding is true.

AI findings are a first pass

  • The guide is asked to confirm a step only when it can see what the step needs
  • Saving a photo without a check never counts as confirmed
  • It is told to report unreadable plates and serials as unclear rather than guess

A person reviews the photos and findings before any claim, refund or repair decision.

Yours to run

Deploy it on your keys, under your brand

  • Keys stay on your server

    A small broker creates inspection rooms with your MediaSFU account. Browsers never receive your API key.

  • Two pages in the box

    An inspector console to create links and verify packages, and the customer’s guided camera page.

  • Your evidence policy

    You decide how customers share packages, how long you keep them and what consent text they see.

  • Runs in five minutes

    Clone, install and open the console with no keys needed. The AI guide switches on when you add your own account.

Live sessions use the rates on the pricing page; the speech, vision and language providers you connect bill you directly.

Questions

What inspection teams ask first

Do customers need to install an app?

No. The inspection runs in the phone’s browser from a link. Cameras need a secure page, so you serve the kit over HTTPS.

Where is the evidence stored?

On the customer’s device. The package is built and sealed in the browser, and nothing is uploaded to anyone’s cloud until the customer chooses to share it through your channel. The AI guide receives the live audio and camera view during the session, after consent.

What does the seal prove?

That the package has not been changed since it was created: no file edited, added or removed, and that it belongs to the case and session it claims. It does not prove who created it, establish legal authenticity or trusted time, or prove that an AI finding is true.

Can we use our own checklists?

Yes. Templates are plain JavaScript: the steps, what the guide checks at each one and which views are required. Adding your own is a few lines.

Who hosts it?

You do. The starter is a reference app you deploy on your own hosting with your own MediaSFU keys, which stay on your server. Your customers see your product, not ours.

What does it cost?

The source is free under the MIT licence. Live sessions are billed to your MediaSFU account at our published rates, and the AI providers you connect bill you directly.

Run an inspection yourself in five minutes

Use a mug or a plain box, export the ZIP, then open it in the inspector console to see what your team would receive.