E ExamMaster

Spoken English · Out and About

Cabs and Autos

Memorisable frames for booking a ride, sharing landmarks, fare talk, finding the driver, waiting, and trip safety.

Getting somewhere by cab or auto is one of the most frequent English exchanges outside the office or the home — hailing an auto in Koramangala, booking an Ola or Rapido from a Hyderabad colony where the app pin never quite lands right, or guiding a driver over a phone call through a Kolkata by-lane at night. None of it needs new vocabulary; it needs six short frames used automatically. Indian English also carries a set of calques from vernacular translation — 'meter se chalo' as 'meter only, meter only', an address handed over with no landmark, a fare settled only after the ride ends — and each concept below replaces one with the direct frame a fluent speaker actually reaches for.

  • Spoken English
  • Easy level
  • 6 concepts
  • 15 practice questions

1Booking a ride: app request versus flagging one down

A Bengaluru commuter booking through Ola, Uber or Rapido answers most of the questions on-screen before the ride even starts — pickup pin, destination, cab type — so the spoken English kicks in only at pickup and drop. A roadside auto in the same city still runs on a live spoken exchange, because there's no app screen doing that work for you.

Hailing an auto starts with a question, not a demand: 'Are you free?' or 'Could you take me to Koramangala?' — 'Koramangala chalo' translated word for word into 'Koramangala, go' reads as an order rather than a request, and spoken English keeps the same everyday politeness for a stranger that any request needs. Once the driver agrees, 'By the meter, please' states which billing you expect without sounding like an accusation.

The calque worth replacing here is 'meter se chalo', carried straight across as 'meter only' or 'go by meter only' — understandable, but not what a fluent speaker says. 'Could you go by the meter, please?' does the same job and reads as an ordinary, polite request rather than a translated instruction.

Figure. App request versus roadside hail: name destination; confirm vehicle details.

Booking frames
SituationFrame
Hailing a roadside autoAre you free? Could you take me to Koramangala?
Confirming you want the meterCould you go by the meter, please?
Booking through an appI've booked a cab to this address on Uber
Choosing a ride type in the appI'll go with the auto option, it's cheaper for a short trip
You flag down a roadside auto in Koramangala and want the driver to charge by the meter rather than negotiate a flat rate. Which line asks for that naturally?
  1. Meter only, meter only.
  2. Could you go by the meter, please?
  3. Go by meter.
  4. (Say nothing and hope the driver uses the meter.)

It states the expected billing as a normal, polite request. 'Meter only' repeated is the calque this concept replaces, 'go by meter' drops the politeness a stranger request needs, and saying nothing risks a flat rate you never agreed to.

2Sharing your pickup and drop with a landmark, not just an address

A GPS pin in a Hyderabad gated colony or a Guwahati by-lane often lands a driver fifty metres from the actual gate, so the frame that gets a ride started on time names a landmark before it names an address: 'I'm right next to the Big Bazaar, near Gate 2' gets a driver moving in the right direction faster than a flat address that means nothing without local knowledge.

Giving the drop works the same way: 'Please drop me near the State Bank, just past the flyover' gives the driver a visible target to aim for, rather than a street name that may not even be marked. Where two landmarks might be confused, naming which side of the road closes the gap: 'the one on the left, next to the pharmacy' is worth the extra clause.

The trap is naming an address alone and assuming the app pin does the rest — a Chennai commuter who says only 'T Nagar' is understood to mean an entire neighbourhood, not the two-metre gate the ride actually needs. A landmark converts a vague place into a findable one and saves a phone call once the driver arrives.

Figure. Share pickup/drop with a landmark, not only a bare address string.

Giving pickup and drop by landmark

  1. Name the pickup landmark firstI'm right next to the Big Bazaar, near Gate 2 — a landmark, not just an address, is what a driver can actually aim for.
  2. Give the drop the same wayPlease drop me near the State Bank, just past the flyover — a visible target beats a street name that may not be marked.
  3. Add the side of the road if two landmarks could be confusedThe one on the left, next to the pharmacy — worth the extra clause when the wrong turn costs a detour.
