why new drivers never open your help section

the faq that already exists

every ops team at a delivery startup knows the feeling. a new driver calls to ask how to start taking orders. inside the app, under help, there's an FAQ titled almost word for word "how do i go online". it's been there since launch. the caller explains it over the phone, closes the call, and wonders why the driver didn't just look.

the easy conclusion is that drivers don't read, or that the FAQ needs better titles. we think both miss what's going on. the FAQ did its job. it just did it in a place the driver wasn't, in a language the driver wasn't thinking in.

this isn't special to driver apps. self-service has a weak record everywhere. in a 2024 Gartner survey of 5,728 customers, only 14% of issues were fully resolved through self-service, and 43% of people said they couldn't find content relevant to their problem (source). those were customers of all kinds of companies, mostly reading in their first language. a new driver on day two, reading a help screen in English, is starting from further back.

why the help section fails new drivers

think about what a help section asks of someone who is stuck. they were in the middle of something, say uploading the back of their licence, and it didn't work. to use help they have to leave that screen, find the help tab, pick the right question out of a list that all looks similar, read an answer written in English, go back, and match what they read to a screen that may have changed in the last release. each of those steps is small. together they're a lot to ask of someone who just wants to start earning.

the language problem alone is enough to sink it. in a 2023 Borzo survey (a company survey, reported by CNBC TV18), 84% of delivery workers said they use a local language while delivering, and 82% said they want a local language inside the app. Play Store reviews say the same thing more bluntly. one Zypp review from october 2026 just says "no option to choose telugu as language".

vocabulary is the next problem. teams write FAQs in the app's own words, because that's how they think about it. "activate your account", "complete KYC", "enable availability". drivers describe the same things in their own words, often a mix of Hindi and English, and the help search, if there is one, rarely bridges that.

and then there's the simplest reason. when a driver is stuck, the fastest thing that feels like progress is to tap the call button. the help section is a detour. the call is a shortcut, even when it takes longer to get through.

language and placement, not skill

it's tempting to read all this as "drivers aren't good with apps". the evidence points the other way. a government study across four metros (VVGNLI) found 92% of gig workers had secondary to graduate schooling. IDinsight found 95% owned a smartphone before they joined. these are people who use their phones all day. the gap is that the app explains itself in the wrong language, in the wrong place.

training videos run into the same wall from another side. a video can be in Hindi, but it lives on its own screen, it plays at its own pace, and it can't see what the driver is looking at. one Rapido captain's review of the training video says it's "Playing In Loop Again And Again". that's a driver who wanted to move on and couldn't.

this reframes the problem in a useful way. the question stops being "how do we write better FAQs" and becomes "how do we get the answer onto the screen where the question starts, in the driver's language". those lead to very different work. the first leads to a content rewrite. the second leads you to look at your onboarding flow, find the few screens where new drivers get stuck most, and put help there.

the answer is on the wrong screen

this is the idea heytappr is built on. it's a voice guide inside your Android partner app. on the screen where a new driver is stuck, it highlights the real button and talks them through what to do in Hindi or their regional language, moving on when they tap. each step is shown as text too, so it still works when the phone is on mute. there's nothing to search and no help tab to find.

it also only says what your team wrote and approved. that matters more in a driver app than almost anywhere, because the questions touch money and documents, and a guide that invented an answer about payouts would cause far more calls than it saved. if you want the longer argument, we wrote about it in why in-app AI shouldn't write its own answers.

it doesn't replace the help section. it covers the part of the job the help section was never in a position to do, which is being there on the documents screen at the moment the photo won't upload.

keep the help section, change what it's for

none of this is an argument for deleting your FAQ. a good help section still earns its place, just for different reasons than cutting calls.

it's where a driver goes to look up how payouts are calculated, what the incentive rules are this week, which documents count as address proof, or what to do after an accident. those are long answers that someone reads with time and intent. they're looking something up, and a list of written answers is the right shape for that.

it's also worth being honest about what neither a help section nor a voice guide can fix. if verification drags on for days, if there's a joining fee or a deposit the driver didn't expect, if they need a team lead to approve a slot, or if there just aren't orders in their area, the driver will stall no matter how clear the app is. those are ops problems. the help section should explain them plainly, and the ops team should own them.

the mistake is expecting the same help screens to also catch the new driver who can't find the online toggle right now. that driver needs something shorter, closer and spoken. so split the jobs. the help section explains. the app shows.

what to do with the questions it misses

start by finding out which questions slip through. take a few weeks of support calls and tag each one by what the driver was trying to do, not which part of the app it touched. rank those intents by volume. the top five usually cover a surprising share of the line, and almost all of them will already have an FAQ. that's your proof the problem is placement and language, not content. we walked through the tagging in detail in the playbook for how-do-i calls.

then answer those five in the app, on the screens where they come from. write the guidance in the words drivers actually used on the calls, in Hindi first and then whatever your next city speaks. keep each step short enough to follow without reading ahead.

finally, measure each question separately, and tie it to first orders. call volume moves with hiring, so it won't tell you whether a fix worked. calls per thousand new signups for one specific intent will. and the number underneath all of it is how many signups reach a first order. Swiggy's DRHP links "quicker onboarding of delivery partners" to its aim to "reduce delivery partner attrition rates", and that's the scoreboard that counts.

a better question to ask

teams usually ask why drivers don't open the help section. it's the wrong question, because it assumes the driver should come to the answer. the more useful one is why the answer isn't already on the screen the driver is looking at, in a language they think in.

once you ask it that way, the fix gets smaller. you don't need a new FAQ or a content overhaul. you need to find the few screens where new drivers get stuck, and be there, out loud, when they do.