Skip to content
Menu
Field service Case study

MFI runs field service across 18 African countries on ERPNext

Ticketing, dispatch, SLAs and escalation for 500 to 2,000 field technicians in 18 countries, on ERPNext.

Field service
Headline result Resolution time cut from 8–10 days to 2–3 daysMFI Document Solutions
Client
MFI Document Solutions
Industry
Field service
Platform
ERPNext · Frappe Framework
Scope
4 modules
1ProblemService requests arrived by phone and email with no ticketing, no status tracking, no SLA tracking and no escalation path, and technicians were assigned late across regions.
2GoalImplement a centralised support system
3What we builtAn ERPNext support implementation with helpdesk, task management and email notifications.
4OutcomeResolution time cut from 8–10 days to 2–3 days
01 · The client

MFI Document Solutions

MFI Document Solutions is a Nairobi-based managed print and document solutions company serving banking, government and healthcare across 18 Sub-Saharan African countries (including Kenya, Uganda, Tanzania, Rwanda, Ethiopia, DRC, Zambia, Malawi, Mozambique and Burundi), with 500–1,000 employees and 500–2,000 field technicians.

Client
MFI Document Solutions
Industry
Field service
Country
Kenya
Engagement
ERPNext support and field-service implementation
Region
Kenya and Sub-Saharan Africa (18 countries)
02 · The challenge

What wasn’t working

Service requests arrived by phone and email with no ticketing, no status tracking, no SLA tracking and no escalation path, and technicians were assigned late across regions.

No structured ticketing system
Manual issue handling via calls and emails
Delayed technician assignment
No tracking of issue status or history
Difficulty monitoring technician performance
No SLA tracking
No escalation mechanism
Poor coordination across regions
What they needed
  • Implement a centralised support system
  • Enable real-time issue tracking
  • Improve response and resolution time
  • Provide customer self-service portal
  • Track technician productivity and service time
  • Introduce structured escalation process
03 · What we implemented

The solution

An ERPNext support implementation with helpdesk, task management and email notifications. It adds a customer self-service portal, one-click issue-to-task conversion, region-based technician assignment and a multi-level escalation matrix.

Modules
  • Support / helpdesk
  • Task management
  • Email notifications
  • Dashboards and reporting

How work flows now

  1. 1Customer issue (portal or call)
  2. 2Ticket in ERPNext
  3. 3Support review
  4. 4Remote resolution or task
  5. 5Technician assignment
  6. 6On-site visit and work log
  7. 7Material request if needed
  8. 8Escalation if unresolved
  9. 9Closure

What we built beyond the standard

  • Customer self-service portal with predefined forms
  • Issue to task conversion (single click)
  • Technician assignment based on region
  • Escalation matrix (multi-level support)
  • Technician time tracking with pause/resume
  • Material request within service tasks
  • Service visit scheduling
  • Preventive maintenance tracking
  • SLA-based alerts
  • Region-based issue routing

Outcomes

  • Centralised system across geographies
  • Faster task assignment and execution
  • Real-time dashboards for management
  • Reduced repeat complaints
04 · The results

What changed for the business

MetricBeforeAfter
Resolution time8–10 days2–3 days
46,720Issues tracked, total issues in the system
39,640Tasks completed
~52,745Assets tracked
Start a conversation

Want this for your operation?

Tell us which case looked closest to yours.