Skip to main content

How to send feedback?

Have feedback or issues with Alsense®? Read this article which describes how to share itwith us

Written by Edoardo Nalon

You can either send feedback directly via Alsense® or you can write an email to alsensesupport@danfoss.com

Feedback via Alsense®

How to find the feedback menu?

You find the send feedback menu on the top menu bar:

Pressing the Help menu icon, will open the feedback menu:

Alsense® send feedback menu

via the Feedback menu, you can report issues or send us ideas for how we can improve the Alsense®.

Automatically Captured Information

When you submit feedback, Alsense® automatically captures some technical details, including:

  • your email address

  • operating system, browser version, screen size and resolution

  • UI preferences, user role and permissions in Alsense®

  • URL of the Alsense® page and the sites and date range you have selected

  • console logs

What happens when I send feedback using the feedback menu?

Deeping on the type of feedback which you share with us, we initiate different processes:

  • Issues/bugs: are evaluated daily by the support team, depending on the severity of the issue response time is according to the support agreement between Danfoss and the customers

  • Improvement ideas: goes through our feature request process as soon as we receive them. we try to get back to you as quickly as possible, but please expect up three weeks evaluation time

  • Translation issues: will follow our normal development cycle, we will not give you any feedback, but communicate the fix in the release note once it is solved

Support via Email

If you have any questions regarding Alsense® software or are experiencing any issues when using it, feel free to contact us at: AlsenseSupport@danfoss.com.

When reporting issues via email, and for us to provide support with the issue, we need you as a customer to provide us with the following information regarding the issue:

  • Aspects of the Service that are unavailable or not functioning correctly

  • Incident's impact on users

  • Start time of Incident

  • List of steps to reproduce Incident

  • Relevant log files or data

  • Wording of any error message

Did this answer your question?