Work AI Brief keeps a visible corrections path for stale tool claims, pricing changes, broken workflow advice, and missing source context.
When to send a correction
- A pricing, availability, feature, or policy claim is wrong
- A workflow explanation now hides a material risk or unresolved unknown
- A source is missing for a claim that changes the reader decision
What to include
- Send the page URL and the exact claim that needs review.
- Include the source, changelog, release note, or product page that supports the correction.
- Expect an acknowledgement within the stated response window and a public fix if the change is material.
Response target
We aim to acknowledge factual correction requests within 3 business days.
How updates appear
Material fixes are reflected on the page. When the correction changes the meaning of the recommendation or workflow rule, the update should be visible to readers.