Settings and activity
36 results found
-
136 votes
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
Esmeil Naqeeb
supported this idea
·
-
238 votes
Nice! The feature you requested is being considered for development. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
Esmeil Naqeeb
supported this idea
·
-
296 votes
Hey all,
We're considering the development of this feature in the coming months and would love to hear how you'd like to see checklists implemented in Atera.
If you'd like to discuss your needs, please schedule some time for a call here:
https://yakov-atera.youcanbook.me/
All the best,
Yakov
Esmeil Naqeeb
supported this idea
·
-
401 votes
Hey all,
We're excited to announce that we're exploring the development of a new feature focused on ticket queues and assigning technician groups in Atera.
Your feedback will be invaluable as we shape this feature to meet your needs and preferences.
If you'd like to provide input on this feature, please schedule some time for a call using the link below:
Your insights and suggestions are essential to us as we continue to improve and innovate within Atera.
All the best,
Yakov
Esmeil Naqeeb
supported this idea
·
-
56 votes
Hey all,
After speaking to many of you and designing this one together, I'm happy to announce we are now beta-testing a new feature focused around technician groups/ ticket queues
The new module allows:
- Creating technician groups for better team organization
- Assigning tickets to groups for efficient workflow
- Filtering and creating custom ticket queues to manage priorities in the tickets list
- New ticket automation rules improvement with new triggers, conditions, and actions
Some use cases for this new feature are:
- Auto-assigning tickets to queues based on conditions
- Notifying admins on escalations
- Round-robin ticket distribution between group members
We hope to finish beta testing and release the feature to all customers soon, we'll be sure to update you once that happens!
Yakov
Esmeil Naqeeb
supported this idea
·
-
61 votesEsmeil Naqeeb
supported this idea
·
-
29 votes
An error occurred while saving the comment Esmeil Naqeeb
supported this idea
·
-
7 votesEsmeil Naqeeb
shared this idea
·
-
1,478 votes
Hello, Thanks so much for submitting your idea! It’s currently under review by our product team, and should a decision be reached to develop it, we’ll keep you in the loop!
Esmeil Naqeeb
supported this idea
·
-
104 votesEsmeil Naqeeb
supported this idea
·
-
170 votes
Hello, Thanks so much for submitting your idea! It’s currently under review by our product team, and should a decision be reached to develop it, we’ll keep you in the loop!
Esmeil Naqeeb
supported this idea
·
-
212 votes
Hello, Thanks so much for submitting your idea! It’s currently under review by our product team, and should a decision be reached to develop it, we’ll keep you in the loop!
Esmeil Naqeeb
supported this idea
·
-
1,750 votesEsmeil Naqeeb
supported this idea
·
-
12 votesEsmeil Naqeeb
supported this idea
·
-
3 votesEsmeil Naqeeb
shared this idea
·
-
966 votesEsmeil Naqeeb
supported this idea
·
-
80 votes
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
Esmeil Naqeeb
supported this idea
·
-
10 votes
Hello, Thanks so much for submitting your idea! It’s currently under review by our product team, and should a decision be reached to develop it, we’ll keep you in the loop!
-
5 votesEsmeil Naqeeb
supported this idea
·
-
14 votes
Hi,
I’d like to suggest a possible improvement that could help streamline ticket handling when multiple recipients are included in the initial email. Currently, the system creates separate tickets when someone replies with the helpdesk email still in CC, as the original tracking number isn’t included. A way to match these replies to the existing ticket could prevent this issue from recurring. Here’s a suggestion for your development team that may help:
1. Track the Original Message-ID: When the helpdesk system receives the initial email and generates a ticket, it could record the email’s unique Message-ID. This ID is referenced in replies, even in cases where users "reply all," making it possible to link each response to the same ticket.
2. Match Using In-Reply-To and References: If Atera could use the In-Reply-To or References headers for replies, it could match emails back to the original ticket by recognizing the original Message-ID. Since the replies from CC’d recipients will contain the In-Reply-To field with this ID, the system could use this as a reference for threading back to the correct ticket.
3. Automated Matching Option: If not currently possible, an additional setting to automate this header-based matching could prevent new tickets from being created when recipients reply to the initial email with the helpdesk still CC’d.
This approach could allow Atera to handle replies in a more flexible way, ensuring that all related messages stay within the original ticket, regardless of who is CC’d or who replies.
Thanks,
Esmeil