Platform case
Before and after a remote recovery
Illustrative images of a typical recovery.
We build diagnostics and reporting software for self-service terminal fleets. On a critical fault the system sends the full diagnosis to the field team, who arrive knowing which module to check. That is exactly what we work on: queue at the branch.
Illustrative images of a typical recovery.
| Alert type | Response | Cover |
|---|---|---|
| Critical: terminal not operating | 4 working hours | Monday to Sunday |
| High: functional fault, no full outage | 1 working day | Monday to Saturday |
| Scheduled: updates and improvements | Agreed window | Outside peak hours |
Response times are set by contract and vary with the location of the machine.
Real reviews from Nakuru clients.
"We finally know which machines are costing us and which are fine."
"Fault history changed which units we replaced first."
"The reports made the replacement budget an easy conversation."
Serving Nakuru with quality materials and certified professionals.
Clear common faults without a call-out.
Interface work for new products and languages.
Uptime, fault patterns and transaction volume.
Interfaces to core systems and card platforms.
Operating system and application updates.
Moving a fleet onto the platform in stages.
The event arrives from monitoring or from the client service desk.
The module at fault is identified and remote recovery is attempted.
If hardware is needed, the diagnosis travels with the alert to the field team.
The event, its cause and the recovery time are recorded on the dashboard.
Contact us today and receive fast, professional service.