Draft-quality learning — verify product identity before hardware troubleshooting

Automation draft weakness

The earlier private draft treated a fuzzy/flashing monitor report as an X-Arcade support case and proposed monitor-isolation steps before confirming the product's actual manufacturer or model.

Manual reply improvement

Matt's public reply 12391161176 identified that the reported monitor was not an X-Arcade product and directed the customer to the actual manufacturer rather than continuing an inapplicable diagnostic path.

New drafting rule

When a ticket refers to a device only by a shared or similar brand name and does not establish an X-Arcade model, order, or product match, verify product identity before offering detailed hardware diagnostics. If the device is not ours, use a brief, factual redirect to the actual manufacturer; do not continue troubleshooting it as X-Arcade hardware.

Confidence effect and storage decision

This is a reusable triage correction from a human public reply. Keep it as a reviewable proposal that is safe for future private-note drafts; it does not assert a general monitor-support policy beyond product-identity verification.