What Neo can do with Axcient
- Find the protected system a backup alert ticket names, and read its backup jobs and each job’s runs: success or failure, the error, and the bytes backed up
- Read each AutoVerify boot test: whether the system booted, the heartbeat, the disk check, VSS and the screenshot
- List restore points by vault, and which ones are mounted now for a restore or a virtualization
- Report each client’s backup health, failed jobs, data backed up, storage use and last AutoVerify on a schedule
- Read x360Cloud backup status for Microsoft 365 and Google Workspace, x360Sync activity and sharing, and your billing usage
- Change a vault’s connectivity threshold. Helpdesk and IT Admin ask a technician first
Your clients are mapped to companies
Neo matches your x360Recover clients to the companies in your PSA and keeps the mapping on the Axcient card’s Organization Mapping tab, refreshed on each PSA metadata sync. Matching uses the client name, exact and then after stripping spaces, case and a legal-form suffix (Ltd, Inc, LLC), soAcmeLaw matches Acme Law. An AI match handles the long tail. A name two of your PSA companies share, or two clients that match the same company, gets no name match: at most an AI suggestion, which waits for you to confirm it.
A name match, or one you confirm, is handed straight to your agents. An 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 x360Recover client mapped to the ticket’s company, so confirm a suggested match before you rely on it. x360Cloud, x360Sync and billing hold every client’s data, so agents read them only outside a ticket, such as in a scheduled report or a chat.
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 Axcient API for the permission groups.
Next steps
Connect Axcient
Create an API key and save it in Neo.
