Skip to main content
All CollectionsAccount settingsEmail settings
Prevent your emails from ending up in your customers’ spam
Prevent your emails from ending up in your customers’ spam

This article will explain what you and your customers can do to avoid your emails ending up in your customers’ spam.

Updated this week

Salonized’s mailing system is designed to maximise the likelihood of your Salonized e-mails being delivered to your customers' inbox successfully - but it can’t be 100% guaranteed.

All email service providers have different delivery rates. Most often, they fluctuate between 88-99%. This means that, on average, for every 100 emails sent only 88 to 99 of them are delivered successfully (you can read more about email deliverability standards here).

At Salonized, we pay a lot of attention to maintain our score as close to 100% as possible. Currently, our deliverability rate fluctuates between 97-99%.

There are various reasons why your Salonized e-mails aren't successfully delivered to your customers. For example:

  • your e-mail may contain wording, images or attachments that trigger spam filters

  • your e-mail may contain shortened or exposed URLs

  • your customer might have at one time marked one of your Salonized e-mails as spam because they didn’t recognise your Salonized e-mail address.

When this happens, this can affect all of the e-mails that you try to send to that specific customer - including the essential ones like the appointment confirmation.

But fear not! There are things that you and your customers can do to minimise the likelihood of your Salonized e-mails from ending up in their spam.


🫵🏼 Things you can do

🔗 Learn more about email deliverability risks

Check out some of these resources to learn more about e-mail deliverability challenges and how you can try to tackle them.

📋 Use a free SPAM checker to review your emails

Use free online resources to check your emails for content that might cause your email to end up in spam.

🔎 Inspect your email templates for potential spam triggers

When you update your e-mail templates or create new ones, it's easy to introduce content that might trigger your customers' spam filters without you realising. Common pitfalls include:

  • Too many images

  • Exposed URLs (URLs that aren't covered by text or an image)

  • Shortened URLs (URLs that have been shortened by servies like bit.ly or tinyurl.com)

👤 Maintain and up-to-date recipient list

If you send bulk e-mails to lots of recipients, and those recipients aren't engaged with your content, this can impact deliverability of all emails that you send. You should regularly "clean-up" your recipients list to make sure that you're not regularly sending emails to customers who aren't engaging with them.


🫂 Things you can ask your customers to do

1️⃣ Move your e-mails from SPAM to the "primary inbox"

The screenshot above shows a Gmail example where you can see that the Appointment Reminder (Afspraakherinnering) hasn't landed in the customer’s primary inbox.

By dragging the email to the primary inbox (Primair) this customer can make sure that your subsequent e-mails will land in their primary inbox.

2️⃣ Add your e-mail as a safe sender

If your customers add your email address to their address book, your emails will end up in their primary inbox.


Frequently Asked Questions (FAQs)

Q: When it comes to email authentication standards, does Salonized use DKIM, SPF, or both?

A: Both.

Q: I've received a "Delivery Status Notification (Failure)" from "MAILER-DAEMON@amazonses.com" - what is this?

A: Salonized uses Amazon SES to send e-mails. The "Delivery Status Notification (Failure)" e-mail will be sent to you by Amazon SES if your e-mail has resulted in a bounce or complaint from your customer's mailbox.

Each time you receive this e-mail, you should check to make sure that your customer's e-mail address is correct, or that the account is still in use. If you have confirmed that your customer's e-mail address is correct and their e-mail account is still in use, please get in contact with support.

Did this answer your question?