Amazon Flex delivery driver — On-the-job English
Study in your language — but on the job you'll speak English. These are the real phrases you actually say for this work, with a note in your language. Not a script; common situations workers report.
Quick drill — pick the best answer, see why. Saved on this device.
✍️ Practice theseConfirming a block & warehouse check-in
This is your very first stop of every Flex shift, and it's mostly listening. You won't say much — you'll hear short, fast instructions ("cart 4," "dock B," "wait for your name") in a loud warehouse and need to act on them. Nail this low-stakes chapter and the rest of the shift goes smoothly; miss a word here and you can lose time before you've even started driving. Once you're checked in and your cart is loaded, it's time to head out and find your first address — that's next.
- 👂 You'll hear
Check in at the desk.
One of the first things you hear when you walk in. "The desk" means the front counter — they want you to check in there, not do something at a table. Walk over, give your name or open the Flex app to show your reservation. Miss it and you stand around waiting; your block can get marked late or forfeited.
- 👂 You'll hear
Your cart's over there.
After you check in, staff point you to your cart — the wheeled cage/rack holding your packages. "Over there" is vague, so watch where they point or gesture. If you're not sure, don't guess; grab the wrong cart and you'll load someone else's route. Reply "Which cart is mine?" or "Sorry, could you say that again?" to pin down the number.
- 👂 You'll hear
Wait for your name to be called.
When the station is busy, they stage drivers and call names one at a time. This means: don't crowd the dock, just stand aside and listen for your name. It's passive — you do nothing until called. If you miss it because you weren't listening (or wandered off), you go to the back of the line and your block clock is still running.
- 👂 You'll hear
Cart 4, dock B.
A compact assignment: your cart is number 4, parked at dock B (dock = the loading bay where you back your car in). Numbers and single letters get lost in a noisy warehouse — B/D/E and 4/40 sound alike. If you're not 100% sure, repeat it back: "Cart 4, dock B?" Load the wrong dock and you delay yourself and block someone else's bay.
- 👂 You'll hear
Back your car up to the dock.
"Back up" = reverse — they want you to back your car into the loading bay so the trunk faces the dock for loading. Don't confuse it with "back away" (leave) or parking somewhere in the back. Do it slowly; docks are tight and busy. Reply "Got it" and go slow, or ask "Sorry, could you say that again?" if unsure. Pull in nose-first and you'll have to redo it while everyone waits.
- 🗣️ You say
I reserved a 3-hour block starting at 4 PM.
Say this at the desk to state exactly which block you booked — the length and the start time. "Block" is the Flex word for the work shift you reserved in the app. Being specific (3-hour, 4 PM) helps staff find you in the system fast. Swap in your real numbers. Vague lines like "I'm here for work" make them ask again and slow your check-in.
- 🗣️ You say
Where do I pick up the packages?
Use this once you've checked in and need to know where to collect your load. In the app the pickup spot is the "delivery station," but on the ground you just ask for the packages. Note "pick up" (collect) — not "pick" one. Listen for the answer as a cart number and a dock/area ("Cart 4, over there"). If you instead say "Where is my package?" they may think you're a customer chasing one parcel.
- 🗣️ You say
Which cart is mine?
A clean way to confirm your assigned cart when "over there" isn't enough. You'll usually hear back a number ("Cart 4") or a pointing gesture. Short and clear beats guessing. Ask before you touch any cart — taking the wrong one and scanning it wastes time and can mix up two drivers' routes.
🧠 Skills this builds
- Your single most useful line this whole shift. Warehouses are loud and instructions come fast; nobody minds repeating a cart number. It's polite, native, and buys you a clean second try. Alternatives: "Could you repeat that?" / "Sorry, what cart?" Never just nod and hope — a guessed number costs far more than asking.
🇺🇸 US workplace note
- Warehouse etiquette: keep it short and move fast — staff are juggling many drivers and don't want small talk. Don't touch or roll away any cart until it's confirmed as yours. Don't block the dock while you sort things out; pull aside. A quick "Got it" or "Thanks" is enough; a thumbs-up works when it's too loud to hear. And never argue about your assigned cart or dock on the floor — check the app or ask the desk calmly.
⚠️ Common mistakes
- Nodding "yes" when you didn't actually catch the cart number, instead of asking again. — You walk off toward the wrong cart, load the wrong packages, and have to undo it all — sometimes after you've already scanned. Asking "Sorry, could you say that again?" up front costs five seconds; guessing costs fifteen minutes.
- Hearing "back your car up to the dock" and driving away, because "back up" got confused with "back away / leave." — You pull out of the bay thinking they told you to move on, and now you're blocking traffic or circling the lot while your cart sits unloaded. "Back up" means reverse in, not leave — when in doubt, watch their hand signals at the dock.
- Saying "Where is my package?" instead of "Where do I pick up the packages?" — Staff hear a customer question — one parcel, singular — and may point you to a returns counter or ask for a tracking number. You want your whole load, so say "packages" (plural) and "pick up." The wrong phrasing gets you a confused look and a slower start.
🔖 Quick reference
Check in at the desk.
One of the first things you hear when you walk in. "The desk" means the front counter — they want you to check in there, not do something at a table. Walk over, give your name or open the Flex app to show your reservation. Miss it and you stand around waiting; your block can get marked late or forfeited.
Your cart's over there.
After you check in, staff point you to your cart — the wheeled cage/rack holding your packages. "Over there" is vague, so watch where they point or gesture. If you're not sure, don't guess; grab the wrong cart and you'll load someone else's route. Reply "Which cart is mine?" or "Sorry, could you say that again?" to pin down the number.
Wait for your name to be called.
When the station is busy, they stage drivers and call names one at a time. This means: don't crowd the dock, just stand aside and listen for your name. It's passive — you do nothing until called. If you miss it because you weren't listening (or wandered off), you go to the back of the line and your block clock is still running.
Cart 4, dock B.
A compact assignment: your cart is number 4, parked at dock B (dock = the loading bay where you back your car in). Numbers and single letters get lost in a noisy warehouse — B/D/E and 4/40 sound alike. If you're not 100% sure, repeat it back: "Cart 4, dock B?" Load the wrong dock and you delay yourself and block someone else's bay.
Back your car up to the dock.
"Back up" = reverse — they want you to back your car into the loading bay so the trunk faces the dock for loading. Don't confuse it with "back away" (leave) or parking somewhere in the back. Do it slowly; docks are tight and busy. Reply "Got it" and go slow, or ask "Sorry, could you say that again?" if unsure. Pull in nose-first and you'll have to redo it while everyone waits.
I reserved a 3-hour block starting at 4 PM.
Say this at the desk to state exactly which block you booked — the length and the start time. "Block" is the Flex word for the work shift you reserved in the app. Being specific (3-hour, 4 PM) helps staff find you in the system fast. Swap in your real numbers. Vague lines like "I'm here for work" make them ask again and slow your check-in.
Where do I pick up the packages?
Use this once you've checked in and need to know where to collect your load. In the app the pickup spot is the "delivery station," but on the ground you just ask for the packages. Note "pick up" (collect) — not "pick" one. Listen for the answer as a cart number and a dock/area ("Cart 4, over there"). If you instead say "Where is my package?" they may think you're a customer chasing one parcel.
Which cart is mine?
A clean way to confirm your assigned cart when "over there" isn't enough. You'll usually hear back a number ("Cart 4") or a pointing gesture. Short and clear beats guessing. Ask before you touch any cart — taking the wrong one and scanning it wastes time and can mix up two drivers' routes.
Sorry, could you say that again?
Your single most useful line this whole shift. Warehouses are loud and instructions come fast; nobody minds repeating a cart number. It's polite, native, and buys you a clean second try. Alternatives: "Could you repeat that?" / "Sorry, what cart?" Never just nod and hope — a guessed number costs far more than asking.
Navigating & finding the address
The map says you've arrived, but you're staring at four identical brick buildings, none of them labeled, and the customer's dot is sitting in the middle of a parking lot. This is the most time-eating part of a Flex block — not driving, but the last hundred feet on foot. Drivers who deliver fast aren't better at English grammar; they're just willing to open their mouth: ask the first resident they see, confirm the building before climbing stairs, and call support the moment the app misbehaves instead of fighting it silently. Once you've found the building or unit, the next step is handling the actual drop-off — gates, doors, and the photo are covered in 'At the delivery location'.
- 👂 You'll hear
Building C is around back, past the pool.
A resident or passerby often points you like this. 'Around back' = go behind the building; 'past the pool' = keep going beyond the pool. Listen for the direction words (back, left, past, around) and follow them one by one. If you mishear the direction, you'll walk to the wrong place and fall behind on the rest of your route.
- 👂 You'll hear
This entrance is for residents only — you'll want the other gate.
You'll hear this at gated complexes when you approach the wrong door. It is not a rejection — 'you'll want the other gate' is friendly for 'the entrance you need is elsewhere.' Ask 'Which way is the other gate?' rather than forcing this one. Pushing a residents-only door can trip an alarm or get you reported as trespassing.
- 👂 You'll hear
Even numbers are on the left, odd on the right.
Residents use this to explain how the units are laid out so you can find yours yourself. 'Even' = 2, 4, 6...; 'odd' = 1, 3, 5... Check whether your unit number is even or odd, then pick that side. If you go to the wrong side you may knock on a stranger's door and waste minutes you don't have.
- 👂 You'll hear
Are you looking for a specific unit?
A resident who sees you wandering may offer help with this. It is your opening — answer with the unit number right away: 'Yes, apartment 12B.' Don't just say 'yes' and stop, or the conversation stalls. Miss this friendly offer and you may circle the complex alone for another ten minutes.
- 👂 You'll hear
Can you try force-closing the app and reopening it?
This is the first thing phone/chat support asks when you report a frozen app. 'Force-close' = fully shut the app (not restart the phone), then open it again. Do exactly that and report back. If you restart the whole phone instead, you may log out of the route and lose more time — so listen for 'the app,' not 'the phone.'
- 🗣️ You say
Excuse me, which building is 4200?
Open with 'Excuse me' before asking a stranger — in the US, jumping straight to the question sounds abrupt. Then name the exact number you're hunting for so they can point you precisely. Say the digits clearly ('forty-two hundred' or 'four-two-zero-zero'). A mumbled number gets you a vague answer and another lap of the complex.
- 🗣️ You say
I have a package for apartment 12B — is this the right building?
Use this to confirm you're at the correct building before climbing stairs or entering. Leading with 'I have a package for...' signals you're a delivery driver, so residents relax and help. Skipping the check and guessing wrong can leave the package at the wrong door — which counts against you if the customer reports it missing.
- 🗣️ You say
Sorry to bother you — do you know where building C is?
The polite way to stop a resident who's walking by. 'Sorry to bother you' softens the interruption; without it, a bare 'Where is building C?' can sound like a demand. Note it's a real question ('do you know where...'), not an order. Sound curt and people brush past you instead of helping.
- 🗣️ You say
The app froze and it won't let me scan the package.
Say this to support when the app itself is broken, not you. Name the two facts: it 'froze' (stuck, unresponsive) and you 'can't scan.' Being specific gets you the right fix fast. Vague lines like 'it doesn't work' make support run through every generic step and burn your delivery window.
- 🗣️ You say
The GPS sent me to the wrong spot — the pin is off by a block.
Report a bad map pin this way so support knows the address is fine but the location is wrong. 'The pin is off' = the dot on the map is misplaced; 'by a block' tells them how far. This framing protects you: it shows you found the right place and the app misdirected you, not that you got lost.
- 🗣️ You say
There's no unit number on the door — how are they numbered here?
Use this when the door is blank and you need a resident to explain the numbering system. Stating the problem first ('no unit number on the door') shows why you're asking, so the answer is helpful. If you guess and drop the package at an unmarked door, you risk a lost-package claim that lands on you.
🧠 Skills this builds
- When a resident rattles off directions too fast or a support agent's accent is hard to follow, this is your reset button. It's polite and completely normal — native speakers use it too. Far better to ask once more than to nod, walk off in the wrong direction, and lose ten minutes. You can add 'a little slower, please' if speed is the problem.
🇺🇸 US workplace note
- Approaching strangers in the US: a quick 'Excuse me' or 'Sorry to bother you' before your question is expected — skipping it reads as rude, not efficient. Keep a normal arm's-length distance and don't block someone's path. Don't follow residents through a security gate or into a building lobby uninvited; that's trespassing, not shortcut-taking. On the phone with support, find a quiet spot, speak slowly, and it's fine to ask them to repeat too. A friendly, calm tone gets you more help than sounding stressed — even when your clock is running.
⚠️ Common mistakes
- Answering "Are you looking for a specific unit?" with just "Yes" and stopping. — The resident doesn't know which unit, so they can't help and the moment passes. Always follow 'yes' with the number: 'Yes, apartment 12B.'
- Telling support "It doesn't work" instead of naming what broke. — Support has to guess and walks you through every generic step, eating your delivery window. Say the specific fault: 'The app froze and it won't let me scan.'
- Dropping "Excuse me" and asking a stranger a bare "Where is building C?" — Without the opener it sounds like an order, and people brush past instead of helping. Lead with 'Sorry to bother you' or 'Excuse me' every time.
- Hearing "force-close the app" but restarting the whole phone instead. — Restarting the phone can log you out of the route and cost more time than it saves. Listen for 'the app' vs 'the phone' and do exactly what was asked.
🔖 Quick reference
Building C is around back, past the pool.
A resident or passerby often points you like this. 'Around back' = go behind the building; 'past the pool' = keep going beyond the pool. Listen for the direction words (back, left, past, around) and follow them one by one. If you mishear the direction, you'll walk to the wrong place and fall behind on the rest of your route.
This entrance is for residents only — you'll want the other gate.
You'll hear this at gated complexes when you approach the wrong door. It is not a rejection — 'you'll want the other gate' is friendly for 'the entrance you need is elsewhere.' Ask 'Which way is the other gate?' rather than forcing this one. Pushing a residents-only door can trip an alarm or get you reported as trespassing.
Even numbers are on the left, odd on the right.
Residents use this to explain how the units are laid out so you can find yours yourself. 'Even' = 2, 4, 6...; 'odd' = 1, 3, 5... Check whether your unit number is even or odd, then pick that side. If you go to the wrong side you may knock on a stranger's door and waste minutes you don't have.
Are you looking for a specific unit?
A resident who sees you wandering may offer help with this. It is your opening — answer with the unit number right away: 'Yes, apartment 12B.' Don't just say 'yes' and stop, or the conversation stalls. Miss this friendly offer and you may circle the complex alone for another ten minutes.
Can you try force-closing the app and reopening it?
This is the first thing phone/chat support asks when you report a frozen app. 'Force-close' = fully shut the app (not restart the phone), then open it again. Do exactly that and report back. If you restart the whole phone instead, you may log out of the route and lose more time — so listen for 'the app,' not 'the phone.'
Excuse me, which building is 4200?
Open with 'Excuse me' before asking a stranger — in the US, jumping straight to the question sounds abrupt. Then name the exact number you're hunting for so they can point you precisely. Say the digits clearly ('forty-two hundred' or 'four-two-zero-zero'). A mumbled number gets you a vague answer and another lap of the complex.
I have a package for apartment 12B — is this the right building?
Use this to confirm you're at the correct building before climbing stairs or entering. Leading with 'I have a package for...' signals you're a delivery driver, so residents relax and help. Skipping the check and guessing wrong can leave the package at the wrong door — which counts against you if the customer reports it missing.
Sorry to bother you — do you know where building C is?
The polite way to stop a resident who's walking by. 'Sorry to bother you' softens the interruption; without it, a bare 'Where is building C?' can sound like a demand. Note it's a real question ('do you know where...'), not an order. Sound curt and people brush past you instead of helping.
The app froze and it won't let me scan the package.
Say this to support when the app itself is broken, not you. Name the two facts: it 'froze' (stuck, unresponsive) and you 'can't scan.' Being specific gets you the right fix fast. Vague lines like 'it doesn't work' make support run through every generic step and burn your delivery window.
The GPS sent me to the wrong spot — the pin is off by a block.
Report a bad map pin this way so support knows the address is fine but the location is wrong. 'The pin is off' = the dot on the map is misplaced; 'by a block' tells them how far. This framing protects you: it shows you found the right place and the app misdirected you, not that you got lost.
There's no unit number on the door — how are they numbered here?
Use this when the door is blank and you need a resident to explain the numbering system. Stating the problem first ('no unit number on the door') shows why you're asking, so the answer is helpful. If you guess and drop the package at an unmarked door, you risk a lost-package claim that lands on you.
Sorry, could you say that again?
When a resident rattles off directions too fast or a support agent's accent is hard to follow, this is your reset button. It's polite and completely normal — native speakers use it too. Far better to ask once more than to nod, walk off in the wrong direction, and lose ten minutes. You can add 'a little slower, please' if speed is the problem.
At the delivery location
The address is the easy part; the door is where deliveries actually go wrong. A gate won't open, a guard blocks you, the callbox rings out, a dog is loose in the yard, or an order suddenly needs a signature no one is there to give. This chapter gives you the short, calm lines that get you past a front desk, complete the drop with the photo Flex requires, and — just as important — let you back out safely when a stop isn't safe to make. If a gate is locked or no one answers, reaching the customer is covered in 'Customer messages & calls' — and if that still doesn't solve it, 'Driver support & appeals' is there to help.
- 👂 You'll hear
Who are you here for?
A guard or front-desk person asks this at a gated community or apartment lobby — they mean 'which resident are you visiting?' Answer with the unit number or last name on the package, not your own name. If you just say 'Amazon,' they'll often ask again, so lead with the apartment number.
- 🗣️ You say
Hi, I'm an Amazon delivery driver — I have a package for apartment 4B.
Your opening line at any gate or desk. Say your role and the destination in one breath so they can decide fast. Keep the tone friendly and matter-of-fact — you have a legitimate reason to be there. Swap '4B' for whatever the app shows.
- 👂 You'll hear
Do you have authorization?
The guard is asking whether you're pre-cleared to enter — some buildings keep a list. You usually don't have formal 'authorization,' so don't bluff. Say you're delivering to a specific unit and ask them to buzz the resident or open the gate. If they still refuse, that's a case for the callbox or support, not an argument.
- 🗣️ You say
Could you buzz me in, or is there a gate code?
Use this at a locked entrance or callbox. You're giving the desk two easy options — press the button to release the door, or share a code — so they pick the fastest one. If they give a code, repeat it back before you hang up so you don't get stuck at the gate.
- 👂 You'll hear
What's the code?
Over a callbox or intercom, the resident may ask you for a code — usually the last few digits of the tracking or order number the app shows, which proves the delivery is really theirs. If you don't see one, just say you're the Amazon driver with their package and ask them to let you in.
- 🗣️ You say
I'll leave it at your front door and take a photo.
The standard leave-at-door line. Flex requires a delivery photo, so you're telling the customer why you're photographing their doorstep — it's proof of delivery, not anything personal. Say it before you crouch to shoot so no one thinks you're taking a random picture of their home.
- 👂 You'll hear
Just leave it at the door.
The customer or desk is telling you they don't need to sign or take it by hand — set it down and go. This is your cue to place it neatly, snap the photo, and mark it delivered. You still take the photo even when they say this; the app needs it.
- 👂 You'll hear
I can sign for that.
At a front desk or from a resident, this means they're offering to accept and sign for a signature-required package. Good — hand them the phone or the slip and let them sign. Note who signed if the app asks; a doorman signing on the resident's behalf is normal and allowed.
- 🗣️ You say
This package needs a signature — could you sign here, please?
Use it only when the app flags the order as signature-required. Hold out the phone with the signature screen ready so the ask is obvious. If no adult is there to sign, you can't just leave it — follow the app's prompt to try again or return it, or you risk the delivery being reversed.
- 👂 You'll hear
You're not on the list.
A guard says this to block you — your name or company isn't pre-cleared. Don't take it personally and don't push past. Calmly explain you're delivering to a specific unit and ask them to call the resident to authorize you. If the guard still won't let you in, that becomes a support / callbox situation.
- 🗣️ You say
No one's answering the callbox — could you let me in, please?
Say this to a guard or a resident walking by after the customer doesn't pick up. It's a polite ask, not a demand. But don't tailgate through a gate someone opens for themselves if they haven't agreed — if you truly can't get in, the honest move is to contact the customer or tell support.
- 🗣️ You say
There's an aggressive dog and no way to reach the door safely — I'm returning this package.
Say this to support (or note it in the app), calmly, when a loose barking dog, a dark unlit path, or any real hazard blocks the drop. Your safety comes first — you never have to enter an unsafe yard or get past a dog. Returning the package is the correct, approved outcome, not a failure on your part.
- 🗣️ You say
I can't get in and I can't reach the customer, so I can't complete this delivery.
Your closing line to support when the gate is locked, the callbox is dead, and no one answers. Report it plainly instead of leaving the package somewhere it isn't safe or authorized. Follow the app's next step (redeliver or return). Never toss a package over a gate just to mark it done.
🧠 Skills this builds
- Your rescue line when a guard's code, an apartment number, or a fast question over a crackly intercom slips past you. Asking once, politely, is completely normal and far safer than guessing a gate code or wrong unit. You can add 'a bit slower, please?' to get it clearly the second time.
🇺🇸 US workplace note
- Front-desk and security etiquette in the US: lead with the unit number, keep your hands visible, and stay friendly even if a guard is curt — they're doing their job. A doorman or concierge signing for a resident is normal and allowed. Crucial boundaries: never push past a gate, never tailgate through a door someone opened for themselves, and never enter a home or a gated yard you weren't invited into. On any unsafe stop — loose dog, no lighting, a hazard — the culture and the rules both back the same choice: your safety first, return the package, and report it. That is a correct delivery outcome, not a mark against you.
⚠️ Common mistakes
- Guessing a garbled gate code or apartment number instead of asking the guard to repeat it. — You punch in the wrong code and get locked out, or leave the package at the wrong unit — a wrong-address delivery that can hurt your standing. One polite 'could you say that again?' would have fixed it in five seconds.
- Skipping the delivery photo because the customer said 'just leave it.' — Flex needs that photo as proof; without it the customer can claim it never arrived, and you have nothing to show. Always take the photo even when they wave you off — it protects you.
- Approaching a loose, aggressive dog or a dark unsafe yard to 'just finish the delivery.' — You risk a bite, a fall, or worse for a single package that isn't worth it. The rules explicitly let you return an undeliverable-safely package — returning it is the right call, not a failure. Force it and you can end up hurt with no support to blame but the choice to go in.
🔖 Quick reference
Who are you here for?
A guard or front-desk person asks this at a gated community or apartment lobby — they mean 'which resident are you visiting?' Answer with the unit number or last name on the package, not your own name. If you just say 'Amazon,' they'll often ask again, so lead with the apartment number.
Hi, I'm an Amazon delivery driver — I have a package for apartment 4B.
Your opening line at any gate or desk. Say your role and the destination in one breath so they can decide fast. Keep the tone friendly and matter-of-fact — you have a legitimate reason to be there. Swap '4B' for whatever the app shows.
Do you have authorization?
The guard is asking whether you're pre-cleared to enter — some buildings keep a list. You usually don't have formal 'authorization,' so don't bluff. Say you're delivering to a specific unit and ask them to buzz the resident or open the gate. If they still refuse, that's a case for the callbox or support, not an argument.
Could you buzz me in, or is there a gate code?
Use this at a locked entrance or callbox. You're giving the desk two easy options — press the button to release the door, or share a code — so they pick the fastest one. If they give a code, repeat it back before you hang up so you don't get stuck at the gate.
What's the code?
Over a callbox or intercom, the resident may ask you for a code — usually the last few digits of the tracking or order number the app shows, which proves the delivery is really theirs. If you don't see one, just say you're the Amazon driver with their package and ask them to let you in.
I'll leave it at your front door and take a photo.
The standard leave-at-door line. Flex requires a delivery photo, so you're telling the customer why you're photographing their doorstep — it's proof of delivery, not anything personal. Say it before you crouch to shoot so no one thinks you're taking a random picture of their home.
Just leave it at the door.
The customer or desk is telling you they don't need to sign or take it by hand — set it down and go. This is your cue to place it neatly, snap the photo, and mark it delivered. You still take the photo even when they say this; the app needs it.
I can sign for that.
At a front desk or from a resident, this means they're offering to accept and sign for a signature-required package. Good — hand them the phone or the slip and let them sign. Note who signed if the app asks; a doorman signing on the resident's behalf is normal and allowed.
This package needs a signature — could you sign here, please?
Use it only when the app flags the order as signature-required. Hold out the phone with the signature screen ready so the ask is obvious. If no adult is there to sign, you can't just leave it — follow the app's prompt to try again or return it, or you risk the delivery being reversed.
You're not on the list.
A guard says this to block you — your name or company isn't pre-cleared. Don't take it personally and don't push past. Calmly explain you're delivering to a specific unit and ask them to call the resident to authorize you. If the guard still won't let you in, that becomes a support / callbox situation.
No one's answering the callbox — could you let me in, please?
Say this to a guard or a resident walking by after the customer doesn't pick up. It's a polite ask, not a demand. But don't tailgate through a gate someone opens for themselves if they haven't agreed — if you truly can't get in, the honest move is to contact the customer or tell support.
There's an aggressive dog and no way to reach the door safely — I'm returning this package.
Say this to support (or note it in the app), calmly, when a loose barking dog, a dark unlit path, or any real hazard blocks the drop. Your safety comes first — you never have to enter an unsafe yard or get past a dog. Returning the package is the correct, approved outcome, not a failure on your part.
I can't get in and I can't reach the customer, so I can't complete this delivery.
Your closing line to support when the gate is locked, the callbox is dead, and no one answers. Report it plainly instead of leaving the package somewhere it isn't safe or authorized. Follow the app's next step (redeliver or return). Never toss a package over a gate just to mark it done.
Sorry, could you say that again?
Your rescue line when a guard's code, an apartment number, or a fast question over a crackly intercom slips past you. Asking once, politely, is completely normal and far safer than guessing a gate code or wrong unit. You can add 'a bit slower, please?' to get it clearly the second time.
Customer messages & calls
Most Flex stops need no talking at all — but a handful each day come with a message. Sometimes it's a live "Where's my package?" while you're two stops away; sometimes it's a note attached to the stop that you must read before you get out of the car. This chapter trains the eyes-and-ears skill: read the short English quickly, act on it correctly, and send a calm one-line reply. If messaging or calling the customer doesn't resolve the issue — a dispute, or no reply at all — take it to 'Driver support & appeals' next.
- 👂 You'll hear
Where's my package?
A live text or call: the customer is anxious and tracking you. It just means "give me an update." Reply that it's on the way — never promise an exact minute, because traffic and other stops can make you late.
- 👂 You'll hear
How long will it be?
Same worried customer asking for a time. The safe answer is a range or "soon," not a promise. If you really can't understand the message, use the meta-skill: "Sorry, could you say that again?"
- 👂 You'll hear
Just leave it at the door.
A clear instruction: don't wait, don't knock — set the package down at the door and go. "Just" here means "simply / no need to do more." Confirm you'll do it, then mark the delivery and take your photo.
- 👂 You'll hear
Leave it with my neighbor.
The customer wants the package handed to (or left at) a nearby unit, often named in the note (e.g. "unit 5"). If the neighbor isn't specified or doesn't answer, don't guess a random door — ask which one, or follow app rules.
- 👂 You'll hear
Leave at back door.
A short, abbreviated delivery note (words like "the" and "please" are dropped). It means: put the package at the BACK door, not the front. Walk around and find it; if you truly can't tell which door, ask before leaving it.
- 👂 You'll hear
Beware of dog.
A warning note, not a request: there is a dog on the property, so be careful — open gates slowly, watch for the animal, and stay safe. It does NOT mean the customer wants anything about the dog. If a dog blocks you, don't force it.
- 👂 You'll hear
Gate code 1234.
The number is the code to open the building or community gate — type it on the keypad to get in. The digits are just an example; use whatever number the note gives. If the code doesn't work, message the customer instead of skipping the delivery.
- 👂 You'll hear
Don't ring — baby sleeping.
A quiet-delivery note: do NOT ring the doorbell or knock. Set the package down softly and leave without a sound. "Baby sleeping" is the reason. Ignoring this and ringing anyway is a common cause of angry customers and low ratings.
- 🗣️ You say
It's on the way — I should be there soon.
The safe reassurance reply to "Where's my package?" or "How long?" It calms the customer without locking you to an exact time. "Should be" keeps it soft. Avoid a fixed number like "in 5 minutes."
- 🗣️ You say
I've left it at your front door.
Use this to report the drop is done. State the exact spot ("front door", "back door", "in the lobby") so the customer can find it. Pair it with the app photo. Being specific about the location prevents "I can't find it" complaints.
- 🗣️ You say
Got it — I'll leave it at the back door.
Use this to confirm you understood a note or instruction (repeat the key detail back). "Got it" = "understood." Reading the note back proves you read it correctly and reassures the customer. Then actually do exactly that.
- 🗣️ You say
Just to confirm — which door should I use?
The polite way to ask for clarification when a note is unclear (e.g. you can't tell which door is "back"). Asking is far better than guessing wrong. "Just to confirm" is a soft, professional opener. Wait for the reply before leaving the package.
🧠 Skills this builds
- Your rescue line whenever you don't catch a text or a phone reply. It's polite and completely normal — customers hear it from many people. Better to ask once than to guess wrong and deliver to the wrong spot.
🇺🇸 US workplace note
- American delivery texts are short and blunt — no greetings, dropped words ("leave at back door"), and abbreviations. That's normal, not rude. Your replies should be short and polite too: a few words plus "thanks" is plenty. Two golden rules: (1) reassure, don't over-promise — never give an exact minute; (2) when a note is unclear, ask before you act. A note is an instruction, not a suggestion — follow it exactly.
⚠️ Common mistakes
- Promising an exact time, e.g. "I'll be there in 5 minutes." — Traffic or the stops ahead make you late, and now the customer feels lied to — that turns a normal wait into a complaint or a low rating. Say "soon" or give a range instead.
- Ignoring a note like "Don't ring — baby sleeping" and ringing or knocking anyway. — You wake the baby, the customer is upset, and it often becomes an angry message plus a bad rating — all avoidable by reading the note first. The note IS the instruction.
- Guessing when a note is unclear and leaving the package at the wrong door without asking. — You mark it "delivered," but the customer can't find it — that can become a lost-package claim and hurts your standing. One quick "which door?" message prevents all of it.
🔖 Quick reference
Where's my package?
A live text or call: the customer is anxious and tracking you. It just means "give me an update." Reply that it's on the way — never promise an exact minute, because traffic and other stops can make you late.
How long will it be?
Same worried customer asking for a time. The safe answer is a range or "soon," not a promise. If you really can't understand the message, use the meta-skill: "Sorry, could you say that again?"
Just leave it at the door.
A clear instruction: don't wait, don't knock — set the package down at the door and go. "Just" here means "simply / no need to do more." Confirm you'll do it, then mark the delivery and take your photo.
Leave it with my neighbor.
The customer wants the package handed to (or left at) a nearby unit, often named in the note (e.g. "unit 5"). If the neighbor isn't specified or doesn't answer, don't guess a random door — ask which one, or follow app rules.
Leave at back door.
A short, abbreviated delivery note (words like "the" and "please" are dropped). It means: put the package at the BACK door, not the front. Walk around and find it; if you truly can't tell which door, ask before leaving it.
Beware of dog.
A warning note, not a request: there is a dog on the property, so be careful — open gates slowly, watch for the animal, and stay safe. It does NOT mean the customer wants anything about the dog. If a dog blocks you, don't force it.
Gate code 1234.
The number is the code to open the building or community gate — type it on the keypad to get in. The digits are just an example; use whatever number the note gives. If the code doesn't work, message the customer instead of skipping the delivery.
Don't ring — baby sleeping.
A quiet-delivery note: do NOT ring the doorbell or knock. Set the package down softly and leave without a sound. "Baby sleeping" is the reason. Ignoring this and ringing anyway is a common cause of angry customers and low ratings.
It's on the way — I should be there soon.
The safe reassurance reply to "Where's my package?" or "How long?" It calms the customer without locking you to an exact time. "Should be" keeps it soft. Avoid a fixed number like "in 5 minutes."
I've left it at your front door.
Use this to report the drop is done. State the exact spot ("front door", "back door", "in the lobby") so the customer can find it. Pair it with the app photo. Being specific about the location prevents "I can't find it" complaints.
Got it — I'll leave it at the back door.
Use this to confirm you understood a note or instruction (repeat the key detail back). "Got it" = "understood." Reading the note back proves you read it correctly and reassures the customer. Then actually do exactly that.
Just to confirm — which door should I use?
The polite way to ask for clarification when a note is unclear (e.g. you can't tell which door is "back"). Asking is far better than guessing wrong. "Just to confirm" is a soft, professional opener. Wait for the reply before leaving the package.
Sorry, could you say that again?
Your rescue line whenever you don't catch a text or a phone reply. It's polite and completely normal — customers hear it from many people. Better to ask once than to guess wrong and deliver to the wrong spot.
Driver support & appeals
Amazon Flex support is where a route goes from a small problem to a real threat to your income. A locked gate, a short pickup, a customer who falsely says 'not delivered,' a block cancelled after you already drove out, a standing drop you didn't cause, or a payment that never arrived — each one can cost you money or your account, and the person on the line often just 'documents' it instead of fixing it. This chapter gives you calm, factual English to report problems, defend yourself with evidence, and appeal — without getting angry and without admitting fault you don't owe. Support handles the day-to-day problems, but if something genuinely dangerous happens on the road — a breakdown, a crash, severe weather — that's 'Accidents & emergencies', and it can happen at any point in your shift.
- 👂 You'll hear
Can you confirm the address?
Support asks this to make sure you're at the right stop before they help. Read the street name and number back to them slowly and compare with your app. If you just say 'yes' without checking, the package can be logged to the wrong place and the problem lands on you.
- 👂 You'll hear
Return it to the station.
Support says this when a package can't be delivered and must go back to the delivery station. Ask them to note in your account that you returned it, and keep the return scan. If you keep it in your car or leave it somewhere, the system can flag it as a lost package and blame you.
- 👂 You'll hear
We've documented your report.
Support says this after you report a problem — it means they wrote it down, not that they fixed it. Don't hang up satisfied: ask directly, 'Will this be removed from my standing?' and get a reference number. Many drivers assume 'documented' means 'resolved' and later find the same mark still hurting their account.
- 👂 You'll hear
Can you send us the delivery photo?
During a 'not delivered' dispute, support may ask for the photo you took at drop-off. You can usually find it in your delivery history in the app — open it and describe what it shows (door, package, house number). This photo is your strongest evidence, so never rush a delivery without a clear photo.
- 👂 You'll hear
Your account is under review.
Support says this when a complaint or a drop in your standing has triggered a review of your account — this is stressful, but stay calm. Ask exactly what triggered the review and how long it takes. Getting angry or demanding won't speed it up; a calm, factual appeal with your evidence gives you the best chance.
- 👂 You'll hear
Can you describe what happened?
Support asks this to hear your side of an incident. Give a short, factual account in order: when, where, and what you did (for example, 'I arrived, the gate was locked, I called the customer twice'). Rambling or getting emotional makes it harder for them to help — keep it to the facts.
- 🗣️ You say
This stop won't let me mark it delivered.
Say this when the app won't let you complete a stop even though you're there. Listen for what support tells you next — they may ask you to confirm the address or to return the package. Don't just skip the stop and drive off; an uncompleted stop can show as an undelivered package on your record.
- 🗣️ You say
Five of the twelve packages are missing.
Say this at pickup when your scan or count comes up short (change the numbers to match your real count). Report it before you leave the station and ask them to note it. If you drive off without reporting a shortage, the missing packages can be counted against you as if you lost them.
- 🗣️ You say
My block was cancelled — what should I do?
Say this when a block is cancelled on you at the last minute or mid-route. Ask clearly whether you'll be paid for the part you already drove and what to do with any packages you have. Note: cancelling a block yourself can hurt your standing, so if Amazon cancelled it, make sure support records that it was not your cancellation.
- 🗣️ You say
I delivered it exactly as the note said.
Say this when a customer falsely claims 'not delivered' but you followed their drop-off note (for example, 'leave at back door'). State it calmly and offer the delivery photo as proof. Don't argue or raise your voice — an accusation feels unfair, but calm facts and your photo protect you far better than anger.
- 🗣️ You say
Could you check the delivery photo?
Say this to point support to the photo you took at drop-off — it's your evidence in a 'not delivered' dispute. Ask politely; a request works better than a demand. If you never mention the photo, support may just accept the customer's complaint and it counts against you.
- 🗣️ You say
This wasn't my fault — could you review my standing?
Say this when your standing dropped for something outside your control (a cancelled block, a false complaint, a system error). Ask for a review and give the specific reason it wasn't your fault. Never admit fault just to end the call — accepting blame you don't deserve can make the mark permanent.
- 🗣️ You say
Can you confirm I was paid for all my blocks?
Say this when a payment is missing or looks wrong. Have the dates and times of your blocks ready so support can look them up. Keep your own simple log of every block you work — without your own records, a missing payment is very hard to prove after the fact.
🧠 Skills this builds
- Use this any time support speaks too fast or you didn't catch something — it's polite and normal, and buys you time. Never say 'yes' to something you didn't understand: agreeing to the wrong instruction (like returning a package you should keep) creates a new problem. Ask them to repeat or slow down.
🇺🇸 US workplace note
- With Amazon support, calm and factual always beats loud and angry — reps document tone, and aggression can hurt your case. Treat the delivery photo as your main evidence and mention it early in any 'not delivered' dispute. Keep your own records: block dates and times, screenshots of cancellations, pickup counts. When you appeal, ask specifically for a 'review' and a reference number, and be honest — appeals don't always succeed, so state facts clearly rather than exaggerating. Never admit fault just to end an uncomfortable call.
⚠️ Common mistakes
- Getting angry or shouting at the support rep. — The rep documents your tone and may end the call; aggression rarely fixes the problem and can make your case look worse.
- Saying 'yes' or accepting fault just to end the call. — Admitting a mistake you didn't make can make a standing hit permanent and cost you future blocks.
- Hanging up as soon as support says 'we've documented it.' — 'Documented' is not 'resolved' — without asking for removal and a reference number, the same mark can keep hurting your account.
- Driving off after a short pickup without reporting the missing packages. — If you don't report the shortage at the station, the missing packages can be counted against you as lost.
- Not mentioning your delivery photo in a 'not delivered' dispute. — Without pointing support to the photo, they may simply accept the customer's complaint and it counts against you.
🔖 Quick reference
Can you confirm the address?
Support asks this to make sure you're at the right stop before they help. Read the street name and number back to them slowly and compare with your app. If you just say 'yes' without checking, the package can be logged to the wrong place and the problem lands on you.
Return it to the station.
Support says this when a package can't be delivered and must go back to the delivery station. Ask them to note in your account that you returned it, and keep the return scan. If you keep it in your car or leave it somewhere, the system can flag it as a lost package and blame you.
We've documented your report.
Support says this after you report a problem — it means they wrote it down, not that they fixed it. Don't hang up satisfied: ask directly, 'Will this be removed from my standing?' and get a reference number. Many drivers assume 'documented' means 'resolved' and later find the same mark still hurting their account.
Can you send us the delivery photo?
During a 'not delivered' dispute, support may ask for the photo you took at drop-off. You can usually find it in your delivery history in the app — open it and describe what it shows (door, package, house number). This photo is your strongest evidence, so never rush a delivery without a clear photo.
Your account is under review.
Support says this when a complaint or a drop in your standing has triggered a review of your account — this is stressful, but stay calm. Ask exactly what triggered the review and how long it takes. Getting angry or demanding won't speed it up; a calm, factual appeal with your evidence gives you the best chance.
Can you describe what happened?
Support asks this to hear your side of an incident. Give a short, factual account in order: when, where, and what you did (for example, 'I arrived, the gate was locked, I called the customer twice'). Rambling or getting emotional makes it harder for them to help — keep it to the facts.
This stop won't let me mark it delivered.
Say this when the app won't let you complete a stop even though you're there. Listen for what support tells you next — they may ask you to confirm the address or to return the package. Don't just skip the stop and drive off; an uncompleted stop can show as an undelivered package on your record.
Five of the twelve packages are missing.
Say this at pickup when your scan or count comes up short (change the numbers to match your real count). Report it before you leave the station and ask them to note it. If you drive off without reporting a shortage, the missing packages can be counted against you as if you lost them.
My block was cancelled — what should I do?
Say this when a block is cancelled on you at the last minute or mid-route. Ask clearly whether you'll be paid for the part you already drove and what to do with any packages you have. Note: cancelling a block yourself can hurt your standing, so if Amazon cancelled it, make sure support records that it was not your cancellation.
I delivered it exactly as the note said.
Say this when a customer falsely claims 'not delivered' but you followed their drop-off note (for example, 'leave at back door'). State it calmly and offer the delivery photo as proof. Don't argue or raise your voice — an accusation feels unfair, but calm facts and your photo protect you far better than anger.
Could you check the delivery photo?
Say this to point support to the photo you took at drop-off — it's your evidence in a 'not delivered' dispute. Ask politely; a request works better than a demand. If you never mention the photo, support may just accept the customer's complaint and it counts against you.
This wasn't my fault — could you review my standing?
Say this when your standing dropped for something outside your control (a cancelled block, a false complaint, a system error). Ask for a review and give the specific reason it wasn't your fault. Never admit fault just to end the call — accepting blame you don't deserve can make the mark permanent.
Can you confirm I was paid for all my blocks?
Say this when a payment is missing or looks wrong. Have the dates and times of your blocks ready so support can look them up. Keep your own simple log of every block you work — without your own records, a missing payment is very hard to prove after the fact.
Sorry, could you say that again?
Use this any time support speaks too fast or you didn't catch something — it's polite and normal, and buys you time. Never say 'yes' to something you didn't understand: agreeing to the wrong instruction (like returning a package you should keep) creates a new problem. Ask them to repeat or slow down.
Accidents & emergencies
Of every chapter in this pack, this is the one to know cold. Breakdowns, crashes, police stops, and severe weather are rare — but when one happens, there's no time to look up a phrase. One sentence you can't produce can turn a fender-bender into a real emergency. The skill here isn't fancy English; it's staying calm, saying the few right words in the right order, and knowing what comes first: safety, then 911 if anyone's hurt, then information. Drill these until they come out without thinking. Emergencies can happen at any point in your shift, not just at the end. Stay calm and follow the steps here first, then circle back to 'Driver support & appeals' to report what happened to the platform.
- 👂 You'll hear
911, what's your emergency?
This is the first thing the 911 dispatcher says when you call. Don't wait for a perfect sentence — answer in a few plain words: 'There's been a car accident.' If you freeze or hang up, help doesn't get sent. Speaking slowly and clearly matters more than grammar.
- 🗣️ You say
There's been an accident. No one's hurt.
Use this when you've been in a crash but everyone is okay. Say the situation first, then the injury status — the dispatcher needs both to decide what to send. If you skip 'No one's hurt,' they may send an ambulance you don't need. Keep it short and factual; don't apologize or explain who caused it.
- 🗣️ You say
Someone's hurt — we need an ambulance.
Use this the moment anyone is injured — you, the other driver, or a pedestrian. This is the most important line in the whole chapter: if someone is hurt, calling 911 for an ambulance comes before photos, before the app, before everything. Don't try to move an injured person yourself. Say it plainly and stay on the line.
- 👂 You'll hear
What's your location?
The dispatcher asks this so responders can find you — it's the one thing they can't help without. Read the street address off a nearby building, or give the two cross streets ('I'm on Main Street near 5th Avenue'). If you don't know, say what you see: a store name, a highway exit number. Don't just say the neighborhood.
- 🗣️ You say
Can I get your insurance and license, please?
Say this to the other driver after a crash to swap details — both of you need the other's insurance info to file a claim. It's a normal, expected step, not an accusation. Say it calmly. Show them yours too. If they refuse or try to leave, that's when you note their license plate and let the police handle it.
- 👂 You'll hear
Are you okay?
The other driver or a bystander asks this to check if you're hurt — it's not an admission of fault and it's not a trick. Answer honestly: 'I'm okay' or 'I think I'm hurt.' If you're shaken, it's fine to say 'Give me a second.' Don't answer 'It was your fault' — that's a different conversation you shouldn't start.
- 🗣️ You say
I'm going to take some photos for the record.
Say this before you start photographing the scene so the other driver knows you're documenting, not being aggressive. Photograph both vehicles, the damage, the plates, and the whole scene. Saying it out loud keeps things calm and makes it clear this is normal procedure. Do this after everyone's safe and 911 is called if needed.
- 🗣️ You say
I've been in an accident during a delivery.
Say this to Amazon support after you've handled safety and info exchange. It tells them your route is interrupted and starts their accident process. Have your delivery block details ready. Report the facts — where, what happened, whether anyone's hurt — but don't guess at fault. This protects you and pauses delivery expectations.
- 👂 You'll hear
Where are you located?
When your car can't be driven, you call a tow — to roadside assistance, your insurance line, or a tow company ('I need a tow truck') — and the dispatcher asks this to send a truck to you. Give the address, cross streets, or a landmark, plus which side of the road you're on and your car's make and color so the driver spots you. If you're on a highway, say the direction and the nearest exit. The clearer you are, the faster help arrives.
- 👂 You'll hear
License and registration, please.
A police officer says this at a stop. The safest response: keep your hands where the officer can see them, tell them where the documents are before reaching ('It's in the glove box'), then hand them over. Stay calm, don't argue, and don't reach suddenly. You can add that you're a delivery driver — but comply first, explain second.
- 🗣️ You say
I'm a delivery driver — I'll move my vehicle right away.
Use this when an officer or property staff says you can't park there or tells you to move. Identify yourself, agree, and move — don't argue that you're 'just dropping off a package.' A parking spot is never worth a confrontation. Say it, then actually move promptly. Being cooperative and quick is what keeps a small stop small.
- 🗣️ You say
It's not safe to drive in this snow — I'm heading back.
Say this to Amazon support when snow, flooding, ice, or extreme heat makes driving dangerous. You're allowed to stop for safety and return undelivered packages — no delivery is worth a crash. State the condition and your decision clearly. Support may ask you to return to the station; confirm you're doing so. Don't push through hoping it clears.
🧠 Skills this builds
- This is your single most important line under stress. When a 911 dispatcher, a police officer, or a tow dispatcher speaks fast and your mind goes blank, this buys you a repeat without panic. It's completely normal — native speakers use it too. You can also say 'Slower, please.' Never pretend you understood and guess; in an emergency a wrong answer sends help to the wrong place. Ask again, every time you need to.
🇺🇸 US workplace note
- 🔴 With police: keep your hands visible (on the wheel or where they can see them), stay calm, don't argue, and don't reach for anything without saying what you're doing first. Comply, then identify yourself as a delivery driver. Never drive away from a stop or a crash — leaving the scene is a serious offense and turns a minor situation into a criminal one. 🔴 At a crash: if anyone is hurt, call 911 for an ambulance before anything else. Exchange insurance and license info with the other driver, but do NOT admit fault at the scene — even a reflexive 'I'm sorry' can be used against you later. Just say 'Let's exchange information.' 🔴 In severe weather: you're allowed to stop and return packages for safety — Amazon expects it. No delivery is worth a crash. These are practical safety norms, not legal advice.
⚠️ Common mistakes
- Driving away from a crash or a police stop because you're nervous or don't want trouble. — Leaving the scene is a serious crime — far worse than the accident itself. It can mean arrest, license loss, and the end of your driving income. However scared you are, stay, and let the process happen calmly.
- Saying 'I'm sorry' or 'It was my fault' at the scene to smooth things over. — A reflexive apology can be treated as admitting fault and used against you by the other driver's insurer. Stay factual: check if everyone's okay, then say 'Let's exchange information.' Let the insurers decide fault later.
- Not calling 911 for an injury because you're worried about cost or your immigration status. — When someone is hurt, an ambulance is a life-or-death priority — 911 is for the emergency, not for checking papers, and dispatchers help everyone. Delaying the call to worry about anything else is the one mistake that can cost a life.
- Arguing with a police officer or refusing to move when told your parking isn't allowed. — Arguing escalates a routine stop and never wins you the parking spot. Comply, identify yourself as a delivery driver, and move right away. Calm cooperation keeps a two-minute stop from becoming a ticket, a tow, or worse.
🔖 Quick reference
911, what's your emergency?
This is the first thing the 911 dispatcher says when you call. Don't wait for a perfect sentence — answer in a few plain words: 'There's been a car accident.' If you freeze or hang up, help doesn't get sent. Speaking slowly and clearly matters more than grammar.
There's been an accident. No one's hurt.
Use this when you've been in a crash but everyone is okay. Say the situation first, then the injury status — the dispatcher needs both to decide what to send. If you skip 'No one's hurt,' they may send an ambulance you don't need. Keep it short and factual; don't apologize or explain who caused it.
Someone's hurt — we need an ambulance.
Use this the moment anyone is injured — you, the other driver, or a pedestrian. This is the most important line in the whole chapter: if someone is hurt, calling 911 for an ambulance comes before photos, before the app, before everything. Don't try to move an injured person yourself. Say it plainly and stay on the line.
What's your location?
The dispatcher asks this so responders can find you — it's the one thing they can't help without. Read the street address off a nearby building, or give the two cross streets ('I'm on Main Street near 5th Avenue'). If you don't know, say what you see: a store name, a highway exit number. Don't just say the neighborhood.
Can I get your insurance and license, please?
Say this to the other driver after a crash to swap details — both of you need the other's insurance info to file a claim. It's a normal, expected step, not an accusation. Say it calmly. Show them yours too. If they refuse or try to leave, that's when you note their license plate and let the police handle it.
Are you okay?
The other driver or a bystander asks this to check if you're hurt — it's not an admission of fault and it's not a trick. Answer honestly: 'I'm okay' or 'I think I'm hurt.' If you're shaken, it's fine to say 'Give me a second.' Don't answer 'It was your fault' — that's a different conversation you shouldn't start.
I'm going to take some photos for the record.
Say this before you start photographing the scene so the other driver knows you're documenting, not being aggressive. Photograph both vehicles, the damage, the plates, and the whole scene. Saying it out loud keeps things calm and makes it clear this is normal procedure. Do this after everyone's safe and 911 is called if needed.
I've been in an accident during a delivery.
Say this to Amazon support after you've handled safety and info exchange. It tells them your route is interrupted and starts their accident process. Have your delivery block details ready. Report the facts — where, what happened, whether anyone's hurt — but don't guess at fault. This protects you and pauses delivery expectations.
Where are you located?
When your car can't be driven, you call a tow — to roadside assistance, your insurance line, or a tow company ('I need a tow truck') — and the dispatcher asks this to send a truck to you. Give the address, cross streets, or a landmark, plus which side of the road you're on and your car's make and color so the driver spots you. If you're on a highway, say the direction and the nearest exit. The clearer you are, the faster help arrives.
License and registration, please.
A police officer says this at a stop. The safest response: keep your hands where the officer can see them, tell them where the documents are before reaching ('It's in the glove box'), then hand them over. Stay calm, don't argue, and don't reach suddenly. You can add that you're a delivery driver — but comply first, explain second.
I'm a delivery driver — I'll move my vehicle right away.
Use this when an officer or property staff says you can't park there or tells you to move. Identify yourself, agree, and move — don't argue that you're 'just dropping off a package.' A parking spot is never worth a confrontation. Say it, then actually move promptly. Being cooperative and quick is what keeps a small stop small.
It's not safe to drive in this snow — I'm heading back.
Say this to Amazon support when snow, flooding, ice, or extreme heat makes driving dangerous. You're allowed to stop for safety and return undelivered packages — no delivery is worth a crash. State the condition and your decision clearly. Support may ask you to return to the station; confirm you're doing so. Don't push through hoping it clears.
Sorry, could you say that again?
This is your single most important line under stress. When a 911 dispatcher, a police officer, or a tow dispatcher speaks fast and your mind goes blank, this buys you a repeat without panic. It's completely normal — native speakers use it too. You can also say 'Slower, please.' Never pretend you understood and guess; in an emergency a wrong answer sends help to the wrong place. Ask again, every time you need to.