Email-In and Email Deliverability Enhancements

Email-In and Email Deliverability Enhancements

Greetings,

We're excited to announce a new feature that enhances the email experience in Bigin: Custom "From" addresses for Email-In replies. Now, both confirmed organization email addresses and the email addresses you use to sign in to Bigin can serve as "From" addresses in Email-In. Additionally, you can apply domain validation via SPF and DKIM keys after this process to further enhance your email setup.

Custom "From" addresses for Email-In replies enabled     

  • We've now enabled the use of custom "From" addresses for Email-In replies. Both confirmed organization email addresses and the email addresses you use to sign in to Bigin will be automatically available as "From" addresses in Email-In. This eliminates the previous limitation that restricted replies to email aliases ending with biginmail.com.
    • Any emails sent to a custom email address, such as support@zylker.com, can be made available for Email-In by forwarding them to an email alias—for example, support@zylker.biginmail.com.

      However, if you attempt to reply to the received email within Email-In, it will be sent using the email alias       support@zylker.biginmail.com, potentially causing confusion for the receiving party, as they might expect the reply to come from support@zylker.com. The custom "From" addresses we've introduced solve this problem by allowing you to use the custom email address (added as the organization's email) as the sending email address. 
    • The email is still sent through Email-In, but with the custom 'From" address set to the organization's email.
    • Once the above process is done, you can validate the domain using SPF DKIM keys.

Enhancements to Email deliverability

Sending emails to customers is a fundamental and crucial feature of any CRM system. It's essential that emails sent from Bigin have excellent deliverability, minimizing bounce rates and avoiding spam folders.

What issue are we addressing? 

When a customer configures an IMAP email within Bigin, emails are sent through the SMTP server associated with that mailbox. In such cases, spam-related issues depend on that specific email server and don't affect Bigin's reputation.

However, in scenarios involving mass emails, organizational emails, or emails sent without configuring a mailbox, emails are sent directly from Bigin servers. If a significant number of these emails end up in spam or get blocked, it can negatively impact the credibility of Bigin's servers and potentially lead to blacklisting, thereby affecting the deliverability of all emails sent through Bigin.

Changes made  

  • The "Add Domain" button has been removed from the Email Deliverability page. Domains are now automatically included on the Deliverability page, eliminating the need for manual addition.
  • The "Delete Domain" button is no longer available on the Email Deliverability page, streamlining the domain management process.
  • The custom domain email addresses that users use to sign in to Bigin will now be displayed on the Deliverability page by default, improving visibility and usability.

How do we plan to address this? 

Now, when you add a new email address to your organization, the associated domain is automatically added to the Deliverability settings. To use your organization's email address for sending emails from Bigin, you need to verify the domains manually.

You can validate email domains for both the Primary Server and Email-In server based on your needs. For users with Email-In installed, the Email-In server is visible.

For example, if you want to use a specific domain only for sending emails from Email-In, you can validate that domain for the Email-In server only. Unverified email domains are marked with a red alert icon.

Email authentication involves a two-step process:

  1. Automatic domain addition
  2. Domain validation
Once a new email address is added to the organization's email addresses, the corresponding domain is added to the Deliverability settings. You'll need to manually verify them to start using your organization's email address while sending emails from Bigin. Validating it helps avoid email bounces and other problems mentioned earlier.


To learn more about Email Deliverability, please view the following help documents:
Notes 
  • The maximum domain count has been raised to 20 for both trial and paid plans.
  • Starting on January 30, any organizational emails that have not been validated will be unable to send emails.
  • The IMAP address cannot be used as the sender address when sending emails in email-in.
That's all for these enhancements. We sincerely hope you find these improvements useful. Watch this space for future announcements.

Thanks!