Newsletters, on the same calendar as social.
Subject, preview and body drafted in the same composer as your social posts, then scheduled by the subscriber's clock.
Limits checked 11/2026. The agent reads the current Email value before every publish.
Read it as the subscriber will.
Subject, preview and the first screen of the body sit in one card, because the first screen is where an email is won or deleted.
- Subject and preview shown together, not separately
- One column at 600px, the width clients actually render
- One call to action, above the fold
One column, 600px wide, one button. It renders in every client that matters.
Read the guideWritten once, measured before it leaves.
Every draft carries the current limit for Email next to it, so the cut happens while you write instead of after a failed publish.
- A character count tied to the live limit
- Hashtags moved to the first comment when the caption is full
- Alt text required before the Queue button turns on
Type in the caption above: the meter answers to the limit shown in the field.
Post when your audience is around.
The planner suggests hours worth aiming for. Take one or ignore it; nothing moves unless you move it.
Best slot Tue 12:30
Suggested windows only. The hour that actually goes out is the one on the calendar.
One column, every client.
1200×628 header; 600px content width. Nothing is designed to rely on a renderer feature that half the clients ignore.
Images: GIF under 1 MB, or a linked still — anything heavier is linked instead of attached.
- 600px content width, the safe default
- One CTA per send
- A plain-text version generated alongside the HTML
A list you are allowed to mail.
Every address keeps the source it came from. An import without a consent column is refused, because a bounced list costs more than it earns.
The send and its announcement.
The newsletter is the long version. The posts that point at it are written from the same brief, each under its own limit, each on its own slot.
- One brief, two lengths
- Every network under its own limit
- The send stays on the subscriber's clock, the posts on yours
Opens and clicks, per send.
Sample numbers from the prototype. Each send keeps its own figures, so a subject line can be judged on its own.
Live in three steps.
No plugin, no copy-paste between tabs. The connection takes a minute; the first post takes as long as the copy does.
Connect the account
Sign in once and choose which Email account or page the agent may post to.
Write and schedule
One brief becomes a post sized for this channel, then takes a slot on the calendar.
Let it publish
Posts leave on their own at the hour you chose. No notification to tap.
The connection can be revoked from the channel's own settings at any time. Revoking it stops publishing; scheduled posts stay in the queue with a warning.
Questions, answered.
01SENDINGWhen does email ship?
In development; the calendar and copy are ready.
02SENDINGWill it use my domain?
Yes, with SPF, DKIM and DMARC set up during onboarding.
03SENDINGCan I import a list?
Yes, CSV with consent fields.
Draft the next send on the same board.
Connect Email, write one brief, and see the first post before lunch.