# `reported_abuse_widely` (phone): three or more accounts reported abuse for the number

The Spaw phone risk signal reported_abuse_widely adds 40 points to risk_score when 3 or more Spaw accounts reported abuse for the number through the phone feedback endpoint within the last 30 days (dataset delivery-feedback).

- Weight: +40
- Dataset: `delivery-feedback`
- Read from: no field of its own
- Default SMS policy: blocks it: reported_abuse_widely is one of the default block_signals (fictional, disposable, reported_abuse, reported_abuse_widely, premium_rate).

It is the only phone signal built from other accounts' reports, and only a count is ever read: how many distinct accounts filed an abused report for the number inside the window. Nothing about which accounts, what they sent or what else they reported reaches your answer. The dataset is delivery-feedback.

Only reports an account's own systems filed through the API count toward it; an abused report typed into the dashboard feeds that account's own reported_abuse but not this count. A monitored phone list flags a number when it starts carrying this signal.

**What it cannot tell you.**

- It is not a verdict on the subscriber: accounts report what their own systems observed, Spaw does not verify the reports, and a number can be reported in error.
- It needs 3 accounts within 30 days, so a number abused against one or two accounts never reaches it.

**What to do.** Refuse it where a verification code or an account depends on the number. The default SMS policy blocks on it: an answer carrying it is ok_to_send false whatever the score.

The SMS policy is set per account with `PUT /api/v1/phone/policy` (https://spaw.co/docs/api/update-phone-policy) or the dashboard's SMS policy tab, and its `block_signals` may list any signal, this one included.

An excerpt of an answer carrying this signal alone, with the number and the other fields left out, because no test number answers it. The score and the decision are worked out as the lookup and the default SMS policy work them out.

```json
{
    "valid": true,
    "country": "GB",
    "line_type": "mobile",
    "line_type_source": "numbering_plan",
    "risk_score": 40,
    "risk_level": "medium",
    "risk_signals": [
        {
            "signal": "reported_abuse_widely",
            "weight": 40,
            "dataset": "delivery-feedback"
        }
    ],
    "ok_to_send": false,
    "blocked_by": "reported_abuse_widely"
}
```

Related:

- [`reported_abuse`](https://spaw.co/docs/signals/phone/reported_abuse): your own account reported abuse for the number
- [`reported_undelivered`](https://spaw.co/docs/signals/phone/reported_undelivered): your own latest report for the number was a failed delivery
- [The weights table in the phone guide](https://spaw.co/docs/phone-intelligence#signal-reported_abuse_widely)
- [POST /api/v1/phone/feedback reference](https://spaw.co/docs/api/report-phone-feedback)
- [Glossary: SMS policy](https://spaw.co/glossary/sms-policy)

Reference: https://spaw.co/docs/signals/phone/reported_abuse_widely