TL;DR: Email Productivity customers see an average 11% inbox volume reduction, with executives recovering 34+ hours a month and Fasken reporting 4,700+ hours saved in 90 days, according to Abnormal AI, but native email tools still lack org-wide enforcement and admin visibility. The real issue is not detection alone, but whether identity-aware filtering can be measured, governed, and trusted at scale.
NHIMG editorial — based on content published by Abnormal AI: Key Insights on graymail filtering and email productivity
By the numbers:
- Abnormal Email Productivity customers see an average 11% reduction in inbox email volume after deployment.
- Executives averaging 480+ fewer graymail messages per month.
- Fasken recovered more than 4,700 hours of employee time in the first 90 days after deployment.
Questions worth separating out
Q: How should teams govern graymail filtering in enterprise email?
A: Treat graymail filtering as a governed identity-control problem, not a mailbox preference.
Q: Why do native email tools fail to solve graymail at scale?
A: Native tools usually classify bulk mail at the tenant level, so they cannot account for individual reading patterns or team-specific relevance.
Q: What should security teams measure to know if graymail controls are working?
A: Measure inbox volume reduction, the share of messages routed as graymail, the roles most affected, and the time recovered.
Practitioner guidance
- Audit graymail as a productivity control, not a user complaint. Measure inbox volume, promotional message share, and time lost by role or team before deciding whether the current filtering stack is adequate.
- Test whether inbox controls are centrally enforceable. Check whether the organisation can apply the control across all mailboxes without relying on individual opt-in or local client settings.
- Require reporting before you accept filtering claims. Ask for dashboard-level visibility into graymail volume, affected users, top senders, and time saved so the programme can be reviewed like any other identity or access control.
What's in the full article
Abnormal AI's full analysis covers the operational detail this post intentionally leaves for the source:
- Behavioral modelling approach used to distinguish relevant mail from low-value mail at the individual user level
- How graymail routes into Outlook and Gmail native folders without changing the employee workflow
- Dashboard metrics for graymail volume, commonly seen senders, and time saved across the organisation
- Customer-level productivity impact details from Fasken's deployment and executive time recovery
👉 Read Abnormal AI's analysis of why native email tools struggle with graymail →
Graymail filtering in enterprise email: what IAM teams need to know?
Explore further
Graymail is an identity-specific governance problem, not a mail-routing nuisance. Native email platforms make broad decisions for the whole tenant, but inbox value is determined at the user level. That means the control boundary is wrong before tuning even starts, because the system cannot express what is relevant to one employee and irrelevant to another. Practitioners should treat inbox clutter as a human identity governance issue, not a simple filtering defect.
A few things that frame the scale:
- Organisations maintain an average of 6 distinct secrets manager instances, creating fragmentation that undermines centralised control, according to The State of Secrets in AppSec.
- Companies are dedicating an average of 32.4% of their security budgets to secrets management and code security, with US organisations leading at 40.8%.
A question worth separating out:
Q: Who should own graymail governance in an organisation?
A: Ownership usually sits across security, IT, and workplace productivity teams, but the accountable group should be the one that can enforce policy and report outcomes. If nobody owns enforcement and reporting, the programme becomes a convenience feature. Governance needs a named owner who can prove the control is active and effective.
👉 Read our full editorial: Graymail filtering gaps show where native email tools fall short