Settings and activity
187 results found
-
12 votes
Lawrence Yau
supported this idea
·
-
29 votesLawrence Yau
supported this idea
·
-
4 votesLawrence Yau
supported this idea
·
-
3 votesLawrence Yau
shared this idea
·
-
11 votesLawrence Yau
supported this idea
·
-
5 votesLawrence Yau
supported this idea
·
-
10 votes
An error occurred while saving the comment -
82 votesLawrence Yau
supported this idea
·
-
4 votesLawrence Yau
supported this idea
·
-
26 votesLawrence Yau
supported this idea
·
-
77 votesLawrence Yau
supported this idea
·
-
146 votesLawrence Yau
supported this idea
·
-
137 votesLawrence Yau
supported this idea
·
-
139 votesLawrence Yau
supported this idea
·
-
6 votesLawrence Yau
supported this idea
·
-
29 votesLawrence Yau
supported this idea
·
-
2 votesLawrence Yau
supported this idea
·
-
35 votesLawrence Yau
supported this idea
·
-
97 votes
Congratulations on helping shape Atera! The feature you requested is currently being considered for development. Please be patient as the process can take a while or even stall to make way for other features. We’ll update you once it’s been implemented and released!
Lawrence Yau
supported this idea
·
-
23 votesLawrence Yau
supported this idea
·
This is important when we need to communicate with a 3rd party - e.g. vendor support - while having all communications logged against a ticket we have open with a customer.
We don't want to change the requestor to the vendor, just to send them an email, since the customer is still the requestor, and we don't necessarily want the customer being bothered with communications between us and vendor support.
Additionally, using tickets to manage these communications with vendors also allows multiple technicians to deal with the vendor and still have the complete history.