EN
NeervoX / Blog / WhatsApp and SMS share the same legal contact quota as calls

WhatsApp and SMS share the same legal contact quota as calls

August 25, 20263 min read

Adding WhatsApp to a collections operation looks like pure upside: another channel, more reach. But if the system counts that quota separately from calls, it exposes you without anyone noticing.

In short

  • The contact limit per debtor adds up every channel.
  • Calls, SMS and WhatsApp share the same quota.
  • A system that counts them separately breaks the rule believing it complies.
  • The quota is checked before sending, not in the report.

The error that raises no error

Most WhatsApp integrations in collections are built as a separate module: its own inbox, its own log, its own rules. It works fine and nobody complains.

The problem shows up in the counting. If the debtor received three calls and the WhatsApp module does not know about them, it will send its own messages as if the quota were untouched. The total goes over the limit and no system flags it, because each one is within its own cap.

The contact quota under Chile's Law 21.320 is per debtor, not per channel. It is the same bucket for calls, SMS and WhatsApp.

How it should be counted

The counter has to live on the customer, not on the channel:

One debtor's quota in the period

Calls made2
SMS sent1
WhatsApp sent1
Quota consumed4

And the check happens before sending. If it happens when building the report, the contact already went out: the report only documents the breach.

The other rules that are shared too

The other side: the conversation breaks

Beyond compliance, keeping channels separate breaks the experience. The customer replies on WhatsApp to the call they did not answer, and that message lands in a different inbox, maybe with a different person, without the context of the phone conversation.

With channels joined, the agent sees a single thread in the customer record, no matter where each message came in. The conversation changes medium, it does not start over.

1quota shared across channels
1thread per customer, not one per channel
0alerts when it is counted wrong

How to audit yours

  1. Take a debtor and use up their quota mixing calls and WhatsApp.
  2. Try one more contact. Does the system block it?
  3. Mark someone as "do not contact" and try sending them a WhatsApp.
  4. Schedule a send outside legal hours. Does it go out anyway?

If any test fails, it is not a discipline problem in your team. It is a system problem.

This article describes how we implement these rules. It is not legal advice.

Frequently asked questions

Do collections WhatsApp messages count toward the legal contact limit?

Yes. The contact quota per debtor adds up every channel: calls, SMS and WhatsApp share the same cap. Counting them separately can push you over the limit without the system noticing.

Can a collections WhatsApp be sent outside permitted hours?

No. Restrictions on hours and holidays apply to collections contact, not only to phone calls.

What happens when a debtor asks not to be contacted?

They are excluded from every channel permanently, not just the phone, and that exclusion has to survive the next list uploads.

Omnichannel with the quota counted right

Try it for 2 weeks with your real campaigns and review the contact log per debtor.

Start my free trial

2 weeks · no card · no contract · we help you set it up

Keep reading