What this helps you do
Audiences group your residents so a message reaches only the people it affects. You always have one All Residents audience that reaches everyone connected and cannot be deleted. Onboarding seeds a small starter set you can rename, archive or replace: maintenance notices, amenities, community events, parking and access, the board and owners, and your staff and vendors. Your buildings, towers, floors, phases and units are not seeded, because every property names them differently: create those as audiences yourself, with the names residents actually use.
When to use it
Use audiences whenever a notice fits part of the property and not the rest: a riser shutoff in one stack, an elevator out in the north tower, a garage level closed for cleaning, a pool closure, a board packet, a vendor schedule, or the social calendar that only some residents want.
How to do it
- Open Audiences.
- Create one audience per building, tower, phase or floor, named the way residents say it: Building A, North Tower, Floors 10 to 15, Garage Level 2.
- Set a floor or a stack to sit Inside its building with Inside audience, so a send to the building covers everything under it.
- Choose how people join each one: residents choose it themselves, the office assigns them, or either. Set Board & Owners and Staff & Vendors to the office assigns.
- Leave Maintenance Notices, Amenities, Community Events and Parking & Access open so residents pick them on their preferences page.
- Use Bulk assign from Connections to place residents into their building after an import.
- Decide per audience whether replies are allowed; leave replies on for anything that asks a resident to arrange a time.
Example
The office creates Building A, Building B and Building C, then nests Floors 1 to 3 inside Building B for the stack fed by the failing riser. When the plumber confirms Tuesday, the shutoff notice goes to those three floors, ninety people instead of eight hundred, and the rest of the property never learns to ignore your messages.
Good to know
- Sending to All Residents asks for a step-up confirmation first, which keeps the property-wide send rare enough that residents still read it.
- There are no rule-based or dynamic audiences, and the Hub does not read your property system: import, then assign.
- A resident can be in several audiences at once: their building, amenities and community events.
- A community manager can be limited to their own property's audiences on the Team screen, both for sending and for reading replies, which is how a management company runs several communities from one place.
- When a resident moves out they disconnect, or you remove them; audiences stay and the next resident joins the same ones.