Skip to main content
Phin Security is security awareness training for MSPs: phishing simulations, training campaigns, and a Report Phishing button in Outlook that turns a reported email into a ticket in your PSA. Connect Phin once with your Phin API client, and Neo agents can read and manage the Phin companies of all your customers.

What Neo can do with Phin

  • On a reported phishing ticket, find the user who reported the email in the customer’s Phin company, read their record for the last 12 months (simulations sent and clicked, trainings assigned and completed, up to date on training or not) and the company’s active campaigns, and write an internal note with the next step it recommends and why: ask the reporter whether they clicked, remove the email from other mailboxes, block the sender, close it as spam, or assign training
  • Answer “is this user trained?” on any ticket, from the same record
  • Add new hires to Phin, edit a user’s details, and sleep or delete leavers
  • Add a company admin, create a company, and read reports and billable users
The Phin routes Neo reads (users, their 12-month totals and active campaigns) do not name the simulation template a user received, so Neo never decides on its own that a reported email was a Phin simulation. A report through Phin’s button is never one: Phin records simulation reports itself and makes no ticket for them.

Start read-only

Pick the Read Only preset when you turn Phin on for an agent. The agent then reads Phin and changes nothing in it, so you can check its recommendations on your phishing tickets before you let it act. The Phishing Report Handler template is a good place to start: add Phin to it.

Each ticket stays with its customer

One Phin API client reaches every company under your partner. On a ticket that names a company, Neo sends a call only for the Phin company that company is mapped to, and refuses the list of every company, a new company and your partner-wide billing. A partner-wide read runs from a chat with Neo or a scheduled agent.

Your customers are mapped to companies

Neo matches your Phin companies to the companies in your PSA by name and keeps the mapping on the Phin Security card’s Organization Mapping tab, refreshed on each PSA metadata sync. A name that matches exactly one of your PSA companies, or a match you confirm, is handed straight to your agents. An AI match waits for you on the Organization Mapping tab. A name two of your PSA companies share, or two Phin companies that match one company, is left unmapped until you set it. Confirm or correct each there; a mapping you set by hand survives every later sync. See Phin Security API for the permission groups.

Next steps

Connect Phin Security

Enable the Phin API and save your Client ID, Client Secret and Partner ID in Neo.