785 results found
-
Include details of the ticket in the Exchange Calendar appt
In our current ticketing system appointments are pushed to Outlook via exchange but include client name, address, phone number, email, who assigned it, who the tech is, and description of the ticket. The calendar piece is pretty important to us. We use this when we get in the car and start driving. Techs are accustomed to opening their calendar, tap the appt, tap the address and navigation takes from there.
1 vote -
Add "Pause" option to tickets
When on a ticket, it'd be a good idea to pause a ticket than outright stop it.
7 votes -
Change contact for multiple tickets
Please introduce the ability to change the contact for multiple tickets at once. It'd be very beneficial to be able to select all the tickets pertaining to a contact and change said contact without having to access each ticket to do so.
11 votes -
Print Ticket history for customer
My customer would like to have a history of all tickets, when he receive the billing.
This history should inherit all communication, which are written. So my customer can check, for what he pay!
6 votes -
Contact Last Comment variable with attachments
Add the attachments of the last comment when sent with the variable Contact Last Comment.
1 vote -
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 -
TICKET HRS
When hovering over a ticket, it would be helpful to see number of hours applied to the ticket without having to click into it.
2 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 -
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 -
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.
15 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 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.
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
- Don't see your idea?