Contact Center page: publish the approved long-form copy without the 99.999% claim #219

New Issue

Closed

opened 2026-09-10 04:13:32 -05:00 by null · 1 comment

null commented

2026-09-10 04:13:32 -05:00

Owner

Levi Halford approved a change sheet for /services/contact-center on 2026-08-28: Contact SEO + Search Sheet APPROVED 2026-08-28.md, kept in .drop/2026-08-28-levi-uc-cc-sheets/ (gitignored client material). The sheet is the spec.

What is true now. The page renders from src/data/services.js through src/pages/ServiceDetail.jsx: title "Contact Center | Queue North", 131 words, three generic H2s, a run-on description, and an unattributed "99.999% uptime reliability" (src/data/services.js:35 and :46).

What to do.

Content in src/data/serviceContent/contact-center.js, a leaf module under page: { seo, hero, sections, related }, rendered by the long-form branch of ServiceDetail.jsx through the shared ContentBlocks renderer.
Title Contact Center & CCaaS Solutions | Queue North, H1 Contact Center & Customer Experience Solutions, the subheading, and the 191-character description, all verbatim (not clamped).
Hero copy under the hero; both CTAs ("Request a Contact Center Review", "Talk With an Engineer") to /contact#contact-form.
Sections 5 to 16 as H2s, each opening with its direct answer; the 17-step implementation sequence as an ol with its detail lines; section 16 ("Why Queue North Technologies?") is a list section with no answer paragraph; the section 11 principle as a callout.
FAQ (section 17) as visible h3 plus p, 10 questions. Related links with section 18's exact anchors: 6 targets, no Infrastructure Cabling.
Remove the 99.999% claim and the old fullDesc and benefits; keep idealFor, which the Services index shows as "Best fit".
Levi's 4 em dashes become commas or full stops, no word changes (Null's direction).

Traps.

Directions to the website manager are mixed into the copy: section 5's closing line, the Reliability wording block, "should be confirmed ... before publication", "Queue North should avoid implying...", "Avoid promising...", "This section should remain factual...". None are published; the content validator rejects them. "Availability varies by platform, edition, licensing, region, and release status." is copy and is published.
No FAQPage schema. Section ids must not start with a digit, so the 8x8 section needs an id like contact-center-8x8.
Read the sheet as raw UTF-8; it has curly quotes. The 8x8 and Webex screenshots are a separate issue.

Verify: the built dist/services/contact-center/index.html has the sheet's title, description and H1 exactly (entities decoded), one h1, every H2 and all 10 FAQ questions, no sheet direction, no 99.999 in dist/ or the bundle, and npm run verify passes.

Levi Halford approved a change sheet for `/services/contact-center` on 2026-08-28: `Contact SEO + Search Sheet APPROVED 2026-08-28.md`, kept in `.drop/2026-08-28-levi-uc-cc-sheets/` (gitignored client material). The sheet is the spec. **What is true now.** The page renders from `src/data/services.js` through `src/pages/ServiceDetail.jsx`: title "Contact Center | Queue North", 131 words, three generic H2s, a run-on description, and an unattributed "99.999% uptime reliability" (`src/data/services.js:35` and `:46`). **What to do.** - Content in `src/data/serviceContent/contact-center.js`, a leaf module under `page: { seo, hero, sections, related }`, rendered by the long-form branch of `ServiceDetail.jsx` through the shared `ContentBlocks` renderer. - Title `Contact Center & CCaaS Solutions | Queue North`, H1 `Contact Center & Customer Experience Solutions`, the subheading, and the 191-character description, all verbatim (not clamped). - Hero copy under the hero; both CTAs ("Request a Contact Center Review", "Talk With an Engineer") to `/contact#contact-form`. - Sections 5 to 16 as H2s, each opening with its direct answer; the 17-step implementation sequence as an `ol` with its detail lines; section 16 ("Why Queue North Technologies?") is a list section with no answer paragraph; the section 11 principle as a callout. - FAQ (section 17) as visible h3 plus p, 10 questions. Related links with section 18's exact anchors: 6 targets, no Infrastructure Cabling. - Remove the 99.999% claim and the old `fullDesc` and `benefits`; keep `idealFor`, which the Services index shows as "Best fit". - Levi's 4 em dashes become commas or full stops, no word changes (Null's direction). **Traps.** - Directions to the website manager are mixed into the copy: section 5's closing line, the *Reliability wording* block, "should be confirmed ... before publication", "Queue North should avoid implying...", "Avoid promising...", "This section should remain factual...". None are published; the content validator rejects them. "Availability varies by platform, edition, licensing, region, and release status." is copy and is published. - No FAQPage schema. Section ids must not start with a digit, so the 8x8 section needs an id like `contact-center-8x8`. - Read the sheet as raw UTF-8; it has curly quotes. The 8x8 and Webex screenshots are a separate issue. Verify: the built `dist/services/contact-center/index.html` has the sheet's title, description and H1 exactly (entities decoded), one h1, every H2 and all 10 FAQ questions, no sheet direction, no `99.999` in `dist/` or the bundle, and `npm run verify` passes.

null added this to the Batch 17: Long-form Unified Communications and Contact Center pages milestone 2026-09-10 04:13:32 -05:00

null added the

labels 2026-09-10 04:13:32 -05:00

null referenced this issue from a commit

2026-09-10 05:05:25 -05:00

feat(content): publish Levi's approved UC and Contact Center pages

null commented

2026-09-10 05:05:50 -05:00

Author

Owner

Shipped in aff8033. /services/contact-center now serves the approved sheet's copy: 2,499 words, 12 sections and 10 FAQs, from src/data/serviceContent/contact-center.js. Title 'Contact Center & CCaaS Solutions | Queue North', H1 'Contact Center & Customer Experience Solutions' and the 191-character description are byte-exact from the sheet. All 12 approved H2s and all 10 FAQ questions present, including the 17-step implementation sequence with its detail lines and the section 11 principle as a callout. The unattributed 99.999% uptime claim is gone from src/ and from the built pages, as section 7 instructed. Levi's four em dashes are commas and full stops, no word changed. Browser checks at four viewports clean; all 13 section anchors deep-link.

Shipped in aff8033. /services/contact-center now serves the approved sheet's copy: 2,499 words, 12 sections and 10 FAQs, from src/data/serviceContent/contact-center.js. Title 'Contact Center & CCaaS Solutions | Queue North', H1 'Contact Center & Customer Experience Solutions' and the 191-character description are byte-exact from the sheet. All 12 approved H2s and all 10 FAQ questions present, including the 17-step implementation sequence with its detail lines and the section 11 principle as a callout. The unattributed 99.999% uptime claim is gone from src/ and from the built pages, as section 7 instructed. Levi's four em dashes are commas and full stops, no word changed. Browser checks at four viewports clean; all 13 section anchors deep-link.

null closed this issue

2026-09-10 05:05:50 -05:00