Sender Pool: unlimited addresses, each with its own limit
A single sending address with a single daily limit was becoming a bottleneck for growing lists. Pulse now manages an unlimited number of sending addresses; each one uses its own Brevo API key and its own limit, and sending is distributed across them automatically.
Every team that sends newsletters eventually hits the same wall: the provider's daily sending limit. As your list grows one address is no longer enough, and the moment you add a second one you start tracking by hand who sent what. From this release Pulse handles all of that for you.
The Sender Pool
The new Sender Pool screen lets you define as many sending addresses as you need. Each row holds the address, display name, daily limit and warm-up preference. When a campaign goes out the system picks the least loaded active sender for that day; when one address reaches its limit the next one takes over and sending never stalls.
Every address, its own Brevo account
The previous approach attached several addresses to a single API key, which meant they all shared one account's limit. Now every sending address is paired with its own API key. In the new "API key ↔ sender pairing" card you add a row with the key, address, name and limit together — as many rows as you like. Re-entering an existing address only updates its key, so your sending history stays intact.
Warm-up: heating new addresses without burning them
Sending high volume from a brand new domain or address on day one damages your deliverability reputation directly. For addresses with warm-up enabled the daily limit ramps up gradually; until warm-up completes the system applies the brakes on your behalf. A scheduled job runs this every day, automatically.
Also in this release
- Delete in mail detail: fixed the broken delete button in the mail detail panel.
- New chat on mobile: added a "New chat" button to the AI chat bubble in the mobile layout.
- Sending screen: the single-sender settings page now points to the Sender Pool.
From this release on, every change we ship is published both on the in-app Version Updates page and here.