heytappr.

how to write guide steps a new driver can follow by ear

a guide can point at exactly the right button and still lose a driver, because the sentence it spoke was in office English, or office Hindi. the fix is mostly about cutting, and about writing the way people talk.

by shritupdated 7 min read

still from The Tale of the Princess Kaguya: Kaguya bent over a low desk by candlelight, practicing calligraphy with a brush
Kaguya practicing calligraphy, from The Tale of the Princess Kaguya (Studio Ghibli, 2013). still shared by studio ghibli for free use.

tl;dr (too long, didn't read)

good guide copy for drivers is one tap per step, uses the exact words printed on the button, and starts with the action. "Go Online दबाइए" beats "to begin receiving orders, kindly change your duty status".

write everyday Hindi, the kind people speak, and keep the English words drivers already use, like order, OTP, online and photo. sarkari Hindi is as hard to follow as legal English.

test it the only way that counts: read each step out loud on a real phone while doing exactly what it says. anything you stumble on, a driver standing outside a restaurant will too.

why the sentence matters as much as the spotlight

when people build a walkthrough, most of the effort goes into targeting. which button, on which screen, triggered by what. the words get written last, usually in English, usually by whoever set up the targeting, and then sent off for translation. then everyone wonders why drivers drop at step three.

watch a new driver follow a guide and the reason is obvious. at every step they have two jobs: understand the instruction, then find the thing it refers to. the highlight helps with the second job. only the words help with the first. and a driver usually hears the step once, often outdoors, sometimes with a customer waiting. there's no time to parse a long sentence, and there's no going back to reread it.

this matters more in driver apps than almost anywhere, because the problem is rarely the phone. a VVGNLI study across four metros found 92% of delivery workers had secondary to graduate schooling, and IDinsight found 95% owned a smartphone before joining. what's missing is the language. in a 2023 Borzo survey, 82% of couriers wanted a local language inside the app. so the copy is where most of the help actually happens.

one step, one tap

the most common mistake is packing a whole task into one step. "go to profile, open bank details and add your account" is three steps pretending to be one. the driver hears it, taps profile, and now has to remember the rest while looking for a menu. half of them will have forgotten the second part by the time they find the first.

split it. one step says open profile, and highlights profile. the next says open bank details, and highlights that. it feels slow when you write it and it's much faster to follow, because the driver never has to remember anything. the guide remembers for them.

this shapes the whole guide too. if a task genuinely takes nine taps, ask whether it's really two tasks. short guides get finished far more often than long ones, and we went through the numbers in onboarding checklist vs guided walkthrough.

One Punch Man, via GIPHY

use the words on the screen, action first

if the button says "Go Online", the step says "Go Online", even inside a Hindi sentence. don't translate the label into "ऑनलाइन जाइए" or "ड्यूटी शुरू कीजिए" if the screen still shows English. the driver hears a word, then scans the screen for it. when the word matches, finding it is instant. when it doesn't, they have to guess, and guessing on a live order is how mistakes happen. if your app is translated, use the translated label exactly as it appears.

then put the action where it lands quickly. in English that means verb first: "tap Accept". Hindi puts the verb at the end, so keep the sentence short enough that the end comes fast: "Accept दबाइए". the label goes first, the verb closes it, and there's nothing in between to wait through.

these two rules fix most bad guide copy. a few examples of the kind of step every partner app has:

before and after, in everyday Hindi and simple English
beforeafter (Hindi)after (simple English)
Kindly upload a clear photograph of the front side of your driving licence.लाइसेंस के आगे वाले हिस्से की फोटो लीजिए।take a photo of the front of your licence.
To begin receiving orders, please change your duty status to online.Go Online दबाइए। अब ऑर्डर आने लगेंगे।tap Go Online. orders will start coming.
Your documents are currently undergoing verification.आपके कागज़ों की जांच चल रही है। अभी कुछ नहीं करना है।we're checking your documents. you don't need to do anything now.
Request the customer to share the delivery OTP and enter it below.ग्राहक से OTP पूछिए और यहाँ डालिए।ask the customer for the OTP and type it here.
Swipe the slider to confirm arrival at the pickup location.दुकान पहुँचकर Reached को खिसकाइए।at the shop, slide Reached.

write everyday Hindi, and keep the English drivers use

the second most common mistake is translating into the wrong Hindi. machine translation and careful translators both tend toward formal, written Hindi. "सत्यापन" for verification, "दस्तावेज़ प्रविष्ट करें" for upload your documents. it's correct, and plenty of drivers would have to stop and think about it. nobody talks like that at a chai stall.

write the way a friendly supervisor would say it out loud. "जांच" instead of "सत्यापन". "कागज़" or just "documents" instead of "दस्तावेज़". "डालिए" instead of "प्रविष्ट करें". and leave alone the English words drivers already use every day: order, OTP, online, location, photo, payout. translating those makes the step harder to follow.

two small grammar choices help a lot. use आप and the -इए form, like "दबाइए" and "लीजिए". it's polite, and it avoids most of the gender agreement Hindi forces on future and past verbs, so the same step works for every driver. and write numbers and money the way they're said. "500 रुपये" reads aloud cleanly. symbols and abbreviations often get read strangely or skipped.

for simple English the rule is the same. short words, no idioms, nothing you'd only say in a meeting. "tap", not "proceed". "your money", not "your settlement". a driver whose first language is Marathi or Tamil should be able to follow the English version too, because many of them will until you add their language. a Zypp review from october 2026 is just "no option to choose telugu as language". simple source copy also makes every later translation easier.

say why only when they'd hesitate

there's a pull to explain every step, because it feels friendly. most of the time it isn't needed. a driver who's trying to go online doesn't need to be told why going online matters. the reason just delays the instruction.

the exception is any step that looks risky, costs money, or asks for something personal. a camera or location permission, a deposit, a bank account, a selfie. those deserve one plain sentence: "location को Allow कीजिए, ताकि पास वाले ऑर्डर मिलें।" a good test: if you were standing next to the driver and they'd look up at you before tapping, write down what you'd say.

and tell them what happens next when it isn't obvious. "अब एक OTP आएगा" stops a driver from tapping again and again while they wait. a driver who did the right thing and isn't sure it worked will usually do it again, or give up.

write it to be heard, and to be read on mute

this matters to us because heytappr speaks every step out loud while it highlights where to tap. but it also has to work silently, because plenty of drivers keep the phone on mute or are standing next to traffic. so every step is shown on screen as well as spoken, and the same sentence has to work both ways.

text that works aloud avoids things that only make sense visually. "the icon on the right" is fine to read and vague to hear, and the highlight already shows where. arrows and slashes get read literally or not at all. long sentences with a clause in the middle are hard to follow by ear, because the listener can't glance back. text that works on mute avoids the opposite problem: it can't lean on tone of voice. short sentences, the button's actual name, plain words. that covers both.

heytappr only speaks the guides your team wrote and approved, so these words are the only words a driver will ever hear from it. your ops team edits them from a dashboard and they go live without an app release, which means fixing a confusing step takes minutes rather than a sprint. it ships as an Android SDK.

test it by reading while tapping

reviewing guide copy in a spreadsheet is almost useless. it all reads fine there, because the spreadsheet isn't the app. the real test takes ten minutes. open the actual partner app on an ordinary phone, read each step out loud, and do exactly what it says, nothing more.

you'll find the problems immediately. the step that says "Start Duty" when the button now says "Go Online". the step that assumes a menu is already open. the Hindi word you had to read twice. fix those, and then watch one new driver follow the guide without your help, ideally in the language they'd choose themselves. heytappr's funnel shows the exact step drivers quit, which tells you which sentence to rewrite next.

see it in your product

fifteen minutes: heytappr answering a real question by walking a user through a real interface, out loud.

questions people ask

How long should a spoken guide step be?

One short sentence with a single tap, usually under ten words. Add a second sentence only when the step is risky, costs money, or asks for a permission, and the driver would otherwise hesitate.

Should guide copy in a driver app be in Hindi or English?

In the language the driver chooses, with Hindi first for most Indian delivery apps. Write everyday Hindi rather than formal Hindi, and keep the English words drivers already use, like order, OTP and online.

Should guide steps translate button labels?

No. Use the label exactly as it appears on the screen, even inside a Hindi sentence. If the app itself is translated, use the translated label.

How do I test guide copy for drivers?

Open the real partner app on an ordinary phone, read each step out loud, and do only what it says. Then watch one new driver follow it unaided, in their own language.

go deeper

keep reading

spotted something out of date? tell us and it gets fixed.