What can Japan’s railway tradition teach us about customer service?
Good passenger service depends less on a new channel than on whether the people answering it can see, own and resolve the same problem.
People search for
Customer service is often framed as a choice between a chatbot, an app or a contact-centre platform. Japan offers a simpler lesson: record a passenger’s concern once and make it available to those who can act on it.
JR East was created in 1987, within a much older railway tradition. Its published reports provide an example. In 2021, it said that it collected around 200,000 customer comments a year, received directly by staff, online and by telephone. These were shared and analysed through its company-wide New Green Information System. The reporting does not show that a shared database cures poor service. It shows a deliberate decision to ensure that the passenger’s contact channel does not set the limits of the record.
JR East has also reported distributing tablet computers to all employees. This does not show that every employee has a complete customer-service tool. It makes a practical point: staff standing with the passenger, as well as a back-office team, should be able to use passenger information.
The gap a passenger will notice
A UK bus passenger may see an Authority’s map, bus stop flags and ticketing information, yet be asked to work out which Operator should receive a complaint about a missed journey, an inaccessible vehicle or a driver’s conduct. In a commercial network, the Operator will rightly need to investigate and respond to many such cases. The Authority may still need to see the pattern: repeated failures at a stop, a school-time problem or an issue affecting several Operators during roadworks.
The practical difficulty is often the hand-off between channels. A report made to an elected member, at a travel shop or through social media can end up in a different spreadsheet from one submitted to an Operator. A passenger who does not know the Operator may give up after being redirected.
The answer varies with local arrangements. An Authority may specify a common customer-contact process in its contracts. An Authority in an Enhanced Partnership will need agreement with participating Operators on what is shared, who acts and how performance is reviewed.
An Authority does not need to take responsibility for every response. It does need to provide a straightforward first contact for passengers and retain enough network-level evidence to manage the service. Records must meet a common minimum requirement: route, direction, stop or location, date and time, journey reference where available, contact channel and action agreed. Reports about staff, lost property and disability-related requests need different handling and access controls. A shared system is no reason to circulate these cases loosely.
Lost property is a useful test. The item may be at an Operator’s depot and the Authority should not imply otherwise. A passenger should still be able to use one clear route, receive a reference number and know which team is checking it. The same principle applies to service disruption: the contact record should reach the appropriate Operator without requiring the passenger to retell the journey.
Make the arrangement testable
Before procuring a system, an Authority can trace a few real contacts from receipt to closure. Follow a complaint made at a stop, one sent online and a call about a lost bag. Can the relevant Operator see the details promptly? Can the Authority identify repeat locations and routes without a manual monthly return? Is there a named owner when a case falls between teams?
Contracts and partnership arrangements should cover response and escalation times, data-sharing responsibilities, required fields, access for contract managers and complaints that raise safeguarding or conduct concerns. A dashboard showing only complaint totals is rarely enough. Transfers between teams, time to a useful answer and repeat contacts can reveal where the process is breaking down.
Do not make a frontline employee use a system that slows an urgent operational response. In some networks, common data fields and a reliable exchange between existing systems will be more practical than replacing every local tool. The Authority should decide what must be consistent for the passenger and what can remain with the Operator.
Our OneContact solution is intended to provide a single customer-contact function across Operators for enquiries, feedback, lost property and complaints. Whether the Authority uses that service or another arrangement, the operating agreement should state who sees the record, who resolves it and how the Authority responds when the same failure keeps appearing.
Useful questions
These questions help test the contact arrangements already in place.
- Can a passenger report a problem without first identifying the Operator and receive a reference they can use with any relevant team?
- Which contact channels feed the same case record, and which are still held separately by an Authority, Operator or Supplier?
- What information does the Authority receive quickly enough to spot repeat failures by route, stop, time of day or contract area?
- Who owns a case that requires action from both the Authority and an Operator and when is it escalated?
- Have the proposed arrangements been tried with actual complaints, lost-property reports and disruption enquiries rather than only demonstrated in a Supplier presentation?
More on Customer Service & Contact