Built for any customer-facing operation
The workflows are configured to your categories, policies and approval paths, not fixed to one industry.
Applied product
A complete customer operations system for organisations without one, built on the same gateway, risk tiers, confidence scoring and audit as the rest of Cortex. If you already run a CRM, Cortex connects to it instead.
The workflows are configured to your categories, policies and approval paths, not fixed to one industry.
Reads run on their own, agent actions are recorded, and sensitive actions stop for a named person.
Model, version, inputs, confidence and the human decision are recorded on every case.
Ten areas, from the customer record through to reporting. Where AI acts, the control level is stated alongside it.
One view of the customer
Identity, contact channels, verification status and customer class in a single record.
Every account, plan or tariff, balance, arrears and service status, with the equipment or assets linked to it.
The customer's location mapped to the part of your network, estate or service area that serves them, with live status. This is what links a complaint to an actual incident.
Invoices, amounts, disputes and a consumption or spend trend over time.
Every interaction on every channel in one chronological view, with direction, handler and sentiment.
Sensitive fields are masked by default and only opened to the roles allowed to see them.
Every channel, one inbox
Agent ownedCreate, assign, update and escalate sit with the agent and are recorded.
WhatsApp, SMS, USSD, email, voice, social, web and walk-in unified into a single conversation timeline.
Create, assign, update, escalate and resolve, with priority, category, status and a named owner.
Per-case timers with a live countdown, warning and breach states, set by category and priority.
Related and duplicate cases are linked so one issue is not worked five times.
Faster handling, human still in charge
AdvisorySuggestions are advisory. The agent owns the send button.
Every inbound message is classified by category, priority and suggested owner with a confidence score. Low confidence goes to a person.
Flags an unhappy or at-risk customer and raises priority automatically.
A short brief on the case before the agent engages.
Suggests the resolution step from your policy and the customer's history, grounded in approved knowledge.
An editable, grounded response is prepared for the agent to review and send.
Stop handling one fault as a hundred tickets
AutomaticCorrelation and grouping are read-only, so they run automatically.
Incoming reports are matched against known faults, outages or service disruptions at that location.
A spike of related contacts is grouped into one parent incident with the child cases attached.
Affected customers can be updated together, with the outbound message itself risk-checked before it goes.
Agents see the incident, its age and the expected restoration rather than guessing.
The queries that generate the most heat
Approval requiredAnything that moves money pauses for a named approver.
Estimated versus actual billing disputes are worked against the written policy, with the policy source shown.
Payments, balances and arrears are read live from your billing and payment systems.
Cortex prepares the adjustment with its calculation and evidence, then holds it for sign-off.
Instalment arrangements are proposed within policy limits and confirmed by an approver.
From the case to the visit
Approval requiredThe dispatcher confirms routing. Service cut or restore is approval gated.
A case becomes a field job with the address, fault type, history and access notes attached.
Jobs are proposed to the right crew by skill, location and load, with the dispatcher confirming.
Crew updates close the loop back onto the case and the customer timeline.
Governed supply actions tracked to a target, for example restoration within 24 hours of a qualifying payment.
One approved source of truth
AdvisoryCustomer-facing AI answers only from approved knowledge and escalates anything sensitive.
Approved policy and procedure articles that ground every answer given.
Agents and AI retrieve only from approved knowledge, with the source shown next to the answer.
A customer-facing assistant on the same approved knowledge, monitored for drift.
Balance, status and case progress without queueing for an agent.
The part most CRMs bolt on afterwards
Approval requiredMoney, service cut or restore, customer data change, mass send and regulatory replies always stop for a person.
Reads run automatically, writes are agent owned, and high-risk actions pause for a named human.
Every high-risk action arrives with full context for sign-off in one place.
Every recommendation and action logged with model, version, timestamp, inputs and the human decision.
Anything the system is unsure about is routed to a person rather than guessed.
Role-based access, single sign-on, privacy masking and encryption in transit. Deploys in your environment.
A reply to a regulator is its own high-risk action and always requires sign-off.
What leadership actually looks at
Service levels, open case volumes, live incidents, sentiment mix and queue depth, per business unit.
Volumes by channel, category and outcome, first contact resolution, handling time and backlog age.
A written management narrative from the numbers, not just charts.
Closed cases scored on empathy, compliance and completeness.
What AI did, what it recommended, what a human approved or rejected, and where confidence was low.
Reports delivered on a schedule to the people who need them, in the format they already use.
No rip and replace
Billing, finance, payments and customer systems connected through the governed connector layer.
Metering, asset and work order systems, mapping and network or incident systems where you run them.
Telephony, IVR, messaging and email platforms feed the same unified timeline.
The CRM acts through your systems rather than replacing them, and every write is tiered and logged.
Three representative views from a Cortex CRM workspace. They show the layout and control levels, not a live product screen.
Customer 360
Amara O.
Residential, verified
Balance
₦12,400
Service status
Normal
Location
Zone 4B
Open cases
1
Latest note
Reported intermittent supply yesterday. Linked to planned maintenance in the area.
Source: agent call, 08:45
Command centre
Open cases
247
SLA at risk
12
Live incidents
3
Avg sentiment
4.2
Cases closed this week
Interaction timeline
09:14 · WhatsApp
AdvisoryCustomer asked about latest bill
09:05 · Voice
Agent ownedAgent confirmed payment plan
08:47 · System
AutomaticPlanned outage notice sent
Yesterday · Email
Approval requiredDispute raised on invoice
Every capability runs through the same governed gateway, with a confidence score and an audit record. Anything that touches money, service, customer data, a regulator or a mass send stops for a named person. Most vendors add automation on top of a CRM. Here the governance is the platform.
See the Cortex platformA useful first meeting
Pick a real case type, tell us who signs off on it today, and we will map the channels, the rules and the approval point in one working session.