Doorstep rescue

#How it works

1. The driver taps "I'm at the door and nobody's answering" on the job's driver page, or your driver app calls POST /v1/confirmations/{id}/rescue.
2. AnyoneIn calls the customer straight away and sends a message in case they can't pick up: "our driver is at your address now and nobody's answering".
3. The agent finds the fastest option the job allows (below).
4. The driver's page shows what was agreed within seconds: wait up to 5 minutes, take it to the neighbour at number 14, collect it from the porch, or take it back. You get a confirmation.updated webhook with rescue set.

If they don't pick up, the driver is told straight away to follow your failed-visit process, and a later reply still updates the page.

#What the agent can agree

It never offers a safe place for a delivery. The longest the driver is asked to wait is 10 minutes.

#The driver page

Every confirmation has a driver link in links.driver: put it on the driver's manifest or in your app. The page shows:

• the customer's first name, the area and the job;
• anything the crew should know from crew checks, such as the floor, the lift, the narrowest point, parking, the photo check and who's signing;
• the rescue button.

It shows nothing else about the customer.

#The result

rescue.statestring

calling, talking, done or no_answer.

rescue.result.intentstring

wait, neighbour, neighbour_with_id, left_out, rebook or human.

rescue.result.minutesinteger

For wait: how long to wait.

rescue.result.whostring

For a neighbour: their name and door number.

rescue.result.wherestring

For left_out, where the item is; for rebook, what suits them.

rescue.result.summarystring

One line for the driver.

A rebook (or human) sets the confirmation to action_needed, so it reaches your team like any other job that needs a person. Rescue works on the delivery day with live keys, and any time in the sandbox, where you play the customer with simulate.