diff --git a/src/content/docs/test-insights/test-frameworks/playwright.mdx b/src/content/docs/test-insights/test-frameworks/playwright.mdx
index 5768583186..4876817223 100644
--- a/src/content/docs/test-insights/test-frameworks/playwright.mdx
+++ b/src/content/docs/test-insights/test-frameworks/playwright.mdx
@@ -7,6 +7,7 @@ import playwrightLogo from "../../../images/ci-insights/playwright/logo.svg"
 import IntegrationLogo from "../../../../components/IntegrationLogo.astro"
 import CIInsightsSetupNote from "../../../../components/CIInsightsSetupNote.astro"
 import BuildkiteTokenNote from "../../../../components/BuildkiteTokenNote.astro"
+import ReviewInTestInsights from "./_review-in-test-insights.mdx"
 
 <IntegrationLogo src={playwrightLogo} alt="Playwright logo" />
 
@@ -126,9 +127,6 @@ steps:
 The reporter automatically collects your test results and sends them to Test
 Insights.
 
-Check the Test Insights dashboard afterward to view execution metrics, detect
-flaky tests, and review test trends.
-
 ## Multi-Project (Cross-Browser) Runs
 
 If your `playwright.config.ts` defines multiple
@@ -154,6 +152,13 @@ env:
 This option is opt-in (off by default) to preserve the history of tests that
 already report without a project prefix.
 
+## Verify and Review in Test Insights
+
+After pushing these changes, your next CI run reports its Playwright results
+automatically.
+
+<ReviewInTestInsights />
+
 ## Environment Variables
 
 | Variable | Purpose | Default |
diff --git a/src/content/docs/test-insights/test-frameworks/pytest.mdx b/src/content/docs/test-insights/test-frameworks/pytest.mdx
index dc6bbcdb76..6e6ba8cf87 100644
--- a/src/content/docs/test-insights/test-frameworks/pytest.mdx
+++ b/src/content/docs/test-insights/test-frameworks/pytest.mdx
@@ -7,6 +7,7 @@ import pytestLogo from "../../../images/ci-insights/pytest/logo.svg"
 import IntegrationLogo from "../../../../components/IntegrationLogo.astro"
 import CIInsightsSetupNote from "../../../../components/CIInsightsSetupNote.astro"
 import BuildkiteTokenNote from "../../../../components/BuildkiteTokenNote.astro"
+import ReviewInTestInsights from "./_review-in-test-insights.mdx"
 
 <IntegrationLogo src={pytestLogo} alt="Pytest logo" />
 
@@ -104,9 +105,6 @@ steps:
 
 The plugin collects your test results and sends them to Test Insights.
 
-Check the Test Insights dashboard afterward to view execution metrics, detect
-flaky tests, and review test trends.
-
 ## Using with Tox
 
 If you’re using [Tox](https://tox.wiki/) to manage test environments, you can
@@ -176,6 +174,13 @@ steps:
 ```
 
 :::tip
-Use `MERGIFY_TEST_JOB_NAME` to make reports clearer in Test Insights, especially when
-running multiple Tox environments or using a matrix.
+  Use `MERGIFY_TEST_JOB_NAME` to make reports clearer in Test Insights,
+  especially when running multiple Tox environments or using a matrix.
 :::
+
+## Verify and Review in Test Insights
+
+After pushing these changes, your next CI run reports its pytest results
+automatically.
+
+<ReviewInTestInsights />
diff --git a/src/content/docs/test-insights/test-frameworks/rspec.mdx b/src/content/docs/test-insights/test-frameworks/rspec.mdx
index 7d422caba7..00bf87be97 100644
--- a/src/content/docs/test-insights/test-frameworks/rspec.mdx
+++ b/src/content/docs/test-insights/test-frameworks/rspec.mdx
@@ -7,6 +7,7 @@ import rspecLogo from "../../../images/ci-insights/rspec/logo.svg"
 import IntegrationLogo from "../../../../components/IntegrationLogo.astro"
 import CIInsightsSetupNote from "../../../../components/CIInsightsSetupNote.astro"
 import BuildkiteTokenNote from "../../../../components/BuildkiteTokenNote.astro"
+import ReviewInTestInsights from "./_review-in-test-insights.mdx"
 
 <IntegrationLogo src={rspecLogo} alt="RSpec logo" />
 
@@ -84,8 +85,12 @@ steps:
 
 The gem automatically collects your test results and sends them to Test Insights.
 
-Check the Test Insights dashboard afterward to view execution metrics, detect
-flaky tests, and review test trends.
+## Verify and Review in Test Insights
+
+After pushing these changes, your next CI run reports its RSpec results
+automatically.
+
+<ReviewInTestInsights />
 
 ## Environment Variables
 
@@ -99,11 +104,11 @@ flaky tests, and review test trends.
 | `MERGIFY_TEST_JOB_NAME` | Test job name identifier | Optional |
 
 :::tip
-The gem auto-activates in CI environments (detected via the `CI` environment
-variable). To enable it outside CI, set `RSPEC_MERGIFY_ENABLE=true`.
+  The gem auto-activates in CI environments (detected via the `CI` environment
+  variable). To enable it outside CI, set `RSPEC_MERGIFY_ENABLE=true`.
 :::
 
 :::tip
-Use `MERGIFY_TEST_JOB_NAME` to make reports clearer in Test Insights, especially
-when running multiple test suites or using a matrix strategy.
+  Use `MERGIFY_TEST_JOB_NAME` to make reports clearer in Test Insights,
+  especially when running multiple test suites or using a matrix strategy.
 :::
diff --git a/src/content/docs/test-insights/test-frameworks/vitest.mdx b/src/content/docs/test-insights/test-frameworks/vitest.mdx
index 2af4eef169..2fec50a076 100644
--- a/src/content/docs/test-insights/test-frameworks/vitest.mdx
+++ b/src/content/docs/test-insights/test-frameworks/vitest.mdx
@@ -7,6 +7,7 @@ import vitestLogo from "../../../images/ci-insights/vitest/logo.svg"
 import IntegrationLogo from "../../../../components/IntegrationLogo.astro"
 import CIInsightsSetupNote from "../../../../components/CIInsightsSetupNote.astro"
 import BuildkiteTokenNote from "../../../../components/BuildkiteTokenNote.astro"
+import ReviewInTestInsights from "./_review-in-test-insights.mdx"
 
 <IntegrationLogo src={vitestLogo} alt="Vitest logo" />
 
@@ -97,8 +98,12 @@ steps:
 The reporter automatically collects your test results and sends them to Test
 Insights.
 
-Check the Test Insights dashboard afterward to view execution metrics, detect
-flaky tests, and review test trends.
+## Verify and Review in Test Insights
+
+After pushing these changes, your next CI run reports its Vitest results
+automatically.
+
+<ReviewInTestInsights />
 
 ## Environment Variables