Your pickup is inside a large residential colony in Hyderabad where the app pin regularly lands the driver at the wrong gate. What should you send the driver before they arrive?
  1. Just come to the address on the app.
  2. I'm right next to the Big Bazaar, near Gate 2.
  3. Somewhere in the colony, you'll find it.
  4. (Wait and call only once the driver seems lost.)

It names a landmark the driver can actually aim for, which a pin alone cannot do inside a large colony. Pointing back at the app pin repeats the exact problem, 'somewhere in the colony' gives no usable target, and waiting until the driver is lost wastes time both sides could have saved.

3Asking about the fare, the meter, and the app's estimate, politely

A ride's price shows up three different ways depending on the city and the vehicle — a metered auto in Mumbai, an app estimate on Rapido or Uber that can move with surge pricing, and a flatly negotiated rate on a roadside auto with no meter running at all — and the polite question fits whichever one is actually in front of you, not one script for all three.

For a metered ride, 'Is the meter running?' or 'What does the meter say?' is a plain, checkable question, not an accusation. For an app ride, the estimate is already on-screen, so the useful question is about a mismatch: 'The app showed a lower fare — has something changed?' names the discrepancy without assuming bad faith.

For a negotiated roadside fare with no meter, agreeing the number before the ride starts is what avoids an argument at the destination: 'How much for this ride?' followed by 'Could you do it for two hundred?' states a counter-offer directly. The trap is starting the ride first and negotiating only once you've arrived, which leaves you with no leverage at all.

Figure. Ask meter versus estimate politely; compare to the app number without accusing.

Fare frames by ride type
Ride typeWhat to ask
Metered autoIs the meter running? / What does the meter say?
App-booked cab, fare looks offThe app showed a lower fare — has something changed?
Roadside auto, no meterHow much for this ride? Could you do it for two hundred?
Any ride, before you startCould you confirm the fare before we start?
You flag a roadside auto with no meter and the driver names a price only after you've already reached your stop. What should you have said before getting in?
  1. Is the meter running?
  2. How much for this ride?
  3. The app showed a lower fare.
  4. (Get in and settle the price at the end, as usual.)

Asking the price before the ride starts, on a route with no meter, is what actually gives you room to agree or negotiate. Asking about a meter that isn't running gets no useful answer, the app-fare line applies to a booked ride rather than a roadside auto, and settling at the end removes your only leverage.

4'I'm right here': guiding a driver who can't find you

The call that starts 'I can't find you' is one of the most common in a booked ride, and answering it with more app details ('check the pin') rarely helps as much as describing what's actually visible from where you're standing: 'I'm the one in the blue shirt, standing outside the pharmacy' gives the driver something to look for with their eyes, not their screen.

When the driver has clearly overshot or is on the wrong road entirely, naming the correction directly saves a second wrong turn: 'You've passed me — please take a U-turn' or 'You're on the wrong side of the road, I'm on the other side' states the exact problem rather than a vague 'you're not close.'

Staying on the line while a driver navigates a Kolkata by-lane at night is often what actually gets the ride started — 'I can see your car now, keep coming straight' confirms progress in real time, rather than hanging up and hoping the driver figures it out. Ending the call the moment you've said where you are is the trap, because a driver in an unfamiliar lane may need a second correction almost immediately.

Figure. Guide with what is visible now: colour, gate, side of the road.

Guiding a driver to you
SituationFrame
Describing what's visibleI'm the one in the blue shirt, outside the pharmacy
Driver has overshotYou've passed me — please take a U-turn
Driver on the wrong sideYou're on the wrong side of the road, I'm on the other side
Confirming they're closeI can see your car now, keep coming straight
A driver calls saying they can't locate you outside a busy Kolkata market. What is the most useful thing to tell them first?
  1. Just check the app pin, I'm right there.
  2. I'm the one in the blue shirt, standing outside the pharmacy.
  3. I'm nearby, keep looking.
  4. (Hang up and wait for them to find you.)

