What Neo can do with INKY
- Find the reported message in INKY and add its verdict, detection reasons, delivery target, sender details, links and attachments to the ticket
- Confirm or reject the user’s report, apply a safe, spam or phish verdict, and resolve the report in INKY when the review is done
- Add a sender, domain or IP to a client’s block list, or allow a sender. Helpdesk asks a technician before either; IT Admin asks before an allow rule only
- Keep a client’s VIP list current, and grant or revoke INKY console roles
- Read your client teams, their protected domains and billable mailbox usage
Your teams are mapped to companies
Neo matches your INKY teams to the companies in your PSA and keeps the mapping on the INKY card’s Organization Mapping tab, refreshed on each PSA metadata sync. Matching uses the team name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Next come the email domains INKY protects for the team, against each company’s website, and last an AI match for the long tail. Organization nodes, which group teams and hold no mailboxes, are not mapped. A name match, or one you confirm, is handed straight to your agents. A domain or 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 teams mapped to the ticket’s company, so confirm a suggested match before you rely on it. 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 INKY API for the permission groups.Next steps
Connect INKY
Create an API key and save it in Neo.
