Picture the Monday-morning strategy meeting on a collections floor in Queens. The ops lead has the dialer report up on the screen, the compliance officer has a printout of the new rule, and someone has circled September 1 on the wall calendar in red. For five years, the floor has run on Regulation F's arithmetic: seven call attempts per account per week, with emails and texts riding along uncounted. Starting September 1, 2026, for New York City consumers, that arithmetic is gone. Three attempts. Per week. Calls, emails, and texts combined. Nobody in that meeting is debating whether it's fair — they're debating which three.

From presumption to hard cap: what the SHIELD Rule actually says

On February 26, 2026, New York City's Department of Consumer and Worker Protection adopted the SHIELD Rule — Stopping Harassment and Intimidation and Ensuring Lawful Debt Collection — which takes effect September 1, 2026. Its headline provision limits debt collectors to three contact attempts within any seven-day period, counted across telephone calls, emails, and text messages together.

If you run NYC accounts, it's worth being precise about how different this is from the federal baseline. Regulation F never set a hard ceiling. It created a rebuttable presumption of a violation at seven call attempts in seven days — calls only, with no numerical limit on emails or texts at all — and left collectors room to argue the facts and circumstances. The SHIELD Rule deletes that flexibility. It's a bright line, and it counts every channel. On New York City accounts, contact frequency stops being a risk-balancing judgment call and becomes a hard operational constraint.

Two more things worth flagging before you recalibrate the dialer. First, the rule reaches further than the old DCWP rules: original creditors — including hospitals and financial institutions collecting their own debt — are covered in certain situations, such as after they've charged off, accelerated the debt, or stopped sending statements. Second, this is a summary written by a software company, not legal advice; the effective date is close enough that your compliance counsel should be reading the rule text itself, not blog posts about it.

The math of three attempts

Don't take our word for how much this tightens things — run your own numbers. Pull last month's activity for your NYC portfolio and compute one figure: total outreach attempts (calls, emails, and texts) divided by right-party contacts. That's your attempts-per-conversation rate. Now imagine buying those conversations on a budget of three attempts per account per week.

Under the old math, an attempt was cheap. If a Tuesday-morning call hit voicemail, you tried Thursday evening, then Saturday, and emailed in between — the strategy could afford to search for the right time of day. Under a 3-in-7 cap, every attempt you spend finding the consumer is an attempt you can't spend talking to them. A wasted touch is no longer a rounding error; it's a third of your week. And the waste is easy to name:

  • A call to a number that hasn't been re-verified since the account was placed.
  • A call at an hour when this consumer has never once picked up.
  • An email into an inbox that has never opened one.
  • A voicemail that gives the consumer nothing they can act on at 9 PM when they finally hear it.

The operators who come out of September ahead won't be the ones who dial fastest. They'll be the ones whose three attempts each carry a working phone number's worth of intelligence: right channel, right time, and a clear path for the consumer to respond on their own schedule.

The rest of the rule is an operations problem too

The contact cap gets the headlines, but two quieter provisions may bend your workflows more.

Consumers can now dispute a debt or request verification at any point in the collection process, through any channel they've been using with you — not just in writing within the 30-day validation window that federal law emphasizes. Operationally, that means a dispute can arrive as a text reply at 11 PM on a Sunday, and it counts. Every channel you use for outreach becomes a channel you're obligated to monitor for intake.

And once a dispute or verification request lands, the clock starts: collectors must produce documentation supporting the debt within 60 days — a default judgment alone doesn't cut it — or send a Notice of Unverified Debt. After that, third-party collectors and debt buyers lose the ability to collect on that account. Medical debt gets additional protections on top, including a requirement that collectors working hospital debt inform consumers about the facility's financial assistance policy throughout the collection process.

The DCWP's stated reason for all this is telling: in its announcement, the agency noted that complaints from NYC consumers about excessive collector contact have risen every year since Regulation F took effect in 2021 — more than tripling between the 2021 and 2024 measurement periods. Regulators read that as an industry that used the presumption as a target rather than a ceiling. Whatever you think of that reading, the era of treating outreach volume as the growth lever is ending in the country's largest collections market — and municipal rules have a habit of traveling.

When outbound is capped, inbound is the strategy

Here's the asymmetry the strategy meeting should actually be about: the SHIELD Rule caps how often you can reach the consumer. It says nothing about how often the consumer can reach you.

Every touch you're still allowed — the letter, the one well-timed call, the single email — points somewhere: a phone number, a link, a QR code. If that phone number rings into a queue staffed 9 to 5, Monday to Friday, then you spent one of your three weekly attempts to generate a callback that no one answered. You can't re-dial the miss until next week. The consumer who finally worked up the resolve to deal with the account at 9:40 PM got hold music, and their resolve doesn't keep.

Under a contact cap, the highest-leverage investment isn't a smarter dialer — it's making sure that every inbound response gets answered instantly, resolved completely, and logged properly, at any hour. That's what an AI agent built for collections does on both sides of the line: voice agents that answer the callback in one ring, verify identity, discuss the account within your compliance rules, and take a payment or set a plan at midnight; chat agents behind the QR code on the letter that do the same silently, in the consumer's language — no small thing in a city where residents speak more than a hundred of them. And because SHIELD-style dispute rights mean a dispute can arrive through any channel at any time, an agent that recognizes dispute language, logs it, and routes it to your compliance queue turns a monitoring obligation into a workflow instead of a liability.

None of this is about replacing your collectors. It's about what their calls are for. When you only get three touches, human attempts are too scarce to spend on voicemail tag — they should go to accounts where a negotiation is actually live, while the always-on channels harvest the responses your letters and calls generate.

Start small, and measure it before September

You have until September 1. That's enough time to run a real experiment instead of a fire drill. Take your NYC placements — or even just the after-hours window on them — and put an always-answered inbound channel behind your existing outreach: a dedicated number your letters and voicemails point to, a chat link in your emails. Change nothing else. Then, after a month, count three things: inbound contacts you would previously have missed, resolutions per outreach attempt, and disputes captured cleanly at intake. Compare that against what the coverage costs — the pricing is published, so that comparison takes minutes, not a procurement cycle.

If the numbers don't move, you turn it off and you've spent a month learning something about your portfolio. If they do move — and rationed outbound has a way of making unanswered inbound expensive fast — you'll walk into September 1 with a call strategy built for three attempts, measured on your own accounts, instead of a dialer schedule with four-sevenths of it crossed out. Setting up the first agent takes minutes; the rule change took the DCWP two years. Use the gap.

V

Verlingo

AI voice & chat agents, in production

Field notes from the front lines - phone calls and chat windows, collections floors and front desks. We build the agents, run them in production, and write down what works.