diff --git a/communicate/maintenance-windows/overview.mdx b/communicate/maintenance-windows/overview.mdx
index cf416ff9..41b2b584 100644
--- a/communicate/maintenance-windows/overview.mdx
+++ b/communicate/maintenance-windows/overview.mdx
@@ -111,7 +111,7 @@ If you publish a [status page](/communicate/status-pages/overview), you can show
See [Status page maintenance](/communicate/status-pages/maintenance-windows) for the full guide.
-Showing maintenance on a status page is part of the Communicate add-on. [View pricing](https://checklyhq.com/pricing).
+Showing maintenance on a status page is available on Communicate Team and Enterprise plans. [View pricing](https://checklyhq.com/pricing).
## Monitoring maintenance status
diff --git a/communicate/status-pages/incidents.mdx b/communicate/status-pages/incidents.mdx
index 8f232a06..e18c2ce9 100644
--- a/communicate/status-pages/incidents.mdx
+++ b/communicate/status-pages/incidents.mdx
@@ -70,7 +70,7 @@ Subscribing to incident notifications is done on your status page. To subscribe,
## Incident automation
-Incident automation is available on Team and Enterprise plans. [View pricing](https://checklyhq.com/pricing)
+Incident automation is available on Communicate Team and Enterprise plans. [View pricing](https://checklyhq.com/pricing)
Automation rules open incidents automatically when checks fail. A rule matches checks by **tag**: when a check carrying one of the rule's tags fails and triggers an alert, the rule opens one incident impacting the components it lists. The incident resolves automatically when the check recovers.
diff --git a/communicate/status-pages/overview.mdx b/communicate/status-pages/overview.mdx
index 258409a8..5a0ce997 100644
--- a/communicate/status-pages/overview.mdx
+++ b/communicate/status-pages/overview.mdx
@@ -47,7 +47,7 @@ Automation rules open and resolve incidents based on your checks. A rule matches
Manage rules on the **Automation** tab of your status page, or in code with the [`StatusPageV3AutomationRule`](/constructs/status-page-v3-automation-rule) construct or the [`checkly_status_page_v3_automation_rule`](https://registry.terraform.io/providers/checkly/checkly/latest/docs/resources/status_page_v3_automation_rule) Terraform resource.
-Incident automation is available on Team and Enterprise plans. [View pricing](https://checklyhq.com/pricing)
+Incident automation is available on Communicate Team and Enterprise plans. [View pricing](https://checklyhq.com/pricing)
## Uptime calculation
@@ -64,6 +64,28 @@ Uptime = ((Total time - Weighted downtime) / Total time) × 100
A group shows the average uptime of its child components. Uptime is driven by incidents, not directly by check results: without an automation rule or a manually created incident, a failing check does not lower uptime.
+## Plans
+
+Status page features come with your **Communicate** plan, which is separate from the plan for your checks and monitors. A Team plan for checks doesn't include the Communicate Team features below.
+
+| Feature | Communicate plan |
+|---------|------------------|
+| Status pages, components and email subscribers | All, including Communicate Hobby |
+| [Custom domain](/communicate/status-pages/custom-domain) | Starter, Team and Enterprise |
+| [Incident automation](/communicate/status-pages/incidents#incident-automation) | Team and Enterprise |
+| [Status page maintenance](/communicate/status-pages/maintenance-windows) | Team and Enterprise |
+| [Password protection](/communicate/status-pages/password-protection) | Team and Enterprise |
+| [Theme customization](/communicate/status-pages/customization) | Team and Enterprise |
+
+See [pricing](https://www.checklyhq.com/pricing/) for limits such as the number of pages and subscribers.
+
+## Status pages and dashboards
+
+Status pages and [dashboards](/communicate/dashboards/overview) both share health outside the Checkly app, but they answer different questions:
+
+- **Status pages** show your services as your customers see them. Each component's status and uptime come from incidents, which you open manually or with automation rules, so a failing check only affects the page when it opens an incident. Visitors can subscribe to updates.
+- **Dashboards** show your checks directly: each check's live status, availability and response times, filtered by tag. Use them for internal teams or technical audiences who want to see the monitoring results themselves.
+
## Monitoring as code
Status pages, components, and automation rules can be fully managed with the Checkly CLI. See the [`StatusPageV3`](/constructs/status-page-v3) construct. `checkly import status-page:` imports an existing page with its components and rules into your project.