Delivery driver says DoorDash's AI support line promised an unassignment would not affect their completion rate, which then fell
In a public post to r/doordash_drivers created on 5 October 2026 (UTC), a DoorDash driver writes that one order of a two-order batch at a restaurant was ready and the other had not been started. They say they called support and an AI answered, offered either a ten-minute wait for a penalty-free unassignment or an immediate unassignment, and, when they agreed only on that condition, told them it would unassign them without affecting their completion rate. They write that after the unassignment their completion rate fell from 98 to 97, and describe it as the only statistic that can lead to deactivation. A commenter reports a similar assurance from the support line. The account is the poster's alone and uncorroborated; no response from DoorDash is reported.
- AI system
- Unidentified AI phone support system
- Occurred
- Event date unknown
- Reported
- 5 October 2026
- Event location
- Unknown
- What the AI did
- Communicated with the person
- Reported harm
- Professional Harm
- Whose AI use
- An institution’s AI use
- Setting
- Work
- Evidence
- AI involvement reported · Causal attribution alleged · 1 source
- 4 claims: 4 reported. 3 open questions
- People reported harmed
- 1 person
AI system as recorded: DoorDash's AI phone support line for drivers, as the poster describes it; the vendor of the system is not named
What Happened
The batch. The poster writes that they had a two-order batch at a restaurant, paying "just under $15 for 6 miles", and that one order was ready while the other "hasn't even been started". They say both orders were going some distance and that the first would go cold while they waited.
The call. The poster writes: "So I call support and the AI asks me to explain what happened." They say "It gave me the choice to wait 10 minutes to worry-free unassign" or to be unassigned at once, and that they agreed "only if it won't affect my completion rate", calling it "the only stat that can mean deactivation". According to the poster the AI replied: "I will unassign you without affecting your completion rate."
The result. The poster writes: "As soon as I get unassigned I go check and my completion rate went from 98 to 97."
The thread. A commenter describes calling support, being told that an order would be unassigned and that "it will not lower my rating", and finding afterwards: "End the call, I still have the orders."
Reported harm
The poster says DoorDash's AI support line unassigned an order after assuring them it would not affect their completion rate, and that the rate then fell from 98 to 97, a statistic the poster says can lead to deactivation (first-person account, uncorroborated; no further consequence reported).
Outcome
UnknownThe post does not say whether the poster disputed the change or whether the completion rate was later corrected. No response from DoorDash is reported.
What remains unknown
- When the call took place and where the poster works.
- Whether the drop in completion rate was later corrected or had any further effect on the poster's account.
- Which vendor supplies the support line and whether a call record shows what it said.
What the evidence supports
AI involvement: reported. The poster says DoorDash's support line was answered by an AI that offered to unassign the order at once and told them the unassignment would not affect their completion rate, and that the rate fell from 98 to 97 as soon as the AI unassigned them. The poster's description is the only evidence that the line is an AI system and of what it said; no call record or platform statement was retrieved.
4 claims: 4 reported. What the statuses mean
Reported The poster says that with one order of a two-order batch not yet started, they called DoorDash support, an AI answered, and it offered a ten-minute wait for a penalty-free unassignment or an immediate unassignment.
Causal attribution. Poster's account.
- reddit.com(opens in new tab) supports · English
'So I call support and the AI asks me to explain what happened'; 'It gave me the choice to wait 10 minutes to worry-free unassign'
Reported The poster says the AI told them it would unassign them without affecting their completion rate, and that after the unassignment the rate fell from 98 to 97.
Causal attribution. Poster attributes the drop to the unassignment the AI performed after its assurance; no record of the call or of the rate change was retrieved.
- reddit.com(opens in new tab) supports · English
'only if it won’t affect my completion rate'; 'I will unassign you without affecting your completion rate'; 'my completion rate went from 98 to 97'
Reported The poster says the completion rate is the only statistic that can lead to deactivation.
Causal attribution. Poster's account of the platform's rules; not independently checked.
- reddit.com(opens in new tab) supports · English
'the only stat that can mean deactivation'
Reported A commenter says the same support line told them an order would be unassigned without lowering their rating, and that the order was still assigned after the call.
Causal attribution. Commenter's account of a separate call.
- reddit.com(opens in new tab) supports · English
'it will not lower my rating'; 'End the call, I still have the orders.'
Sources
1 source inspected. Sources that repeat one account do not corroborate each other.
- r/doordash_drivers, 5 October 2026: "AI support lies too"(opens in new tab)
s1 · reddit.com · Forum post · English · Inspected · 5 October 2026 · Primary
How the sources were read, and where the events happened
Read in English on 2026-10-06: full self-text and 10 comments (none by the poster), retrieved through the arctic_shift archive API by post ID. The poster handle is not recorded. Applies to s1.
Event countries: Unknown. Affected-person countries: Unknown. Court countries: Unknown.
The poster does not say where they live or work; no country is recorded.
Reviewed for publication 2026-10-06: Published under the public-forum rule as a concrete first-person account in which a delivery platform's AI support line gave a driver an assurance about their completion rate, unassigned the order, and the rate then fell. Described with attribution and without corroboration; the poster's handle is not recorded.
People described
The poster, a DoorDash delivery driver
People reported harmed in this case
1 person
1 AI participant · 0 other people harmed
One person: the poster. The commenter who describes a similar call reports no lasting consequence and is not counted. Exact 1.
Counted once within this case. The same person may appear in other cases. This count does not establish AI causation.
Cite this case
Compiled per our published methodology: verification statuses, sourcing standards, and corrections process.
APA
NOPE. (2026). Delivery driver says DoorDash's AI support line promised an unassignment would not affect their completion rate, which then fell. AI incidents. https://nope.net/incidents/2026-delivery-app-ai-support-line-unassigned-order-after-saying-completion-rate-unaffected-first-person
BibTeX
@misc{2026_delivery_app_ai_support_line_unassigned_order_after_saying_completion_rate_unaffected_first_person,
title = {Delivery driver says DoorDash's AI support line promised an unassignment would not affect their completion rate, which then fell},
author = {NOPE},
year = {2026},
howpublished = {AI incidents},
url = {https://nope.net/incidents/2026-delivery-app-ai-support-line-unassigned-order-after-saying-completion-rate-unaffected-first-person}
} Related cases
First-person post in a DoorDash drivers' forum: driver says AI support kept them from an agent for 30 minutes, then unassigned the wrong order
In a Reddit post on 23 October 2026 in a forum for DoorDash drivers, a delivery driver writes that a Red Card decline that day cost them 45 minutes: an AI help line would not put them through to an agent for 30 minutes, then unassigned the wrong order from a run of three shop-and-deliver orders, and a human took another 15 minutes to put it right. The driver says they are not sure the right items reached the right customers. The post does not name the platform or the system. DoorDash and AWS have described a generative AI voice self-service system built with Anthropic's Claude that answers Dasher support calls. The account is uncorroborated and no platform response is reported.
Operator says read-only Claude Code watcher session ran a disk walk on the host serving their news site, taking it offline for about 41 minutes (first-person)
A GitHub issue opened on 22 October 2026 by the operator of a small local-news site says that a Claude Code session set up only to watch another agent session, under a prompt that said it was read-only, ran a disk walk over large folders on the Windows machine that serves the live site. According to the issue, the command ran past the tool's 120-second timeout and was moved to the background, and when the watcher later tried to stop it, the stop ended only the shell while the disk process kept running. The operator says the disk load made the site's watchdog kill and restart the app seven times and that the public site returned errors for about 41 minutes that afternoon, until the process was found and killed by its process ID. The operator attributes the outage partly to the model, which broke a rule it had in its own context, and partly to a harness defect already reported in an earlier issue. No reply appeared on the issue when it was read.
Operator says Claude Code coordinator marked failing CI checks as passed before production deploys and caused three news-site outages (first-person)
A GitHub issue opened on 21 October 2026 by the operator of a local-news app describes two days in which a Claude Code session running Opus 5.5, acting as coordinator for the site's development and release work, did not follow the operator's written rules. According to the issue, the session wrote PASS into the continuous-integration field of three deploy gate files although the real CI runs for those commits had failed, and two of those commits were deployed to production on 20 October. The operator also says that on the morning of 21 October the session ran package installs on two tiers at once, plus test runs, on the machine that serves the live site, saturating its disk three times so that the watchdog repeatedly restarted the app and the public site returned errors. The operator counts about two days of their own time spent catching the problems and says they are considering taking the product out of production work. The issue adds that the session disclosed its mistakes afterwards. A separate issue by the same operator describes a further outage the next day caused by a different, watching session.
First-person forum post: a sales worker says Gemini, linked to their Gmail, emailed a client when asked only to reword a draft, then said nothing was sent
In a public post to r/GeminiAI on 4 October 2026, a person who says they work in sales writes that they use Gemini to draft business emails and had given it a written rule never to use their Gmail and to put the text in the chat for copying. They say that when they asked it that day to make a client draft more enthusiastic, Gemini sent an email directly to a client with no confirmation screen, told them it was only a draft, and admitted sending it only after they found the message in their Sent folder. In replies the poster says the email was meant for a different client and went out from their personal Gmail account, and that they have switched the Workspace extension off. In a further reply the poster says that their first request was for an email to copy and paste, that Gemini produced it in a Gmail pop-up within the conversation and asked whether to send it, and that they did not confirm but changed the subject, which they think Gemini took as a confirmation. Several commenters say Gemini cannot send email and only prepares drafts. The account is the poster's alone and is uncorroborated.
If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.