A successful portal gives an enterprise several reasons to be pleased. Many people can raise a question at a convenient time, the record can be easier to follow and routine requests may require less explanation. I support that progress. I become cautious when the digital share is used to answer a different question: whether the remaining assisted route can now be removed. Adoption tells us where contacts arrived. It does not, by itself, describe the needs of the people who chose another channel or establish what will happen when that choice disappears.
The percentage leaves a group behind
Our fictional April 2025 sample contained 1,200 property-service contacts. Eight hundred and forty came through the portal and 360 by telephone. The digital share was seventy per cent. The adoption sponsor saw a strong case for moving towards a portal-only arrangement, and the figure offered an appealingly simple story about progress. I asked us to keep the other thirty per cent in the discussion as a group with actual questions. Their existence was not necessarily evidence of reluctance to use technology. It could reflect the kind of explanation their situation required.
Property service often sits between several responsibilities. An occupier may know the symptom without knowing which team owns it. A managing agent may speak for more than one account. A question may require context that the most common request categories do not capture. A well-designed portal can support many of those situations, but the adoption rate alone does not show that it already does. We needed to understand the remaining contact paths before making the channel decision. Otherwise, a successful digital programme could become the reason the enterprise removed the explanation some users still needed.
The argument for a single route was not unreasonable. Maintaining several channels creates coordination work, and colleagues may duplicate effort when a caller also submits a digital request. A consistent entry point can improve the record. I wanted those costs considered honestly alongside the risk of leaving the residual group with an unsuitable path. The choice was not between supporting the portal and resisting it. The real decision concerned the service arrangement that should accompany the portal at that stage of its development, with evidence about the people and questions affected.
I therefore supported a twelve-week assisted arrangement costing SGD360,000 while operations and technology examined the service journeys. The cost made the decision concrete. We were choosing to retain capacity and learn, rather than assuming assistance could continue indefinitely without resources. The period also created a responsibility to use the observations. An assisted route should not become an excuse to leave avoidable portal difficulties untouched. It should help the team understand which problems can be improved in the digital process and which still need a different kind of conversation.
Compare what the measures actually describe
The sample recorded first-contact disposition for 720 of the 840 portal contacts and 180 of the 360 telephone contacts. Those figures were useful, but their meaning required care. A disposition described a stated next step or outcome at that first contact. It did not mean that every issue had been completely resolved. Nor were the two channel groups interchangeable samples in a controlled experiment. People had selected their routes, and the mix of questions differed. A direct comparison could prompt investigation, but it could not establish that the portal alone caused a better final service outcome.
The temptation was to combine the high digital share with the stronger disposition proportion and infer a straightforward workforce benefit from further migration. That would skip several questions. What work remained after the first disposition? Which telephone contacts could reasonably use the current portal? Would removing assistance reduce the work or move it into repeated, escalated or poorly described requests? We had not established those answers. I wanted the programme to preserve the real strengths of the portal without relying on an inference that the observations did not yet support.
This distinction matters because different measures serve different management purposes. Channel share helps explain demand. First-contact disposition helps examine the initial service route. Final resolution, user experience and resource consumption need their own evidence. A programme can improve one without improving all at the same rate. A clear account allows operations to decide what to examine next. A single broad success label makes that harder, especially when the label is used to justify removing the very route through which the difficult questions are currently becoming visible.
I also wanted the remaining work described in terms that the service team recognised. A contact waiting for an authorised property decision is different from a contact waiting because the user cannot find the appropriate form. The first may need a better handover between owners; the second may need a clearer interface or explanation. Technology can support both, but the intervention should follow the actual difficulty. Treating every telephone contact as a failed digital conversion would conceal that distinction and encourage the programme to improve its adoption measure rather than the occupier's next useful answer.
Design the next answer before removing the route
At the end of an assisted period, the enterprise still needs a decision. I would expect the team to explain which needs the portal can now support, which require assistance and how the remaining responsibilities will be carried. That might lead to a narrower assisted service, a changed digital route or continued support for specific questions. The evidence should determine the arrangement. A channel should not remain solely because it has always existed, but neither should it disappear solely because a majority has found another route convenient. The minority still belongs within the service proposition.
For a CIO, this is a useful place to examine the boundary between product success and operating success. The technology team can deliver a capable portal and still need the partnership of property operations to decide how people are served. I want that relationship visible in the investment account. If the proposal includes a workforce or cost benefit, the operating choices required to produce it should be stated. A digital adoption figure cannot make those choices on behalf of the people who remain responsible for service quality and the difficult cases.
My practical rule is to design the next answer before removing the existing route to it. The answer may come through a better portal, an assisted conversation or a clearer handover to an authorised colleague. What matters is that the enterprise understands how the user will proceed. Seventy per cent digital adoption can be a valuable result without settling every subsequent decision. Keeping that distinction allows the programme to build on its success while remaining accountable for the people whose needs the headline percentage leaves outside the frame.