Review Copilot availability memo
This is a fictional announcement for Review Copilot, an example product used to practice review.
Audience
Enterprise admins and developer productivity leads who need a clear rollout note before enabling Review Copilot for more teams.
Customer message
Review Copilot is available for teams that review Markdown PRs, branch documents, generated HTML reports, Draft Reviews, review consensus, Knowledge Brain repositories, and opted-in preview-app feedback in Commentary.
The feature helps reviewers collect comments in one document-first workspace while keeping GitHub and Azure DevOps as the source of truth. It also gives agents a bounded context packet so they can propose changes without scraping private rendered pages.
What customers can try
| Review surface | Best first use | Sign-in requirement |
|---|---|---|
| Public Markdown PR | Read a rendered launch brief | Read-only without sign-in |
| Static HTML report | Review generated migration output | Sign in to comment |
| Draft Review | Review pre-Git customer copy | Owner signs in to create |
| Live Preview Review | Comment on a UI control | Preview owner opts in with SDK |
Rollout guidance
Start with documentation-heavy repositories, then expand to release notes, support playbooks, and generated reports after the first two review cycles. Keep Pro-preview features usable during the no-billing phase and show the reusable Pro notification when the UI surfaces gated creation paths.
Support handoff
Support should be ready to explain the difference between rendered document review, provider line comments, sandboxed HTML Preview, and opted-in Live Preview Reviews.
Open edits
- Add billing-language examples before sending to customers.
- Name the owner for rollback communication.
- Verify billing and checkout use consistent effective-date language before launch.