Sponsor follow-ups, speaker invitations, cold outreach, member newsletters: all of it leaves from your own partnerships@ or office@ mailbox, and nothing leaves without a person saying yes, a daily cap, a suppression check, and an unsubscribe link.
CommsOperator campaigns run multi-step email sequences from your own Microsoft 365 mailboxes, so replies come back to the inbox you already answer from. Every drafted step waits in an approval queue unless an admin explicitly enables automatic delivery for one fixed template. Each mailbox sends at most 200 emails a day by default and the rest wait, new mailboxes warm up gradually, suppression is two-tier and one-way, unsubscribe is one click, and permanent bounces suppress automatically.
Write the cadence once and let it run for hundreds of contacts, step by step, with the delays you set. When someone writes back, their follow-ups stop. Templates declare their variables, so a missing company name stops the draft instead of sending 'Hi ,' to a prospect.
Every email a sequence wants to send waits for a person. You see the exact message, the mailbox it will leave from, and anything the compliance check flagged. Nothing approved within seven days? It never sends. Letting a campaign deliver on its own is a deliberate admin decision, and it only holds for the exact template that was approved: change a word and it goes back to review.
Your domain's reputation is guarded whether or not anyone is watching. Each mailbox sends at most 200 emails a day by default and the rest go tomorrow, nothing is lost. New mailboxes start slow and ramp up. Bounce and complaint thresholds follow Gmail and Yahoo's published limits, and if they climb, the campaign pauses itself.
Once someone opts out, nothing can email them again, and no click, import, or admin action can undo it. Hard bounces, opt-outs, and people who left their company block every channel. A marketing unsubscribe still allows a reviewed one-to-one reply, so a real conversation can continue.
Send the member newsletter through the delivery service you already pay for. An editor, an archive, and test sends, with Mail Flow by default or Amazon SES, Brevo, or SMTP behind it. With Mail Flow, unsubscribes, complaints, and bounces flow back and update the member's list status.
A campaign reports meetings booked and deals won, not opens. In-email polls collect an answer with one click, replies are classified by intent, and outcomes are tied to the deal they produced.
Numbers from the production instance and behaviour checked against the code. No projections, no testimonials.
What this module does not do today, and what to do about it. If one of these is a blocker, you know before you commit, not after.
Not by default. Every drafted step waits for a person. Automatic delivery exists for one fully fixed template: an admin reviews the exact rendered sequence and confirms it, and any change to the template cancels that consent.
Each mailbox sends at most 200 a day and defers the rest, new mailboxes ramp up gradually, bounce and complaint thresholds pause a campaign, lists can be verified before launch, and permanent bounces and opt-outs suppress automatically.
The tokenized link suppresses the address immediately, with no login and no second question. A marketing unsubscribe stops all automation while still allowing a person to reply one to one; a full opt-out blocks every channel. Suppression cannot be undone from the UI.
For the editor, the archive, polls, and list management, yes: WomenTech Network moved 1,088 newsletter campaigns across. Delivery still runs through a provider, Mail Flow by default, or Amazon SES, Brevo, or SMTP if you already have one.
Tell us what you run and we will be straight about the fit. Private beta. A person reads every request.