- or
No existing idea results
- ~ No ideas found ~
4720 results found
-
Dateien an Ticket hinzufügen
It would be convenient if files could be attached to a ticket.
A current workaround is to create an internal note and then attach the file, but then it becomes necessary to search for the file in the ticket history whenever the ticket becomes longer.1 vote -
ticket activity messages
I think it would be very useful that ticket's history section reflects which Rules has been applied (appearing on history as the rule's title), and not just the action. This would work as a kind of "debug", helping us to confirm which rules are really applied on each scenario and accelerating/helping a lot our learning curve.
1 vote -
link to a ticket on mobile opens the app rather than web page
When you receive an email and it contains a link to a ticket, tapping the link should check if the app is installed and if it is, open it to display the ticket.
14 votes -
Alerts for new ticket and ticket replies
You know how alerts will play a sound when it happens? That would be great if you could make tickets do the same thing. If someone creates a ticket I would like to be able to turn on a sound notification just like the alert sound settings. I already get ticket notifications on my phone so I do not feel like this is would be hard to integrate into the web dashboard.
1 vote -
Agent chat
Please make an option to disable and enable automatic ticket creation the Agent chat that create ticket after two minutes of conversation.
Please, We want to chat with the user and leave the user create the ticket or the IT to create the ticket manually.
We need this option to interact with the user with no limit, please make this happened.
1 vote -
misfunction on Action "Send email to Technician"
Misfunction detected on following scenario:
Rule Trigger: Ticket Requester Responded
Conditions: no conditions
Action: Send an Email To TechnicianThis action only works when just one of the implied users is a Technician. But when implied users are both Technicians, this action doesn't works.
I identified this as a misfunction because on complex helpdesk structures it's needed one Technician to create an incident specifically for other higher level Technicians (incident not related with any "normal" requester, but specifically for internal IT troubles between different Technicians). This way, the important thing here is not related with the Requester role in any way, but the email of AssignedTechnician in order to execute the action correctly.
Misfunction detected on following scenario:
Rule Trigger: Ticket Requester Responded
Conditions: no conditions
Action: Send an Email To TechnicianThis action only works when just one of the implied users is a Technician. But when implied users are both Technicians, this action doesn't works.
I identified this as a misfunction because on complex helpdesk structures it's needed one Technician to create an incident specifically for other higher level Technicians (incident not related with any "normal" requester, but specifically for internal IT troubles between different Technicians). This way, the important thing here is not related with the Requester role in any…
1 vote -
i18n on mail Templates vs Rules
The current implementation on Email Templates vs rules makes it difficult to manage a multilanguage scenario. For N templates representing the same notification in different languages, it's needed to generate 1 rule for each language in order to respond the Requester in an appropiate way on their language. In our case, with an international sctructure of different departments abroad, it's implying an enormous collection of rules than, in essence doing exactly the same thing but in different languages.
I think would be very useful to develop i18n characteristic on email templates vs rules, as explained:
- 1:N relationship on "1 template target topic" : "N language implementations".
- Related views grouped by "Target topics".
- If so, just 1 rule will be needed to manage multilanguage scope about an specific trigger. I mean, when I create rule, Atera will implicitly manage "reaction to" multilanguage scenario, always based on the language of Requester on their profile. An example: For an specific Rule "X", when Atera notifies to the Requester (or Technician), it will evaluate the language on his profile, and will make use of templates for this language.
The current implementation on Email Templates vs rules makes it difficult to manage a multilanguage scenario. For N templates representing the same notification in different languages, it's needed to generate 1 rule for each language in order to respond the Requester in an appropiate way on their language. In our case, with an international sctructure of different departments abroad, it's implying an enormous collection of rules than, in essence doing exactly the same thing but in different languages.
I think would be very useful to develop i18n characteristic on email templates vs rules, as explained:
- 1:N relationship on "1 template…
1 vote -
Tab based system to view tickets
When you click on a ticket to read it, it opens it in a tab at the top of the screen and pauses time tracking for every ticket except the one you are viewing.
This would be useful for comparing information between tickets without having to open multiple browser tabs.
1 vote -
Audit Log via API
The ability to access Audit Log from API or atleast export and send via email on a schedule.
9 votes -
Simplify Logon process on MobileApp
Please simplify logon process for the mobile app (iOS).
It should work like in other apps where you just open the app and do Face-ID, no fiddling with entering email-address and clicking through a lot of pages. This is a real inconvenience when you want to quickly react to a push notification/alarm!
27 votes -
Dynamic Dropdown
Have the Ability to have a Dropdown that is Dynamic for example if I wanted to add a custom dropdown on a user where I can set their manager I can create a custom dropdown where it lists all the users in my account for me to select. This can even be extend to Dropdown with dependences where I can limit/group the users by site.
5 votes -
Change Customer Notes to a multi-line text block
As it is now, the Notes feature in the Customer view is nearly useless. Having to type everything separated by commas or slashes is an ugly solution to a problem that shouldn't exist.
Please let us create multi-lined notes within that block so we can use it more efficiently. And please, allow us to separate notes by pressing Enter to insert new lines.
5 votes -
Splashtop Headless Support
Splashtop appears to support headless displays, but not the version within Atera. Request to upgrade Splashtop within Atera to support Headless displays as that trend continues to grow.
5 votes -
On devices page have a relationship (contact) column and customer column to show who the device belongs to.
On the devices list, show a column for what contact and customer that devices belongs to.
The relationship field is important and this uses the contact details for who this device belongs to, some devices are being logged into as a generic username or maybe being logged into using old details, therefore for the username field can be unreliable.
5 votes -
Bread Crumb Trail
Would be a nice feature to have a bread crumb trail at the top of the window for navigating up one more more levels.
In some instances within sites or reporting, the back button is not useful. Only option is to go back to the left menu and start from the main menu item.
5 votes -
View Button in Knowledge Base
When attaching images in the Knowledge Base, The only option is to download or delete the attachments. It would be nice to view the images and see what has been attached instead of downloading it locally to the computer.
5 votes -
Add e-mail signature manually
There currently is no way to add the e-mail signature again once it's been deleted.
It would be nice to be able to simply click a button to get it back, instead of having to go back to the ticket list and opening the ticket again.
Even better:
the ability to choose between several signatures4 votes -
Define Standard Device Folder Structure For multiple/all Customers
I would like to create a "default" Device Folder Structure that can be deployed to all or multiple customer without recreating it every time.
2 votes -
Battery Info (API and Report)
Please add the following info to the classic report and more importantly the API export functionality.
Battery ID
Battery Health
Battery Design Capacity
Battery Full Charge Capacity
Battery Cycle CountThis info is available in the agent page for specific agents but being able to export it to a CSV would allow us to know, on mass, which devices have "x" low battery health and need replacing!
4 votes -
Scheduled Ticket Reply Functionality
Idea Overview:
The core of this proposal is to introduce the capability for users to draft ticket replies and schedule them to be automatically sent at a later time. This feature would be invaluable for managing communication outside standard business hours, allowing for strategic planning of responses to ensure they are delivered at the most appropriate times without manual oversight.
Benefits:
Improved Efficiency: Users can manage their workload more effectively by drafting responses when convenient and scheduling them for optimal delivery times.
Enhanced Work-Life Balance: This feature supports a healthier work-life balance by accommodating work schedules, especially for those who prefer or need to work outside traditional hours.
Client Satisfaction: Scheduled replies can help maintain timely and consistent communication with clients, improving their overall experience and satisfaction.
Operational Flexibility: It adds a layer of flexibility in handling tickets, enabling a more strategic approach to communication and workload management.
Implementation Consideration:
We understand that new features require careful planning, development, and testing. However, we believe the scheduled ticket reply functionality aligns well with Atera's commitment to enhancing user experience and operational efficiency. It could be integrated into the existing ticketing system with options to set specific dates and times for each reply's delivery.Conclusion:
Adding a scheduling feature for ticket replies could be a game-changer for many Atera users, offering a new dimension of control and efficiency in managing client communications. We are excited about the potential benefits this feature could bring to the Atera platform and its user community.Idea Overview:
The core of this proposal is to introduce the capability for users to draft ticket replies and schedule them to be automatically sent at a later time. This feature would be invaluable for managing communication outside standard business hours, allowing for strategic planning of responses to ensure they are delivered at the most appropriate times without manual oversight.
Benefits:
Improved Efficiency: Users can manage their workload more effectively by drafting responses when convenient and scheduling them for optimal delivery times.
Enhanced Work-Life Balance: This feature supports a healthier work-life balance by accommodating work schedules, especially for those who…
1 vote
- Don't see your idea?