In this guide
Why voice messages complicate work
To transform an audio message into an actionable item, a staff member must: listen to it, understand who's speaking, identify the property, extract the problem, assess urgency, note details, and forward the content.
Don't ban them: structure them
An overly rigid policy risks shifting everything to phone calls. It's better to accept audio and automatically transform it into text. The transcription should be linked to the original file, associated with the sender, searchable, and verifiable.
From transcription to ticket
Transcription alone isn't enough. The system must extract an operational record with subject, property, area, proposed urgency, attachments, and requested action. AI can propose this structure, but the office must be able to correct it.
Managing transcription errors
Noise, accents, and technical terms can produce errors. Best practices: preserve the original audio, highlight uncertain words, request confirmation for critical data, record operator modifications.
Photos also need context
A photo of a stain on the wall doesn't indicate where it is, how long it's been there, or whether it's getting worse. The system must request missing information in a simple way.
The advantage for residents
Residents continue to communicate in the way they know. They don't need to download an app, create a password, or understand the office's internal structure.
The advantage for the office
The office obtains organized data, can search requests, and distribute work. An absent staff member doesn't take the memory of conversations with them.
Frequently asked questions
Sources and further reading
Want to turn WhatsApp into a workflow?
See how qb-Domus turns reports, photos and voice notes into trackable tasks.
REQUEST EARLY ACCESS