- or
No existing idea results
- ~ No ideas found ~
5065 results found
-
Delete everything Atera when a client is lost.
When losing a client there should be a way to delete EVERYTHING; Atera agent, Splashtop, AnyDesk, and any apps purchased through Atera, This should work for any unit online and for any off-line unit when it comes back online, without disturbing the client's users.
14 votes -
Show active Network adapter
It would be great to see under the hardware heading which network adapter is currently active and what the in/out metrics are. Our remote users are instructed to use the ethernet cable we provide but some try to get away with using their wifi connection, which is not robust or reliable enough for our proprietary software.
2 votes -
shortcut
Customize the default shortcut Ctrl + F12 to post a ticket
2 votes -
Intune
Provide a UWP app for Intune AutoPilot for MDM and deployments over the cloud.
16 votes -
Lineup tickets / requestor advise
When a "requestor" adds a ticket in the system, it is quite very helpful to be advised by the number of already opened tickets in the system , so he/she will know how many cases the technicians have to deal with before start working to theirs.
1 vote -
billing email address
Can we please have a different Billing email address to the primary contact email address?
12 votes -
Generic or branded agent name
Agent should be generic name or allow branding
White Label branding is in nearly all competitors products to allow branding! Atera should also allow customizing and branding or generically displaying the install program name and folder name, as well as in the Apps and Add Remove Program Files.
Instead of “Atera” under Program Files or Program Files (x86), or the Apps and Add Remove Program files use something like "ITSupportAgent" or “CompanyNameSupport” Customers see the Atera program and do not know it and uninstall it. If it was the IT department or service providers name they would recognize it.
Branding of the agent should follow through from the install program, folder names, program name and add remove programs or Apps. The agent should really have no mention of Atera unless a person opts to.
This would very extremely beneficial to both in house IT departments and It service providers.
Agent should be generic name or allow branding
White Label branding is in nearly all competitors products to allow branding! Atera should also allow customizing and branding or generically displaying the install program name and folder name, as well as in the Apps and Add Remove Program Files.
Instead of “Atera” under Program Files or Program Files (x86), or the Apps and Add Remove Program files use something like "ITSupportAgent" or “CompanyNameSupport” Customers see the Atera program and do not know it and uninstall it. If it was the IT department or service providers name they would recognize it.
Branding…
14 votes -
API Feature
Is it possible to allow the current API ton include Serial Number, Device Manufacturer, or Device Model.
4 votes -
Text box drag to enlarge
I don't like how the text box, when typing notes/replies, has to either be Fullscreen or letterbox style.
I just want to be able to drag the text box to make it longer, rather than have to bounce in and out of Fullscreen.
2 votes -
Chrome OS
The ability to install RMM software on Chromebooks and other ChromeOS devices.
27 votes -
Permission option to close other tech ticket
Currently there is a permission option to view other technician ticket but there should be an additional permission (on and off) for a technician ability to close tickets that don't belong to them.
SLA, time entry and CSAT are linked with ticket owner and tech should not have the ability to close ticket on behalf of another technician. Only team leader or Admin should have this ability. We want all our tech to view all tickets, as when a customer calls and if the tech is not available, they can provide update to client. But technician should be restricted from closing other technician's ticket.Currently there is a permission option to view other technician ticket but there should be an additional permission (on and off) for a technician ability to close tickets that don't belong to them.
SLA, time entry and CSAT are linked with ticket owner and tech should not have the ability to close ticket on behalf of another technician. Only team leader or Admin should have this ability. We want all our tech to view all tickets, as when a customer calls and if the tech is not available, they can provide update to client. But technician should be restricted from…5 votes -
2 votes
-
System to handle email notifications to copied recipients on tickets, not rely on "Reply All" from email client
No notification sent to copied parties on ticket if primary customer does not use "Reply All" when they respond to a ticket via email or if they delete email recipients from email response.
You cannot rely on the customer to click on "Rely All", if you do and there is another party that needs to be included for example an escalation with their manager or a "cover your butt side", they will not receive the communication reply to the ticket.
I have had a recent incident whereby the primary removed their manager from the "Reply All" email, so it wasn't sent to them. Upon liaising with the manager, I found that they didn't receive the last response and had no idea what I was talking about as they had been dropped by the primary user from the email.
To constantly check if "Reply All" is being used or to go through and configure Outlook clients to do this by default is a lot of extra work from the tech side.
As an example of how other systems work, accounting systems.
If I respond to the system's email, the email hits the system, the entry is made and any user that is attached to the invoice/ticket will be sent my response from the system. That to me makes more sense.With Atera there is no control of the communication workflow.
No notification sent to copied parties on ticket if primary customer does not use "Reply All" when they respond to a ticket via email or if they delete email recipients from email response.
You cannot rely on the customer to click on "Rely All", if you do and there is another party that needs to be included for example an escalation with their manager or a "cover your butt side", they will not receive the communication reply to the ticket.
I have had a recent incident whereby the primary removed their manager from the "Reply All" email, so it wasn't…
1 vote -
Help Desk Administrator
Atera should have additional billable (or free...) roles other than technicians. We have project managers & help desk admins that do not provide technical support.
We don't use Atera's ticketing because our admin staff would cost us an extra $300/month just for them use the help desk, nothing else.
We would love a discounted "role" of a "Help Desk Manager" who like a technician has granular access to help desk tickets per assigned client. But that's all they can do.
We have someone that can manage tickets, assign tickets, but do not have to be a full $150/month agent since they're not using 90% of the software.
Atera should have additional billable (or free...) roles other than technicians. We have project managers & help desk admins that do not provide technical support.
We don't use Atera's ticketing because our admin staff would cost us an extra $300/month just for them use the help desk, nothing else.
We would love a discounted "role" of a "Help Desk Manager" who like a technician has granular access to help desk tickets per assigned client. But that's all they can do.
We have someone that can manage tickets, assign tickets, but do not have to be a full $150/month agent since…
10 votes -
Approval for knowledgebase
Have the ability to set approval workflow for articles in knowledge base. Suggested status would be: "For approval", "Approved", "Rejected".
"For approval" and "Rejected" shouldn't be visible in customer knowledge base in customer portal, but "For approval" should be visible in internal knowledge base in Atera, for selected roles. Admin-roles should be able to see everything in Atera.Also be able to set who can approve and who can submit for approval, lets say for internal knowledge base Tier 1 technician can only submit, but admin can approve and reject. For customer knowledge base selected customer end user (preferably IT-manager) can approve articles together with admin.
Have the ability to set approval workflow for articles in knowledge base. Suggested status would be: "For approval", "Approved", "Rejected".
"For approval" and "Rejected" shouldn't be visible in customer knowledge base in customer portal, but "For approval" should be visible in internal knowledge base in Atera, for selected roles. Admin-roles should be able to see everything in Atera.Also be able to set who can approve and who can submit for approval, lets say for internal knowledge base Tier 1 technician can only submit, but admin can approve and reject. For customer knowledge base selected customer end user (preferably IT-manager)…
5 votes -
Automatically install ONLY defender security updates
Automatically install ONLY defender security updates so we can create a patch automation just for this. It would be super handy for clients who don;t have the money to buy paid antivirus and adds value to us as their support solution.
4 votes -
Bitdefender needs to have an uninstall password DURING deployment.
Bitdefender needs to have an uninstall password DURING deployment. I spoke with BitDefender and they said to allow local management and then add the password and then change it back to cloud managed. Not having this functionality in the cloud to set per customer is unacceptable.
4 votes -
Multiple email addresses for a single user
Having a single email address for a user account leads to fragmentation of the helpdesk ticketing system. For example, a person working from home may not have access to their work email (associated to a user account in Atera), and may need to create a helpdesk ticket using their personal email. The fragmentation of the ticketing system happens where their user account associated with their work email will not have the tickets that come in with their personal email. The user will also need to manage two accounts in Atera, one for their work email and one for their personal email.
Having a single email address for a user account leads to fragmentation of the helpdesk ticketing system. For example, a person working from home may not have access to their work email (associated to a user account in Atera), and may need to create a helpdesk ticket using their personal email. The fragmentation of the ticketing system happens where their user account associated with their work email will not have the tickets that come in with their personal email. The user will also need to manage two accounts in Atera, one for their work email and one for their personal…
8 votes -
MS Defender Report
I'd like to create a report that shows the results of the last MS Defender scan. I can do it for an individual pc by running Get-MpComputerStatus in Powershell, but it doesn't look very good and I have to do it for each individual pc. Being able to run a report for every monitored pc in each clients office would be nice.
5 votes -
Make a larger selectable area around the check box
A lot of spurious tickets and alerts get created and are intermingled among legitimate tickets and alerts. Selecting all, although easy, is out of the question. While clicking through several tickets and alerts quickly, the check box is easily missed. The check box size itself is fine, but it would be nice if the hot spot around the check box were larger.
1 vote
- Don't see your idea?