If a SnagitPro guide gives a wrong price, an unsupported license rule, or a step that does not match your version, report the specific claim through the contact page. You do not need to write a replacement article or provide a screenshot.
What to include
- The page URL and the sentence, table entry, or numbered step you are questioning.
- Your app version and operating system when they affect the issue.
- What you saw instead, plus a current official source if you have one.
- For a price or license mismatch, the country, currency, plan, and purchase route involved.
A short, specific report is enough to start a check. Screenshots are optional. Remove passwords, license keys, activation codes, account details, and private customer information before sending one. Reader names and identifying material should not be published without permission.
How a report is checked
The editorial standard requires the claim to be checked against the relevant primary source: the vendor's store, support documentation, release notes, or operating-system instructions. Version and platform matter. A Windows procedure should not be presented as a Mac fix, and an old license rule should not be applied to every current subscription.
Documentation review does not establish that a step was performed on physical hardware. Any actual hands-on result must state its setup, version, date, and observations, as described in the research and verification method. A search snippet or generated answer is not sufficient evidence.
If sources conflict or a reported result cannot be confirmed, the uncertainty needs to be explained. Unsupported wording should be qualified or removed; a missing answer must not be filled with an invented test or quotation.
What a correction changes
Before a substantive edit, preserve the previous version. A supported correction must reach the visible text and any matching table, FAQ answer, metadata, or structured data. Check affected internal references too, then re-read the saved page. Changing one link is not a complete article fact-check.
A material factual correction changes information that could affect a reader's decision or actions, such as a price, license restriction, destructive troubleshooting step, or platform requirement. Under this policy, it needs a dated note explaining the changed claim. A revised timestamp alone does not tell the reader what was wrong.
A product update can make previously correct advice stale. State the affected version or date when updating it. A spelling or formatting fix usually needs no separate correction note, but it must not be described as a new factual review.
What the dates mean
- Published is the original publication date.
- Updated records an edit to the page. It does not, by itself, prove a complete fact-check or a new hardware test.
- Last checked or a similar review label must describe the review actually performed. A check limited to prices, links, or one version must state that scope.
The standard does not allow dates to be refreshed solely to make old advice look new. Older pages may not yet meet every part of the current process; this policy is not a claim that every historical change already has a correction note.
Priority and response time
There is no guaranteed response or correction deadline. The priority is information that could expose private data, delete work, cause an unnecessary purchase, or misstate a license restriction. A report still needs verification before its proposed correction is accepted.
For a TechSmith account, purchase, refund, or license-recovery problem, contact TechSmith Support. SnagitPro's contact route is for the publication; it does not provide access to vendor accounts.
Policy correction, September 12, 2026: removed unsupported promises of live-interface checks and reading every report. Clarified the scope of review dates and the need to explain material factual corrections.
Last reviewed: September 12, 2026.