CRM

MClifton
Contributor

emails from addresses that don't contain a first or last name.

SOLVE

I'm trying to find a solution to an ongoing problem with emails we capture creating contacts in HubSpot.  The issue is the large number of emails that start with, accounting@ or purchasing@ or parts@.  I realize these will be captured but they don't really provide us with a personal contact for correspondence if there isn't a name attached to the email content.  Are people just letting these create new contacts each time or deleting them since they may not be professional for marketing email campaigns.

0 Upvotes
2 Accepted solutions
Jnix284
Solution
Hall of Famer

emails from addresses that don't contain a first or last name.

SOLVE

hi @MClifton I don't delete them since we typically email them transactional emails or 1:1 and it will keep adding them back, but I do make sure to mark them as Non-Marketing since we aren't sending marketing emails to them.

 

I have a workflow that looks for blank first name and/or last name, which triggers a cleanup task for larger accounts, for others I create a filtered view that I check-in on periodically (quarterly or monthly depending on volume).

 

I usually just update first name to be the department, like "Accounting" and last name to be the name of the company, like "Company" so it would read as "Accounting Company" so at least it isn't blank and when we get notifications it's clear who it is.

 

If someone replies to the email with a signature and they are the POC using the email, I change it to their first/last name to allow personalization tokens to work.

 

Curious to see how others handle 👀

 


If my reply answered your question please mark it as a solution to make it easier for others to find.


Jennifer Nixon

View solution in original post

0 Upvotes
karstenkoehler
Solution
Hall of Famer | Partner
Hall of Famer | Partner

emails from addresses that don't contain a first or last name.

SOLVE

Hi @MClifton,

 

This really depends on how these addresses are generated.

 

If, for example, they're being generated through a connected team email address in a conversations inbox, I'd argue that these contacts aren't eligible for marketing communications at all (lack of a legal basis). Their use is limited to the request they submitted via email and if for that request, that's the preferred channel of communication, I would respect this and simply address the recipients in a generic way. After fulfilling the requests and answering the messages, you should implement a deletion concept that removes these records from your system unless there is a continued legal basis for processing their data (e.g. them being a customer).

 

As a second case, let's assume that these emails are provided in marketing forms or other lead generation channels, such as lists provided by events or through lead gen ads. In this case, the contact chose to use this email address and I would respect that choice that they want marketing emails to go to a shared inbox rather than a personal one. Here the biggest challenge becomes the salutation in an email but that can be fixed with workflows or smart rules, simply filtering for all contacts where the email contains sales, info, accounting, purchasing etc.

 

In other words: It depends where these contacts are coming from. That should inform what you do with them. Marketing emails should only be sent to contacts where there is a legal basis for marketing communication.

 

Hope this helps!

Karsten Köhler
HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer

Beratungstermin mit Karsten vereinbaren

 

Did my post help answer your query? Help the community by marking it as a solution.

View solution in original post

2 Replies 2
karstenkoehler
Solution
Hall of Famer | Partner
Hall of Famer | Partner

emails from addresses that don't contain a first or last name.

SOLVE

Hi @MClifton,

 

This really depends on how these addresses are generated.

 

If, for example, they're being generated through a connected team email address in a conversations inbox, I'd argue that these contacts aren't eligible for marketing communications at all (lack of a legal basis). Their use is limited to the request they submitted via email and if for that request, that's the preferred channel of communication, I would respect this and simply address the recipients in a generic way. After fulfilling the requests and answering the messages, you should implement a deletion concept that removes these records from your system unless there is a continued legal basis for processing their data (e.g. them being a customer).

 

As a second case, let's assume that these emails are provided in marketing forms or other lead generation channels, such as lists provided by events or through lead gen ads. In this case, the contact chose to use this email address and I would respect that choice that they want marketing emails to go to a shared inbox rather than a personal one. Here the biggest challenge becomes the salutation in an email but that can be fixed with workflows or smart rules, simply filtering for all contacts where the email contains sales, info, accounting, purchasing etc.

 

In other words: It depends where these contacts are coming from. That should inform what you do with them. Marketing emails should only be sent to contacts where there is a legal basis for marketing communication.

 

Hope this helps!

Karsten Köhler
HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer

Beratungstermin mit Karsten vereinbaren

 

Did my post help answer your query? Help the community by marking it as a solution.

Jnix284
Solution
Hall of Famer

emails from addresses that don't contain a first or last name.

SOLVE

hi @MClifton I don't delete them since we typically email them transactional emails or 1:1 and it will keep adding them back, but I do make sure to mark them as Non-Marketing since we aren't sending marketing emails to them.

 

I have a workflow that looks for blank first name and/or last name, which triggers a cleanup task for larger accounts, for others I create a filtered view that I check-in on periodically (quarterly or monthly depending on volume).

 

I usually just update first name to be the department, like "Accounting" and last name to be the name of the company, like "Company" so it would read as "Accounting Company" so at least it isn't blank and when we get notifications it's clear who it is.

 

If someone replies to the email with a signature and they are the POC using the email, I change it to their first/last name to allow personalization tokens to work.

 

Curious to see how others handle 👀

 


If my reply answered your question please mark it as a solution to make it easier for others to find.


Jennifer Nixon
0 Upvotes