Option to set email to private and not log it

[SebastianB]

Hi, it would be great to specify the privacy setting for emails or contacts that will be logged in the CRM. As some conversations & emails have to be confidential, it would be great to have a setting that tells Hubspot which emails to log and which not to log. For that, a "blacklist" of sorts could be a solution where all the companies & contacts are listed from which conversations should not be logged. Another way to do this would be to define a short code which can be added to the email in order to make it private, and thus not logged.

I would greatly appreciate it if you could implement a similar feature.

Thank you!

All the best,
Sebastian

[SebastianB]

Hi everyone, 

We have a feature available within the CRM and within our Sales extensions called the Never Log list. You can add individual email addresses and/or domains to the list to prevent emails sent to those addresses from logging (and thus from creating contacts).  We apologize for not updating this thread sooner!

Here is a link to our knowledge base article detailing the steps to set this up! 

Best,

Caitlin

[#3]

Much needed feature.   for a variety of reason this feature is a no brainer necessity

[#4]

I agree with the others. I ran into this issue today. We routinely CC our colleagues on emails to leads and constantly having to delete the extra contacts created. Hope you implement this soon.

[#5]

I join others here in requesting that this critical feature be added. In a separate forum chain, I think jveler_ecrs did an amazing job quantifying the negative impact of having to manually uncheck the track and/or log buttons on every email:

30 people x 15 clicks per day (conservatively) x 2 seconds per click = 15 minutes of lost time per day, 1.25 hours per week, or 62.5 hours per year. 62.5 x an average $60K salary = a cost of $1,875 / yr. If 100 companies have this same undesired behavior, pay their sales reps, has the same size team, then you're talking about adding $187,500 of combined, unnecessary labor cost per year. In addition that lost time could be used for inbound training and/or additional prospecting.

In addition to the labor cost from conservative time estimates, I feel it is a way for HubSpot to quickly inflate (unnecessariy and unwanted) our number of contacts in our account forcing us to go over our contact limit and pay for additional contact allotments.

If the same 100 companies have this issue and over the course of one year adds 1,000 contacts to each of their accounts at $10/mo/1000 for Hubspot overages, then Hubspot just made $12,000 additional revenue because they won't provide an option that a base of customers desire.

[#6]

Agreed this is a big problem. We have a need to blacklist domains - it's not an option not to. For two reasons: 1. To prevent vendors and other non-sales/customer contacts from going to the CRM.  2) To restrict certain IPs and known corporate domains from receiving email or ads or starting a new trial of our software (authentication at the time of landing page form submission). 

Here is the workaround we are using with Zapier for the 1st example of catching/removing contacts created that match a domain from the Blacklist.   The second example is a bit more involved, happy to share via PM though.

Apps involved:

Hubspot CRM

Google sheet with list of blacklisted domains

Formatter by Zapier

Webhooks by Zapier (Hubspot Email API- PUT)

Webhooks by Zapier (Hubspot Contacts API- PUT)

Zap Flow:

Step 1: Trigger:  New contact created in Hubspot CRM

Step 2: Action: Formatter by Zapier - Transform: Split Text.  Input: email. Separator: @.  Segment Index: Second

(this creates the domain value for lookup purposes)

Step 3: Action: Google Sheets look up spreadsheet row: Spreadsheet: Blacklist. Worksheet: domain. Lookup column: domain. Lookup value: Formatter - domain

Flow only continues if successful match.

Step 4: Action: WebHooks by Zapier: PUT

This unsubscribes the contact ID of the contact (select from the Trigger step) from all email in Hubspot.

JSON code here: Hubspot Email API:  update_status

Example PUT URL:
https://api.hubapi.com/email/public/v1/subscriptions/example@domain.com

Example PUT data for unsubscribing an email address from all email:
{
    "unsubscribeFromAll": true
}

Example PUT data for unsubscribing from specific email types:
{
    "subscriptionStatuses": [
        {
            "id": 7, "subscribed": false
        }
    ]
}


On success, returns a 200 response with this JSON:
{
    "status": "ok"
}

Step 5: Action: Webhooks by Zapier: PUT

This deletes the contact ID of the contact (select from the Trigger step) from Hubspot.

JSON code here: Hubspot Contacts API:  delete_contact

Example DELETE URL:
https://api.hubapi.com/contacts/v1/contact/vid/61571?hapikey=demo

Example JSON output:
{
  "vid": 61571,
  "deleted": true,
  "reason": "OK"
}
   

[#7]

Please add this feature ASAP! Realized we needed to prevent contacts from a certain domain from being added and the only answer is "uncheck the box". There really needs to be a better way to do this.

[#8]

Agreed, this would be valuable. 

[#9]

So, there's a blacklist in HubSpot for this. It's in Settings->Sales->Log Email in CRM.

Doesn't that cover it?

[#10]

Hi Madhavaji,

It works well enough if you are emailing directly but I found that when you do a round robin type email and a blacklisted address responds it is saved in hubspot anyway.

Alex.

[#11]

Interesting, thanks @Alexaustin,

Will test this out thoroughly and report back.

[#12]

I don't know if anyone has let you know - but this does exist now in the Sales Plug-In (althought it needs some improved functionality).

If you are in Hubspot and you go to your settings within the Plug-In, there is now a place to enter addresses/domains that you want to exclude from syncing/tracking.

IMPROVEMENT request for Hubspot - I'd love it if there was a way to exclude domains and have it automatically applied to all the users of the plug-in. For example - I would like to exclude our external IT and our insurance contacts (I know I can't minutely exclude every single little thing - but this would help).