Role-based email detection

Role-based addresses such as info@ and sales@ reach a function, not a person. Understand the risks and how Kawaa flags them.

What are role-based emails?

Role-based emails are associated with a function or department rather than an individual. Examples include:

• info@company.com
• support@company.com
• sales@company.com
• admin@company.com
• contact@company.com
• webmaster@company.com

Risks of sending to role-based addresses

• Multiple recipients - May forward to many people
• Higher complaint rates - More likely to be marked as spam
• Lower engagement - Often monitored infrequently
• Consent is hard to show - Not everyone who reads a shared inbox signed up for your mail

Best practices

• Exclude role-based emails from marketing campaigns
• Only send to role addresses for transactional/support purposes
• If you must include them, set expectations for lower engagement

API response

A role address is reported with a top-level status of role and the boolean data.flags.role_account. The response does not name which role it matched. Branch on the local part yourself if you need that.

{
  "success": true,
  "data": {
    "email": "support@company.com",
    "status": "role",
    "quality_score": 70,
    "flags": {
      "disposable": false,
      "role_account": true,
      "free_provider": false
    }
  }
}