What happened
On October 20, 2026, New York City’s Department of Consumer and Worker Protection (DCWP) announced proposed rules for automated customer service. This is neither a chatbot ban nor an already adopted law. The official docket says Proposed; comments are due November 19, with a public hearing scheduled that day.
What the proposal says
The proposed text calls for automation disclosure at the start, in the interaction’s language. Lack of a human-contact option would create a rebuttable presumption of a violation. It does not require instant, round-the-clock human service: when staff are unavailable or queues unreasonably long, alternative channels with stated hours or response times are permitted.
It also proposes at least three years of machine-readable compliance records, including interaction logs. This is not equivalent to requiring complete transcripts of every conversation.
Who should care
Small businesses offering automated customer support. The legal context is New York City; applicability to a particular company, including a cross-border business, requires separate legal assessment. The proposal creates no new general obligation for Ukrainian businesses.
Nadali’s practical takeaway: review not only the quality of a bot’s answers, but whether customers can actually obtain help when automation fails.
What to review in your workflow
These are editorial recommendations, not a statement of current legal duties:
- Follow the customer journey with a difficult request the bot should not resolve alone.
- Check where a request for a person goes, who sees it and who answers.
- Compare promised support hours and response times with how the team actually works.
- Do not collect extra personal data just because of this news. Align log content and retention with your legal and security requirements.
Illustrative example: a hotel bot cannot understand a request to correct a booking. A useful check is whether it routes the request to a responsible employee instead of returning the guest to the same menu. This is not a tested business case.
Verification limits
We read the official proposal and announcement, but did not assess applicability to individual businesses or test support systems. These materials do not establish an effective date.
Author: Nadali. Prepared with AI. Sources checked on October 22, 2026.
Cover: an original conceptual AI-generated illustration for Nadali, not an event photograph or evidence of testing.
