Email mailing lists
Turn product news, practical guides and customer updates into messages for your email list. Create with AI, review with your team and publish through a connected mailbox.
A clearer start.
A useful next step.
Our new onboarding guide brings your first steps together. Open your workspace and explore the guide.
Explore the guideFrom list to publication
Each email publishing channel has its own recipient list. Connect the sender, organize your audience and use the publishing workflow to prepare, review and schedule a message. Delivery details help your team understand what happened to each recipient.
Use a supported Microsoft 365, Gmail OAuth or IMAP / SMTP connection. Select the authorized sender and create a publishing channel for its list. A connected support mailbox does not automatically populate a mailing list.
Add and edit recipients, paste addresses or preview a CSV import. Review invalid and duplicate entries before importing. Each channel supports up to 1,000 recipients; imports preserve existing opt-outs and disabled entries.
Use the publishing writing assistant to help prepare content, then check the facts and wording. Set the subject and content format, inspect the sender and example recipient in the preview, apply configured approvals and schedule the publication.
An illustrative example
Your team has published an onboarding guide. Prepare an email that explains what the guide helps readers do, keep the subject specific and point to the next action. Preview the final message before scheduling it for the relevant list.
Subject: Your next onboarding step
Our new onboarding guide brings your first steps together. Open your workspace and explore the guide.
After sending starts, inspect the per-recipient results. Provider acceptance is separate from confirmed delivery. Investigate failures and uncertain outcomes before deciding what to retry.
Illustrative content only. No email or SMS is sent from this website.
Your list. Your publishing controls.
Set up the list, message and delivery options for the work you intend to run.
Individual delivery is the default. Optional BCC batches contain up to 50 recipients. Recipient-specific unsubscribe links require individual delivery, so BCC and unsubscribe are alternative settings.
Use a channel-specific subject and choose plain text or filtered HTML. Email supports attachments that pass the configured safety checks, within the product’s file and total-size limits. Preview the composed message before dispatch.
Unsubscribe is optional and initially off. When configured, its confirmation suppresses that recipient for the channel. Importing an address again does not automatically reactivate an unsubscribed or removed recipient.
Inspect pending, accepted, delivered, failed, uncertain and suppressed recipients. Retry eligible failures from the original send. Accepted and uncertain attempts are not blindly replayed, and later list edits do not rewrite a send already in progress.
Practical details
Know how the list, sender and delivery fit together.
Supported connection-backed publishing includes Microsoft 365 delegated, shared and application mailboxes, Gmail OAuth and IMAP / SMTP mailboxes. The account, permissions and publishing channel must be configured for the deployed workflow.
Yes. Preview a CSV containing an address and optional name, then review duplicates and invalid entries before importing. You can also paste addresses or manage recipients manually. This is a channel-owned list; automatic Contacts synchronization is not part of this workflow.
Use the existing publishing writing assistant to draft and refine the content. Your team checks facts, subject, audience and links, then applies the configured review and scheduling process. This does not imply automatic audience segmentation or personalization.
The workflow described here exposes delivery outcomes. It does not advertise email-open, link-click or conversion analytics. Provider acceptance alone should not be read as proof that a recipient opened a message.
Broadcasting does not create Tickets. Customer replies require a separately configured active Support channel and the relevant routing. Keep the outbound publishing list and inbound support workflow distinct.
Build the surrounding workflow
Bring content creation, list publishing and customer support together with the right configuration.
PUT IT INTO PRACTICE
Follow the setup, understand the controls and find the next step.
Import email recipients, preview a mailing, configure per-channel unsubscribe and inspect individual or BCC delivery results.
Set up Microsoft 365, Gmail or IMAP/SMTP mailbox connections, activate email ticket intake and understand synchronization and delivery limits.
Create a post, check channel variants, choose review and scheduling, and read publication results in EleonEcho.
Your next chapter, with AI
Bring your publishing, marketing and support work into Echo.
