Editorial preview: vendor recordings and hands-on verdicts are pending. What counts as evidence.

A claim should
stand up to a check.

Corrections help keep the research useful. Send the page, the specific claim and the evidence that needs another look.

Contact the editor

The public editorial mailbox has not been configured for this preview. We cannot receive reports through this page yet.

What to include

  • The URL and heading of the affected page.
  • The wording you believe is incorrect and your proposed correction.
  • A primary source URL, model or plan name, and the date you checked it.
  • Any relevant context, such as billing period, region or product version.

Remove account numbers, payment details, API keys and other private information from supporting material. Ask before sending a person's voice recording or confidential production content.

How corrections are handled

The editor checks the report against the cited source or retained test evidence. A substantive correction should explain what changed, when it changed and whether it affects the conclusion. A source update must not be presented as a new listening test. Unresolved questions remain labelled as unresolved.

Providing evidence does not guarantee a particular verdict. Vendors can flag factual errors; they cannot purchase removal of a documented limitation or a better score. See the testing method and the disclosure policy.

Privacy and response expectations

This page has no submission form, tracking or file upload. If you choose to email, your email provider and the recipient's provider process that message. Include only the information needed to check the issue. We do not promise a response deadline in this preview.