Book a demo

Guides

Crew checks and photos

Ask the customer about the way in and for photos, work out whether it will fit, and keep timestamped evidence for every job.

A failed visit isn't always "nobody in". The sofa doesn't fit the stairs, there's nowhere to park, or the wardrobe for collection is still assembled. Crew checks ask the customer the right questions on their page, before the day, and put the answers in front of your crew and your systems.

What the customer is asked

JobAsked by default
CollectionsThe way in, and a photo of the item ready to go
Two-person and install deliveriesThe way in (a photo of it is optional)
Signed-for, age-checked, high-valueNothing extra

Change it per job with checks when you create or update: { "photo": true, "access": true }.

The way in asks for:

  • a house, flat or other;
  • the floor;
  • whether there's a lift;
  • the stairs: none, straight, or narrow or turning;
  • the narrowest doorway or hallway in cm, if they can measure it;
  • parking: right outside, nearby, permit or restricted, or difficult;
  • whether there's an old one to take away;
  • anything else the crew should know.

Photos can be up to three. The customer's phone shrinks each one and strips its metadata, including where it was taken, before it's sent. We ask them to keep people out of shot.

After a customer confirms, if anything's still missing, they get one short message asking for it with their link.

Will it fit?

Send item sizes, and AnyoneIn compares them with what the customer tells us:

order.items
[{ "name": "Corner sofa", "dimensions": { "width": 95, "height": 88, "depth": 240 }, "weightKg": 70 }]

An item can be turned and tilted, so its smallest side has to pass the narrowest point. The result is in checks.access.fitRisk:

fitRiskMeaning
okIt should pass the narrowest point
tightWithin 5 cm, or a long item on turning stairs
unlikelyIts smallest side is wider than the narrowest point. Your ops email is alerted and the customer is told you'll be in touch
unknownNo sizes, or no measurement from the customer

checks.access.notes adds anything else the crew should know, such as "Carry up to floor 3 with no lift" or "Parking needs a permit or is restricted".

The photo check

Each photo is checked by AI against the job:

  • For a collection: is it the right item, and is it packed, or taken apart if needed, and easy to reach?
  • For a delivery: is there anything on the way in that could stop the crew?

The result is advice for your team, not a decision.

checks.photo.resultstring

pass, doubtful (unclear, or the photo doesn't show enough) or fail (a clear problem). Anything but pass alerts your ops email.

checks.photo.summarystring

One sentence for your team, such as "The wardrobe is taken apart and bagged by the door."

checks.photo.concernsarray

Short notes on anything that could stop the job.

checks.photo.photosarray

Each photo's id, at, contentType, bytes and sha256.

Every change to the checks sends a confirmation.updated webhook, so the answers can go straight onto your manifest.

Evidence

GET /v1/confirmations/{id}/evidence returns everything about a job in one document, for a dispute or a complaint:

  • the timeline (every message, reply, call turn and what the agent understood);
  • the outcome and who's signing;
  • the access answers;
  • each photo with its SHA-256 and a link;
  • the doorstep rescue, if there was one.

GET /v1/confirmations/{id}/photos/{photoId} returns a photo itself. The hash shows the photo hasn't changed since the customer sent it.

Photos are stored in London and deleted with the job, 90 days after the delivery date.

Base URL https://api.anyonein.co.uk/v1, for test and live keys alike. Found a mistake? Tell us.