How to Verify a Lost Property Claim Without Publishing the Answers

Decide what the public listing should reveal

A useful listing gives enough context for recognition without displaying personal information. For a wallet, an outside photograph may be appropriate; its contents and readable cards are not. For keys, avoid publishing an address tag. For a device, keep notifications, account details and serial numbers private.

Staff should check both the picture and description. Hiding a detail in the image is not helpful if the caption gives it away. vFound lets staff separate public photographs and descriptions from private item notes. vFound AI’s privacy guard adds a safety net: when photo auto-fill reads a photo that shows an ID, a bank card or a lit screen, it switches that photo to staff-only, while the item stays listed. The team still decides what is appropriate to publish.

Use open questions with evidence value

Ask for a feature that is not visible in the catalog. Examples include a distinctive mark on a case, an item inside a bag, or a private detail about where the object was left. Choose questions relevant to the actual record rather than demanding the same information for each item. In vFound, guests can also add proof photos to a claim, such as an older photo of the item on their phone.

These examples are a starting point, not proof that a claim is genuine. Consider the evidence together and use the venue’s escalation process when uncertain.

Use an AI claim check as a second pair of eyes

A busy desk can miss a mismatch. vFound AI reads a new claim’s answers and proof photos and compares them with your private record, including the details you kept out of the listing; the result appears on the claim a moment after it arrives. It then gives staff a suggestion: consistent, mixed, inconsistent or not enough detail. It lists any red flags and proposes a question to ask next.

One red flag it looks for is an answer copied from the public listing. Anyone who has read the page can repeat what it says; the owner is the person likely to know what it leaves out. Treat an answer that contradicts your private notes with the same care, and use the suggested question as a neutral follow-up.

AI suggests. Your team decides. The claim check never approves, declines or otherwise changes a claim on its own, and it never identifies people from images. Use it as a second opinion that makes a reviewer slow down when something does not fit, not as a verdict. When the suggestion and your own judgment disagree, your judgment and your venue’s process win.

Keep the review proportionate and private

Do not request account passwords, device PINs or full payment-card details. A guest can demonstrate access to a device in person without telling staff the unlock code. If your policy requires identity checks, use the approved private process and only collect what is needed.

Keep evidence and staff decisions with the claim, accessible to the people handling it. Avoid forwarding copies through personal email or posting proof in a public comment. Explain why a detail is being requested when it is not obvious to the guest.

Language should not get in the way of a precise question. When a guest writes in another language, vFound translates the message for your team, and staff can reply in the guest’s language.

Handle uncertainty before promising collection

If answers do not match, ask a neutral follow-up or send the claim to the designated reviewer. If two people claim the same item, pause the handover and follow the venue’s dispute process. Do not release it simply because one person replied first.

Make the status clear internally: awaiting information is different from approved. Record the basis for the decision in a concise private note without copying more personal information than necessary.

Close the loop at the handover

For an approved claim, agree where and when collection will happen, what reference to bring and how third-party pickup is authorized. At the handover, check the correct item reference and record who completed the return. For shipping, confirm the address and suitable service before dispatch and keep the tracking information with the record.

vFound supports each step. Guests can book a pickup time within your venue’s hours and get an add-to-calendar link and a reminder. You can require a second manager’s approval before a high value item is released, the guest’s signature at pickup is printed on the claim record, and changes to the item’s details are kept in a field by field history.

Review the workflow with a synthetic item: one colleague publishes it, another submits a claim, and a third completes the handover using only the record. That rehearsal shows whether the next shift will have what it needs.

See the handling guide for storage and review steps, and the response templates for clear guest messages.