Beehiiv & Substack specialist. I fix newsletter setup: domain/DNS, welcome sequences, migrations. Emails in the inbox, not spam. DM ‘AUDIT’ for a free check.
How I set up a Beehiiv newsletter system for a US executive recruiting firm (StealthJobs) that achieved 44%–48% open rates and 0% spam complaints across 9,898 cold contacts 👇👇👇
https://t.co/HPejhJw7U1
Beehiiv has two ways to welcome new subscribers:
1️⃣ One welcome email (all plans)
2️⃣ A welcome automation with several emails (paid plans)
If both are on, people get two welcomes. Switch one off.
Which do you use?
Irebami | Email Newsletter Specialist
@_chrisbroadfoot@beehiiv Nice. When you do the cleanup, send one “still want this?” email to people who haven’t opened in a while, then remove the ones who stay silent. Opens may dip a little, but inbox placement usually gets better.
3 numbers to check after every email send:
📊 Open rate
🖱️ Click rate
🚫 Spam complaint rate (keep it close to zero)
Low opens? These three help you tell if it’s your subject line or the spam folder.
Which one do you check most?
Irebami | Email Newsletter Specialist
@MillyTamati@beehiiv Agreed, the first email sets the tone for everything after. I’ve seen it on the automation side too: a Swedish course I set up hit 90% completion on its welcome sequence. Do you prompt a reply in that first one?
Happy new week and happy new month! ✨
Two months left in 2026. What’s ONE thing you want to finish before the year ends?
Drop it below. I’ll cheer you on 👇
Irebami | Email Newsletter Specialist
Step 5: Scale up only when the numbers stay clean. That’s how the list finished with 0 spam reports.
Reply WARM and I’ll send you the checklist, or DM AUDIT for a free check.
@rheosoph@vmkbuilds Year two is the real test. Domain reputation, list hygiene, and complaint rates all drift once the launch energy fades. Sending is easy. Staying in the inbox is the job.
@illyism Link wrapping is a sneaky one. A redirect domain that doesn’t match your sending domain can trip filters, and scanners pre-click links, so click data gets noisy. A custom tracking domain on your own subdomain fixes most of it. Are you skipping tracking or self-hosting it?