What Neo can do with Mimecast
- Find a reported phishing email and judge it from Mimecast’s link, attachment and impersonation results, then write the evidence and its verdict on the ticket
- Find an email Mimecast held and the reason, then release or reject it
- Block a sender or a malicious link, and permit a wanted one
- Remove a malicious email from every mailbox it reached
- Read and change policies, users and groups, domains and DMARC Analyzer settings
Your Mimecast accounts are mapped to clients
Neo matches each Mimecast customer account to a client in your PSA and keeps the mapping on the Mimecast card’s Organization Mapping tab, refreshed on each PSA metadata sync. With the mapping, an agent works in the right client’s Mimecast account by its account code. Matching starts with the name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Then come the account’s own mail domains in Mimecast, against the website on a PSA company. Neo skips a free-mail domain, anonmicrosoft.com domain and a domain that two accounts share. Last comes an AI match for the long tail.
A name match, or one you confirm, is handed straight to your agents. A domain match or an AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it.
Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right client by hand. A mapping you set by hand survives every later sync.
Next steps
Connect Mimecast
Create an API 2.0 credential in Mimecast and save it in Neo.
