What Neo can do with usecure
- When a user reports an email, check usecure for a course, policy or phishing simulation it sent that user at that time, and answer the user: genuine training to complete, a phishing test, or suspected phishing to handle
- Add a new starter as a learner, put them in their groups and enrol them on courses and the gap analysis
- Mark a leaver inactive, which keeps their training history, or delete a learner
- Send a policy to learners to sign, and see who has not signed
- Read course results, phishing simulation results (who opened, clicked, entered data or reported), breached accounts and each client’s risk score
- Invite and remove the client contacts who sign in to the usecure console, and change a client’s plan or settings
Your clients are mapped to companies
Neo matches your usecure client companies to the companies in your PSA and keeps the mapping on the usecure card’s Organization Mapping tab, refreshed on each PSA metadata sync. Matching uses the company name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Next comes the domain the client signed up to usecure with, against each company’s website, and last an AI match for the long tail. Prospects 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 usecure company 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 usecure API for the permission groups.Next steps
Connect usecure
Copy your usecure API key and save it in Neo.
