Settings and activity
25 results found
-
7 votes
-
5 votes
-
28 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!
-
10 votes
-
3 votes
-
163 votes
-
1 vote
-
1 vote
-
3 votes
-
13 votes
-
370 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
-
1 vote
-
15 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!
-
50 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!
-
8 votes
-
5 votes
-
258 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
An error occurred while saving the comment 
Daryn Craine
supported this idea
·
-
7 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!
-
6 votes
-
132 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!
Daryn Craine
supported this idea
·
In it's basic form just adding tasks in a ticket. Either one or 10 etc. have the ability to keep adding as the need arises. Sometimes a failed backup ticket from an alert could just have a task to check to say "successful backup recorded" but agents may want to add multiple tasks so this needs to be expandable.
In a more complex form...So, to name another PSA we have used Datto/Autotask. Here they have the ability to setup templates or what they call SpeedCodes, for tickets. So selecting a 'New User Setup - Generic' template would pre-fill in the fields such as
Ticket Type: Request
Product Family: User/Mail Admin
Product: User Create/Departure
It would also create the Ticket title "New User - <Name Here>" and some pre-filled text for the description etc.
But the power really comes in those 10+ tasks it would add for the new user setup so we can make sure office juniors can check off the items as they go to setup the user and escalate what is left or we can be assured all tasks are done (with the name of the agent being added to the task to show who did it.
Additional templates could be added for more complex customers who had their own specific tasks for onboarding/offboarding.
Closing a ticket would then check if all tasks have been completed and it could not be closed (or a reason provided) if tasks not completed. So a task may be setup email on phone but the agent closes the ticket... reason for missing task, end users doesn't want company emails on their phone etc.