Black Knight Msp User Guide

Getting Started With Black Knight MSP

The platform is an MSP management tool built for smaller to mid-size IT teams. It handles ticketing, RMM integration, billing, and client documentation under one roof. Most people find it after shopping around for something cheaper than ConnectWise or Autotask and finding it roughly in that price range with a simpler interface. Setting it up takes a few days depending on how messy your existing client data is. I spent three full days just cleaning up CSV exports before importing anything. You will save yourself hours if you normalize your client names, addresses, and contact info first instead of letting the import wizard sort through garbage.

Black Knight Msp User Guide Navigation

The dashboard splits into five main sections: Dashboard, Clients, Tickets, Contracts, and Reports. That last one is honestly the weakest part. The reporting engine gives you basic ticket volume and SLA compliance metrics. If you need custom reports or drill-down analytics you will hit a wall quickly. I ended up pulling raw data through the API and building my own dashboards in Google Sheets. It took an afternoon of Python scripting but it was way better than staring at the built-in report builder. The ticketing module works fine for day-to-day operations. Creating a ticket, assigning it to a tech, updating status. Standard stuff. What trips people up is the escalation rules. They exist but they are not intuitive. You have to manually configure each rule individually through the settings menu rather than using a template. I configured about twelve escalation paths over two evenings. Once they were in place though they worked reliably.

Integrations And The RMM Side

Black Knight integrates with several RMM tools. The ones I have seen commonly used are NinjaRMM and Atera. Connecting them usually goes smoothly through the integrations tab under Settings. You paste in the API keys and the sync begins. Monitoring data, device counts, and alert histories start flowing into the ticketing system automatically. Here is something most people miss. The RMM alerts that create tickets sometimes arrive without enough context. An alert fires, a ticket is generated, and the tech opens it to see a device name and an error code that means nothing without additional investigation. The workaround I found was to modify the alert payload template in the RMM side and include the last five events from the event log in the ticket description field. This cut initial diagnosis time from twenty minutes down to roughly four for most incidents.

Pricing And Contract Setup

Contracts in Black Knight are where the platform shows its real value for recurring revenue management. You set up per-device or per-user pricing, define service level tiers, and link everything to specific clients. The billing automation runs on a monthly cycle and generates invoices automatically based on the contract terms. I ran into a problem once where a client changed their user count mid-cycle and the invoice had already been generated. The system does not automatically adjust partially-generated invoices. I had to void the original invoice and recreate it with the updated count. This cost me about forty-five minutes of back-and-forth and a phone call to the client to explain why the invoice number changed. There is a setting called "lock billing date" somewhere in the contract template area that prevents mid-cycle changes after a certain point. I set mine to lock three days before the invoice run. It eliminated that particular issue entirely.

Black Knight Msp User Guide Common Pitfalls

One thing nobody warns you about is the backup and restore process for your configuration data. The platform has an export function but the exported files are not human-readable. They are encrypted JSON blobs. When I had to restore a client database after accidentally deleting a bulk group of devices, I spent two hours trying to parse the export format before realizing there is no documented way to do it yourself. I opened a support ticket and the response came back within six hours with a manual restore. For a tool that markets itself on self-service, that was a frustrating gap. The mobile app is functional but bare-bones. You can view tickets, update statuses, and check client info. That is about it. There is no offline mode, which means if you are doing on-site work at a client with spotty connectivity you are stuck. I keep a lightweight notebook for capturing ticket details during low-connectivity periods and then batch-update everything when I am back online. It is not elegant but it works.

Support And Community

Support runs through a ticketing system within the platform itself. Response times vary depending on your contract tier. I am on the standard tier and my typical response time is four to six hours during business hours. Weekend support is not included. This is fine for internal issues but if your whole operation breaks down on a Saturday you are on your own until Monday morning. The knowledge base is searchable but sparse. I found the most useful information by posting specific questions in the community forum. The moderators are responsive and sometimes the product team chimes in with technical answers. It is not a formal documentation channel but it fills gaps the official guide leaves behind. If you are evaluating this platform against alternatives, the honest assessment is that it is solid for straightforward MSP operations. It handles the basics well without the bloat of enterprise tools. The limitations show up when you need deep customization, advanced reporting, or complex billing scenarios. For a team of five to fifteen technicians running mostly standard support contracts it does the job. Beyond that you will outgrow it.