Managed Service Providers (MSPs) send reports to build client trust by demonstrating the value they offer clients and providing transparency on how they perform against key performance indicators (KPIs) or metrics like ticket handling, device management, issue identification, system uptime, incident response times, and resolution rates.
Sending custom reports to multiple recipients can be a challenge if the company name entered in the MSPbots app varies across different integrations, leading to data inaccuracies. For example, a company entered as ABCTechSolutions in MSPbots may be registered as ABCTech in NinjaOne and ABC-Tech Company in Xero.
To send reports to multiple clients successfully, you must create a mapping relationship of company name variations and configure your datasets and widgets to use a client mapping filter. This article discusses the steps to create and send reports to multiple clients successfully.
Prerequisites
You need admin permissions to create dashboards and reports and configure the settings. If you don't have enough permissions, contact your administrator for help.
How to configure custom reports for multiple clients
1. Complete the Client Mapping settings.
Open the MSPbots app and go to Settings > Client Mapping, where you can map the company names to those set in the MSPbots app.
For instructions on how to map client names to their corresponding companies and integrations, read the article Automated Client Mapping.
Once completed, the mapping will ensure that the company names for different integrations will be associated with the corresponding company name in the app. All company updates will then be reflected on each of the mapped companies and integrations.
2. Create a company slicer in your report.
Create a dropdown company slicer with the mapped_company_name field to show the mapped companies in the Client Mapping settings.
You can browse the template datasets with the mapped_company_name field and find a dataset that is suitable to your business needs.
For information on creating slicers, read the article How to Create a Slicer in Widgets.
3. Map the widgets to the company slicer.
Edit each widget in the dashboard and map them to the company slicer you created.
-
- Go to Dashboards on the MSPbots app and open the report.
- Hover the cursor over the upper-right corner of each widget, click the ellipsis ... and Edit.
- In the Widget Builder window, go to Dataset and edit the Data Source. Click the ellipsis ... on the data source then click Edit.
- Ensure the following settings are selected in the Dataset window:
- mapped_company_name field
- Slicer checkbox
-
Client Mapping Slicer
If your chosen dataset does not have the mapped_company_name field, submit a Technical Support Request to have the field added to your required dataset.
- Refresh the report and verify if the mapping and data are correct. The report should show details for the selected company only.
Sending the custom report to clients
To share reports using the client's PSA, refer to How to Create Scheduled Reporting for Dashboards and Reports.
To send reports using an Automated Contact List, refer to Sending a Scheduled Report Using the Automated Contact List.
Template datasets with the mapped company name field
Below are the datasets containing the mapped_company_name field. Widgets and dashboards that use these datasets can be linked to the company slicer.
- Autotask Ticket Details - Layered
- Autotask Ticket History
- Autotask Time Entry Details - Layered
- Backup Radar Policies
- ConnectWise Manage Activity Data
- ConnectWise Manage Agreement Addition List
- ConnectWise Manage Configuration Data - Legacy
- ConnectWise Manage Configuration Ticket Statistics Last 60 Day
- ConnectWise Manage Contact Data
- ConnectWise Manage Service Tickets 120 Days
- ConnectWise Manage Ticket Details - Layered
- ConnectWise Manage Time Entry Last 120 Days
- Customer Thermometer Responses
- Datto RMM Machine Statistics
- Halo Actions Details - Layered
- Halo Asset Details
- Halo Feedback - Layered
- Halo Ticket Details - Layered
- IT Glue Office 365 Licenses
- Kaseya VSA Application Statistics
- Kaseya VSA Disk Statistics
- Kaseya VSA Machine Statistic
- N-Able N-Central Active Issues
- N-Able N-Central Device Patches
- N-Able N-Central Devices
- NinjaOne - OS Patch Installs
- NinjaOne - Operating Systems
- NinjaOne - Software
- NinjaOne Device Volumes
- NinjaOne Devices
- NinjaOne OS Patches Not Installed
- SimpleSat Answers
- SmileBack ConnectWise Reactions
- Sophos Endpoints
- Sophos Endpoints Data
- SyncroMSP - Ticket Timer
- SyncroMSP Machine Statistics
- SyncroMSP Ticket Statistics 210 days