Conversational Incident Reporting on WhatsApp

MetaDynamic developed a conversational incident-reporting approach that guides employees from an initial message towards a structured business record. The work connects a familiar messaging experience with a defined reporting process, using focused questions to collect the information a reviewer needs. The purpose is to make the conversation useful beyond the exchange of messages.

The reporting journey brings together the location, event description and relevant supporting information before handing the record to the responsible review process. MetaDynamic's role connects conversational design with business workflow integration. The project story focuses on that reporting journey and its operating boundaries, without disclosing client-specific information or private employee conversations.

Familiarity with messaging does not guarantee a complete incident report. An open message may describe a concern without identifying the location, event category or information needed for follow-up. A useful conversational experience needs to ask focused questions without making the employee repeat the same information in several different ways.

The workflow must also distinguish a conversation from a submitted report. An employee may stop responding before the required details have been provided. The reviewing team needs to understand whether a business record has been created and what information is available, rather than assuming that every message represents a completed submission.

Reporting conversations can contain sensitive information. A photograph may show employees or internal operating details, and an employee may provide information that falls outside the reporting purpose. The conversation therefore needs clear boundaries around what it requests, how it handles uncertainty and when a person should take over.

The conversational approach guides the employee through a bounded reporting task. Focused questions collect the location, event category and description in a sequence that supports a useful handover. The language should make each question understandable and give the employee an opportunity to correct information before the reporting process continues.

A summary connects the conversation with the business record. Presenting the collected information together helps the employee recognise whether the report reflects the intended observation. The reporting acknowledgement should explain the next step in the process without presenting receipt of a message as a completed investigation.

The downstream workflow connects the captured details with the record and its review responsibility. Business actions need to remain separate from conversational responses so that a failed action is not mistaken for a successful submission. A useful reporting journey makes the status of the record understandable to the employee and the reviewing team.

Human handover remains an essential part of the experience. Unclear requests, incomplete information and matters outside the agreed reporting task need a defined route to a responsible person. The conversational channel supports the reporting process; it does not make operational or safety decisions independently of the organisation's authorised review arrangements.