Find injury and hazard reports in reviews and returns
Reads reviews, returns, contacts and warranty claims for harm or near harm and names the hazard for your safety team. It never decides what to report.
Try it on this example
Where the text came from (review, return comment, support chat, email, call, warranty claim): Support chat
Product type from the catalogue: Power bank 20,000 mAh, USB-C
The whole text
- Does the text describe a safety incident in which the product harmed, or could have harmed, a person, an animal or property?Yes98%
- What kind of hazard does the text describe?Fire or overheating100%
- How badly was anyone hurt, according to the text?None100%
- Does the text say a child was hurt, exposed or near the product when it happened?Yes95%
- Does the text describe damage to property other than the product itself?Yes95%
- Does the customer say it happened more than once, or to other units or other people?No95%
- Does the customer mention a lawyer, a regulator, an insurer, a claim or the press?No90%
- Is the description specific enough to understand what happened without contacting the customer?Yes96%
These are real answers stored from one run on this example.
The prism behind it
Find injury and hazard reports in reviews and returns
Fields
- Where the text came from (review, return comment, support chat, email, call, warranty claim)
- Product type from the catalogue
- The whole text
Context
The texts are customer reviews, return comments, support chats, emails, call transcripts and warranty claims about consumer electronics sold by a direct-to-consumer brand: earbuds, headphones, speakers, power banks and chargers. Every text is read. Texts that describe a safety incident go to the product safety team the same day, where a trained person reads each one. A safety incident is an event in which the product harmed, or could have harmed, a person, an animal or property other than the product itself: overheating, swelling, smoke, fire, melting, sparks, electric shock, burns, cuts, parts coming loose that a child could swallow, a battery or magnet swallowed, a skin reaction, or a product that collapsed or fell. A near miss counts: a battery that swelled and got too hot to hold is an incident even if nobody was hurt. A quality complaint is not an incident: a product that stopped working, charges slowly, sounds bad, broke without any hazard, or arrived damaged. Figures of speech are not incidents: "this bass is fire", "the price is killer", "it blew me away". The words of a support agent or a template are not the customer's report. These answers route texts to people. They do not decide whether an incident must be reported to a regulator, such as the Consumer Product Safety Commission in the US or the market surveillance authorities in the EU. The safety team and counsel decide that.
Questions
Does the text describe a safety incident in which the product harmed, or could have harmed, a person, an animal or property? Yes / No
Apply the definition of a safety incident in the context to what the customer describes. Count near misses. Do not count quality complaints, figures of speech, or the words of an agent or template. Yes: The customer describes an event in which the product harmed, or could have harmed, a person, an animal or property other than the product. No: The text describes only a quality problem, praise or a figure of speech, or no event at all.
What kind of hazard does the text describe? Choice
Pick the hazard the customer describes. When the text describes more than one, pick the one that caused or came closest to causing harm.
How badly was anyone hurt, according to the text? Scale
Judge only what the customer says happened to people. Damage to property alone is None.
Does the text say a child was hurt, exposed or near the product when it happened? Yes / No
Count a child or baby the customer mentions as using the product, holding it, sleeping or playing near it, or hurt by it. Count the customer's son or daughter only when the text shows they are a child, for example by an age or a school year. Yes: A child was hurt, exposed or near the product when the event happened. No: No child is mentioned in connection with the event.
Does the text describe damage to property other than the product itself? Yes / No
Count scorch marks, burns, melting or stains on furniture, bedding, floors, clothes or other devices, and any fire or water damage in the home or car. Damage to the product alone does not count. Yes: Something other than the product was damaged. No: Only the product was damaged, or nothing was.
Does the customer say it happened more than once, or to other units or other people? Yes / No
Count a customer who says this unit did it before, that a replacement or a second unit did the same, or that a friend, family member or other reviewers had the same problem. Yes: The customer says the event happened more than once or to other units or people. No: The customer describes a single event with this unit only.
Does the customer mention a lawyer, a regulator, an insurer, a claim or the press? Yes / No
Count a mention of a lawyer or solicitor, a product safety or consumer regulator, trading standards, an insurer, a compensation claim, or going to the press or social media. Yes: The customer mentions at least one of these. No: The customer mentions none of these.
Is the description specific enough to understand what happened without contacting the customer? Yes / No
Judge whether a safety analyst could tell from the text what the product did and what the consequence was. Yes: The text says what happened, to what or whom, and roughly how. No: The text is too vague or short to tell what happened, such as "dangerous product, avoid".
Lens columns
reports_incident, reports_incident_probability, hazard_type, hazard_type_probability, injury_severity, injury_severity_average, child_involved, child_involved_probability, property_damage, property_damage_probability, happened_before, happened_before_probability, legal_or_regulator_mentioned, legal_or_regulator_mentioned_probability, enough_information, enough_information_probability
Run it on your own text
Add this prism in the app, change any question, and test it on a file of your own.