Keepit

Keepit backs up SaaS data such as Microsoft 365, Entra ID, Google Workspace, Salesforce and Dynamics 365 into its own cloud. Each client is a Keepit customer account under your partner account, each protected service in it is a connector, and each backup or restore of a connector is a job. Connect Keepit, and Neo agents can work the tickets Keepit’s notification emails open in your PSA, and check every client’s backups.

​

What Neo can do with Keepit

• Connector health. Read each connector’s health (healthy, unhealthy or critical) and the reason Keepit gives, such as lost authentication.
• Backup jobs. Read backup and restore jobs with their state, errors and summary, and what a connector runs now.
• Backups and restores. Start a backup after a technician fixes the cause, and restore deleted mail or files in place.

Common uses:

• Backup alert tickets. Match a Keepit notification ticket to its connector, read its health and failed jobs, and note the cause and the next step.
• Job status checks. Report a connector’s failed or running jobs on request.
• Daily backup check. List each client’s unhealthy connectors and failed jobs on a schedule.

​

Your customer accounts are mapped to companies

Neo matches your Keepit customer accounts to the companies in your PSA and keeps the mapping on the Keepit card’s Organization Mapping tab, refreshed on each PSA metadata sync. Customer accounts under a reseller below your partner account are matched too. Matching uses the account’s company name, then its contact’s name, exact and then after stripping spaces, case and a legal-form suffix (Ltd, Inc, LLC). An AI match handles the long tail. A name two of your PSA companies share, or two accounts 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 Keepit customer account mapped to the ticket’s company, and only that account’s connectors. A ticket filed under your own company reaches no customer account, so set the ticket’s company to the client first. Calls that hold several clients’ records, such as the share link list and the audit log, are for runs with no ticket company, such as a scheduled check 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.

​

What Neo hides

Keepit answers in XML; Neo reads it as JSON and hides credentials before the agent sees an answer. Connector passwords, share passwords, token passwords, session keys, download link keys and job tokens read [hidden by Neo]. Neo refuses a write that sends that value back.

​

What always asks

Some Keepit writes always wait for a technician’s approval, whatever the agent’s settings, and some operations Neo never sends. Both lists, with the reasons, are in Safety Controls.

​

Next steps