+39 379 368 2435
Dublin 8, Ireland
Amazon delivery accounts

Amazon driver appeal: what to send and how to explain it

Put the message, the dates and the useful screenshots in one place. You can then explain the problem without sending a long, confusing story.

September 27, 2026 • 3 min
Editorial Review

This public guidance is maintained against Northline's case-review methodology.

About the methodology
Written by
Michele Corvo
Published
September 27, 2026
Updated
September 27, 2026

Start an Amazon driver appeal with the message about your account. Save it, note the date and check what you are being asked to explain. Then gather the few records that help answer that question. A clear explanation is easier to follow when each attachment has a purpose.

If you are unsure whether your account is Flex, Relay or DSP-related, check the program guide first. It will help you work out who needs to receive the information.

1. Keep the whole message

Save the full email or take screenshots that include the full app message. Keep the date, case number and any instructions about a review. A cropped line saying your account is blocked may leave out the reason or deadline.

For a Relay driver, ask the carrier to check what appears in its account too. For a DSP driver, keep the employer’s message as well as any Amazon notice. You may need both to understand what happened.

2. Write down what happened, in order

Use short lines with dates and times. Include the block or load number if you have it. Say what happened, what you did next and when you contacted support.

Example of a useful timeline

8:20 a.m.: arrived at the pickup site. 8:23 a.m.: the app showed a check-in error. 8:25 a.m.: called support. This is an example only. Use your actual times and say when you are unsure.

Save anything that supports those times. A call log shows when you called; a support message may also show what you were told. If you only remember a conversation, describe it as your recollection.

3. Choose the attachments that explain the problem

  • Missed block: the booking, cancellation confirmation or check-in error.
  • Delivery issue: the delivery details, support message and return confirmation, where relevant.
  • Selfie or ID check: the error message and the driver status shown in the account.
  • Carrier insurance: the policy dates, company name and the document named in the notice.

Keep the original files. If you add an arrow or note to a screenshot, save that as a separate copy. Use simple file names so the reader can find the attachment mentioned in your message.

You do not need to send unrelated customer details or a large folder of personal documents. Start with what explains the event and what the notice asks for.

4. Save every earlier appeal and reply

Keep all appeals exactly as you sent them, including the attachments and Amazon’s replies. Put them in date order. This lets you see what has already been explained and what is still unanswered.

If an earlier message gave the wrong date or left something out, correct it clearly. If you cannot find a submission, say it is missing. Do not recreate it from memory and present it as the original.

5. Make the request easy to understand

Open with the decision you want reviewed. Explain the event, point to the useful attachment and ask for a specific action. You might be asking Amazon to check a cancellation time, review a failed selfie or explain the reason for the block.

Before sending, check the latest instructions, the recipient and any deadline. Keep a copy of what you submit and the acknowledgment you receive.

For help with the wording, continue to the Flex appeal guide or Relay driver guide. Company account problems are covered in the carrier guide; DSP drivers should start with the employer questions.

Recommended case page

For case-specific help, start with Amazon Flex, Relay or DSP: who should you contact?.

Open Amazon Flex, Relay or DSP: who should you contact?
Related case pages

Review these only if the evidence points to a different issue.