People do not necessarily experience a terminal as a collection of contracts. They arrive at a named place, find a bus, ask a question and try to continue a journey. The organisations involved may see the same sequence as several distinct transactions. A fare belongs to a bus operator. A purchase belongs to a retail licensee. A terminal-service matter belongs to the concession enterprise within its agreed scope. Those distinctions are real. The problem begins when the public-facing identity suggests one comprehensive answer while the actual response consists of several organisations explaining why the question belongs elsewhere.
Our fictional review in 2025 covered 210 enquiries. We identified 138 concerning bus fares or refunds, forty-seven concerning terminal services and twenty-five whose responsibility remained unresolved. Those figures describe an examined set and its initial categories. They do not report a resolution rate or establish how often the same pattern occurs across all terminals. I found the unresolved group especially useful. It prevented the discussion from assuming that the relevant boundary was always obvious, even to the people responsible for explaining it. The chief executive's task was to turn the distinctions into a workable response without pretending that they had disappeared.
The traveller's account and the contract account
The traveller may be right that the difficulty arose as part of their experience of our terminal. That does not necessarily mean our enterprise is the party authorised to decide a fare refund. Both statements can be true at once. If management treats the first statement as an error, the response can become dismissive. If it treats the second as a minor technicality, the company can promise an action it has no power to deliver. I wanted the service design to preserve the legitimate account of the experience and the legitimate account of responsibility, rather than choose one and invalidate the other.
The service team's wish for a single desk was understandable. A shared point of contact could make the place easier to navigate. Yet a desk is an interface, not automatically a new decision-maker for all the organisations behind it. The authority to consider a refund, the records needed and the way personal details can be handled remain material. I did not want the appearance of simplicity to conceal a collection of unresolved arrangements that staff would discover only when a traveller asked for action. A useful public interface needs agreed relationships behind it, including a clear account of where participation is incomplete.
Finance and legal colleagues were right to question broad language about taking care of the entire journey. They were not necessarily arguing for indifference. Their concern was that a reassuring phrase could be understood as a financial or service commitment beyond the company's role. I asked that concern to be brought into the design of a useful response, rather than used to end the discussion. The enterprise still had forty-seven terminal-service matters of its own in the reviewed set. It needed to retain those clearly while finding a practical, authorised route for some of the fare-related questions.
Helping without inventing authority
We developed referral arrangements with participating bus operators and spent ₹44 lakh on the defined coordination work. Participation mattered: the programme did not cover every operator merely because the terminal hoped for a complete offer. The arrangements needed agreement about what would happen after a question was referred and appropriate treatment of the personal details involved. I would not describe those safeguards as a universal technical design or a legal conclusion. Responsible owners had to establish the actual process for the parties concerned. My role was to fund and support a proposition that could be carried out within those arrangements.
A referral also needed to be described as a referral. It was not a refund decision or a promise that money would be paid. That distinction can sound modest in a commercial presentation, but it matters to the person deciding what to expect next. If the enterprise uses language suggesting settlement and delivers only another introduction, it has added confusion even while trying to help. The right promise depends on what the participating organisations have actually agreed. Better service can consist of a more intelligible route to the accountable party, without requiring the terminal company to become that party for every transaction.
There is a risk of making boundaries so prominent that they become the whole conversation. Staff can learn to recite what the enterprise does not do more readily than explain what it will do. I wanted management to examine that possibility as well. Our own matters should receive our own response. Participating-operator matters should follow the agreed route. Cases outside those arrangements need an honest explanation of the available next step, rather than a reassuring phrase unsupported by a relationship. The distinction is operational work, not merely a disclaimer at the end of a page or a script designed to protect the brand.
The unresolved group belongs in the report
Twenty-five enquiries remained unresolved in their responsibility classification at the review date. We retained them as such. Assigning them away from the company would have made our own account appear simpler, while accepting them all as ours could have implied a duty before it was understood. The unresolved category was not a permanent answer to the traveller. It was an instruction to management that further examination was required. Directors could see that the proposed response had limits and ask how those limits were being addressed, instead of receiving a complete-looking allocation that concealed uncertainty inside the figures.
I would distinguish this classification work from the eventual outcome of each enquiry. Knowing which organisation should consider a question does not establish that the question has been answered well, that a payment is due or that the person is satisfied. The reviewed figures should not migrate into a claim about resolution merely because the coordination programme has been launched. If we later report outcomes, they need their own definitions and evidence. Keeping those stages separate protects the usefulness of the original review and prevents an initiative from accumulating achievements that its actual account does not support.
The board contribution I see here is an ability to ask how a shared public identity relates to the enterprise's real authority. Directors should not manage individual fare questions. They should understand whether the company's promise can be delivered through the relationships and resources behind it, and whether management retains responsibility for its own part. The enquiry review gives that discussion a concrete shape without requiring a sweeping claim that one desk or one brand can solve the entire journey. It also leaves a legitimate role for challenge where the presentation sounds more complete than the agreements supporting it.
I would build these relationships earlier in the public-facing design of a concession. The issue is predictable even when the particular enquiries are not. Several organisations will meet in one place, and travellers will not necessarily know the boundaries management sees. A thoughtful response can help them without pretending those boundaries are irrelevant. Our programme retained our own matters, created an agreed route for some operator matters and left the unresolved group visible. That is a limited result, but it is one the enterprise can explain. A shared name becomes more credible when it describes what the organisations can actually do together, rather than concealing what they have not yet agreed.