Dinner Has Reached the Building but Not the Resident

The food left the restaurant at 7:38pm.

The tracking app showed it moving through the city for nine minutes, updating its position every forty-five seconds, providing the kind of granular locational data that is both unnecessary and somehow essential. At 7:47pm, the order was shown as "arriving." At 7:47pm, a call came from an unknown number.

The gate.

The Search History

7:47pm: Unknown number. Answered. Delivery person at gate. Gate code provided: 4421. Call ends.

7:51pm: Same unknown number. Answered. Delivery person at gate. Gate code provided again: four-four-two-one, said with more spacing this time. Person on phone says yes yes. Call ends.

7:53pm: Tracking app checked. Order still showing "arriving."

7:54pm: WhatsApp message from unknown number: "bhaiya gate nahi khul raha."

7:54pm: Searched: "how to explain gate code over phone."

7:55pm: Walked down to gate.

The Complexity

The gate code is four digits. The delivery person has a phone and a box of food. The resident has a phone and a code. The transaction should take thirty seconds.

The gate, however, requires the code to be entered within four seconds of the beep, which is a constraint that is not communicated anywhere except on a small laminated notice attached to the gate that is not visible from the outside.

The delivery person was entering the code correctly. The timing was wrong. This information was not available over the phone.

The Resolution

The resident went down. The gate was opened manually. The food was exchanged. The resident noted, on the way back up, that this was the third time this month. The laminated notice remains on the inside.

A message was sent to the building group: "Can we please put a notice outside about the four-second window?" The message received seven reactions. No notice was installed. The search history will have a new entry next week.