What if someone keeps scanning or spamming notices?

Most scans are real move requests. A few become repeat messages, off-topic notes, or harassment. Here is what CarWhoWa already limits, and what owners can do.

What the system throttles

For the same vehicle and the same visitor identity (for example device signals or IP), sending is rate-limited. Exact limits follow service settings. When limited, the system usually stops hammering you with pushes and does not keep burning quota for no reason. Under contact rules, the page may also show the contact phone so the visitor can call instead of flooding text.

A vehicle also has a concurrent session cap. Opening or rejoining a session does not spend quota. One notice is charged when a stranger’s inbound message is successfully pushed to you. Your replies on the web, LINE, or Telegram do not spend that notice quota.

Sessions close after an idle period (exact minutes follow the service). If the visitor still needs contact after that, they continue through the page flow again—idle threads do not run forever.

These controls cut short spam bursts. They cannot guarantee zero abuse if someone switches devices or networks.

What you can do right away

Pause receive on that vehicle in the owner site if you need quiet now. Visitors see a generic “temporarily unreachable” style message; the real reason is not exposed.

If a sticker was photographed or the old code should die, reissue the QR. The old code stops working; reprint and replace the sticker yourself. Reissue is part of the owner flow—there is no separate “reissue fee”; plan and quota rules still follow your subscription.

Report clear abuse in-product so ops can review. Ops may restrict visitors or disable a vehicle QR or account when needed. You see scan counts for your vehicles, not scan detail—that is intentional.

If quota is burning

First check whether many real move requests stacked up, then pause, reissue, or report. When quota is empty, notice pushes pause and the page shows the contact phone so callers can dial. See when message quota runs out.

When to escalate

Threats, stalking, sexual harassment, or crime signs: keep the thread and contact police or the right authority. The move-notice page is not an emergency line.

For tone and clearer move requests, see how to write a move notice. Privacy basics: parking contact and personal data.

Decide abuse vs busy parking days

Look at message content, timing clusters, and sudden scan spikes. Real needs are short and specific; abuse often repeats, is empty, or is unrelated to parking.

Threats deserve records and police where needed. Flooding deserves pause + reissue + report. Unclear cases: pause receive for a few hours, watch, and self-test the sticker and notices.

Do not argue in-thread or add more personal data. If needed, reply once that you cannot help with non-parking matters, then report or call the authorities.

Prevention extras

Do not add phone numbers, home addresses, or personal social accounts on the parking card. Do not post the QR as a permanent public contact channel.

Fleet vehicles need someone who actually receives notices. Quiet codes only burn quota and create complaints. When staff change, re-check pause and reissue status.

Abuse cannot hit zero, but you can raise the cost and shorten how long it lasts. Rate limits first, pause and reissue second, report and police third—in that order, not by arguing in the chat.