What does a good lost property service look like?
Passengers need a single place to report a lost item and a credible way to reach the person who can find it.
People search for
In this article
Lost property may seem minor until it reaches a contact centre. A passenger who has left a bag wants to act quickly. If they do not know the Operator or are passed from one phone number to another, a missed connection can lead to a web form and repeated follow-up.
The Authority should ask whether it presents one understandable network to passengers when several Operators hold the records and items. It does not have to centralise lost-property storage at every depot. Its task is to remove uncertainty when passengers first report an item and ensure the hand-offs work.
Start with a report that can be acted on
Passengers should have one obvious place to report an item, regardless of the Operator. It should be a structured intake. A free-form message must be interpreted and re-keyed by a member of staff.
SBB’s online lost-property service is a useful example. It asks passengers to describe the item using a pre-selected menu with clear categories. It also gives specific prompts for phones, keys and wallets, where details such as a serial or key number can help distinguish one item from another. The operational detail makes the service useful, while the interface can remain simple.
For a bus network, the fields should reflect what can be checked: route or service, date, an approximate time window, direction of travel where known, boarding or alighting point, item category, colour or brand and a distinguishing feature. Requiring every field may deter some passengers. Making every field optional produces reports that are difficult for an Operator to use. The form needs sensible prompts and a route for passengers who cannot provide much detail.
Make the operating hand-offs visible
A report form alone will not recover an item if the record goes unanswered. The Authority needs agreement with each Operator on who receives a report, how it links to found-property records and what passengers are told while the search is under way. This also covers when a driver or depot logs an item, whether the portal shows that the report has been received and when the passenger is told that no match has been found.
The Authority must ensure that the relevant Operator receives enough information to search, update the case and arrange collection or return. Before launch, agree access, retention and escalation arrangements, particularly for documents, bank cards, medication and high-value items. These categories may require instructions different from those for an ordinary lost umbrella or coat.
An integrated ticketing scheme cannot create this service on its own. A ticketing app may help a passenger identify a journey. It does not establish who logs found property, where an item is stored or who sends the next message. The customer-service arrangements and, where relevant, the Operator contract, must define these responsibilities. OneContact has been designed to support these capabilities. Speak to us to find out more.
Keep human help for the cases that need it
Self-service does not remove the need for a telephone route. Some passengers cannot easily use an app or Authority portal; others may be reporting medication, travel documents or an item needed that day. A directed telephone service can work well when it captures the same core information and explains the next step. Vague message-taking creates a separate queue, so the service should capture a structured report.
A staffed line can also fail the passenger. If a contact-centre colleague forwards an incomplete description to an unknown depot, the passenger has no useful answer. Call volumes, accessibility needs and the reported items should determine the support offered. The Authority should ask for evidence. It should not assume that a particular channel is always cheaper or kinder.
Put it in the specification, then test the ordinary cases
For an Authority procuring or changing this service, the specification should state what a passenger can do, who owns each update and how the Authority will monitor the process. Suppliers can provide the technology. The service also relies on timely found-item records from Operators and named staff who resolve exceptions.
Test the journey with plausible reports before accepting it: a coat with no route number, a phone with an identifiable feature, an item reported on the wrong service and an item already recorded by an Operator. Look at the acknowledgements, routing and status messages as well as the form itself. An app or Authority portal that submits a report successfully but gives no indication of what happens next will still generate avoidable calls.
Useful questions
Use these questions when reviewing the current service or a proposed change.
- Can a passenger make one report without first knowing which Operator ran the vehicle?
- Does the report capture enough consistent information for an Operator or depot to search its records without calling the passenger back for the basics?
- Who is responsible for receiving, updating and closing the report and what does the Authority see if those actions are late?
- Are there clear, accessible routes for passengers who cannot use the online form or who have lost an item requiring urgent or different handling?
- Has the Authority tested the end-to-end process with real-looking reports across more than one Operator?
More on Customer Service & Contact