Our spam-risk read is powered by a community sensor: verified accounts and a key-gated reporting API contribute supplementary, advisory signals about numbers. We designed it so the signal is useful and hard to game — reports are weighted by credibility, kept private, and always open to dispute.
You already field unknown callers all day. Flag the bad ones and you make the read better for everyone — and the more you contribute, the more reporting capacity you earn. Verifying a business number raises your limits, weights your reports more, and lets you enrol your own numbers so spoofed calls reported against you are shielded from your read. Give a little signal, get a lot back.
A community report is a supplementary, advisory signal — never an accusation, a verdict, or proof that a particular call happened. A verified account picks the tags that fit a number, and that contribution feeds the number’s community spam-risk read alongside usage patterns and other inputs. The read is informational only, kept human-in-the-loop, and it is never the sole reason anyone is denied a product, service, or opportunity. If a report is wrong, it can be disputed and corrected.
Reports flow in two lanes. Accounts with a verified business number report in the accountable lane: their reports are reporter-weighted and build credibility over time, because there is a known, accountable identity behind them. Free and personal accounts report in the crowd lane: a bounded, deferring, credibility-firewalled signal. The crowd lane can nudge a cold, unknown number, but it cannot sink a verified number on its own — the model is deliberately asymmetric so that a flood of low-cost reports can never overwhelm an established, accountable number.
Every reporter has a private credibility weighting that decides how much a report counts. It is derived from internal signals — account standing, corroboration with other accounts, and similar — and it is recomputed as accounts report over time. We use it to keep reporting fair and to resist abuse and Sybil attacks. Credibility is never shown publicly, and a number’s report surfaces at most a tag and an aggregated count — never the identity of a personal reporter.
The sensor is built to be useful without exposing people. We never publish raw phone numbers, and a verified individual’s name is never put on display. Reporter identities — especially in the crowd lane — stay private. On the reporting API a report is tags-only, with no free-text body, so personal details and unverified claims stay out of the programmatic path by construction. A person reporting on the website can add a short, length-capped note about the call — it stays human-moderated and open to dispute. What surfaces publicly is an aggregated, advisory read, not a dossier.
Spammers often forge a real business’s number as the caller ID. When a business enrols its own number and runs the pre-call check before placing calls, we can tell whether a reported call actually originated from the real owner. If the evidence says it did not — the hallmark of a spoofed call — that report is treated as a supplementary signal about the spoofing and withheld from the genuine owner’s read and from public listings, rather than penalising the very business whose identity was forged. It is corroboration-gated and always hedged: we never claim certainty, only that a reported call is unlikely to have been the owner’s. This is disclosed in our Privacy and Terms, and integrators can wire it up from the integrations page.
The sensor is give-to-get: verified accounts that contribute reports help everyone get a better read, and they get more capacity in return. Verifying a business number raises an account’s reporting limits and weights its reports more in the community read. Developers can report programmatically through the key-gated reporting API using a single-use receipt from a prior lookup — the receipt is an anti-replay nonce and rate control, not proof a call occurred. See the API docs for the full request shape.
Reports are submitted in good faith, but people make mistakes — so every report can be challenged. If a number you own is reported, you can dispute it and request a correction, and we give the people behind every number a fair way to be heard. The community signal exists to fight fraud and help good calls get through, not to brand anyone.
A report is a supplementary, advisory signal — a verified account flags a number with one or more tags (for example, robocall) so the community read can reflect it. It is never an accusation, a verdict, or proof that any particular call happened. There is a human in the loop and every report can be disputed.
Accounts with a verified business number report in the accountable lane — their reports are reporter-weighted and build credibility over time. Free and personal accounts report in the crowd lane — a bounded, deferring signal that can nudge a cold unknown number but cannot sink a verified number on its own.
Reporter credibility is a private, internal weighting that decides how much a report influences the community read. It is derived from signals like account standing and corroboration with other accounts. It is used to keep reporting fair and resist abuse — it is never shown publicly, and a number’s report surfaces at most a tag and an aggregated count, never the reporter’s identity for personal reporters.
No. Crowd-lane reports are bounded and deferring by design, and reporter credibility weights each one. The community signal can sway a cold, unknown number, but it cannot on its own sink a number that has a verified business behind it.
You can dispute it. Reports are submitted in good faith but people make mistakes, so every report can be challenged and a number’s owner can request a review. The community read is advisory and informational, never the sole reason anyone is denied a product, service, or opportunity.
Spoofing forges a real number as the caller ID. If you enrol your business number and run the pre-call check before you dial, we can tell when a reported call did not actually originate from you — the signature of a spoofed call. Those reports are then treated as a supplementary signal about the spoofing and withheld from your own read and from public listings, so the business whose identity was forged is not the one penalised. It is corroboration-gated and always hedged — we never claim certainty.