Live data from Hacker News

Lessons learned from onboarding emails with no HTML styling

blog.palabra.io

21–30 of 178 posts

Re: Lessons learned from onboarding emails with no HTML styling

#21
post #18

While on the topic of onboarding emails and how the read focuses around early stage company development, what I would like to also see is a breakdown of lessons learned with SMTP services and how to approach for an early stage company. Anyone have any advice/recommendations/suggestions?

Use a service with an API instead of SMTP directly. I like AWS SES (even if you don't use their hosting) as it is easy to integrate, fast and extremely cheap (10ct for 1k mails).

Re: Lessons learned from onboarding emails with no HTML styling

#22
post #17

In this thread: lots of grumpy people forgetting that if you’re on HN you are weird and not representative I email 10,000+ engineers 3x+ per week. Individually they’re all grumpy and ugh about email. En masse, only 0.01% of them unsubscribe and 24%+ read the emails. Many even email back saying how wonderful they are. And yes adding emojis to both subjects and emails themselves helps. The open and engagement rates imp…

Totally agree here, would also add that adding value to each email sent is actually the most important part. Subject lines, emojis and images improve read rates. Value is what makes people actually stay around

Re: Lessons learned from onboarding emails with no HTML styling

#23
post #18

While on the topic of onboarding emails and how the read focuses around early stage company development, what I would like to also see is a breakdown of lessons learned with SMTP services and how to approach for an early stage company. Anyone have any advice/recommendations/suggestions?

we started with Mailgun and moving to Amazon SES. We actually created Palabra to not have to deal with those services directly. If you want to try our third party tool instead of handling them yourself let me know

Re: Lessons learned from onboarding emails with no HTML styling

#24

I caution the use of emoji, I've seen so many stack overflow job posts with memey use of emojis and it just makes me cringe and I find it hard to take the company seriously.

Why can't I just disable emoji in email subjects in gmail? I'd definitely like to.

Re: Lessons learned from onboarding emails with no HTML styling

#25
I run a SAAS and still personally (non-automated) send a welcome /check-in/onboard email to every single signup. I've sent a 1000+ in the last year.

I try to make them really personalized. Like if your website is acmewidgets.com - I'll put "Acme Widget Help?" as the subject.

My own takeaways:

1. Plain Text for sure

2. Super short - my standard sort of email is now about 3 sentences.

3. Ask a question - in my case there's a couple of driving reasons to sign up so I try and make sure they're doing ok.

Even with all of the above I still maybe am only getting a 30% response rate.

Re: Lessons learned from onboarding emails with no HTML styling

#26

I caution the use of emoji, I've seen so many stack overflow job posts with memey use of emojis and it just makes me cringe and I find it hard to take the company seriously.

Emojis in subject line reliably increase open rate in my experience. Also others report the same:

https://www.outreach.io/blog/will-emojis-increase-reply-rate...

Maybe SO emails go over the top though

Re: Lessons learned from onboarding emails with no HTML styling

#27
post #2

Good points in here, but I disagree about using a person's name as the From address. If I'm getting an email from Notion, I want it to show up as "From: Notion" in my inbox, not "From: Ivan". I have several companies that do this and I never know who the email is from, which adds some cognitive friction I don't need when triaging my inbox. You can put your name in the subject line if you want.

this is an interesting point. I think the email address matters if you expect people to answer. In the superhuman example, I know the CEO isn't sending me those emails, but I'm more likely to reply if I have a question. Palabra's onboarding emails come from my personal email address and many people reply with questions directly to me, which really helped us get immediate feedback

Re: Lessons learned from onboarding emails with no HTML styling

#28
post #9

To add to the points others have made: If I see an email with a name in the title I don't recognize, I instantly think it is spam. Please do not do this, it neither helps with your credibility nor does it help to build a "connection". I want to know where this email is coming from, and if I have signed up at Spotify, I expect to recieve my emails from Spotify, not Tom whoever at Spotify.

I really dislike emails that claim to come from a person but obviously come from an automated system - I find it remarkably dishonest.

Edit: I don't mind if I think the person is even vaguely aware I exist. But an email claiming to be from an executive of some huge company saying how happy they are that I have signed up doesn't fall into that category.

Re: Lessons learned from onboarding emails with no HTML styling

#29
post #9

To add to the points others have made: If I see an email with a name in the title I don't recognize, I instantly think it is spam. Please do not do this, it neither helps with your credibility nor does it help to build a "connection". I want to know where this email is coming from, and if I have signed up at Spotify, I expect to recieve my emails from Spotify, not Tom whoever at Spotify.

> I always feel awkward when I don’t know who is writing on the other side. Is it the CEO? Someone from Sales? Is it a super intelligent baby?

Why would someone feel awkward? It's from neither of those. It's automated so I think it's awkward and misleading to use a name.

Re: Lessons learned from onboarding emails with no HTML styling

#30

I disagree with the premise of the article: “Every SaaS company must start their onboarding sequences with a welcome message that is sent when a user joins the platform. This is a must by now, since everyone who signs up will expect some sort of confirmation of their transaction.” These emails invariably waste my time. They repeat what the website already told me when I signed up. If I sign up for your SaaS, I expect…

When you need to track down your username months later it's nice to have that confirmation you can find later. It does not hurt to give your customers a searchable database of transactions and such.
Post reply on HN