Start with the buyer’s version
“Does it still have this problem?” leaves two things unclear: what “it” refers to and which problem the buyer has in mind. The buyer might be considering a current listing, a remaining unit of the discontinued version, or a used product. A recent comment does not establish a recent product version.
Ask for the model or revision shown on the listing and the exact use case. For an accessory question, request the accessory model and relevant specification; do not request personal purchase details. If the listing lacks a revision, ask the product owner to identify it before connecting the video’s result to that purchase.
Record the buyer’s wording without replacing it with a broader question. “Will this work with my charger?” should not become “Is the new version better?” The former needs a compatibility answer; the latter invites an unsupported comparison.
Keep three evidence records separate
Use a short worksheet so that a difference in one field does not silently become a claim about the whole product.
| Record | Fields to retain | What it establishes |
|---|---|---|
| Video test | Video URL, segment start and end, displayed model or revision, settings, connected accessories, exact words and visible result | What the creator showed for that configuration |
| Buyer’s question | Comment link, original wording, intended model or listing, accessory and intended task | The question the reply needs to answer |
| Current specifications | Revision, document title and date, relevant passage, stated conditions, product owner and unresolved items | The current feature or limitation the evidence actually supports |
Treat an unreadable label as unresolved rather than identifying the version from appearance. A release date alone also leaves the tested unit uncertain. Record whether the version comes from a visible label, the description, or the creator’s own clarification.
For each proposed sentence, name the record that supports it. A current connector specification can support a statement about the connector. It cannot establish runtime, performance under load, or compatibility with every accessory. Keep these distinctions in a table of supported, tested and untested compatibility when several configurations need answers.
A hypothetical reply that preserves the review
The following scenario is invented to illustrate the method. Assume a creator tested the now-discontinued Revision A of a portable recorder and showed that recording stopped when external power was connected. Its revision label and barrel power input are visible. A buyer now asks whether Revision B can record while connected to their charger. In this hypothetical, the current manual documents a USB-C input and charging while idle, but says nothing about recording during charging.
A possible reply, based only on those assumed observations and documents, is:
“The video tests Revision A, shows its barrel power input, and records an interruption that we are not disputing. The current Revision B manual lists a USB-C input and charging while idle. That does not establish whether it can record while charging or whether your charger is compatible. Which charger model are you considering? We will ask the product owner to confirm those points before giving you a compatibility answer.”
This reply preserves the observed problem, identifies an evidenced difference, and leaves the buyer’s central question open. Avoid changing the final sentence to “the issue is fixed”: a connector change and idle charging support do not demonstrate that result.
Do not recast an old review as a review of the current product or promise an improvement without supporting evidence.
Refer uncertain compatibility to the product owner
Send a specific request rather than asking someone to approve a reassuring sentence. The product owner needs enough detail to answer the actual configuration.
- Provide the reviewed revision, current revision, buyer’s intended task and accessory specification, with the supporting passages attached.
- Ask whether the requested combination is supported, has been tested, or remains untested. Request the conditions and a document or test record that supports the answer.
- Keep the reply limited while that answer is pending. Acknowledge the question and identify what needs confirmation without predicting the outcome.
- Use the returned evidence to answer the narrow question. If it covers a different accessory or operating mode, explain the remaining gap rather than extending the result.
Refresh a prepared reply when the listing or specification changes. A sentence approved for one revision should not carry over automatically; YouTube comment approval and timing provides a related way to keep approval tied to the reply being used.
What to deliver with the final comment
Retain the video segment, version evidence, buyer’s original question, current document passage, unresolved items and final reply together. Include the owner’s response when a compatibility question required confirmation. Someone taking over the conversation should be able to trace every product claim without rereading the entire video.
Record the comment’s location and check time separately from the accuracy of its content, using a comment visibility acceptance sheet. A visible reply does not prove that its version comparison is correct. The delivery should make both the evidence and the remaining limits easy to inspect.
Want to see how AI engines describe your brand today?
Get a free growth audit