[ngayerie]

Adds channel-selection guidance and fixes several content issues on the Contacting Cloudflare Support page.

DEE-4049

What changed

• Add "Phone, chat, or support case?" decision table so customers know which channel to use for which type of request
• State live chat weekend hours: unavailable Friday 17:00 PT (00:00 UTC Saturday) to Sunday 18:00 PT (01:00 UTC Monday)
• Add footnote to Methods table noting chat is Monday–Friday only
• Point Business plan customers to live chat for urgent weekday issues
• Fix step 6 nested list in Submit a support case: remove literal \- artifacts and deduplicate repeated "Steps to reproduce" and "actual vs expected results" items
• Remove redundant "Finding your Unique Customer ID" subsection; fold location of the Unique Customer ID into the Emergency phone support intro
• Merge "View open support cases" and "Add participants to open support tickets" into a single "Manage support cases" subsection
• Fix sentence-case headings: "Emergency Phone Support" → "Emergency phone support"; "Service Level Agreements and Objectives" → "Service level agreements and objectives"
• Remove positional language ("Below are definitions of the priority levels")
• Replace utilize with use in footnote; remove broken anchor #getting-help-with-an-issue
• Update SLOs section to name Business/Pro/Free explicitly; remove duplicate Free plan case limitation statement

[cloudflare-docs-bot]

AI Review

✅ Reviewed e8c9c0b · 9 findings · incremental

👉 Fix in your agent 👈

Fix the following review findings in PR #34705 (https://github.com/cloudflare/cloudflare-docs/pull/34705).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification.
- If you disagree, explain why.
- If you need clarification before deciding, ask those questions.
- Then share your plan for which issues to tackle and in what order.

After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.

The comment must come before the commit because the next review reads PR comments.

## Style Guide
- S-0953c089 | src/content/docs/support/contacting-cloudflare-support.mdx:51 | Heading ends with a question mark
  Per the headings rule, a heading must not end with `.`, `?`, `!`, or `:`; `## Phone, chat, or support case?` ends with `?`.
- S-1d1023bf | src/content/docs/support/contacting-cloudflare-support.mdx:85 | Directional word `below`
  Per the writing style rule, directional words such as `below` must be replaced with a direct reference by name or link; the sentence still refers to the `method below`.
- S-0a7933cc | src/content/docs/support/contacting-cloudflare-support.mdx:110 | Use `select` instead of `click`
  The step uses `click` for a UI element; per the style guide, use `select` for UI elements.
- S-121caa1a | src/content/docs/support/contacting-cloudflare-support.mdx:100 | Use `select` instead of `click`
  The step uses `click` for a UI element; per the style guide, use `select` for UI elements.
- S-10dec545 | src/content/docs/support/contacting-cloudflare-support.mdx:135 | Use `select` instead of `click`
  The step uses `click` three times for UI elements (`Technical Support` tile, `Billing`, `Create a Case`); per the style guide, use `select` for UI elements.
- S-0457c7be | src/content/docs/support/contacting-cloudflare-support.mdx:160 | Use `select` instead of `click`
  The step uses `click` for a UI element; per the style guide, use `select` for UI elements.
- S-1d9dcaeb | src/content/docs/support/contacting-cloudflare-support.mdx:205 | Use `select` instead of `click`
  The step uses `click` for a UI element; per the style guide, use `select` for UI elements.
- S-01fc9e1c | src/content/docs/support/contacting-cloudflare-support.mdx:211 | Use `select` instead of `click`
  The step uses `click` for a UI element; per the style guide, use `select` for UI elements.
- S-0af1cacb | src/content/docs/support/contacting-cloudflare-support.mdx:232 | Use `select` instead of `click`
  The step uses `click` for a UI element; per the style guide, use `select` for UI elements.

Style Guide

• src/content/docs/support/contacting-cloudflare-support.mdx:51 · Heading ends with a question mark

  Per the headings rule, a heading must not end with ., ?, !, or :; ## Phone, chat, or support case? ends with ?.

• src/content/docs/support/contacting-cloudflare-support.mdx:85 · Directional word below

  Per the writing style rule, directional words such as below must be replaced with a direct reference by name or link; the sentence still refers to the method below.

• src/content/docs/support/contacting-cloudflare-support.mdx:110 · Use select instead of click

  The step uses click for a UI element; per the style guide, use select for UI elements.

• src/content/docs/support/contacting-cloudflare-support.mdx:100 · Use select instead of click

  The step uses click for a UI element; per the style guide, use select for UI elements.

• src/content/docs/support/contacting-cloudflare-support.mdx:135 · Use select instead of click

  The step uses click three times for UI elements (Technical Support tile, Billing, Create a Case); per the style guide, use select for UI elements.

• src/content/docs/support/contacting-cloudflare-support.mdx:160 · Use select instead of click

  The step uses click for a UI element; per the style guide, use select for UI elements.

• src/content/docs/support/contacting-cloudflare-support.mdx:205 · Use select instead of click

  The step uses click for a UI element; per the style guide, use select for UI elements.

• src/content/docs/support/contacting-cloudflare-support.mdx:211 · Use select instead of click

  The step uses click for a UI element; per the style guide, use select for UI elements.

• src/content/docs/support/contacting-cloudflare-support.mdx:232 · Use select instead of click

  The step uses click for a UI element; per the style guide, use select for UI elements.

Commands

• /review Run a review now.
• /full-review Review the entire PR diff.
• /disable-auto-review Stop automatic reviews.
• /rebase Rebase against production.

[github-actions]

Worker Preview URL: https://gh-ngayerie-dee-4049-contact-support-channel-gu.previews.developers.cloudflare.com
Worker Preview Deployment URL: https://3a04e361.previews.developers.cloudflare.com

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/support/contacting-cloudflare-support/	https://gh-ngayerie-dee-4049-contact-support-channel-gu.previews.developers.cloudflare.com/support/contacting-cloudflare-support/

[cloudflare-workers-and-pages]

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://ngayerie-dee-4049-contact-support-channel-guide.previews.developers.cloudflare.com (commit e8c9c0b)

This URL reflects your latest Preview deployment

Preview Deployments by commit

Status	Deployment URL	Commit	Updated (UTC)	See this deployment's details
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://8ec20d79.previews.developers.cloudflare.com	e8c9c0b	2026-10-28T23:41:23.383Z	Visit the dashboard ↗