Noise concern message
Send this the same evening you learn about noise, while the group can still turn it down.
{Guest name}, I am writing about noise at {Property name} during quiet hours ({Quiet hours}).
What I know: {What you observed}. What I need tonight: {What you need}.
These hours are the ones on the listing for this stay. Please reply in this thread once the volume is down. If I have the time wrong, tell me.
When to send
Send a noise note when you have a current reason: a neighbor’s message, a monitor you trust, or you are there and can hear it. {what_you_observed} is that reason, stated narrowly. “A neighbor on the west wall wrote at 11:20pm that music was loud enough to hear lyrics” is something the guest can check against the room. “You are being disruptive” is a verdict. {what_you_need} is the change tonight: music off the speaker, the balcony door shut, the group moved inside. {quiet_hours} is copied from the listing.
{guest_name} may not be the person who is loud. Write to the thread anyway. The booker is the one who agreed to the listing. Avoid naming a guest you cannot see, and avoid guessing which friend is responsible.
Do not send this because a monitor flicked once at 8pm if {quiet_hours} start at 10. Devices misfire. A single spike during allowed hours is not this message. A pattern during {quiet_hours}, or a neighbor who describes an ongoing party, is.
Timing tip
The same evening is the whole point. A note the next afternoon about last night’s bass does not give them a night to fix, and it reads as a file you are building. If you learn about it at 11, send it at 11. If you learn at breakfast, send a shorter note that asks them to keep {quiet_hours} tonight, and describe {what_you_observed} as last night so you are not pretending it is still happening.
If they are asleep when you write, the message is still worth sending. They will see it in the morning and the second night often changes. Do not also knock unless you are comfortable being at the door and the listing’s quiet hours are actively being broken in a way a knock would stop. A knock can escalate. The thread is the default.
Common mistakes
A fine, a threat of removal, or a new curfew is the serious mistake. {quiet_hours} is a published rule. {what_you_need} should be compliance with that rule, not a penalty you invented. If the platform has a formal process for a party, use that process separately. This message is the direct ask. Stacking three punishments in the first note makes a reasonable guest defensive and does not lower the volume any faster.
The second is an observation you cannot support. “The sensor says 90 decibels” when you have not read the sensor, or “the neighbors have called the police” when they have not, will be quoted back at you. {what_you_observed} is what you actually have. If a neighbor forwarded a complaint, say a neighbor wrote to you, not that you witnessed the room.
The third is sarcasm. “Hope the party was worth it” feels good to send and bad to reread in a dispute. The template stays flat on purpose. Keep your edit flat. You can be firm in {what_you_need} without being sharp.
If it continues
One follow-up is enough inside this template’s job: a reply that {what_you_need} has not happened, with the time. After that, use the platform’s tools and, if you are documenting for later, write down times on the incident report. Do not send a string of messages every ten minutes. A guest who is ignoring the first note will not be persuaded by the sixth, and the thread becomes hard to read.
Thank them briefly if they do turn it down. One line. Do not extend it into a lecture about how hosting works. The night is over when the volume is down.