Summary
Email sync filtering can be configured in the "Settings" Global Tool
You (as a Planhat admin) set them up for your whole tenant
There are three main categories of email sync filtering:
"General Rules" - specify which email addresses are internal (i.e. belonging to you and your colleagues, rather than prospects/customers)
"Participant-Specific Rules" - define pairs of Users and End Users where emails should not be synced ("Emails stop list") or only be synced ("Emails white list")
"Email-Specific Rules" - configure filters to exclude emails with other characteristics, e.g. out-of-office replies
Who is this article for?
Planhat builders/admins, e.g. Tech/Ops
Article contents
Introduction
π Important to note
This is a technical deep-dive article - read on if you're a Planhat admin/builder and would like to learn how to configure which emails are synced into your organization's Planhat tenant. If instead you would like to learn about configuring the sync of your own emails into Planhat, check out our separate article here.
Note that the email filtering discussed in this article is separate from:
Connecting your own email account to Planhat and specifying which of your own folders/labels (e.g. "Inbox" and "Sent") to sync
Applying filters in Data Explorer or Pages (e.g. Inbox Pages) to filter emails that have already been synced into Planhat
Email is one of the main methods of communication with your customers and prospects, and so it's important to sync your emails into the Planhat platform, where they can be viewed by the whole team, and seen in the context of other types of data.
Let's say you've already connected up your work email account (Gmail or Outlook) to Planhat, and specified the folders to sync. But does this mean literally all the emails in those folders will be synced to Planhat? What if there are emails you don't want to be synced?
The first thing to note is that in Planhat, only emails to/from your customers or prospects are included in the sync, because emails (a type of Conversation record) are always associated with a Company in Planhat. Emails are mapped to Companies by looking at End User email addresses, and domains specified in Planhat for each Company. So no need to worry about your father emailing you family photos, or your stamp collectors' newsletter - none of those personal emails will get synced into Planhat, so you're not cluttering the view of your colleagues, or accidentally sharing private information.
But sometimes, this email address / domain matching alone is not enough. There still could be some emails that are "noise" (irrelevant), and still some sensitive (private) content, even if those emails are associated with a Company in your Planhat tenant. That's where enhanced filtering options in the "Settings" Global Tool come in. There is a lot of flexibility here, so you can define exactly how you would like to filter emails.
In this article, we'll explain the variety of email sync settings that you can use to specify which emails are synced into Planhat.
π Definitions
CRM data in Planhat is structured into "models", similar to the "objects" you may be familiar with from other tools. In the context of email filtering, the key models you should be aware of are:
"Company" represents businesses/organizations who are your customers or prospects
"End User" corresponds to individuals at Companies (who are typically users of your product)
"User" is a different model that's used for users of Planhat, i.e. you and your colleagues. You may sometimes hear this called "team member"
"Conversation" is a model where your "logged activities" are saved - this includes communication with customers and prospects (e.g. emails, tickets and chats), and also meetings (such as kick-off calls, QBRs, training sessions and so on)
"Records" are individual instances of those models - e.g. a Company record could be "Microsoft".
What is email sync filtering?
Email sync filtering is a series of settings that you use to prevent specific emails from being synced into Planhat. Where you configure these settings is also where you can choose whether related email domains are automatically added to Companies in Planhat. You can even use email-specific rules retroactively, to clear up existing emails in your Planhat tenant (e.g. remove unimportant out-of-office replies).
Email sync filtering is applied to your organization's Planhat tenant as a whole. It can be configured by you as a Planhat admin, as long as your Role has the "Admin Access" workflow permission and you therefore have access to the "Email Sync" part of the "Settings" Global Tool (shown below).
Click the image to view it enlarged
As you can see in the screenshot above, this email filtering has three categories:
"General Rules"
Here you specify which email addresses are internal - bearing in mind that internal emails (e.g. between you and a colleague) are not synced into Planhat
You can also choose whether "related domains" (used to map new End Users to Companies) are added to Companies automatically
"Participant-Specific Rules"
Here you can exclude or include emails from the sync, based on combinations of Planhat Users (your team members) and your End Users
"Email-Specific Rules"
With these rules, you can exclude emails based on wording in the email
This applies to future emails, but can also be used to clear out unnecessary emails that have already been synced
Why use email sync filtering?
There are two main advantages to email sync filtering:
You reduce "clutter" in your tenant by excluding irrelevant emails - e.g.:
You can exclude out-of-office replies and calendar invites, as these emails may not be necessary/useful
You state which email addresses are internal (e.g. those of contractors working for you), so internal emails aren't synced in
You improve data security by excluding emails containing sensitive information - e.g.:
If your organization's payroll provider is a customer and therefore a Company in Planhat, exclude the emails between them and your Finance team to avoid confidential discussions being synced in
If you have a User (team member) whose partner works for a customer Company, prevent their email correspondence (personal messages) from being synced in
With the range of different rule types available in Planhat, these settings can be general and wide-reaching, or really specific. You can use the customization options to tailor the behavior to best suit your organization.
How to set up email sync filtering
Now you understand the principles, let's deep-dive into the practical details of how you set this up.
We'll start by explaining how to navigate to these settings within your Planhat tenant, and then we'll go through each of the individual settings.
Settings
To configure email sync filtering, begin by navigating to the "Settings" Global Tool, which you can get to by clicking on your tenant name in the top-left corner of Planhat, and selecting "Settings".
Once in Settings, scroll to the "Email Sync" category, and select "Filtering".
π Important to note
Your Role needs the "Admin Access" workflow permission for you to access the "Email Sync" part of the "Settings" Global Tool.
General Rules
The general rules block out domains or email addresses.
The first box you'll see is "Internal Domain":
Internal domains are the ends of your work email addresses - e.g.
mycompanyname.com
ormycompanyname.co.uk
Multiple domains can be stated in this box - make sure to list all that your organization uses (separated by commas)
This is used to identify which email addresses are internal - and internal-only emails (not involving Companies - customers and prospects) are not synced to Planhat
Another setting related to domains is the toggle switch "Don't add related domains Automatically":
By default, this will be disabled, meaning related domains will be added to Companies automatically - so if a new End User with a new email domain is manually added to a Company in Planhat, that new domain will automatically be added to the Company's "Related Domains" system (standard/default) field
The Related Domains field can be used to create new End Users, if we can match the domain in a new email address to an existing Company in Planhat
E.g. if your tenant includes the Company "Radleys", with the stated domain of radleys.com, and then you receive an email from meg@radleys.com, a new End User can be created for Meg at Radleys (if this End User doesn't already exist)
Whether this automated End User creation is enabled or not is controlled by a general setting called "Automatic Detection of New Contacts" in the "Account Setup" section of the "Settings" Global Tool - speak with your CSM or TAM, or our Support team, if you would like to change this setting
Alternatively, if you want to want full control over the domains associated with each Company, you can enable this toggle switch to turn off this automated process
You'll see another box for "Internal Emails":
Here you can specify individual email addresses to be marked as internal
This allows you to prevent the syncing of email communication with a particular email address that is internal but doesn't share your domain, such as a consultant working for you
Participant-Specific Rules
The next section of settings applies to emails with specific combinations of Planhat Users (i.e. you and your team members) and End Users (your customers and prospects).
For example, although you would want almost all emails related to your customers/prospects to get synced into Planhat, correspondence between your CEO and the CEO of a customer/prospect might contain commercially sensitive information that you don't want everyone to see. Or maybe a Company is both your customer and your accountant, and when your Finance team asks them a question, you don't want those emails synced into Planhat, as they could contain sensitive payroll information. Or perhaps one of your Users has a friend or relative who's an End User, and they don't work together but do use their work emails for personal messages, and you'd like to block the sync of that.
With "Emails stop list", you can configure specific combinations of a Planhat User and one or more End Users (specified by email address). If an email includes that User and at least one of the End Users, that email will not be synced into Planhat (regardless of whether there are any other Users or End Users included in the email).
"Emails white list" is a similar method of filtering, but works the other way around. If a User is added to the white list, then the only emails of theirs that will be synced into Planhat are those with the specified End Users (email addresses).
Note that Users should only be added to a stop list or a white list, not both.
Email-Specific Rules
Sometimes, you might want to exclude particular emails from the sync based on criteria other than participant email addresses - such as a particular word or phrase in the subject or body of the email.
In the "Email-Specific Rules" section, you build rules to filter what syncs into Planhat. If an email matches a filter/rule, it will be excluded from the sync. You can even use these rules retroactively to "clean up" (remove) previously synced emails!
When you click to add an email-specific rule, you can either create a new custom filter (see this separate article for more on designing filters) ...
... or you can choose from a variety of example template filters, which you can either use without further configuring, or edit.
The templates (titles/names shown above) illustrate some typical use cases for email-specific rules, such as excluding meeting invites, out-of-office replies, and emails from "no reply" email addresses. These are emails that can be considered clutter in your Planhat tenant, as they aren't particularly useful or actionable.
π Case study
Let's take a closer look at a specific example. Shown below is a filter for excluding Google calendar invite emails, which we have created by starting from the "Calendar Invites" template and editing it slightly.
You'll notice it looks very similar to filters you may see elsewhere in Planhat - for instance, you can choose between "Match all" and "Match any". In this specific rule, we're using "Attachment name" to identify an attachment type associated with calendar invites.
In addition, we have specified that the subject does not start with "Re:", as that would indicate that someone has replied to the calendar invite - i.e. that it's an email that has been manually sent, so you'll likely want it to be synced into Planhat.
While you're designing a filter (whether from scratch or from a template), it can be helpful to click "Show matched emails" - this runs your filter/rule on the emails currently synced to your Planhat tenant. You can use this to double check that the rule is configured as desired, and it also gives you an indication of how many emails it's likely to affect. (Note that this is optional: you will still see matched emails when you click "Save", as we discuss below.)
When you are finished, click "Save". Before saving, Planhat will run the "Show matched emails" check, and present the results like in the second screenshot below.
As you can see in the orange buttons in the screenshot above, you then have the option to apply the filter/rule to just new emails that could be synced in future, or also to first remove existing emails that match the filter/rule. This can be a good way to "tidy up" the existing emails in your tenant, rather than only making changes to the sync going forward.