What Neo can do with Tier2Tickets
- Find the PC behind a button ticket by its hostname, or by the report that carries the ticket number
- Confirm the PC is in your Tier2Tickets inventory and which client group it belongs to, and note its online state, last seen time, agent version and MAC address on the ticket as an internal note
- Read the diagnostic report a button press filed: the user’s message and selections, the contact, and the PC’s diagnostics
- List a client’s PCs that are offline or run an old agent version
- Ask an online PC for a new diagnostic report and attach it to the ticket
- Show the user a toast notification or a popup message
- Rename the desktop icon, pin the button to the taskbar, move a PC to another group, or upgrade its agent
Your groups are mapped to companies
Each PC sits in a group, the client name your installer or the Device Management page gave it. Neo matches your groups to the companies in your PSA and keeps the mapping on the Tier2Tickets card’s Organization Mapping tab, refreshed on each PSA metadata sync. Matching uses the group name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). A nested group (CLIENTS/ACME) matches by its last part. Last comes an AI match for the long tail. NOTGROUPED, where a PC with no group sits, is never mapped.
A name match, or one you confirm, is handed straight to your agents. An AI match shows on the Organization Mapping tab, where you can confirm or correct it. A company can own several groups. A nested group (ACME/OFFICE) is mapped on its own, so a parent mapped to one client never reaches a child that belongs to another.
On a ticket that names a company, Neo sends a call only for the group that company is mapped to, and checks each PC and report it reads or acts on belongs to that group. The full group list is read only outside a ticket, such as from a chat with Neo. Neo never sends an action to every group (ALL).
Next steps
Connect Tier2Tickets
Create an API key and save it in Neo.
