Identify
A job starts with a number, not a map pin. The number is the recipient, the farm asset, or the meter — whatever the visit is actually for.
Syncabi Networks / Locate
Syncabi Locate turns a phone number into a precise, consented position — and links the person standing there to the courier, technician, or irrigation crew on the way to them. It is the spatial layer of Syncabi Networks: the same infrastructure that keeps fields connected, used to answer the question every operation in Rwanda eventually hits. Where, exactly?
Across Rwanda and much of East Africa, a home is a description: a hill, a lane, a blue gate. Addressing systems assume a grid that was never drawn, so software written elsewhere fails at the last kilometre.
The phone number is the one identifier almost every household and every farmer already carries. Syncabi Locate treats it as the address key, so nothing has to be registered, mapped, or memorised first.
Deliveries fail on the final call, not the long haul. Field crews lose hours finding a valve. Both are the same problem: a destination that exists in someone's head and nowhere in the system.
How it works
The sequence matters more than any single signal. Consent comes before resolution, and the fix tightens in the open, with the sources on the record.
A job starts with a number, not a map pin. The number is the recipient, the farm asset, or the meter — whatever the visit is actually for.
The network asks the handset before it locates anything. An SMS or USSD prompt, answerable on any phone, grants access for this job only.
Cell timing, handset positioning, and the household's own saved landmark are layered until the radius is small enough to walk to. Each source is recorded.
The fix becomes a short code and a route. The courier or technician sees the pin while the job is open, reads back a handover code, and the pin is revoked.
Prototype
Type a Rwandan mobile number, approve the request as the person holding that phone would, and watch the fix tighten as each signal lands. Then dispatch, follow the route, and close the job with a handover code. Switch scenarios to see the same layer used for an irrigation call-out.
Prototype. Nothing here contacts a network or a handset — the fix is derived from the number you type so the same number always lands in the same place. Accuracy figures illustrate what layered signals can support, not a measured result.
Where it is used
Delivery and irrigation look like different businesses, but they fail in the same place — at the point where a system has to find something it can only describe.
Delivery
A courier leaves the depot with a route instead of a conversation. The recipient never has to explain the way, and the operator gets a delivery that can be planned, measured, and repeated.
Irrigation
A valve, pump, or sensor is registered against the farmer's number. When a line drops pressure, the technician is routed to the asset itself rather than to the farm gate and a walk.
Operating rules
Nothing resolves without an answer from the handset. Consent is per job, expires with the job, and is refusable without losing the service.
A courier holds a position for the duration of a delivery, not permanently. When the handover code is read back, the pin is revoked and the route is closed.
Every fix carries the sources that produced it and the radius they support. A location the network cannot justify is reported as uncertain, not rounded into confidence.
The consent flow runs on USSD as well as smartphones. A system that only works on a data plan does not work for the households that need it most.
Syncabi Locate
A delivery operation, a cooperative, an irrigation scheme — if the last kilometre is where the day breaks down, that is enough to have a useful first conversation.