Writing and sending an issue
The composer is built for one job: an intro, then links grouped under headings, each with a line from you.
-
The composer
The page an issue is written on: subject and preheader, the markdown intro and its four toolbar buttons, what autosaves as you type, and which issues stay editable.
-
Sections
How the headings in an issue work: the four you start with, renaming and reordering them, moving links between them, and why an empty one never appears.
-
Adding links and writing the comment
Paste a URL, let Issue Mint read the page, then write the line that makes people click. Field limits, markdown in comments, and dragging links into order.
-
Sponsored links and sponsored banners
How a confirmed booking reaches the composer, why inserting it is a button rather than automatic, what banner artwork needs, and how sponsorship is disclosed.
-
Previewing an issue
The email, web and plain text previews, what each one catches, why nothing in a preview is tracked, and why there is one email template rather than a choice.
-
Sending an issue now
What Send now commits you to, every blocker the publish panel can show and how each one clears, and the parts of a send that cannot be taken back.
-
Scheduling an issue
Picking a send time in the newsletter's timezone, what scheduling checks, unscheduling before it starts, and how a scheduled date picks up a booked sponsor.
-
What happens when you send
The send pipeline as a walkthrough: the frozen recipient list, rendering once, batches and rate limits, retries, and why a restart cannot mail anybody twice.
-
A first send that waits for review
Why a first hosted send above two thousand recipients waits for a person, how many times you are told before it happens, and why it never happens twice.
Try it on your own list.
14 days, every feature, no card. Sending works from the moment you sign up.
Start your trial