699 results found
-
Automation based on technician reply
Currently, you cannot create any ticket automations for when an engineer replies to a ticket.
I.e set status to pending when engineer replies to ticket.
44 votes -
Place Knowledge Article in Ticket Response
We should have the ability to search and place relevant Knowledge articles as a response to a ticket that has been created.
9 votes -
Block emails from anyone who is not a contact
Create a simple option to block anyone who is not a contact or using the domain of the client company. Will help stop spam emails/tickets being created.
1 vote -
ticket notes
Clients should get details of a ticket when a ticket is created not just the ticket number the actual notes that technicians write when creating a ticket.
7 votes -
Create & Due Dates for Tickets
Add option to set a due date for a ticket.
Add Create Date and Due Date columns on the Tickets page
17 votes -
Abiltiy to add a TAG to a NEW ticket
We would like to add a TAG on NEW tickets we create
1 vote -
Ticket Description Snippet
The ability to include the initial ticket description in email templates.
4 votes -
Mobile app
It would be very interesting and very useful if the atera mobile application allows interaction with tickets so that field technicians who come to resolve incidents on site can record their times, used products and services, economically valued, and collect the customer's signature. . basically it would be interesting to be able to use it as a ticket application to close work orders on site.
3 votes -
Ticket Lock
This is essential in preventing double responses on tickets.
Ticket locking feature. Once a tech is on a ticket, all actions within the ticket would be locked for subsequent techs that visit.
That is, as long as the original tech is on the ticket or after a set amount of time while the original tech is on.
For example, Tech 1 views the ticket. Tech 2 views the ticket and it is locked. Tech 1 leaves the ticket. Tech 2 can now edit/respond to the ticket.
OR
Tech 1 views the ticket. Tech 2 views the ticket and it is…34 votes -
Add New Trigger - Custom Fields
The options to trigger automations should include a change to a custom field. These can be selected as a condition, but, we would like to use them as triggers.
8 votes -
SLA That does not require first response
Our organization does not track first response. Only requires tickets to be completed in 24hrs. It does not appear that I can set this up currently.
1 vote -
Ticket Summary
Have an editable summary pinned to the top of a ticket.
Useful for ticket notes, checklists, projects, master tickets etc4 votes -
Third kind of note in ticket that allows requestor and techinician to see it, but no email sent.
Allow a technician or requestor to post a comment that both can see, but no email is generated. This allows for information to be tracked that should not be in an email, but both parties need to see it.
1 vote -
Lock or freeze the ticket buttons at top of the ticket window.
Lock or freeze the ticket buttons at top of the ticket window.
When working with a long-standing ticket, a lot of scrolling is required to read the conversation history. It would be very help to then not have to scroll back to the top of the window to navigate to the agent or add a reply or note to the ticket.
If the six buttons at the top of the ticket window were locked in place, or in a banner at the top of the page, it would make navigation much easier.
7 votes -
Delay Sending of Response
Hi,
It would be helpful to have an option to delay the reply to a ticket. So that you can compose the reply but set it to send at time /date of your choosing. Similar to that Outlook's delayed send.
Thanks
7 votes -
Ticket Type - Tasks
Ability to assign Tasks to tickets. Most other ticketing systems do this. Ticket cannot be closed unless the task is completed (or reason entered).
For example, Backup Failed could come with a simple task that MUST be completed before the ticket can be closed... 'Successful Backup Performed'
Above is the simplest form but for a new PC installation we could add several tasks to ensure the Agent remembers to everything and bring uniformity and transparency to the customers experience with certain tasks.
29 votes -
Limit Customers from changing ticket status and types
Customers should not be able to change:
Ticket Status
Ticket Priority
Ticket Impact
Ticket TypeUnless main contact
Sure this is common sense?
4 votes -
Allow end users to attach files/images to tickets.
When creating a ticket the end user may have a screenshot of the problem they'd like to share, allowing image attachment capabilities to the API would give them the option of need be.
3 votes -
Remove '______Please Reply Above This Line______' from email preview
When clients receive an email, the preview should be the first few sentences of the body as it is on Outlook and other email clients. When technicians reply to a ticket from Atera, the users receive '___Please Reply Above This Line___' on the email preview and that just looks unprofessional as well as there is no real benefit as the user has to actually click on the email to view the body. I have been using Atera for almost 2 years and I can assure you it was better before without this preview feature.
1 vote -
Assign Ticket based on devices and not agents
Tickets for monitored endpoints - there's not a linux agent yet, but I can monitor them. However, I cannot assign them to a ticket as I can only assign actual "agents". For example, I'm monitoring a linux server, if I click the "create ticket" button the agent field is blank... because it doesn't have an agent. It would be great if I could assign devices to tickets based on the device as opposed to the agent for this reason.
8 votes
- Don't see your idea?