Settings and activity
44 results found
-
13 votes
Danny Stergiadis
supported this idea
·
-
87 votesDanny Stergiadis
supported this idea
·
-
51 votesDanny Stergiadis
supported this idea
·
-
25 votes
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
Danny Stergiadis
supported this idea
·
-
17 votesDanny Stergiadis
supported this idea
·
-
7 votesDanny Stergiadis
supported this idea
·
-
5 votesDanny Stergiadis
supported this idea
·
-
6 votes
An error occurred while saving the comment Danny Stergiadis
supported this idea
·
-
22 votesDanny Stergiadis
supported this idea
·
-
7 votesDanny Stergiadis
supported this idea
·
-
12 votesDanny Stergiadis
supported this idea
·
-
2 votesDanny Stergiadis
shared this idea
·
-
4 votesDanny Stergiadis
shared this idea
·
-
54 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!
An error occurred while saving the comment Danny Stergiadis
commented
This would be great. Instead of polling closed tickets to import into other systems for billing or alerting, we can wait for Atera to post to a webhook each time a ticket is opened and closed. Saves stress on Atera's system from constant polling and is more efficient. For example we built an integration to remind techs there are unassigned tickets or tickets that haven't been responded to. And we built another that imports tickets into QuickBooks Desktop as sales orders.
Danny Stergiadis
supported this idea
·
-
26 votes
Nice! The feature you requested is being considered for development. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
Danny Stergiadis
supported this idea
·
-
3 votesDanny Stergiadis
supported this idea
·
-
3 votesDanny Stergiadis
supported this idea
·
-
634 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!
Danny Stergiadis
supported this idea
·
-
6 votes
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
An error occurred while saving the comment Danny Stergiadis
commented
Further to this, data should be linked to the customer not the contact. Currently tickets are directly related to contact, and contact is related to customer. When you delete a contact who was fired at customer location all tickets and underlying data are deleted. This should not happen. Employees come and go...we are not billing that employee or have to answer to them. We answer to management at our customer. This needs to change.
Danny Stergiadis
supported this idea
·
-
20 votesDanny Stergiadis
supported this idea
·
We use the API to pull tickets details, time and other fields to create invoices in QBO. But we can't pull products added to any ticket through the API as this doesnt exist as a function. Some background: When a customer orders new computers (or any hardware) we save the product details of those computers and the labour/time to setup, etc into the ticket. Right now we have to flag the ticket with a custom field in order to ensure someone visits the imported QBO Invoice and adds the products manually. This is very time consuming. Having an API to access the products by ticketID is very important.