Frequently asked
questions.
The common questions we hear from passengers, transport operators, insurers, drivers and partners.
What is DFKover?
+
DFKover is digital infrastructure for intercity road travel. We help transport operators create structured trip and passenger records and connect eligible journeys to insurance workflows provided by licensed insurance partners.
Is DFKover an insurance company?
+
No. DFKover does not underwrite insurance. Insurance products distributed through DFKover are provided or underwritten by licensed insurance partners.
Does a passenger need to download an app?
+
No. DFKover is designed to work around the journey passengers are already taking. At supported parks, an authorised agent or operator can register the trip and passenger, while confirmation can be sent directly to the passenger.
How does DFKover work at a park using handwritten manifests?
+
A manifest officer or park agent can create the trip digitally, register the vehicle and driver, capture passenger information and complete the manifest through DFKover without requiring the transport company to first build an online booking system.
What if the transport operator already has online booking software?
+
DFKover can work alongside an existing booking workflow. The goal is to connect existing trip and passenger information to the protection and journey-record layer rather than require staff to enter the same information twice.
When is insurance attached to a passenger journey?
+
The insurance workflow begins after the required trip and passenger information has been captured. The exact process depends on the agreed insurance product and partner integration.
How does a passenger know whether insurance was issued?
+
Passengers should receive a confirmation or other policy evidence showing the outcome of the insurance workflow. The relevant policy or insurer terms remain the authoritative source for the insurance cover.
Who underwrites the insurance?
+
Insurance products are underwritten by licensed insurance partners. DFKover provides the transport, distribution and trip-data infrastructure around the journey.
What happens when something goes wrong during a trip?
+
DFKover can retain the passenger, journey, vehicle, driver and cover record needed to support operational follow-up. Insurance claims remain subject to the relevant insurer’s claims process and policy terms.
Can DFKover start with just one park or route?
+
Yes. Our preferred approach is to start with a defined operating environment, prove the workflow with real departures, identify what needs improvement and expand from there.
What is the DFKover driver-benefits programme?
+
DFKover is building toward a system where verified commercial journeys and mileage can accumulate into a portable driver activity record that may support eligibility for partner-provided benefits.
Are driver benefits already available to every driver?
+
No. The broader driver-benefits layer is still being developed. Availability and eligibility will depend on the relevant benefit programme, participating partners and applicable terms.
Does DFKover use AI?
+
AI is not required for DFKover’s core journey and insurance workflow today. Over time, as reliable trip data grows, machine learning may help with areas such as pattern detection, risk analysis and operational decision support.
Where is DFKover based?
+
DFKover is based in Abuja, Nigeria, and is starting with Nigerian intercity road transport.