Skip to main content

Noise Monitoring Analytics

Monitor noise patterns across your portfolio, understand how alerts are resolved, and identify your most affected properties.

Written by Emilie Pain

Noise Monitoring Analytics gives you a portfolio-wide view of noise events over a selected date range surfacing patterns across units rather than individual incidents. Use it to identify which units generate the most events, how many alerts it takes to resolve issues, and where threshold or messaging adjustments could help.

What you can see

  • Total noise events: threshold crossings across your portfolio in the selected period

  • Events per unit: ranked list of which units generate the most events

  • Resolution rate: average number of alerts needed to resolve each event

  • Impacted units list: all units with noise events and their event counts

  • Trend over time: noise frequency plotted across the selected date range to reveal seasonal or recurring patterns


How to access

Web app

Go to web.minut.com/reports → click Noise Monitoring Analytics

Mobile app

Open app → tap Reports at the bottom of the screen

Export

Download a PDF for the selected date range to share with your team or include in operational reviews


How to act on what you see

High-event units

Units consistently at the top of the list may need lower thresholds, stricter quiet hours, or different guest onboarding messaging. Give them a dedicated noise preset so you can tune them without affecting the rest of your portfolio.

Slow resolution rate

If most incidents reach the third warning, consider making your automated message content more direct, adjusting the escalation timing in your noise preset, or adding Call Assist where it is available in your market.

Seasonal patterns

Higher weekend or peak-season event counts can inform when to run proactive guest communication at check-in.

Threshold refinement

Units with very few events may benefit from slightly lower thresholds to catch noise earlier before it escalates to neighbours.

For documenting a specific incident- to support a dispute or insurance claim use the Noise incident report instead. Analytics shows patterns; incident reports show evidence.

Did this answer your question?