Customer Relationship Management Platforms

The customer who explains it three times

A customer sees a deduction they do not recognise. They call the contact centre and explain it. The agent emails the branch that holds the account. Three days later the customer walks in, and the officer at the counter asks them to start from the beginning. Nothing has been lost. The first note is in one mailbox, the second in another, and the third was never written down. What the customer takes from it is that the institution does not remember them.

This shape is common here, and not because anyone is careless. Institutions added service points quickly: branches, a contact centre, agents, an app, a USSD menu, and now messaging and social media, where a complaint is public before it is logged. Each arrived with its own way of noting what happened: a register, a spreadsheet, somebody's inbox. Customers came the other way, taught by mobile money to expect an answer inside the conversation they are in. Products across institutions look increasingly alike, so service is much of what a customer chooses between.

It matters most where the relationship is the product. A bank with relationship managers over its retail and SME customers loses something real each time an officer moves and takes what they knew. A SACCO's members are its owners, and being treated as a stranger by an institution you part-own is felt personally. Microfinance institutions hold their relationships in the field, with officers who do not stay forever. Telcos and fintechs have the reverse problem: each case is small, and a great many arrive at once.

One history, and the work that hangs off it

The first thing that changes is what a member of staff sees when a customer reaches them. Who they are, what they hold across savings, loans, cards and channels, what they have contacted you about before, what was decided, and what somebody promised them. The same picture serves a contact centre agent, a branch officer, a relationship manager and a field officer, and it is the difference between a conversation that continues and one that starts over.

Around it sits the work. Complaints and service requests captured where they arrive, each with a category, a named owner and a date it is due, keeping their history when they move between teams. Escalation when one ages or a customer comes back a second time. Notes from calls, counter visits and field visits that the next person to serve that customer can read. The requests staff handle on a customer's behalf: statements, card replacements, standing instruction changes, limit reviews, contact updates, closures. Queues a supervisor can read by branch and by team: what is open, what is late, who is carrying too much. And management reporting on volumes, on repeat complaints and on where they come from.

Handover deserves its own mention, because institutions lose most there and notice it least. A relationship manager resigns or moves branch, and their successor inherits a list of accounts and little else. Every conversation about a delayed harvest, a seasonal squeeze or a fee argued over two years ago begins again.

Which of this goes live first is decided with you, against whichever costs you more: the complaint backlog or the handover gap.

A complaint is evidence, not correspondence

For a supervised institution, complaint handling is an obligation as well as a courtesy. Banking in Tanzania is supervised by the Bank of Tanzania, and an institution is expected to deal with complaints and to show how it did so. When a case is reopened months later, by a customer, a supervisor or your own board, the answer has to be a file: what was said, when, who took it on, what was decided, and what the customer was told.

This is the test email fails. A thread sits in the mailboxes of whoever was copied, and it leaves with the officer who owned it. No set of inboxes can say how many complaints of one kind arrived last quarter, how long they took, or how many are still open. Those are the first questions asked when something goes wrong.

A service history is also a concentration of personal information, some of it sensitive: income, health, family circumstances, disputes with you. Tanzania has a Personal Data Protection Act. Who may read a customer's history, how long it is kept and how a customer exercises their rights are yours to settle, and we build to them.

Where it starts, where it stops, and what sits next to it

Three things get called customer management, so the boundary is worth stating. Lead generation is the work before somebody is a customer: interest, prospects and follow-up until they open something. This begins where that ends, once a person holds a product with you and their experience starts accumulating. Administration portals are different again: they run the institution internally, the approvals, the back office, the controls. This one is about the relationship rather than the operation.

Its place among your systems is straightforward. Your core banking system records what a customer holds. Your channels are where they transact. Neither remembers a conversation, and conversations are much of what customers judge you on. We build those channels too, so this can extend what you run or form part of a wider programme.

What you have to settle for any of it to work

Most of what decides whether this succeeds is settled on your side, and little of it is technical. Service standards come first. Nothing can be tracked against a deadline until somebody commits to one: how quickly you acknowledge, how quickly you resolve, by type of case, and whether those promises are published or held internally. Operations has to believe the numbers before they are set.

Then the complaint framework. What counts as a complaint rather than a query. The categories you report on. Who owns a case at each stage, what escalates it, and who may close one. Most institutions have a policy that says one thing and a practice that does another, and closing that gap is yours.

Then access. Whether one branch sees another's customers. Whether a contact centre agent sees arrears. What a field officer carries on a phone. These are risk and data protection decisions for your compliance function rather than questions for a project team.

Then the history you already hold, the part most often underestimated. It sits in spreadsheets, mailboxes, branch registers and notebooks, and it is uneven. How far back you carry it, what is worth cleaning and what is left behind each cost something. Last, the discipline: a branch that keeps its own book alongside the service record makes the record incomplete, and an incomplete one is quickly a record nobody trusts. That is settled by how service performance is measured, not by training.

Working with us

We start with discovery: how service actually runs across your branches, contact centre and field teams, what your complaint policy says and what your people do instead. That produces a scope and a 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 rather than status reports, and the source code and documentation are yours from the first commit. Afterwards we support it and train your people, including the supervisors who will run the queues. There is no lock-in, by design and by contract.