Settings and activity
6 results found
-
3 votes
An error occurred while saving the comment 
Stephane Lamarchand
supported this idea
·
-
3 votes
An error occurred while saving the comment Stephane Lamarchand
commented
Hi Damien, idea strongly supported!
Device Health notifications should be actionable without requiring an additional investigation step.
Today, an email may indicate that several devices have stopped sending heartbeats, but support teams still need to access Device Hub to determine which rooms or devices are affected.
Including optional device information such as Site, Room Name, Device Name and Last Heartbeat would:
- Accelerate troubleshooting
- Reduce support workload
- Improve operational responsiveness
- Support global and distributed support teams
- Increase the practical value of Device Health notificationsThis enhancement would also significantly expand the usefulness and distribution of Device Health notifications. Because the email would become self-contained and actionable, it could be safely shared with local support teams and operational stakeholders who do not have access to Device Hub, improving collaboration and accelerating issue resolution.
For organizations managing large international deployments, actionable alerts are significantly more valuable than simple summary counts. The best monitoring alert is one that allows a support engineer to understand the issue and initiate a corrective action without needing to access another system.
Stephane Lamarchand
supported this idea
·
-
3 votes
An error occurred while saving the comment Stephane Lamarchand
commented
Hello Damien! Indeed, strongly supported idea!
In enterprise environments, monitoring and administration are 2 different responsibilities. Local IT support teams need visibility into device health, alerts, firmware status and diagnostics, but do not require access to configuration settings or administrative functions.
A dedicated Device Health Read-Only role would:
- Enable proactive support and faster incident resolution
- Reduce administrative dependency
- Support least-privilege security principles
- Improve governance in multinational deployments
- Increase end-user satisfaction by reducing meeting room disruptionsThis functionality is already a standard RBAC capability in many enterprise management platforms and would greatly improve Device Hub adoption within large organizations.
Stephane Lamarchand
supported this idea
·
-
6 votesStephane Lamarchand
supported this idea
·
-
13 votes
-
14 votes
Hello Damien! Idea indeed strongly supported!
This enhancement would move validation to the point where the user can still take corrective action, instead of notifying them after the reservation has already failed.
Requiring a meeting subject before submission would:
- Prevent avoidable booking failures
- Reduce user frustration
- Decrease support tickets
- Improve booking quality and compliance
- Increase confidence in the Outlook + Eptura reservation workflow
Users should receive immediate feedback while creating the booking, rather than discovering the issue later through a rejection email.
Preventing the error is significantly more effective than explaining the error afterwards.