You can use these to restrict which of your organization’s emails and events are processed by Nektar. There are three kinds of controls:
Nektar screens out emails sent by automated systems and email addresses that don’t belong to a specific person (such as support@…
and sales@…
).
You may additionally block emails and events with specific email addresses, email domains, subject line keywords and private calendar events.
Nektar screens out emails or events where all participants are internal to your company, tools (e.g. notifications, conference rooms, meeting recorders), distribution lists (e.g. sales@
, support@
) or using personal email addresses (e.g. @gmail.com
).
You may configure additional email addresses and domains as ignored, i.e. treated like internal for activity screening purposes.
<aside> <img src="/icons/warning_blue.svg" alt="/icons/warning_blue.svg" width="40px" /> Note: If an activity passes screening, all its participants are stored and processed in Nektar — including ignored an internal ones.
</aside>
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />
Note: This section describes read rules. Activities and contacts must also pass write rules to be written to Salesforce.
</aside>
Nektar only creates records that can be linked to existing Salesforce records.
@gmail.com
).Additionally, write rules can be configured to further restrict which Activities, Contacts and Opportunity Contact Roles are created.
<aside> <img src="/icons/traffic-cone_blue.svg" alt="/icons/traffic-cone_blue.svg" width="40px" />
Write rules are in beta; contact us to implement them.
</aside>