TLD CRM BoostPatch 9.5.0 – The One About Emails (Finally)

|

It’s finally here. Sendgrid has now been fully implemented on all Triggers and function for TLDCRM ( Except for the Mailer Campaigns, that is for later ).

For Context: TLDCRM Always had a mailer function, but we had originally implemented via Amazon SES (Simple Email Service). The problem with Amazon SES, is that it uses the Entire AWS Account’s Bounce Rate and Complaint Rate to determine wether or not the SES Service is at risk, and with a very low threshold of .5% being allowed as Bounces, Our Clients sending Emails to THEIR clients were far exceeding the rates causing our account to be locked / shut down.

While this wasn’t as big of a deal in the past, because we integrated and enabled Multifactor Authentication via Email, of which is now a requirement to use, having our SES Account disabled due to Rogue / Reckless Client usage of the Email system was something we couldn’t risk anymore.

Otherwise we both Clients and our Staff would end up locked out of the CRM in general.

We began implementing SendGrid with the Esignature System since it allows subuser based account segregation, and planned to migrate the rest of the Triggers and function in the CRM to follow suite, but we got busy.

Now more than ever with the CMS Changes in ACA, email is becoming more and more important. Today we rectify the issue of Emails not being available to send through TLD for your Clients.

The only thing that is not yet available related to Emails is the old Mailer Campaigns system that is still configured for SES, and needs to be migrated. This one is a little more tricky since it runs on a timed process in the backend in a different language entirely. We will get to this one shortly as it hasn’t really been an area of contention versus Welcome Emails and CSR Emails for example.

We have also updated our public-facing domain name to @tld.email instead of @tldcrm.com to avoid it coming into our inboxes on replies, and to also separate the domain reputation from our primary domain so we have less issues with MFA and Report emails that still go through SES.

We may in the future configure the system to receive emails on your behalf at this domain, unless you use a custom domain of course which is highly recommended to use, which would then go into your own inboxes.

Mailer Changes

  • Features now Enabled / Safe to use.
    • Email on Data Post
    • System / Product Level Quote Email
    • System / Product Level Welcome Email
    • CSR Confirmation Emails
    • CSR Completed Emails
    • Mass Send Email
  • New Email Domain for Public Facing Emails
  • Mailer Configuration
    • Can be found at Settings -> Mailer
    • Status Tab
      • This is where you can see if your SendGrid User is ready or not.
      • Test Email
        • You can test your emails right here
    • Domain Tab
      • Custom Domain Registration can now be done right from TLD.
        • Use the Authenticate New Domain Section under the Domains Tab
          • Once the domain id added, you can click the download button to get the DNS Entries you need to set for your Domain.
          • Once you have them set properly, you can then click the Validate domain Button to Validate.
          • Once Validated you should be able ot use your domain name for emails anywhere in the system that allows it.
      • See Attached Domains
        • By Default you should have tldcrm.com, ins.link and tld.email as usable domains for now.
      • Attach Existing Domains
        • If you accidentally Detached a domain you can reattached it here.
    • IP Tab
      • Don’t worry about this for now. This will allow us to add IP’s to certain accounts if we need it in the future.
    • Reputation Tab
      • Reputation Metrics can be seen by clicking on the Refresh Metrics button on this Tab.
    • Sync Tab
      • This is where there are some useful Buttons for Refreshing Data from SendGrid

Other Fixes

  • The Esign Email Confirmation Template was accidentally sending the Confirmation Template. This has been Fixed