What Neo can do with CyberQP
- Verify a caller before a password reset or an account change: Neo sends the end user a CyberQP push, and CyberQP adds the result to the ticket
- Give a technician temporary admin rights at a customer for a ticket: Neo creates or enables a JIT account under your JIT policy, for the duration you allow, and disables it when the work is done. Creating or enabling a JIT account always asks a technician first
- Find a customer in CyberQP with its agent GUID, and hand the install token and GUID to your RMM’s CyberQP install script
- Read an account’s password or a JIT account’s OTP code for a technician who asks in chat. Each read always asks a technician first
- Check CyberQP’s audit events: who verified, elevated or read a password, and when
Your customers are mapped to companies
Neo matches your CyberQP customers to the companies in your PSA and keeps the mapping on the CyberQP card’s Organization Mapping tab, refreshed on each PSA metadata sync. Agents then read a customer’s accounts and JIT accounts by its CyberQP id, with no search by name. Matching uses the customer name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the long tail. An exact name that matches exactly one of your PSA companies, or a match you confirm, is handed straight to your agents. A mapping gives an agent that customer’s accounts and passwords, so every other match waits for you on the Organization Mapping tab: a match after stripping a legal-form suffix, a name two of your PSA companies share, two CyberQP customers on one company, and an AI match. Confirm or correct each there. 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.Next steps
Connect CyberQP
Create CyberQP API credentials and save them in Neo.