You can use these to restrict which of your organization’s emails and events are processed by Nektar. There are three kinds of controls:

Screening rules

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 that you do not wish Nektar to write in your Salesforce. You can do so under these categories.

• Block until date - All events with the start date and email sent until this date will be blocked by Nektar.

• Private calendar events - When toggled on, these events will not be read by Nektar.

• Email addresses - Activity will not be captured by Nektar if any participant matches these email addresses

• Email domains - Activity will not be captured by Nektar if any participant matches these email domains.

• Subject line keywords - Emails or events with subject line containing any of these words ****will not be captured.

• Body patter keywords - Emails with body containing any of these words ****will not be captured.

  Rule Behaviour for Subject line and Body pattern keyword matching

  • Case Insensitive Matching

    Matching is not case sensitive. For example, if confidential is blocked, Nektar will also block Confidential and CONFIDENTIAL.

  • Exact phrase matching for multi-word patterns

    Multi-word patterns are treated as exact phrases, not as individual words.

    • Example: If Do not write is blocked, the system will only block messages where this entire phrase appears together.

  • Special characters are treated literally

    Words containing special characters are matched exactly as written.

    • Example: If Accepted: is blocked, Nektar will block accepted: and Accepted:, but not Accepted without the colon.

  • Line Breaks, Spaces, Underscores, and Numbers

    These are accepted as valid prefixes or suffixes to the blocked words.

    • Example: If NDA is blocked, the system will also block NDA2, NDA-attached, and NDA_attached.

• Suggestion for what you should consider to screen

Special domains and email addresses

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.

• Suggestions for what you should consider to add here

<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>

Write rules

Nektar only creates records that can be linked to existing Salesforce records.

• Contacts must link to an existing account or contact via a shared, non-public domain name. Consequently, Nektar will never create contacts with public domains (such as @gmail.com).