®
Mandated Emails and Required Notices
Mandated emails are one-time messages you are legally or operationally required to send, such as policy updates, security notices, service changes, or other required customer notices.
Contact Bento support before sending a mandated notice. We can help you review the plan, avoid common deliverability problems, and choose the safest setup for your account.
Before You Send
Do not send a required notice from your main marketing Site without checking with Bento first. These sends often include users who have unsubscribed from marketing email, gone inactive, or have not heard from you in a long time.
That can affect deliverability, reporting, and unsubscribe state if it is handled inside your normal marketing Site.
If the message is not legally or operationally required, treat it as normal marketing email and send only to people who should receive marketing from you.
Recommended Setup
For most mandated sends, create a new Site inside your existing team and upload the required recipients there.
This keeps the notice separate from your main marketing Site and helps avoid changing or confusing unsubscribe status for your normal campaigns, sequences, and automations.
A simple workflow:
- Contact Bento support with the reason for the required notice.
- Create a new Site in your team for the mandated send.
- Upload all users who must receive the notice to that Site.
- Build the required notice as a one-time broadcast.
- Send only the required content, without extra marketing or promotional copy.
Keep the message focused on the required notice. If the email includes promotional content, inbox providers and recipients may treat it like marketing email.
Sending Domain
Creating a new Site does not mean you should send from a brand-new domain.
Do not send a mandated notice from a new domain. Brand-new domains have no sending reputation and are more likely to be throttled, filtered, or treated suspiciously by inbox providers.
If Bento support recommends separating the sender, use a subdomain of an established domain instead. For example, you might send from notices.example.com or updates.example.com rather than buying or registering a new domain just for the notice.
Before sending, make sure the subdomain has verified DNS records in Bento and enough time for authentication to propagate. If you already have a healthy sending domain and support confirms it is the better path, use that instead of introducing a new sender.
High-Volume Notices
If the mandated notice needs to reach more than 1 million users, plan provider outreach before sending.
Work with Bento support first, then open tickets or support requests with major inbox providers where possible, especially Yahoo and Hotmail/Outlook. Let them know the reason for the required notice, the sending domain or subdomain, expected volume, sending window, and the fact that the message is a mandated notice rather than a marketing campaign.
This does not guarantee inbox placement, but it gives large providers context before they see an unusual volume spike from a broad audience.
Sending Pace
Send slowly over the longest time horizon possible.
Even when a notice is required, mailbox providers still evaluate volume, recipient engagement, complaints, bounces, and sending history. A slower send gives inbox providers more time to accept the traffic and reduces the chance of throttling or reputation issues.
If the notice does not need to reach everyone immediately, spread it over days instead of hours.
After Sending
When the mandated send is complete, archive the temporary Site.
Archiving the Site keeps your team clean and prevents ongoing billing from continuing for users who were only uploaded for the required notice.
Before archiving, confirm:
- The broadcast finished sending.
- You exported or reviewed any reporting you need.
- No follow-up sends are planned from the temporary Site.
- Bento support has confirmed there are no remaining deliverability concerns.
Once complete, archive the Site and continue sending normal marketing email from your main Site.