A deactivation notice can feel abrupt and frightening when you rely on the app for income. Pause, save the notice and deal with the stated reason first.
Deactivation can feel immediate: access disappears, deliveries stop and the explanation may be short. The first task is not to argue with every possibility. It is to preserve the notice and the records needed for a focused appeal.
Dashers are generally engaged as independent contractors, but classification law and platform rights can vary by state and contract. A deactivation is not automatically unlawful. It may still be worth checking whether the stated reason matches the delivery record, whether an appeal route exists and whether the platform received relevant evidence.
Save the deactivation notice, appeal confirmation, delivery history, ratings or completion data, screenshots of relevant orders, customer-support messages and any safety or identity-verification correspondence. Keep personal customer information out of your file unless it is necessary and you are authorized to retain it.
Question | Document to preserve |
|---|---|
What reason was given? | Notice and policy link |
What happened on the relevant delivery? | Offer, route and support messages |
Was an appeal sent? | Submission confirmation and reply |
Write a narrow appeal that answers the stated concern with dates and records. Do not invent facts or send material that is not relevant. If the issue affects income, keep an earnings snapshot as well.
Caira can build an appeal checklist from the notice and screenshots. It cannot promise account reinstatement.
Example: a deactivation after a disputed delivery
A Dasher is deactivated after a customer complaint about a delivery that was left at the address shown in the app. The Dasher has a delivery photo, support messages and a map screen, but waits two weeks before appealing. The records may still help, yet an early, focused appeal is usually easier to assess than a long account built from memory.
A practical next move
Save the notice before the account screen changes.
Keep the order, route and support records tied to the stated event.
Check the appeal deadline and submit one concise explanation.
Retain the confirmation and case number.
An appeal should answer the reason given. It should not include unrelated customer data or speculation.
Appeal the stated event first
If the notice concerns a delivery, organize the appeal around that order: date, instructions, delivery record and support case. Do not include customer addresses or unnecessary personal information in a public post or broad email.
A five-line factual account of a claimed non-delivery is usually more useful than a long account of prior ratings. Preserve the near-term appeal deadline first; classification or local-rule questions can be considered on their own track.
Keep the next conversation narrow
When a workplace record is messy, a broad accusation can make it harder to get a useful answer. Lead with the small set of facts that can be checked now. Ask for the reason and deadline in the notice. Then ask for the trip-specific in-app evidence. Finally, confirm the confirmation that the appeal was received.
That sequence does not concede the wider issue. It simply makes the first response measurable. Save a copy of the question, the reply and any attachment. If the answer changes later, the record will show exactly what was said and when.
Use dates and job details, not conclusions.
Keep originals before annotating copies.
Escalate urgent health or safety risks promptly.
This guide is general information, not legal, financial, medical or tax advice.