It describes something visible from the street, which actually helps in a crowded market where a pin isn't precise enough. Pointing back at the app repeats the problem, 'nearby' gives no usable detail, and hanging up removes the one channel that could correct a wrong turn.

5Cancelling a ride, or asking a driver to wait, without the awkwardness

Two different problems both feel awkward to raise out loud — cancelling a ride you've already booked, and asking a driver who has arrived to wait a few minutes — and both have a short, direct frame that avoids the guilt-driven over-explaining that usually replaces it.

Cancelling before the driver has started moving is a one-line message, not an apology essay: 'I need to cancel this ride, sorry for the trouble' states the fact and the courtesy in one breath. Once a driver has already arrived and is waiting, asking for a few minutes is equally direct: 'Could you wait five minutes, please? I'm just coming down.'

The criterion that decides which is fair is whether the driver has already started moving toward you: a cancellation minutes after booking, before anyone has driven anywhere, costs little. Asking a driver who has already arrived to wait an unstated amount of time is what actually causes frustration, so naming a specific number of minutes — not 'just a second' — is what keeps the wait acceptable to both sides.

Figure. Cancel or ask to wait with a clear line; silence is what creates awkwardness.

Cancelling or asking to wait
SituationFrame
Cancelling before the driver has movedI need to cancel this ride, sorry for the trouble
Driver has arrived, you need a momentCould you wait five minutes, please? I'm just coming down
Driver already been waiting a whileI'm so sorry for the delay, I'll be right there
Genuinely can't make it after a long waitI have to cancel now — I'm really sorry, please charge me if there's a fee
A driver has already arrived outside your building and you need three more minutes to come down. What should you say?
  1. Just a second.
  2. Could you wait five minutes, please? I'm just coming down.
  3. Cancel and I'll book again.
  4. (Say nothing and hope the driver waits.)

It names a specific number of minutes, which keeps an already-arrived driver's wait acceptable rather than open-ended. 'Just a second' understates the real wait, cancelling on an arrived driver is more disruptive than a short wait, and saying nothing risks the driver leaving with no explanation.

6Speaking up: sharing your trip and flagging a safety concern

Sharing a trip's live location with a family member or friend is one tap in most apps, and saying so out loud to the driver is not an accusation — it's a normal, stated habit: 'I've shared my trip with a friend' is a plain fact, said the same way whether or not anything is wrong.

Confirming the basics before getting in is equally routine and equally worth saying aloud: 'Can you confirm the driver's name and the number plate?' checks the ride against what the app shows, and asking it every time — not just when something feels off — is what makes it unremarkable rather than suspicious-sounding.

If something during the ride genuinely feels wrong — the driver takes an unfamiliar route, or ignores a request — speaking up directly and early is what actually works, rather than staying quiet and hoping it resolves itself: 'Please take the route on the app' or 'Please stop here, I'd like to get out' are said plainly, without apologising for asking, because a clear instruction in the moment is safer than a polite silence that assumes the driver will notice something is wrong.

Figure. Safety language: share the trip, speak the concern, exit if needed.

Speaking up on a ride

  1. Share the trip and say soI've shared my trip with a friend — a plain, routine fact, not an accusation, said the same way every ride.
  2. Confirm the driver and plateCan you confirm the driver's name and the number plate? — checked against the app before getting in, every time.
  3. Say the correction directly if something feels wrongPlease take the route on the app / Please stop here, I'd like to get out — stated plainly and early, not left for the driver to notice on their own.
A driver takes a route that's clearly different from the one shown in the app, and it's making you uneasy. What should you say?
  1. Nothing — the driver probably knows a shortcut.
  2. Please take the route on the app.
  3. This seems weird, but okay.
  4. (Wait until the ride ends and report it afterward.)

It states the correction directly and early, which actually addresses the concern while it can still be acted on. Assuming a shortcut, voicing discomfort without a clear ask, and waiting until after the ride all leave the actual problem unaddressed in the moment.

