What would you like to see Atera and ChatGPT do next?

@Yasmin from Atera - you asked for it 😉

1. Dynamic groups instead of, or in addition to, the current folders. You recently partnered with ESET, please check out their management console to see what dynamic groups can do. ConnectWise, Datto RMM, and N-able N-central all do this.
2. Event based scheduling. Having scripts or some kind of action occur on an event schedule: user login/logoff, endpoint startup/shutdown, wifi disconnect/reconnect, any interval of idle activity / resume from idle activity, on RMM events (this would be like when an agent goes offline/online, when an IT Automation Policy executes, or any other RMM events that occur outside the endpoint itself). Event based schedules like this exist in most other RMM providers. Again, check out ESET's management console - because of how ESET implements dynamic groups, it also inherently supports event based scheduling. Once you have an event system in place you can add those events to an endpoint's main page - this is something that NinjaOne does extremely well and greatly aids in seeing what has happened on an endpoint very quickly.
3. State management. This is something that ConnectWise and several other RMM providers do very well. With these other RMM systems, you can define the state of the endpoint as you'd like to have it - installed software, wifi profiles, power/battery profiles, auto lock/logoff, etc. When an endpoint falls outside of the desired state, it is quickly brought back into the correct state. ConnectWise in particular has a really useful software whitelist/blacklist that can trigger alerts and/or run scripts when specific software is installed/uninstalled on an endpoint.
4. IMPROVED REPORTING. Atera has lots of data, but so much of it is inaccessible to us. The basic "classic" reports are very surface-level and don't actually show me any actionable information, nor can I drill down into them. The "advanced" reports give you an updated interface and barely more information, but are certainly not worth the additional cost just to have them. Here's an actionable report I might want to see: all endpoints without SSD boot drive, or all laptops, or all laptops with a battery health < 82%, etc. Once again, look at ESET's management console for their reporting system - not only can you create custom reports with extreme detail, but on the web interface they can be drilled into. But ESET isn't the only one that can product very detailed reports out-of-the-box: ConnectWise, N-able, and Kaseya all do a fantastic job of advanced reporting - the reports are ugly as sin and they're a nightmare to create, but they contain all the data you need them to in almost any way you can imagine it.

There are lots of other things that would really make the RMM part so much more useful. Atera specific improvements might be things like:

1. Decouple tickets/contacts/endpoints (many-to-one and one-to-many relationships instead).
2. Integrate existing data points into existing functionality (like pair top processes with the sample points on the CPU and memory graphs to make them more meaningful - use your imagination, go crazy).
3. Make it easier to hunt down problems (this is very vague, and I'm sure there are a lot of ideas here, but one that would make things easier for me is to include the name of the Threshold Profile and the Threshold Item on alerts).
4. One-click "Send Logs to Atera". This is one thing that really bugs me as I occasionally have problems with the Atera agent for various reasons. Most of the time the process to collect the information that Atera needs to troubleshoot the problem requires me to interact with the endpoint(s) in question. But I don't want to schedule time to interrupt my clients so that I can collect data for my vendor to fix a problem with their software. I don't mean for this to be mean or rude, but my clients are paying me to maintain their endpoints, so it doesn't look very good when I have to interrupt them to fix a problem on my end. MSP360 does an incredible job at this - I've been using them for backup at my clients for at least 5yrs. They have a simple process to collect their own agent's logs plus a day from the Windows event logs and automatically send them to support and optionally attach them to an existing ticket. And the end user never gets interrupted.
5. Pay Dave Long for PSAtera and maintain it yourself. This is one of the most useful tools for working with Atera, but as your API changes PSAtera will need to be updated and it doesn't look like Dave has the time to do it. Syncro has their own Powershell module that is very powerful - it can do things like create tickets, add time to the ticket, run scripts from your Syncro account, send emails, upload files, etc.

Not related to RMM, but another idea is to decouple Atera add-on services from accounts where appropriate. For instance, you may have 1 person tasked with admin things - they might need access to advanced reporting and invoices from within Atera, but would not need to manage any endpoints or interact with tickets. In this case assigning a license for advanced reporting and some limited-scope user account to that user makes more sense than purchasing an all-access pass for them. Similarly, another user might be in charge of onboarding and needs access to Network Discovery, so allow Network Discovery to only be assigned to that person and not everyone. This makes the value for Atera go up because now growing MSP's aren't paying for things they don't need.

Here are some ideas that would set Atera apart because no one has these features:

1. Conditional reboot schedules based on endpoint state (like idle time or user logon status). For instance I would want to automatically reboot an endpoint after updates are installed but only if there is no user logged in. If a user is logged in, I would want to instead notify them.
2. Trend data for alerts. Alerts are generated all the time, but in what frequency, how do alerts relate to one another, are there patterns that can be realized (ie: similar time, endpoint configuration, event ID, network, etc). This would help discover root causes for issues by being able to correlate the data from multiple endpoints and/or customers to realize trends on what's happening.
3. Timeline of events that have occurred or will occur on an endpoint. For instance, when I go to an endpoint's device page it would be great to see that it was rebooted 2 days ago, then Sharon logged in, then some app was installed, then Bill logged in a day later and opened a ticket, and the endpoint is scheduled to be restarted automatically this coming Saturday due to updates applied from IT Automation Policy named "ABC". Then give me a calendar view with filters that I can adjust to show me what's happening on the endpoints now and in the future. This can help with finding downtime, planning large software deployments, onboarding/offboarding, etc. All of this information is currently present in Atera but it requires so much hunting and browser tabs to get to!

Honestly, I feel like there are so many other areas that Atera can focus on to make it an excellent RMM and PSA platform, and none of those areas include ChatGPT and 3rd party integrations. This is all core platform stuff.