There are several internal methods email servers use to authenticate and verify that email is being sent from a legitimate sender. These include SPF records and authentication methods like DKIM and DMARC. Further reading: What are DMARC, DKIM, and SPF?
Chili Piper will send emails on your behalf to customers and your end-users under our chilipiper.com domain. The emails are not sent from your custom domain.
As a result, you don't need to add DNS records or authentication on your end, and you can know confidently that Chili Piper does its best to validate and verify the emails we send are not to be blocked as spam.
Some examples of emails sent to customers include Reminders and Meeting Invites. These will come from generic chilipiper.com email addresses that are unmonitored inboxes.
Why are the emails ending up in spam?
Despite all of our validation and authentication methods, sometimes spam detection can still prevent your emails from making their way to customers.
Some common reasons your emails might still be blocked include the following:
- The email address of one of your reps or the email of a guest is on a known deny-list
- The text in your subject line or description are detected to have characteristics common to spam
- Examples include words like "Free", special characters, lots of uppercase letters, or descriptions that only contain a link and no text
- Multiple customers have flagged your emails as spam
- The customer has blocked you
- Incorrect spelling or grammar
- And many other reasons that may be outside of your control
Making some simple adjustments to the way your Meeting Types are formatted can lend a helping hand to the validation we deploy to ensure your emails make their way to your customers.