709 results found
-
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 -
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.
40 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 -
Ticket list shows title as "#1234 Ticket Title", open ticket shows title as "#1234 Ticke but a search shows results as "Ticket Title #1234 "
Ticket list shows title as "#1234 Ticket Title".
Open ticket shows title as "#1234 Ticket Title".
But search result shows as "Ticket Title #1234", search should instead show "#1234 Ticket Title".3 votes -
Additional options when entering a ticket, "Add and Resolve"...
When adding a ticket rather than just "add" the ticket, could we get another option to "add and resolve". This helps when entering tickets after the fact, we would not have to go back in and resolve...
Thanks, Phil
3 votes -
Add indicator on ticket that a remote session is active or when the last remote session was held
Either somewhere on the ticket, indicate who is currently viewing the ticket (or who has most recently viewed the ticket) or something indicating a tech is currently remoted to that device. For example, I had an urgent ticket come in and I reached out (via external communication) to a specific tech to address the ticket. By looking at the ticket I can see in he's assigned the ticket to himself and asked the contact for permission to remote to her computer. She responded and now I don't know what is going on (and because they are gold customers and a…
4 votes -
Unique calendar integration per technician
Today, the integration is for 1 calendar per account - making us use a shared calendar
9 votes -
Ability to assign a device to a ticket regardless of contact
So recently we discovered that when you assign a device to a ticket, it assigns that same device to any ticket associated with the ticket contact. So let's say you have 4 tickets open for the same user, if you assign a device to one of those tickets, Atera assigns that same device to all of that user's tickets.
This is problematic for may of our clients because we have quite a few clients that utilize multiple systems whether it be they have a desktop and a laptop or sometimes it may be something like a multi-user device where the…
22 votes -
open ticket directly after creating
When creating a ticket after saving it open the ticket directly, instead of having to go and select it from the ticket queue.
1 vote -
Editing Existing Cases
Please can you add the below feature to the Helpdesk - Editing an existing case.
We find ourselves updating incorrect cases, E.G – Case 2149 is assigned to Tech A but updates Case 2148 which is assigned to Tech B. Unfortunately, we cannot remove this update thus having to re-create both cases.1 vote -
Time sheet including in ticket communication so customers can view the work!
Time sheet should be in ticket for customer to read !!
Now the customer have to guess what kind of work we've done for them.
Or wait until we make a report. The actual work done should be in the ticket for the customer to read! Just as part of the conversation.4 votes -
Show previous calendar events as well as future ones on a ticket
When adding calendar events to a ticket, it would be helpful to also be able to see all past calendar events. Being able to set a default subject of the calendar event would also be helpful along with the customers name.
1 vote -
Remember recently used email addresses
It would be nice if the ticket emailing system would remember past email addresses used in the CC section etc...
1 vote -
Ticket documentation // automatic knowledgebase
Current setup:
A user can raise a ticket which will be handled by the supporter.
When the problem is solved then the ticket will be closed.
The customer can view all old tickets from himself (except he is the main contact) through the customer portal.Problem:
Quite often you get tickets like "Word does not start". Then you perform your troubleshooting and guide the user to a problem which you already had 3 times before.
At some point in time you think about creating a knowledgebase article about it so the user can find it.
Knowledgebase article do have a…3 votes -
I don’t want all incoming emails to create contacts in Atera.
I don't want all the contacts to be created in Atera.
Ideally an email with a known domain would open a ticket under the specific customer, otherwise it would be under unassigned. There should be no mandatory requirement for creating contacts to open a ticket.I don’t need all these contacts and I will lose my main contacts visibility.
1 vote -
Create Custom Tags
Being able to create our own custom tags for ticket automation would be very beneficial. Setting a tag using ticket automation rules is already possible, so this addition would be a huge improvement.
18 votes
- Don't see your idea?