Every "No" Needs a "Why": How We Fixed Our Driver Onboarding Feedback Loop

Drivers could register in minutes, then disappear into a black box. Here's how we rebuilt document review so every driver knows the status of every document, why it was flagged, and how to fix it, without calling anyone.

8 min read

Getting started as a Twende driver should be effortless, whether you sign up directly inside the Twende Driver app or on the web.

We built our registration flow to get drivers onboarded in three clean, structured steps:

  1. Personal details. Who you are and how we can reach you.
  2. Vehicle details. Locking in the vehicle specs, from the vehicle type and manufacturer all the way down to the plate number.
  3. Documents. Uploading the credentials we need to verify before anyone drives with Twende: national ID, driving licence and insurance.

Hit Submit, a confirmation screen appears, and the application streams directly into our system.

Now, here was the real bottleneck: submitting was easy, but following up? Drivers were left in the dark, having to call or message our staff just to understand why their application had stalled. Someone on our team would look it up, scroll through the documents and say, "Ah, your licence photo is blurry. Can you send it again?" The answer had been sitting in our system the whole time. We just never sent it back to the person who needed it.

We hated that friction. So we built a far more transparent experience.

The black box after "Submit"

When you build mobility infrastructure, you spend a lot of energy on the moments users can see: the booking flow, the map, the ride itself. Onboarding drivers feels like plumbing in comparison. A form goes in, a decision comes out.

But for a driver, onboarding is the product. It's the first thing we ask of them, and it decides when they can start earning. Every day an application sits in limbo is a day of income lost.

Before the fix, the silence after "Submit" cost everyone:

  • Drivers lost days waiting, then more time chasing an answer.
  • Our team answered the same handful of questions over and over, one phone call at a time.
  • Twende lost good drivers who gave up, assuming the silence meant "no" for good.

None of those people were doing anything wrong. The system was.

How we built a black box without meaning to

It's worth being honest about how this happened, because we suspect it's common.

We designed document review for the reviewer. Our admin tools made it fast for our team to look at an application and make a decision. But a decision is only half of a feedback loop. The other half is the decision reaching the person it affects, in a form they can act on. We had built the first half and assumed the second.

On top of that, the status the driver could see was too coarse. An application was pending, approved or rejected: one bit of information to describe a process involving five separate documents, each of which could go wrong in its own way. "Rejected" doesn't tell you whether to retake a photo, renew your insurance or find a different document entirely.

When a system can't answer a question, people answer it themselves, by phoning you. A support ticket is very often a product bug that hasn't been filed yet.

What we built

The fix came in three parts, all now live in the Twende Driver app. The heart of it is a new screen: Account Status, a real-time tracker for everything a driver has submitted.

1. A status for every document, in real time

We stopped treating an application as a single yes or no. On the Account Status screen, every document has its own status (pending, approved or rejected), and the driver sees each one update as it happens: national ID, driving licence, insurance and the rest. No more guesswork.

That sounds like a small change. In practice, it's the difference between "your application was rejected" and "your ID and insurance are approved, and your licence needs another look". The first is a dead end. The second is a to-do list with one item on it.

2. Feedback a driver can act on

When a document is flagged, the driver now sees exactly why, in plain language: the image is blurry, the document has expired, the information doesn't match the rest of the application, or it's the wrong type of document.

Behind that is a design decision we feel strongly about. On the reviewer's side, rejecting a document isn't a free-text box. It's a short list of clear reasons, and you can't reject without choosing one.

We chose a fixed list over free text on purpose:

  • It's consistent. Two reviewers looking at the same blurry photo give the same answer, not "pic unclear" from one and "please resubmit" from the other.
  • It's translatable. We operate across English, French and Swahili-speaking markets. A known reason can be translated properly once. A note typed in a hurry can't.
  • It's actionable. Every reason maps to something the driver can actually do: retake the photo, renew the document, correct the details, upload the right file.
  • It teaches us. When reasons are structured, we can see which ones come up most often. If blurry photos dominate, the fix isn't more reviewers. It's better guidance at the moment the driver takes the picture.

3. Appeals inside the app

Reviewers are human, and automated checks aren't perfect. Sometimes a document is flagged when it shouldn't be. A name can be spelled one way on an ID and another way on a licence. A photo can look worse on a reviewer's screen than it does in hand.

So drivers no longer have to start over or call us. The whole appeal happens right where the problem is shown:

  1. Tap the flagged document on the Account Status screen, for example a driving licence marked as invalid.
  2. Replace it on the spot with a new photo or file.
  3. Write a brief explanation, for the cases where the document was fine and the context was missing.
  4. Confirm with your password.
  5. Resubmit for compliance review.

It takes seconds. The new document and the explanation go back for review together, so the next reviewer has the context the first one didn't.

Step four deserves a word, because it's the one people ask about. Why ask for a password inside an app the driver is already logged into? Because an appeal replaces an identity document. Phones get shared, borrowed and left unlocked on a table. We don't want anyone except the account owner to be able to swap the licence on a driver's profile, so we ask for one extra second of proof at exactly the moment it matters. Removing friction everywhere else is what earns us the right to add it here.

An appeal is a feedback loop running in the other direction. We tell drivers why; they get to tell us why too.

The reviewer's side of the loop

Closing the loop for drivers also meant changing how our team works.

Our document review screen now shows the driver's checklist on one side and the selected document on the other, next to the information our system extracted from it automatically. A reviewer can compare what the document says with what the driver entered without opening a single new tab, then approve or reject each document individually.

Every decision, with its reason, is recorded in an audit trail. That matters for accountability: when a driver appeals, we can see exactly what was decided, by whom and why. It also matters for safety, which is the part we want to be very clear about.

Transparency doesn't mean a lower bar

There's a fear that sometimes comes with this kind of change: if you explain every rejection and make appeals easy, aren't you making it easier to get through?

No. Our vetting is strict, and it stays strict. As we wrote in Safety First, checking every driver properly is central to what Twende promises passengers. None of that changed.

What changed is that strict no longer means opaque. A driver with an expired licence is still not getting on the road. But now they know that's the reason, and they know exactly what to do about it. We'd argue that a vetting process people understand is stronger, not weaker: drivers who know the rules can follow them, and the ones who try to get around them stand out more clearly.

Our opinion, stated plainly

If you're building any system where people submit something and wait for a decision, such as driver onboarding, loan applications, seller verification or visa forms, here's what we'd tell you:

  1. Every "no" needs a "why". A rejection without a reason isn't a decision. It's a support ticket you've scheduled for later.
  2. Every "why" needs a "what next". A reason only helps if the person can act on it. Design the reasons around the actions.
  3. Make status as detailed as the process. If five things can go wrong, show five statuses, not one.
  4. Structure your feedback. Fixed reasons are consistent, translatable and measurable. Free text is none of those.
  5. Let people answer back. Your reviewers will make mistakes. Give people a fast, built-in way to correct them.
  6. Spend friction deliberately. Remove it everywhere you can, so you can afford it where security needs it, like re-entering a password before replacing an identity document.

Total transparency, zero hassle. We're removing every barrier we can find so our drivers spend less time waiting and more time earning. For a driver, that's the whole point. For us, it's a reminder that building mobility infrastructure isn't only about vehicles and maps. It's about the people who make the platform move, and how we treat them from the very first tap.

Ready to ride with Twende?

Join the waitlist and be among the first to experience safer, fairer transport in African cities.

Related posts