Write and send your first newsletter issue

You will be able to write, test and send one newsletter issue to your list in the format you chose.

Write the body of your first issue before the subject line, run a fixed set of checks, test it on at least two devices, send it to your consented list, and log the send straight away. The whole exercise takes about forty minutes. The first issue is the hardest one to send, and the pre-send checks catch the real mistakes, so there is less left to worry about when you send it.

Priya runs a newsletter for parents of P5 children (an example scenario) and sent her first issue on a Thursday evening. The topic was the working-backwards heuristic, with one worked example and a link to a printable practice question on her site. Her subject line was "The heuristic most P5 children skip" and her preview text was "One worked example, and a question to try at home tonight."

Her test caught two problems. The practice question link went to last year's version of the page, and the greeting showed "Hi ," for a test contact with no first name. She fixed the link, set the first-name fallback to "Hi there", and sent the final issue to 312 parents in her newsletter segment. Her log row recorded the date, the time, the 312, the subject line and preview text, and the practice question link.

Writing the email before the subject line

Pick your topic from the three you listed in lesson 5.1, and write in the format you chose there. Write to one subscriber, as lesson 5.3 described: one main idea, one main link, short paragraphs.

When the draft is done, read it on a phone, or at least in a narrow window. Cut anything that does not serve the one idea. If the email has drifted into two topics, save the second one for the next issue.

Write the subject line and preview text only once you know exactly what the email says. Start from the pairs you drafted in lesson 5.2 and check each one against the finished email, because a line written before the draft often promises something the final email dropped. Write several options and pick the clearest.

If your tool can test two subject lines and pick the winner by clicks, set that up with your two best. On a small list, treat the result as a hint only, as lesson 5.2 warned.

Checks to run in the editor and preview

Do these checks in the tool's editor and in its preview:

Click every link in the body, one by one, to confirm it goes to the right page. Confirm the unsubscribe link is in the footer and works. Confirm the sender name is a real person your readers recognise, as set up in lesson 4.3. Confirm the reply address goes to an inbox someone reads. Fill in the preview text field so the inbox does not show filler. Find each merge field, the placeholder the tool fills with a subscriber's own data such as first name, and give it fallback text for people without that data. Add a short text description (alt text) to every image, and confirm the email still makes sense with images off.

Take particular care with the unsubscribe link. The Gmail and Yahoo requirements from module 3 expect it, and a missing or broken one is the fastest way to collect spam complaints. Singapore's Spam Control Act also has an unsubscribe rule, but it covers unsolicited commercial electronic messages sent in bulk, not every marketing email. Each of those messages must include a contact point, such as an email address, that the recipient can use to send an unsubscribe request. If you are not sure whether your sends fall under the Act, read its Second Schedule on Singapore Statutes Online.

A merge field fallback is the text shown when a subscriber's data for that field is missing. Priya's "Hi there" replaced "Hi ," for contacts without a first name.

Testing on two devices and sending to your list

Send test emails to yourself on two devices if you can: a phone and a laptop, or two different email apps. If a colleague or friend is willing, include them in the test. You may have read past the same typo four times, and a second pair of eyes catches it.

In each test, check the inbox view first, where the sender, subject and preview appear together. Then open the email and go through it as lesson 5.4 described, in light mode and in dark mode. Fix whatever you find. If the changes were large, send one more test.

Then send to subscribers with marketing consent, leaving out the addresses you suppressed in lesson 3.5. A suppressed address is one your tool is set never to email. Most tools ask you to pick a list, tag or segment at the send step, so double-check that choice before you confirm.

Recording the send in your log

Straight after sending, add a row to your send log. This is a simple record with one row per send, with columns for the date, time sent, audience name and size, subject line, preview text, the one main link, and notes for anything unusual. Leave space for results, which you fill in later.

The log feels like admin, but without it you cannot compare issues fairly. By next month you will not remember whether a better result came from the topic, the subject line, the day or a bigger audience. Module 8 builds the monthly review on this kind of log.

You are done when you have sent one issue to your consented list after testing it on at least two devices, and your log shows the date, time, audience and size, subject line and preview text.

Send your issue now, then fill in the record the activity below asks you to keep.

Write one newsletter issue in your chosen format, test it on two devices, then send it to your list. Record the subject line, preview text, send time and audience size.

Course

Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).