Notes

  • Booking a ride: app request versus flagging one down: A Bengaluru commuter booking through Ola, Uber or Rapido answers most of the questions on-screen before the ride even starts — pickup pin, destination, cab type — so the spoken English kicks in only at pickup and drop. A
  • Sharing your pickup and drop with a landmark, not just an address: A GPS pin in a Hyderabad gated colony or a Guwahati by-lane often lands a driver fifty metres from the actual gate, so the frame that gets a ride started on time names a landmark before it names an address: 'I'm right ne
  • Asking about the fare, the meter, and the app's estimate, politely: A ride's price shows up three different ways depending on the city and the vehicle — a metered auto in Mumbai, an app estimate on Rapido or Uber that can move with surge pricing, and a flatly negotiated rate on a roadsid
  • 'I'm right here': guiding a driver who can't find you: The call that starts 'I can't find you' is one of the most common in a booked ride, and answering it with more app details ('check the pin') rarely helps as much as describing what's actually visible from where you're st
  • Cancelling a ride, or asking a driver to wait, without the awkwardness: Two different problems both feel awkward to raise out loud — cancelling a ride you've already booked, and asking a driver who has arrived to wait a few minutes — and both have a short, direct frame that avoids the guilt-
  • Speaking up: sharing your trip and flagging a safety concern: Sharing a trip's live location with a family member or friend is one tap in most apps, and saying so out loud to the driver is not an accusation — it's a normal, stated habit: 'I've shared my trip with a friend' is a pla

Formulas

  • Hailing a roadside auto | Are you free? Could you take me to Koramangala?
  • Sharing your pickup and drop with a landmark, not just an address: Name the pickup landmark first; Give the drop the same way; Add the side of the road if two landmarks could be confused
  • Metered auto | Is the meter running? / What does the meter say?
  • Describing what's visible | I'm the one in the blue shirt, outside the pharmacy
  • Cancelling before the driver has moved | I need to cancel this ride, sorry for the trouble

Exam traps & shortcuts

  • Booking a ride: app request versus flagging one down — Could you go by the meter, please?
  • Sharing your pickup and drop with a landmark, not just an address — I'm right next to the Big Bazaar, near Gate 2.
  • Asking about the fare, the meter, and the app's estimate, politely — How much for this ride?
  • 'I'm right here': guiding a driver who can't find you — I'm the one in the blue shirt, standing outside the pharmacy.

Reference tables

Each row is a recurring moment in a ride, its load-bearing frame, and the calque or habit it replaces.

Cabs and autos, on one sheet
MomentLoad-bearing frameReplaces
Confirming the meterCould you go by the meter, please?Meter only, meter only
Giving your pickupI'm right next to the Big Bazaar, near Gate 2A bare address the app pin alone can't place
Asking the fare upfrontHow much for this ride?Getting in first and negotiating at the end
Guiding a lost driverI'm the one in the blue shirt, outside the pharmacyJust check the app pin
Asking a driver to waitCould you wait five minutes, please?Just a second, with no number given
Flagging a safety concernPlease take the route on the appA polite silence hoping it resolves itself

Recap

Six lines that carry a cab or auto ride from booking to drop, anywhere in India.

State the billing, don't repeat it
Could you go by the meter, please? Never 'meter only, meter only' — that's the calque this topic replaces.
Landmark before address
I'm right next to the Big Bazaar, near Gate 2 — a landmark gets a driver moving; a bare address doesn't.
Agree the fare before you get in
How much for this ride? — asked before the ride starts, when you still have room to negotiate.
Describe what's visible, not the pin
I'm the one in the blue shirt, outside the pharmacy — helps a driver who's already checked the pin and still can't find you.
Name a number of minutes
Could you wait five minutes, please? — specific and fair, not an open-ended 'just a second'.
Speak up early and plainly
Please take the route on the app / please stop here — said directly, not left for the driver to notice.

Practise Cabs and Autos

Reading is free and needs no account. Practice, mocks and progress live in the app.

  • 15 exam-style questions on this topic, with explanations
  • A 5-question practice set that ends the chapter
  • Timed mocks scored with the real marking scheme
  • Readiness tracked per topic, kept on your device
Continue with Google — freeNo card, no trial. Works offline once installed.