Communications

Resident communications with cost controls, not an open firehose

Conversations and broadcasts are separate on purpose. Notices target the exact hierarchy — building, floor, unit — with a reach preview and a spend cap before send.

Conversations and broadcasts are different jobs

A resident asking about their rent is a conversation; a 72-hour entry notice to a building is a broadcast. Mixing them in one inbox loses both. Ayillo keeps 1:1 conversations on the resident's record and broadcasts as a separate, audited notice with a frozen recipient snapshot. Every broadcast targets a hierarchy — portfolio, property, building, floor, unit, or person — with include and exclude lists, so the right people are reached and nobody pays to text the wrong building.

Cost controls that prevent an accidental SMS blast

  • Pre-send reach estimate: reachable vs unreachable per channel, with a recipient ceiling that asks for confirmation above your threshold.
  • Per-organization monthly send budget with a soft warning and a hard cap.
  • SMS used as escalation only by default — in-app and email first.
  • Duplicate suppression so the same resident isn't paid for twice in an hour.
  • Acknowledgement tracking with a non-responder list and resend to unread.

Large portfolios can never fire an unbounded SMS blast by accident.

FAQ

Frequently asked

Can residents reply to a broadcast?

Broadcasts are one-way notices; replies route to the manager's conversations inbox scoped to that resident.

Does it support multiple languages?

Yes. Per-resident preferred language is stored and notices are prepared per language before send.

Related resources

Keep exploring