# `role`: a shared role inbox such as info@ or support@ rather than a person

The username is on the open list of role addresses. The inbox is shared, monitored unevenly, and rarely read by the person who filled in your form.

- Appears in: `reason`
- Verdict: risky
- Risk weight: +30
- Billing: 1 credit, like every deliverable or risky answer. Repeats of the same address are free for 7 days.

The local part matches the open role-address list (info, support, sales, admin, billing, noreply and around a thousand more), synced weekly. Role inboxes belong to a function rather than a person, get forwarded and filtered unpredictably, and carry higher complaint rates.

The mailbox is still probed, so mailbox_exists can be true for a role address; the verdict stays risky.

**What to do.** Accept role addresses on B2B forms where a shared inbox is expected, but keep them out of marketing sends and personalised sequences.

```json
{
    "email": "support@acme.com",
    "deliverable": "risky",
    "reason": "role",
    "role": true,
    "risk_score": 30
}
```

Reference: https://spaw.co/docs/reasons/role