702 results found
-
opening a ticket on a user's behalf shows technician's comment as the users
If I open a ticket on behalf of a user, the public comments entered on the initial ticket form will show as being posted by the user rather than the technician who opened the ticket.
1 vote -
Internal Tickets
Internal Only tickets - Is there a way to create an internal ticket for a customer and not have it show on the Customer Portal?
We need to create tickets for internal tasks and or quotes we need to do and do not want the client to see these tasks. We still want to align the tasks/quote with the client and user.
We would like them NOT to email any info to the client about these internal-only tickets.
We did a workaround with Ticket Status (Quote, Quote Closed), but it would be nice to have it native in Atera.
We…
1 vote -
ticket type
I would like the ability to change the options for Ticket Type and Ticket Priority.
5 votes -
Ticket automation condition for self\signed in technician.
The purpose of this condition is to allow an automation that can alert another technician that a ticket has been assigned to them but not if you are becoming the assigned tech. Currently there isn't a condition of "Self" that would stop the automation from running when assigning a ticket to yourself. (Example: A tech is out on PTO or needs to assign a ticket to a different tech. They make the assignment change and the rule emails the newly assigned tech.) That works just fine but without the Self condition, when I assign a ticket to myself during standard…
1 vote -
Private note
Ability to send a private note to a user.
Example, sending a private note to the user's manager for approval. They will receive an email and be able to view the ticket and add their comment into the private/public section.4 votes -
Allow removal and edition of comments inside tickets
If you could please provide us with the option to remove and edit comments in our tickets. As of now, if we put a comment in the wrong ticket, or if we make typos or errors in our comments, we cannot correct them as the comments seem to be there to stay permanently.
2 votes -
Attach an Agent to manual ticket
When creating a ticket manually, no agent can be assigned
This would be relevant for back-office ticket creating -> Technicians
1 vote -
Assign requestor based on reply-to email not sender
When using using tools like wufoo or jotform the email incoming is from no-reply@jotform.com (sender email). That creates the tickets and assigns the ticket to the user no-reply@jotform.com. Jotform/wufoo have the capability to use an email collected in their form to add as the "reply-to email". I use this currently with zendesk from both wufoo/jotform so the tickets are assigned to the correct requestor.
Please add that as an option for inbound email tickets or the ability to run a ticket automation to update the requester based on this attribute.
1 vote -
Closing Ticket
I have a question. Some of our users have noticed that when we close a ticket, it creates another email. Is it possible that when we close the ticket, it keeps the original email from the first creation?"
1 vote -
Change default ticket type when ticket is logged
Good Day Please let us change the default ticket type, as when someone emails a ticket, its an incedent. Can we choose the default
2 votes -
Organize Ticket Properties
I'd like to be able to determine the order of the ticket properties, as there are a few that we can't seem to move, even if the default and the ticket form have them in a certain order. Some items, while important to know, are not often changed and therefore could be further down on the list but do not show as so, even when on the bottom of both 'custom fields' and the form template lists.
12 votes -
which technician is currently working on which call
Hi
We are interested in the option for the service call manager to be able to see which technician is currently working on which call.
Is there such a thing?1 vote -
Display CC in Ticket
The new layout does not allow to display other (cc-)receipients of an e-mail any more.
Can you please add that feature again?11 votes -
Mass Ticket Responses
The ability to select multiple tickets at once and submit a single response for all of them. Typically we have to copy/paste the same generic message when onboard or offboard tickets come in, saying they will be finished by a certain time. With this, we'd be able to type out a single message and be done with it until we are able to work on the ticket.
2 votes -
formatting code
Having the ability to paste code into a ticket reply or internal note would be immensely helpful. It would be nice to be able to paste code into my ticket notes and easily copy it for future use.
Could be implemented similarly to how Discord or Slack by surrounding the text with backticks
5 votes -
Internal notes
It would be useful to be able to keep the internal note at the very top of the ticket just beneath the most recent message.
Also if we could use the same note/notepad for each internal note entry created.
It's very frustrating having to scroll through the entire thread just to compare an internal note that was created at the beginning of the ticket.
It would also help other technicians reviewing the tickets to be able to see all internal notes a tech created in a ticket. It gives them a quick recap of the troubleshooting process that was taken…
1 vote -
Ticket automation based on support email address
It would be great for us to be able to create ticket automations based on which support address received the email.
Currently we have multiple SLAs for a particular client depending on the service type. So we have created additional support email addresses for the different service types but cannot manipulate the incoming ticket based on the support email address.
1 vote -
Ticket retention
We need a way to place a retention policy on the tickets that are under closed or deleted status.
Example: if ticket a ticket is closed or delete for 6 months of last modified date, then completely remove it from the platform. Sometimes our users send sensitive data over tickets even when we request they do not and we want to ensure if there is ever a data breach that the threat actor cannot mine legacy data.
1 vote -
Internal reply edit button
An edit button should be in place for internal replies.
This would make tickets generally more readable and less cluttered.2 votes -
support time-based automation rules in cascade
Would like support for time-based automation rules in cascade.
As an example, a ticket is automatically set to pending after 3 days with no response. Then set to closed automatically after 3 additional days with no response.Based on my conversation with support, currently, if changes were applied to the ticket automatically, the next rule that should be triggered will not work.
3 votes
- Don't see your idea?