Currently the ticketing profile creates a time entry when a auto created ticket is oepened ( when a service fails). We cant auto bill clients for services failing. We bill for fixing them. AS such it would make sense to enter a time entry into the ticket before it is autoclosed due to return to normal state.
I work for a company that utilizes MSP Manager, however we cannot fully integrate with MSP Manager because the financial aspect cannot communicate with Sage. This idea request is to build an integration tool that allows MSP Manager to communicate with Sage, this will help multiple company infrastructures to streamline as they will be able, like us, to more easily manage clients, tickets, and billing in one place.
Currently we can only map sites in N-Central to the root account in Autotask. We should be able to map sites to Autotask locations.
similar to how you configure ConnectWise PSA Integration. Currently we are unable to utilize PSA integration as AutoTask has asked us not to enable it - it will cause downtime of their service every time our server syncs due to it currently trying to sync all active leads/prospects/customers instead of just customers.
The current system of selecting the correct customers for ticketing profiles is quite a hassle. When you want to add only specific customers to the ticketing profile you have to press add multiple times, until you have all the customers for which you want to configure the profile. Next you have to select all the customers that don't need the ticketing profile and delete them. A checkbox construction would be much easier ...more »
Have the ability to configure and send notifications based on the last time an agent has communicated with the NCentral server. The purpose would be to review this on a monthly basis and connect with clients about devices that are offline to help keep NCentral more organized.
I know there are filters and dashboards that can be created, but the ability to generate a PSA ticket would also be nice.
Recent Ticket Data Limit – 3 Days is too short With NCentral integrated with ConnectWise, the NCentral “Create Ticket” options are available for a device. Tickets created via NCentral will then show up in the “Recent Tickets” list for that device. However, these tickets shall only appear for three (3) days. A ticket not updated for three days will be removed from the list and placed back if updated. Three days is not ...more »
I'd like the ability to use 1 probe with multiple discovery jobs where each job would import the discovered assets into a specific site in N-Central. This would help with having the assets show up in the correct site in CW configurations and ensure that technicians can quickly see all devices in a specific site without going through any additional steps. Currently discovery jobs want a probe per site in N-Central which ...more »
If TeamViewer Host is already installed on a machine and contains a static password for example for a third party administrator, it is not possible to connect to the machine over the dashboard. This is caused by the GFIMAX password placed as second or third password in the TeamViewer host password management and the agent fails to complete the integration or to identify the GFIMAX password.
For each device in N-Central, OSInfo and OSType are written to the Notes field in the corresponding Autotask configuration item. I'd like the ability to disable this. We'd like to put our own notes for each device in Autotask, but N-Central overwrites them with each sync. The device notes field also syncs with ITGlue so those notes are overwritten as well.
Currently we have our Autotask PSA integrated with the Solarwinds RMM. We can open tickets and view tickets created from the failed check outages without having to manually search in Autotask. We need the same ability to open the link to the configuration in IT Glue. Special notes for devices should be saved in our documentation source, i.e. IT Glue, but without this, getting everyone to manually find the computer in ...more »
Would like backup integration for Mac/Linux client machines in order to not have two dashboards for managing devices.