From WhatsApp to a traceable building incident

A resident’s report usually arrives with a building, area and description spread over several messages. The flow for property administrators turns them into a reviewable incident, without stating that there is already a supplier or repair. If the notice contains data from a private home, different permissions apply than those for a common area. The shared reference must not reveal identity, telephone number or private circumstances to other neighbors.

01

01

02

03

Record what was observed, not the cause

"There is water next to the elevator" describes a visible situation. It does not demonstrate the origin, responsibility or solution. The issue must retain that difference so that the team can decide how to check it.

Identify building, entrance or common area, approximate time and attached material. When the building is missing, the agent can ask for it; when the location is ambiguous, it marks it as pending instead of assigning a building by context. Add a way to indicate whether the notice affects access, elevator, supply, or security, but uses approved operational categories. The goal is to direct the review, not determine the cause. Photos and audios remain associated as contributed material, with defined access and retention controls.

The priority declared by the neighbor is also data, not expert opinion. Emergency and escalation rules should come from management and provide human channels when there is immediate risk.

02

Combine reports without erasing their differences

Several neighbors may report the same problem with different times and areas. Grouping can reduce duplicates, but requires explicit criteria: building, location and time window, as well as review when in doubt.

Don't automatically merge two issues just because they contain similar words. Water in two portals can have different causes and responsible parties. Keep the associated messages and allows the case to be separated.

A common reference helps continue communication. Each new notice can add context to that reference without creating another queue, as long as the system indicates who linked it and why.

03

Referring does not mean assigning a provider

The first destination can be the incident queue, the building committee or an on-call person, according to verified rules. The “handed off” state describes that internal transfer; it does not show that a supplier has accepted the work.

To show "assigned" would require a real external source and its response. To show “resolved”, verified closure evidence. The sandbox ends early because there is no persistent professional backend or connection to providers.

The execution receipt must identify the building, location, description, reference and pending decisions. This way the team can review without rebuilding the chat and the neighbor understands what has been recorded.

04

01

02

03

Validate the flow with difficult issues

Test incomplete locations, third-party messages, repeat reports, and possible emergencies. Verify that the agent requests minimal information and offers the approved channel without diagnosing the fault.

05

Measure avoided duplicates, fields corrected, and classification time. Do not attribute the repair time to the agent: it depends on decisions, suppliers and availability that are left out of the initial record.

06

In the property managers demo, you can see an incident created and handed off locally. The supplier and repair remain pending review, and the flow never reports a repair that has not happened.