Enterprise Administrative Portals

The platform nobody puts in the business case

Digital channels get budgets. The work they create behind them usually does not. A mobile app, an agent network, a USSD menu and a payments service each produce work only your staff can settle: a duplicate payment to reverse, an account locked after too many wrong PIN attempts, a stolen handset to de-register, a fee to waive because you got it wrong.

Where nothing has been built for it, the work still happens, through routes nobody designed. A branch manager telephones someone in IT. An operations officer asks in writing for a record to be corrected by hand. A supervisor's approval arrives as a message on a phone. The customer is served, and nothing about it is recorded anywhere a third party could examine. The institution ends up running on the discretion of a few technical staff, which is slow on a good day and hard to defend on a bad one.

The pattern is common across Tanzania and the region, where channels arrived fast and operations were left to catch up. In a bank the work is spread across a contact centre, branch operations, product, finance and compliance, and the same request gets handled differently depending on who receives it. In a SACCO or a microfinance institution one person may raise a correction, approve it and be the only one who knows it happened, which is exactly the arrangement an examiner looks for. For a fintech or a telco there is no branch network to absorb rising support volume, so the back office breaks first.

What your own staff come here to do

This is the working day for people who never appear in your marketing: contact centre agents, branch operations officers, product managers, finance, risk and compliance staff, and the supervisors who sign things off.

The tasks it usually carries: finding a customer and seeing what they hold and what they have done recently, while they are on the telephone; investigating a transaction and reversing or correcting it; unlocking accounts, resetting PINs and re-registering a customer on a new handset; adjusting a limit within an agreed band; blocking and unblocking cards and channels; capturing and resolving a complaint; waiving a charge; amending products, fees and cut-off times; administering agents, merchants and partners; managing your own staff's access; and producing the reports finance, risk and your board ask for, including the returns you file.

Different roles want different things from the same platform. A contact centre agent needs one view, answered in seconds, with a customer on the line. A branch operations officer works a queue and cares what is outstanding at close of business. A product manager wants to change a fee without raising a request with anybody. Internal audit wants to read, and nothing else. Which go live first is decided with you, and the better start is the handful of tasks generating the most requests to IT today.

Dual control, and the first thing an auditor asks for

Some of these actions move money or change what a customer is permitted to do: reversing a transaction, waiving a fee, raising a limit, repricing a product, granting another member of staff access. In a supervised institution those are not tasks one person should complete alone. Dual control on them is a governance requirement rather than a preference, and which actions need one, and who may give it, is for your risk, compliance and internal audit functions to settle.

The other half is the record of who did what, readable by somebody other than the person who acted. That is what makes an internal investigation possible, settles a dispute where two accounts disagree, and lets you answer a question about last quarter without relying on anybody's memory. It is often the first thing an auditor asks for: who has access, what each person can do, whether anybody can approve their own work, and whether access was withdrawn when a member of staff left.

One further decision sits here, and Tanzania's Personal Data Protection Act makes it unavoidable. Support staff look at customer information in order to help customers, and how much each role needs to see is a choice rather than an accident. Full details for some, less for others, and a position on when a reason has to be given for looking. Most institutions leave this open until something forces it.

What it costs to leave this to IT

Institutions accumulate administrative tools the way they accumulate channels, one at a time. The agent network has a console, the card business has another, a payment arrangement brings a third party's portal, and the core banking system has its own back office, built for a banking operations department rather than a contact centre. Staff end up with several logins and no single answer to who can do what.

The cost of leaving it alone is rarely counted. It shows up as operations staff waiting on IT for routine changes, as an auditor asking who approved something and nobody being able to say, and as every new channel arriving with another tool and another set of staff logins to look after. Whether that means one portal across the estate or one covering the platforms you are building now is a scoping question.

What you have to settle before it can be built

Almost everything that shapes this platform is an organisational decision, and those decisions are harder than they look because most have never had to be written down. Roles come first: who does what, in which department, and up to what value. Most have job titles and a shared understanding, then find in discovery that two branches work differently and that several people hold authority nobody formally granted.

Then the second approver. Which actions require one, who may give it, and what happens at eight in the evening when the person who normally approves is unreachable. That is where policies fail in practice: a rule that cannot be followed on a Sunday gets worked around, and the workaround is what an auditor eventually finds. Coverage is the same question larger: which tasks must be available outside working hours, and how long a customer waits for a reversal on a Saturday, are service decisions with a cost.

Then your people. This changes jobs. Staff who used to raise a request and wait will carry out the action themselves and answer for it, which is a training matter and, for some, a grading one. Alongside it sits an access process with an owner: how a joiner is granted access, what changes when somebody moves department, and who removes it on the day a person leaves. That last is commonly the weakest control in an institution, and it belongs to human resources and operations.

Working with us

We start with discovery, and here that means sitting with the people who do the work: the contact centre, branch operations, the staff who raise requests to IT today and those who receive them. Out of it comes a scope and a delivery plan, and the plan is yours whether or not we go on to build it.

Through delivery you see working software in an environment you control, and the people who will use it try it while it is built rather than at handover. Source code and documentation are yours from the first commit. Afterwards we support the platform and train your staff, including the supervisors who approve what other people do. There is no lock-in, by design and by contract.