745 results found
-
Ticket SLA warning
It would be really helpful if we could set up an automation rule that would alert us if a ticket is going over a certain SLA. Our SLA is 4 hours and so the system should be able to send an email to us - or a designated manager - to alert them of the fact.
17 votes -
Contact Last Comment variable with attachments
Add the attachments of the last comment when sent with the variable Contact Last Comment.
1 vote -
ticket status change
Ticket automation to change status of "resolved" to "closed" within a specified amount of time. Would like the ticket status to change automatically.
8 votes -
User email ticket updates to include subject
Users sometimes email in with info only in the subject, or they set out of office with no info in the body. If this occurs all we see in the ticket is a blank entry.
Solution would be to include the email subject.2 votes -
Ticket organisation
It would be helpful to have a ticket target date visible on the dashboard which can be used to sort and filter tickets by their due dates. This could then be developed to flag tickets which sit with predefined timescales (e.g. Due in 7 / 5 / 3 days) and change the colour of the ticket (e.g. green / amber / red) to draw attention to it.
6 votes -
Assign ticket to Customer Location/Folder
Customers have different locations (Folder in Atera Case), need to assign ticket based on customer location
1 vote -
Bulk Reassign Tickets to Agent
We could do with a system to bulk reassign a number of tickets from one contact/agent to another, this way we can easily keep old tickets for records and remove old contacts without losing their tickets or having to reassign potentially hundreds of tickets individually.
1 vote -
helpdesk agent improvement
Ability to add custom drop down options for the status of tickets. This will allow to use Atera as project management tool as well.
3 votes -
create ticket with remote connect to customer computer
Having a ticket automatically created when a tech hits the Connect button to remotely login to a customer machine. There are times when a tech will connect to a computer to do or check something when there is not already a ticket created. Having a ticket automatically created or opened to fill in by the tech any time they connect would keep them from forgetting to track their time or documenting what they do. We are still using GoToAssist for remote support and at the end of each session a box pops up for the tech to fill in notes…
8 votes -
Ticketing Task Manager
For example let’s say you have a large project that exists as a ticket such as updating a hosted application. This would include several tasks such as updating the application on the server and then updating the client application at your business locations across the country.
Atera could have a ticket that will act as a parent (For this example it will generically be called Update Application)
Update Application could be assigned to a manager so they can monitor the ticket and create the child tickets update server, update computers at HQ, update computers at branch 1, update computers at…9 votes -
When opening a ticket from an agent, that agent should be automatically assigned to the ticket.
When creating a ticket from an agent, it does not set that agent in the ticket.
The agent is automatically set based on which contact is selected when creating the ticket. (I have just confirmed this is the case with support)There is also no Agent menu on the New Ticket page, so technicians need to open the ticket again after creating it to correctly set the agent.
Contact and Agent should be independent as often we need to clear changes (buying software, hardware upgrades, etc.) with some form of management -be it business owner or their finance department- before…
17 votes -
Add ability to delete tickets through ticket automation
Add the feature to delete certain tickets through ticket automation based on certain automation rules.
3 votes -
Customer vs. technician update
Cannot appear to differentiate between a customer update and technician update in a ticket. The “Ticket Contact Responded” trigger actions on both tech update and customer update.
4 votes -
Ticketing Product Family Automations
We offer a variety of services and not all customers have all of our services so it would be good to show/hide product families dependent on the customer.
We can then setup alot of automations depending on what product family is selected. For instance we offer, IT services, cyber security services, hosted phone & broadband services.
As an example we might setup automations if a customer selects an option within our "Hosted Phones" product family, but if a customer doesn't use us for their phones then we don't want them to see that product family.
This would open up a…2 votes -
Option to unlink Contact from Agent
Currently, if there are multiple Tickets open from one Contact, and the Agent is changed on one, it is automatically changed on the other. This causes issues in three cases.
1- If there is a main Contact for a Customer that all requests go through, there will likely be multiple Tickets open for different devices.
2- For new user/hardware deployments, requests generally come from one Contact. We may get a couple in a row, somewhat overlapped, but unrelated.
3- If a user has multiple devices and has a ticket open for each, as stated in the request below
https://atera.uservoice.com/forums/936306-ideas-and-feedback/suggestions/44068440It…
7 votes -
ticket improvement
Split ticket in activities. every activities should have a different contract. like on site and remote support have different price but ticket is the same.
Then after ticket is closed contract nedd to be unchangeble.3 votes -
Transfer/Migrate Help Desk Tickets
I am currently using another help desk platform but would like to start using Atera's Help Desk. I have open tickets. I want to transfer the open tickets from my current help desk to Atera's help desk platform so that I can start using Atera's Help desk right away
7 votes -
Increased visibility of ticket status - such as the whole line being shaded differently
With the new ticket view it is harder for the support team to differentiate on the list which tickets are "awaiting customer response" or "awaiting technician response" as there is a just small circle of either green or purple next to the status. We would like tickets where they are awaiting our reply to be obvious at a glance to prevent a reply from being missed.
6 votes -
Filter Tickets by Last Modified
It would be helpful if we could filter by Last Modified - e.g. Last Modified last week but not this week, so we can easily see if there are any tickets that we've missed out on updating.
6 votes -
Pin a ticket
Pin a ticket to the top of the list.
5 votes
- Don't see your idea?