4715 results found
-
Ability to assign ticket to customer, not contact
I want to be able to assign a ticket to a customer without choosing a contact.
31 votes -
3rd party patch management automation dynamic grouping
We came to Atera from using PDQ Inventory/PDQ Deploy and were admittedly spoiled rotten with how well that solution worked. This is in the scope of what PDQ refers to as "dynamic collections" - and this is something Atera would benefit hugely from, should they choose to go after this. I tried to keep this brief, and failed miserably - my apologies in advance, and gratitude to anyone that reads to the end ;)
For full context this video does a good job outlining dynamic collections in PDQ: https://www.youtube.com/watch?v=wVWzNhZHPV4
Here's the scenario:
We have ~50 3rd party software titles that…6 votes -
Calendar (Calendly) Scheduler
The service allows customers to easily schedule appointments with our technicians for either an in-person visit or remote repair. Similar to Calendly.com, customers can choose from the available free times in our technician's calendar to set up a convenient appointment. Once the customer selects a time, both parties will receive a calendar invite to confirm the appointment. This process ensures a smooth and efficient scheduling experience for our customers.
8 votes -
Passwords
Notes under passwords needs to be expandable. Most account have addition information and PIN's etc.
Example belowAcc#
PIN#
Serial #
Product key#
Main contact#3 votes -
Ticket Automation Rules - "ticket created" email - stop email loops
The current "Ticket Created email" automation rule works well most of the time. However, when we need to get a third-party support company involved, they often have an equivalent system that sends an automatic "Ticket Created" email, that creates a new Atera ticket, and sends back a "Ticket Created" email, ad infinitum. In our case we had 18 new tickets created in the seven minutes until we noticed the loop. If someone had not been looking at the Unattended queue, it could have been many more.
My idea is for Atera to be able to identify a "Ticket Created email"…
4 votes -
set a script-based check run interval
Be able to set the 'run interval' of a script-based check. We are running into issues battery life on laptops and hitting api limits
3 votes -
Need a device filter for assigned threshold profiles
Need a device filter added for assigned threshold profiles. We need to easily filter devices to see which may not have a threshold profile assigned at all. Or that do not have the correct threshold profiles assigned. And then be able to add them via a multi check box.
3 votes -
Custom Assets View
Custom Assets
Should be able re-organize which fields shows in the dashboard, instead of the default Name, Type, Folder and Contact.
Also an option for the date field to have an alert. For example if you are tracking support services renewals for the customer, it should alert you when renewal is within 30 days.
15 votes -
Auto install default remote with Agent
Maybe this is a bug, but I notice on the Android Mobile app (using a fully updated Google Pixel 6a) if you have not run the remote connection from a PC initially, the option to Connect on mobile is greyed out. After connecting at least once to trigger the install it works on mobile as expected.
Maybe this is how it is supposed to be, but it would be nice if the default remote got installed fully when the agent does. Often times when out remote and installing new agents, it is nice to quickly verify full connectivity from mobile…
5 votes -
show device count on customers
The customers table should show how many devices each customer has, and optionally how many are online. Bulk onboarding agents is more painful than it needs to be without this.
3 votes -
Create ticket trigger under ticket automation rules for patching
Trigger for generating a new ticket if patches are applied manually through devices tab by a technician. Seeing as this is a manual action by a technician and not done through automatic patch management it would warrant a ticket being generated for a specific agent/contact with a relevant time entry.
4 votes -
Technician Role permissions
Roles within Admin need to have the ability to have more control of what features each group has.
Under RMM, the "Edit Device" feature is too strict. We want to be able to allow certain technicians to edit device names but not be able to delete them.Setting that can be turned off so that no technicians have the ability to delete anything.
13 votes -
Customizable Availability Monitoring
The ability to get an alert if a device is offline for so long, like say an hour, instead of getting an alert for a device going offline, when it is only restarting or something similar
2 votes -
Clone scheduled ticket
Being able to clone a scheduled ticket, or bulk create the same scheduled ticket to multiple customers at the same time would be very helpful.
As simple as having a 'Save' and 'Save as New' button when editing the scheduled ticket would be a really good start.
27 votes -
knowledge base Report
Create an option to pull reports on knowledge base as to who viewed and how much times the articles was viewed
5 votes -
Mobile needs a Dashboard page
Please include a dashboard tab in the mobile app. I have no way to monitor everything from a tablet on my desk. I would like to be able to see everything and not choose ALerts or Tickets. TY!
6 votes -
Free Account User for Admin Purposes
I gather it won’t happen everywhere but certainly happens at our end (and most companies I work with); but we employ an accounts lady who handles all purchase ledger invoicing (buying a pen, paying for the supply of gas or electricity but also for Office365 or AWS) which is mostly done via our business partners portals.
So basically one (free of charge) account should be made available per company that strictly covers administrative duties limited to Atera subscriptions and licensing, add and remove agents’ licences, edit payment details such as credit card details, invoices, etc.33 votes -
Author of Knowledge Base Articles
It would be good to know the author/source of a Knowlege Base article. We have several contributors and it would be good to know the source to check validity, follow up with them for clarification, reward those that are frequent/prolific contributors of KB articles. We can already see the creation date. It should be fairly easy to add a field for Author/Creator of KBs.
1 vote -
Better structure to the KB
It would be nice if we could build a deeper KB tree. Currently it can only be two layers deep.
L1: Category
L2: Section
It would be nice if we could go at least 1 layer deeper and have subsections.9 votes -
When assigning agents to tickets, show logged in user in dropdown.
The dropdown when assigning an agent to a ticket should show the current user, as only this way we know which device has the problem (as users don't always work at the same PC)
1 vote
- Don't see your idea?