Turn return comments into codes that say whose fault it was
Reads each return comment next to the reason picked and gives your return code, who caused it and which page detail misled. It never refuses a return.
Try it on this example
Reason the customer picked in the returns portal: Defective
Product type from the catalogue: Wireless noise-cancelling earbuds
Customer's return comment
- Which of our return codes best fits the customer's comment?Not compatible75%
- Who caused this return, judging only from the comment?Product page99%
- Which product page detail does the comment say was wrong or misleading?Compatibility99%
- Does the customer's comment contradict the return reason they picked in the portal?Yes94%
- Does the comment say the item was used beyond trying it out?No93%
- Does the comment mention a battery that swelled, overheated, smoked or leaked, a burning smell, a shock or an injury?No90%
- Does the comment say enough to assign a return code?Yes95%
These are real answers stored from one run on this example.
The prism behind it
Turn return comments into codes that say whose fault it was
Fields
- Reason the customer picked in the returns portal
- Customer's return comment
- Product type from the catalogue
Context
The returns are from customers of a direct-to-consumer consumer electronics brand: earbuds, headphones, speakers, power banks and chargers. In the returns portal the customer picks a reason from a list and may write a comment. Returns are free, so customers often pick whichever reason is quickest, and the comment is the better evidence. Judge from the comment, using the product type; use the picked reason only where a question asks you to compare with it. Our return codes: - Damaged on arrival: arrived cracked, dented, scratched or broken, or in a crushed box. - Defective: never worked, or stopped working or behaves wrongly in normal use (will not charge, will not turn on, drops out, one side silent). - Not compatible: does not work with the customer's phone, computer, car or other device. - Not as described: differs from the product page in anything other than compatibility: specifications, battery life, features, colour, size or contents. - Missing parts: a part, accessory, cable or ear tip missing from the box. - Wrong item sent: a different product, model or colour from the one ordered. - Arrived late: arrived after the customer needed it. - Uncomfortable: works as described but does not fit or is uncomfortable to wear. - Performance: works as described but the sound, battery or features are not good enough for the customer. - Changed mind: no longer wanted, a gift not wanted, or bought by mistake. - Better price elsewhere: found it cheaper. The product safety team must see every return that mentions a battery that swelled, got hot, smoked or leaked, a burning smell, a shock, or an injury: such a unit needs a dangerous goods return label, not a normal box.
Questions
Which of our return codes best fits the customer's comment? Choice
Read the comment and the product type against the return codes in the context. Pick the code for the main reason the customer gives, whatever reason they picked in the portal.
Who caused this return, judging only from the comment? Choice
Judge what the comment says caused the return. This sorts returns for reporting and fixing; it does not decide whether the return is accepted.
Which product page detail does the comment say was wrong or misleading? Choice
Read the comment for a detail of the product page, photos or specifications that the customer says was wrong or led them to expect something else. When the comment names more than one, pick the one that caused the return.
Does the customer's comment contradict the return reason they picked in the portal? Yes / No
Compare the comment with the reason the customer picked. Count a contradiction when the comment gives a different kind of reason, for example "Defective" picked and the comment says it works but does not pair with their phone. A comment that adds detail to the picked reason is not a contradiction. Yes: The comment gives a different reason from the one picked. No: The comment fits the picked reason, adds detail to it, or says too little to compare.
Does the comment say the item was used beyond trying it out? Yes / No
Count use for days or weeks, taking it out and about, or wear and tear the customer describes. Opening the box, pairing it and trying it for a short time is trying it out. This sends the item to inspection for resale grading; it is not a judgment of the customer. Yes: The comment says the item was used for more than a short try. No: The comment says it was only tried out or not used, or says nothing about use.
Does the comment mention a battery that swelled, overheated, smoked or leaked, a burning smell, a shock or an injury? Yes / No
Count any mention of these, even in passing and even if the customer calls it a defect. Warm during normal charging is not a mention unless the customer says it was too hot to hold or unsafe. Yes: The comment mentions at least one of these. No: The comment mentions none of these.
Does the comment say enough to assign a return code? Yes / No
Judge the comment alone. Yes: The comment gives a reason for the return that fits a code. No: The comment is empty, repeats the picked reason in one or two words, or gives no reason, such as "returning" or "n/a".
Lens columns
return_code, return_code_probability, fault_owner, fault_owner_probability, misleading_attribute, misleading_attribute_probability, comment_conflicts_selected, comment_conflicts_selected_probability, used_beyond_trying, used_beyond_trying_probability, safety_mention, safety_mention_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.