Multiple Spam Checkers for Different Workspaces
Taylor Jennings
Spam checker settings apply globally across all workspaces. Teams with different spam tolerance requirements per workspace, such as stricter filtering for a high-spam region, have no way to configure this independently.
Admins should be able to configure separate spam checker instances with different thresholds for different workspaces, so each workspace can apply the spam filtering level appropriate to its context.
A single global spam threshold is too blunt for organizations with varied audiences across workspaces. Per-workspace configuration prevents over-blocking in permissive contexts and under-blocking in high-spam ones.
Taylor Jennings
Merged in a post:
Apply different spam checker settings per form or product line
R
Radost Kalanova
Spam checker settings are applied globally, with no way to configure different rules for different forms. Teams that need to allow personal email addresses for one product while blocking them for another have no way to do so.
Admins should be able to configure spam checker settings at the form level, so different forms can apply different rules based on the audience or product they serve.
A single global spam setting doesn't work for organizations with multiple products or audiences. Form-level spam configuration prevents legitimate leads from being blocked on forms where personal emails are acceptable.