Ideas
Our approach to product feedback
The benefits of giving us your product feedback
What happens to your product feedback
Our product teams meet regularly to go through new requests. Once we have verified that a request isn’t already available in the system, we change the status to Accepting votes so that more people can vote, prioritize, and give us information. This allows us to gauge demand, gather use cases, and establish impact & value.
How we choose what to implement
- Customer feedback - there are many ways we listen for your feedback:
formal customer interviews and other research activities
events like Greenbyte Forum conferences and trade shows
comments and votes on issues in Greenbyte Influence - CSM team insights - our CSM team knows which issues are the most challenging and most common for customers.
- Product analytics - we track how users move through the system, which helps us understand how existing features are being used.
- Product strategy - our long-term strategic vision for the product.
Custom applications
-
over due site/device access notification
I think a feature that notifies us either audibly or via pop up box to site accesses that have gone overdue would be very useful so as to keep visitors as safe as possible while visiting our sites. it means we can then react quicker to over due situations and start the escalation process to reaching them to check on there welfare much quicker . Taking into account that a lot of the sites are in remote locations and so response times to possible accidents or injuries needs to be as quick as possible.
4 votes -
Notification
In the Plan section suggest to get a notification if someone goes beyond the working end time.
1 vote -
Notification when new devices are added for API-using partners
A simple notification to partner companies that devices have been changed or added. A change log to allow third party users of API or other to reconfigure their systems and add new devices to API. Alternatively there would be an option to include ALL devices in the API with new sites and devices added automatically.
3 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
e-mail notifications in plain text at the start and the end of a statusevent. The Header is the same in both cases, whic his not comfortabel
The First word in the header of the second email when the status ist resolved, should be "RESOLVED" or something similar. thus one can easiliy differentiate between an initial status event an the end of this event
3 votes -
Task Email Notifications NEED to include a link to the task.
Notifications through email are very convenient but there needs to be a link to the task being referenced in the notiication email - there is currently a task number which makes it easier to find the task in GB but if there was just a link to the task, a reply comment or edit could be made.
At the same time - there should be a link to the monitor site page from within the View Task page - this would make it very simple to receive an email notification from a task update - click on the link to…
6 votes -
Add ability to filter for status type when setting up a new notification scheme for specific codes
Ability to filter for status type; stop, warning etc, informational, when setting up a new notification scheme for specific codes.
5 votes -
E-mail/Push note to the creator of a task when the expected end time has passed
When a task is done and the expected end time passed and the task ist unresolved. Then the creator or the person who make the latest update gets a reminder through email or push note.
4 votes -
Email specified persons when site access records are created
Could we please set up a notification to be able to email specified persons when site access records are created. ie one of our Asset managers would like to be emailed when a site access record is created for the wind farm he is responsible for.
5 votes
- Don't see your idea?