FAQ: How Do I Mass Delete Bad Email Addresses/Contacts With Bad Email Address?
We don't recommend deleting bad email addresses as it's too easy to then add them back in later (with no record the email is bad, staff will just see that the field is empty and add the same address back in again). This will reset the email to "unverified" status and you will be able to send an email to that address again. If you send too many emails to a bad address, recipient email domains will flag your domain as a spammer and blacklist you. Since Fundly CRM won't send to bad email addresses (to prevent you from sending to bad addresses and getting blacklisted) there is no harm in just leaving the bad email addresses in place.
Furthermore, we STRONGLY recommend that after you send a communication to contacts, you monitor that communication's metrics. Soft bounces are temporary blockages that prevent the email from being delivered, such as a full mailbox. If the blockage isn't resolved within three days, then the status changes to hard bounce and the email is marked as bad. However, the email address is actually still good (or, it will be once the temporary blockage is resolved). Deleting these addresses would result in deleting good email addresses that just need to be reset to unverified (do this by deleting the email address, saving the contact record, paste the email back in, and save the record again). However, there is no way to distinguish on a contact's record a "soft bounce that became a hard bounce" bad email versus a "straight up bad email address." You need to monitor the metrics for your communication - reviewing them immediately after your communication finishes sending/is delivered - to identify any soft bounces. Continue to monitor the soft bounces for 3 days. At the end of the 3 days, any that have become hard bounces, you should reset. You can delete the rest of the bad emails from inside the sent communication, if you so desire (but, as stated above, we don't recommend doing that).
Comments
0 comments
Article is closed for comments.