Multilingual resident communication means every resident can report a problem, ask a question, and receive an urgent notice in a language they actually understand. URBI solves it with Arthur, a resident facing AI that works in ten languages over phone, SMS, email, and in app chat, from a knowledge base management controls, plus building news with per resident delivery tracking.
Why is language such a hard problem in resident communication?
Language is a hard problem because most buildings communicate in one language while their residents speak many. In the United States, more than 1 in 5 people age 5 and older speak a language other than English at home, across over 500 individual languages and language groups. The number of people speaking another language at home nearly tripled between 1980 and 2019, reaching 67.8 million.
Inside a building, that gap shows up in very practical ways:
- Notices go out in one language only. A water shut off memo that a resident cannot read is a memo that did not happen.
- Family members become unpaid translators. A resident's teenager ends up on the phone explaining a leak because nobody else in the household is comfortable in the office's language.
- Urgent messages get misunderstood at the worst time. Fire alarm testing, elevator outages, and evacuation instructions leave no room for guesswork.
- Some residents stop reaching out at all. Small maintenance issues go unreported until they become expensive ones, and the manager reads silence rather than a language barrier.
None of this is a resident problem. It is a communication system problem, and it lands hardest on residential buildings in diverse cities and on student housing with international students arriving every fall.
What do property managers usually try first?
Managers usually try some mix of bilingual hiring, ad hoc translation, and free machine translation. Each helps a little. None of them scales to a building where residents speak six or eight languages.
| Approach | What it solves | Where it breaks |
|---|---|---|
| Hiring bilingual staff | Great service in one or two extra languages | You cannot hire for every language, and coverage disappears when that person is off shift or leaves |
| Family members translating | Gets the immediate message across | Puts the burden on residents, breaks privacy, and fails when the family member is unavailable |
| Phone interpretation services | Professional quality for serious conversations | Per call arrangements add cost and delay, so they get saved for emergencies, not daily questions |
| Free machine translation | Fast rough translations of written notices | Nobody checks the output, it translates whatever it is handed instead of an approved answer, and it does nothing for phone calls |
| Multiple posted copies of notices | Covers the two or three biggest language groups | Doubles or triples the work for every notice, so it only happens for the big ones |
The pattern is the same in every row. These are patches applied per message and per conversation. The fix that scales is a communication layer that speaks the resident's language by default, on every channel, from answers the manager controls. That is the standard we used when reviewing the best building communication software.
How does Arthur answer residents in ten languages?
Arthur is URBI's resident facing AI, and it supports ten languages today across every channel: phone, SMS, email, and in app chat. A resident calls the building's number, Arthur answers in the building's voice, and the conversation continues in whatever language that resident is comfortable in.
The conversation is not just talk. Arthur has tool access, so it acts on what the resident asks:
- A resident reports a leak in their own language. Arthur files the service ticket with the right priority, confirms it back, and notifies the property manager.
- A resident asks to book the party room. Arthur checks availability, confirms the details, and completes the booking, with no translator in the middle.
- A resident texts at 11pm about heat that stopped working. Arthur answers instantly and follows up until the issue is resolved, the same way it handles any after hours maintenance call.
Sensitive actions stay protected. Changing autopay requires a PIN, and some actions are gated behind property manager approval. Arthur speaks ten languages, but gets no extra permissions in any of them.
The practical effect for the manager is simple. You stop needing a staffing plan for every language in the building. The teenager translating the maintenance call goes back to being a teenager. Residents who never contacted the office start reporting problems while they are still small.
Who decides what Arthur tells a resident in another language?
Management decides. Arthur is not improvising a translated answer of its own. It answers from a property scoped knowledge base, so the guest parking rule a resident hears in one language is the rule the office wrote in another.
When Arthur does not know something, it escalates to the property manager with a summary instead of guessing. The manager answers once, in their own language. Arthur puts that answer in its own voice, relays it in the resident's language, and saves it to the knowledge base with semantic matching, so the next person who asks is answered without interrupting anyone. Managers view, edit, and delete those entries. More in our post on who controls what the AI tells residents.
What happens to the conversation after Arthur handles it?
Every Arthur conversation is logged for management. Calls are transcribed, summarized, and sentiment scored, and every interaction ties back to the resident's record. The record is guaranteed even when a caller hangs up part way through. The manager does not need to speak the resident's language to know what was asked, what Arthur did, and how the resident felt.
That logging is the difference between an AI answering service and a system of record. When a board member asks what unit 804 reported last month, the answer is in the file, in the manager's language, with the ticket attached. It is what separates URBI from a traditional answering service that hands you a stack of message slips.
How do you make sure urgent notices actually reach every resident?
You make sure by tracking delivery per resident instead of posting a notice and hoping. URBI's news system lets the manager write a post, pick the audience (the whole building, specific floors, or a custom group), attach documents, and send it by push notification and email. Then the platform tracks who saw the post, resident by resident.
For urgent messages, three things stack on top of that:
- Urgent posts pin to the top of every resident's home screen in the app, so the shut off notice is the first thing they see.
- An AI urgency scan reads the manager's draft and suggests raising the priority when the text contains phrases like "shut off" or "evacuation".
- Buildings using URBI Display can take over every lobby and elevator screen in seconds for fire, water, or board notices.
One honest boundary: URBI does not claim automatic translation of the static documents you attach, like bylaws or AGM packages. What the delivery tracking gives you is proof of reach. You can see which units have not opened the urgent notice and follow up with those residents, through Arthur or in person, instead of assuming a posted memo did its job.
Frequently asked questions
How many languages does Arthur support?
Arthur supports ten languages today. That coverage applies across all of its channels: phone, SMS, email, and in app chat. Arthur answers in the building's own tone of voice, so a resident calling in another language still gets an answer that sounds like your building, not a generic bot. If you need to confirm a specific language, ask hello@myurbi.co.
Does URBI translate my notices and documents?
No, and we will not pretend otherwise. Translation of static documents and written notices is not a claimed URBI feature. What URBI provides is Arthur handling live resident conversations in ten languages, plus news delivery tracking that shows exactly which residents received and saw each notice, so you know where a follow up is needed.
Can management read conversations that happened in another language?
Yes. Every Arthur conversation is transcribed, summarized, and sentiment scored, and it ties back to the resident's record. Managers see what was asked and what was done without needing to speak the language the conversation happened in. Tickets Arthur files land in the same maintenance workflow as every other request.
Is this only useful for large towers?
No. Any building where residents speak more than one language benefits, because the alternative is hiring or improvising per language. It is especially useful in student housing with international residents and in smaller buildings that could never justify multilingual staffing but still have residents who avoid calling the office.
If your notices only work in one language, part of your building is not hearing you. URBI gives every resident a front desk that speaks their language, answers from a knowledge base you control, and a record of every conversation. Write to hello@myurbi.co and we will show you Arthur answering in the languages your building actually speaks.
