What Neo can do with Mesh
- Search a client’s inbound and outbound mail in the Live Email Tracker by sender, sender domain, recipient, subject or Message-ID, and add each message’s verdict and status to the ticket
- Read why Mesh held a message: its event log, the rule or policy that decided, and a preview of its text
- Answer “did we get anything from example.com?” with the list of messages from that domain and what Mesh did with each
- Release a quarantined message to the user, or delete, report, remediate or undo remediation. Helpdesk asks a technician before each one
- Allow or block a sender or domain for a client or for one user. Helpdesk and IT Admin ask before an allow rule
- Read and manage customers, domains, custom rules, policies, users, reports and the audit log
Your customers are mapped to companies
Neo matches your Mesh customers to the companies in your PSA and keeps the mapping on the Mesh card’s Organization Mapping tab, refreshed on each PSA metadata sync. Matching uses the customer’s company name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC), and last an AI match for the long tail. A name match, or one you confirm, is handed straight to your agents. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it. On a ticket, an agent reaches only the Mesh customer mapped to the ticket’s company. Before it releases a message or changes a rule, Neo reads from Mesh that the message or rule belongs to that customer. Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync. See Mesh API for the permission groups.Next steps
Connect Mesh
Create an API key and save it in Neo.
