Overview

Everything registered for VitalCX in 00-admin/artifacts.json, generated from the approved PreWiki projection

Core Principle

Every client brain should separate source material, approved truth, strategy synthesis, active work, and learnings. Oracle can then answer from the right layer instead of mixing raw notes with approved claims.

Promotion Rule

Raw notes and meeting comments do not automatically become approved client truth. They move through this path:

Agency Workflow Rule

Every strategic idea should be traceable to at least one of:

• Client-approved source.
• Meeting log.
• Public research source.
• Strategy article.
• Performance learning.
• Prehealth operator judgment clearly labeled as inference.

Overview

Use this file to capture the operator interview.

Question Log

1. What is VitalCX's official website and one-sentence description in your words?

• Kapture CX: https://www.kapture.cx
• Sierra AI: https://sierra.ai

One-Line Description

VitalCX is a Healthcare Experience Platform that automates and coordinates operational work between patients and care teams.

Category

Healthcare Experience Platform (HXP).

Category Claim

The Only Global Healthcare Experience Platform.

Business Model

The source implies a B2B healthcare platform serving hospitals, health systems, clinics/providers, urgent care, and RCM companies. Pricing and packaging are still unknown.

Products And Services

• VitalCX: primary platform brand.
• GraceAI: AI sub-product for real-time healthcare interactions.
• VXN / Vital Experience Network: network/partner sub-brand.
• VCX: abbreviated shorthand logo mark.

Operational Scope

• Scheduling
• Triage
• Referrals
• Outreach
• Medical records
• Revenue cycle management

Prehealth Responsibilities

Primary V1 responsibility: Website 2.0 for SEO/AEO dominance.

• Website strategy.
• Information architecture.
• SEO/AEO content architecture.
• Category narrative and page messaging.
• Competitor-positioning strategy against Kapture CX and Sierra AI.
• Brand-faithful web copy.
• Conversion path planning for demo requests.
• Claims-safe proof point usage.

First Deliverables

1. Website 2.0 strategy brief.

Timeline

Unknown.

Approval Stakeholders

Unknown.

Questions For Operator

• Who owns final Website 2.0 approval?
• What CMS, hosting, analytics, and SEO stack will the site use?
• Are we replacing the current site entirely or evolving it in phases?
• What is the target launch date?

Objective

Build VitalCX Website 2.0 into the authoritative web presence for Healthcare Experience Platform search and answer-engine discovery.

Primary Strategic Priority

SEO/AEO dominance.

• Traditional search results.
• AI answer-engine references.
• Category-definition queries.
• Healthcare workflow automation queries.
• Patient access and revenue cycle operations queries.
• Competitor comparison and alternative queries.

Category Territory

VitalCX should own the idea that healthcare experience is created in operational moments: scheduling, triage, referrals, outreach, medical records, revenue cycle, patient access, billing, and the handoffs between patients and care teams.

Direct Competitors

• Kapture CX: https://www.kapture.cx
• Sierra AI: https://sierra.ai

Website 2.0 Narrative Spine

1. Define the category: Healthcare Experience Platform.

SEO/AEO Content Pillars

1. Healthcare Experience Platform

Source Role

This file summarizes the new 2026 website Figma archive for Oracle. It updates the visual implementation layer, component library, and agent-output display rules. It does not replace the approved VitalCX strategic foundation, voice guide, or claim-safety rules.

Extraction Summary

• Figma file name: VCX | 2026 Website Design
• Exported at: 2026-07-02T17:02:38.491Z
• Archive version: 106
• Node changes parsed: 50883
• Pages parsed: COVER, Internal Only Canvas, ----------------------------------------, -------, ------, ----, ARCHIVE, ---, WIREFRAMES, LAYOUT, BRAND, ---, LIBRARY, ---, CHROME, INSPO
• Thumbnail stored as: thumbnail.png
• Token payload stored as: design-tokens-2026.json

Layout Pages

• SECTION: 0.0-VCX-Home
• SECTION: 3.0-VCX-Who We Serve
• SECTION: 3.1-3.3-VCX-WWS-Subcats-Template
• SECTION: VCX-Nav
• FRAME: VCX-Phase 2-Sitemap
• SECTION: 1.0-VCX-Platform
• SECTION: 2.0-VCX-Solutions
• SECTION: 4.0-VCX-Success-Stories

Library Sections

• SECTION: Icons
• SECTION: Assets
• SECTION: Inputs
• SECTION: Button + Link
• SECTION: Dividers
• SECTION: Header
• SECTION: Tabs
• SECTION: Micro-Elements

Component Signals

• Row/Cards (560 instances)
• Icon (319 instances)
• Link (304 instances)
• card (191 instances)
• Arrow (184 instances)
• Color Chip (178 instances)
• icon (133 instances)
• Card (107 instances)

Website Copy Signals

• ©VitalCX All RIghts Reserved
• Version 1.0 © 2026 VitalCX All rights reserved vitalcx.com
• For information contact: email@vitalcx.com
• 1.555.555.1234 email@vitalcx.com
• We create clarity patients can feel.
• Customer Experience
• 1234 Main St. Anywhere, NY
• Healthcare Operations Excellence

Overview

Canonical logo folder: PreWiki/Clients/VitalCx/Oracle Brain/Brand Assets/Logos/.

Colorway naming

Note the reversed accent is Soft Sky #A3C7FF, not Vital Blue: Vital Blue lacks contrast on

VitalCX full lockup: 1012 × 242, 4.18:1

vital-cx-full-black-TM.svg · vital-cx-full-white-TM.svg · vital-cx-full-white-blue-TM.svg ·

VCX compact mark: 578 × 208, 2.78:1

vcx-full-black-blue-TM.svg (primary) · vcx-full-black-TM.svg · vcx-white-blue-TM.svg ·

VXN mark: 700 × 214, 3.27:1

vxn-black-blue-TM.svg · vxn-black-TM.svg · vxn-white-blue-TM.svg · vxn-white-blue-TM-1.svg (actually mono white: see Defects)

Vital Experience Network lockup: 1202 × 232, 5.18:1

vital-exp-net-black-blue-TM.svg · vital-exp-net-black-TM.svg ·

Overview

This run ingested the design bundle at

What the bundle defines

Total machine tokens extracted: 134 → 03-brand/design-tokens.json (grouped, with

Structure map (bundle)

vitalcx-design-system/

Conflicts (open questions for the brand owner: captured, NOT resolved)

1. Deck fonts vs website fonts.

• Deck harvest (/Users/cleverish/predeck/work/vitalcx/client-spec.json, harvested from
• Design-system bundle (colorsandtype.css): display Fields / Fields Display +
• Both are real, both source-backed. Presentations currently follow the deck harvest;
• Bundle: --text-primary → --color-black #1C1A19.
• 2026 Figma extraction (03-brand/figma-2026-patterns.md, master-brand-guide 2026
• #001E4D does not exist anywhere in the bundle token set. Open question: which text
• Bundle: Ocean Navy #003181 (Primary 800).
• 2026 Figma extraction: deep navy #001E4D. Near-duplicate roles; both captured,

Gaps: not defined in the bundle (honest empty sections, nothing invented)

rules (subtle transitions, hover→Vital Blue border, no bounces, no infinite loops).

• Motion tokens: no duration/easing/curve tokens. Motion exists only as qualitative
• Grid tokens: no column/gutter grid definition beyond --max-width and page padding.
• Breakpoint tokens: none defined.
• Icon SVG exports: custom two-tone icon set exists only inside the Figma file
• GraceAI logo: described in README.md (glyph forms a "G" echoing a power-on symbol)
• Success semantic color: --color-success-bg aliases --color-vital-blue; there is
• Template frames with META.TEMPLATE / SLOT.\ grammar: the bundle is a rank-4 source

NEEDS-SOURCE register

placeholder traces to the bundle, master-brand-guide.md, voice-messaging.md, or

• 03-brand/interactive-brand-guide.html: zero NEEDS-SOURCE values, every filled
• 03-brand/design-tokens.json / design-tokens.css: none (pure extraction).
• Blocked-by-gap items (not NEEDS-SOURCE tokens, but unbuildable until sourced):

Brand Essence

VitalCX makes healthcare operations feel coordinated, visible, accountable, and human. The brand should express operational precision without losing the emotional stakes of patient experience.

Category Claim

The Only Global Healthcare Experience Platform.

Positioning Statement

For hospitals, health systems, clinics/providers, and RCM companies, VitalCX is a Healthcare Experience Platform that handles and automates the operational work between patients and care teams: scheduling, triage, referrals, outreach, medical records, and revenue cycle management.

Core Tagline

Customer experience is vital. And nothing is more vital than healthcare.

Brand Promise

Create clarity patients can feel by turning operational reliability into better patient experiences.

Personality Traits

• Confident
• Warm
• Authoritative
• Precise
• Humane
• Clinically credible
• Calm under complexity

Must Always Do

• Lead with clarity, coordination, accountability, and patient experience.
• Maintain clinical credibility with a warm, human edge.
• Use Fields/Fields Display for headlines and Albert Sans for body/UI.
• Use Vital Blue as the primary brand color.
• Use the "V" frame system as the primary graphic device.
• Use custom two-tone icons, or clearly flag Lucide as a fallback.
• Use source-backed claims for healthcare, compliance, and performance statements.

Must Never Do

• Do not use emoji in final brand assets.
• Do not use unsupported metrics, testimonials, or HIPAA claims outside the V1-approved design-system source.
• Do not use corporate jargon or generic AI hype.
• Do not rely on complex gradients, patterns, textures, or decorative illustration systems.
• Do not use warm golden photo treatments.
• Do not set display headlines in all caps.
• Do not mix VitalCX context with any other Prehealth client.

Escalate To Human When

• A claim involves HIPAA, compliance, clinical outcomes, revenue results, cost savings, speed improvements, retention, or patient satisfaction.
• A metric appears in the UI kit but has not been separately approved.
• A visual direction requires custom iconography that is not in the source bundle.
• A deliverable mentions hospitals, health systems, clinics, RCM companies, urgent care, or AI capabilities in a way that may imply specific proof.

Voice Principles

• Confident, warm, authoritative.
• Clinical credibility balanced with empathy.
• Short, declarative sentences with a humane edge.
• Direct and precise; avoid corporate jargon.
• Pair technical capability with emotional resonance.
• Make operations feel like patient experience, not back-office plumbing.

Perspective

• Use second person for customer-facing copy: your business, your patients, your care teams.
• Use first person for brand statements: We create clarity patients can feel.
• Keep the customer and patient impact visible.

Casing

• Headlines: sentence case. Never all caps for display headlines.
• Eyebrows/labels: uppercase, tracked out, small size.
• Button labels: Title Case, e.g. Schedule a Demo, Request Demo.
• Subheads/body: sentence case.

Words And Phrases To Use

• Healthcare Experience Platform
• visibility
• coordination
• accountability
• clarity
• patient experience
• care teams
• operational reliability

Words And Patterns To Avoid

• Bloated enterprise-speak.
• Generic AI hype.
• Casual slang.
• Emoji.
• Unsupported superlatives beyond approved positioning.
• Claims about HIPAA, outcomes, savings, speed, retention, or patient satisfaction unless approved.

Approved Copy Examples From Source

• The Only Global Healthcare Experience Platform.
• We create clarity patients can feel.
• Everything between patients and care.
• Six core services, one coordinated platform.
• Visibility and accountability at every step.
• Intelligent technology purpose-built for healthcare.
• Trained by experts, guided by human-centered design.

Primary ICP

Healthcare organizations responsible for high-volume patient interactions and operational coordination.

Named Audiences From Source

• Hospitals
• Health systems
• Clinics/providers
• RCM companies
• Urgent care organizations

Buyer/User/Champion Distinction

Needs operator confirmation.

• Economic buyers: health system executives, operations leaders, patient experience leaders, revenue cycle executives.
• Operational champions: patient access, scheduling, care coordination, RCM, clinical operations, contact center, and digital transformation leaders.
• Daily users: care team staff, patient access teams, billing/RCM teams, outreach teams, referral coordinators.

Jobs To Be Done

• Coordinate patient interactions across fragmented workflows.
• Reduce manual operational work between patients and care teams.
• Improve visibility and accountability across scheduling, triage, referrals, outreach, records, and RCM.
• Deliver a calmer, clearer patient experience.
• Support staff with AI that reduces friction instead of adding complexity.

Pains And Objections

Source-backed pains:

• Missed callbacks.
• Unclear instructions.
• Long hold times.
• Patients falling through referral gaps.
• Manual back-and-forth around records and coordination.
• Operational complexity creating patient experience breakdowns.
• Security/compliance confidence.
• Integration effort.

Desired Outcomes

• Timely, coordinated care at scale.
• More visible and accountable patient-care team interactions.
• Reduced patient and staff friction.
• Better operational reliability.
• Better patient experience.

Core Offers

The uploaded design system presents VitalCX as one coordinated platform with six core service areas:

Product Architecture

• VitalCX: primary Healthcare Experience Platform.
• GraceAI: AI sub-product for real-time patient interactions and healthcare-specific intelligence.
• VXN / Vital Experience Network: network/partner brand.
• VCX: shorthand logo/mark.

Packaging And Pricing Notes

Unknown from uploaded source.

Funnel Stages

Inferred from UI kit:

• Awareness: category claim and HXP positioning.
• Consideration: platform services and solutions by audience.
• Conversion: Request Demo / Schedule a Demo.
• Sales enablement: service-specific proof and operational use cases.

Sales Objections

Likely objections needing operator confirmation:

• HIPAA/security risk.
• AI accuracy/trust in healthcare.
• Integration complexity.
• Operational change management.
• Proof that the platform improves patient and business outcomes.

Enablement Assets

Available source-backed assets:

• Brand guide/design system.
• Website UI kit.
• Logos and fonts.
• Platform service copy.
• GraceAI product spotlight copy.
• Approved sales deck.
• Case studies.
• Pricing/packaging.

V1 Approval Scope

The following metrics and testimonial language come from the uploaded VitalCX design system and are approved for V1 use.

Safe Non-Quantitative Proof Language

• Healthcare-specific platform.
• Human-centered design.
• Six coordinated operational service areas.
• Visibility and accountability across patient-care team interactions.

Reapproval Trigger

Reconfirm these claims before using them outside the V1 Oracle/brand system rollout, especially in paid media, regulated claims, investor materials, or final legal-approved web launches.

Website

• Lead with category clarity.
• Use Fields headlines and Albert Sans body/UI.
• Use pill CTAs with arrow-circle pattern.
• Keep copy declarative and precise.
• Build for SEO/AEO dominance.
• Include concise answer blocks and question-led sections.
• Create page clusters around Healthcare Experience Platform, GraceAI, patient access automation, referrals, outreach, medical records, RCM, and competitor alternatives.
• Use V1-approved proof points where they strengthen conversion and answer authority.

Social

• Use insight-led hooks.
• Avoid casualness, emoji, and unapproved metrics.
• Tie each post to healthcare operations and patient experience.

Sales Enablement

• Keep proof claims citation-aware.
• Organize by buyer problem, platform capability, operational impact, and risk reduction.
• Include compliance/legal review for healthcare-sensitive claims.

Ads

• No quantitative claims unless approved.
• Avoid generic AI hype.
• Use direct promise plus healthcare-specific context.

SEO/AEO

• Define terms in plain language before expanding.
• Use direct answers near the top of pages.
• Build comparison pages around category fit, not attack copy.
• Use structured FAQ sections.
• Tie every topic back to healthcare operations and patient experience.
• Avoid generic "AI customer service" language unless contrasting against competitors.

Priority Channels

Primary priority: Website 2.0 for SEO/AEO dominance.

Content Pillars

1. Healthcare experience is operational.

• Patient experience breaks in the handoffs, wait times, unclear instructions, referrals, records, and billing moments.
• VitalCX coordinates the operational layer that sits between patient need and care delivery.
• GraceAI is trained by healthcare experts and guided by human-centered design.
• Operational reliability becomes a calmer, clearer patient experience.
• Scheduling, triage, referrals, outreach, medical records, and RCM as one coordinated platform.
• Missed referrals, billing errors, unclear communication, and delays are not back-office issues; they affect care.

Recurring Formats

• Category POV posts.
• Service-specific explainers.
• GraceAI product spotlights.
• Patient-experience belief posts.
• Operational breakdown carousels.
• Sales enablement snippets.
• Website/product page sections.

Posting Cadence

Unknown. Needs operator confirmation.

Hooks And Angles

Source-backed or source-derived:

• Healthcare runs on moments.
• Clarity is the product.
• Operational excellence is patient care.
• Technology should reduce stress, not add complexity.
• People deserve better than automated indifference.
• Close the referral loop, every time.
• Route patients to the right care, faster.

Existing Winners

Unknown.

Source Snapshot

• URL: https://artera.io/
• Date accessed: 2026-06-28
• Source ID: SRC-021
• Raw source: 01-sources/raw-urls/2026-06-28/competitors/artera/homepage.md
• Homepage screenshot: 01-sources/screenshots/2026-06-28/competitors/artera/homepage.png
• Role: Discovered direct/adjacent healthcare communication competitor
• Segment: Healthcare AI agents / patient communications

Brand Positioning

Artera positions around healthcare ai agents / patient communications. The captured homepage makes this visible through the lead line, product navigation, and workflow terms recorded in the source capture.

Messaging And UX Signals

• Primary headline: AI Agents for Healthcare
• Product story: AI service squads for calls, intake, scheduling, payments, referrals, care gap closure, and communications.
• Visual audit note: use the captured homepage screenshot for design review and deck reference.

Source-Backed Strengths

• Clear ownership of healthcare ai agents / patient communications language.
• Public homepage provides concrete workflow terms that can inform VitalCX comparison strategy.
• Competitor is useful for SEO/AEO category mapping and Website 2.0 positioning.

Weaknesses Or Gaps

These are strategic inferences from the captured homepage, not claims about product performance.

• VitalCX should own the operating layer across communication plus operations.
• VitalCX should avoid attacking this competitor and instead clarify the category boundary.

VitalCX Website 2.0 Opportunities

• Build source-backed comparison/alternative content only where Prehealth approves competitor pages.
• Use VitalCX language: Healthcare Experience Platform, visibility, coordination, accountability, GraceAI, and healthcare-specific operational workflows.
• Route direct feature, compliance, pricing, customer, or performance comparisons through human review.

Source Snapshot

• URL: https://www.assorthealth.com/
• Date accessed: 2026-06-28
• Source ID: SRC-020
• Raw source: 01-sources/raw-urls/2026-06-28/competitors/assort-health/homepage.md
• Homepage screenshot: 01-sources/screenshots/2026-06-28/competitors/assort-health/homepage.png
• Role: Discovered direct healthcare AI voice competitor
• Segment: Healthcare AI voice agents / patient journey

Brand Positioning

Assort Health positions around healthcare ai voice agents / patient journey. The captured homepage makes this visible through the lead line, product navigation, and workflow terms recorded in the source capture.

Messaging And UX Signals

• Primary headline: Every Patient, Precisely Guided
• Product story: AI voice agent for referrals, scheduling, intake, triage, follow-up, and specialty workflows.
• Visual audit note: use the captured homepage screenshot for design review and deck reference.

Source-Backed Strengths

• Clear ownership of healthcare ai voice agents / patient journey language.
• Public homepage provides concrete workflow terms that can inform VitalCX comparison strategy.
• Competitor is useful for SEO/AEO category mapping and Website 2.0 positioning.

Weaknesses Or Gaps

These are strategic inferences from the captured homepage, not claims about product performance.

• VitalCX should clarify why HXP is larger than a voice agent.
• VitalCX should avoid attacking this competitor and instead clarify the category boundary.

VitalCX Website 2.0 Opportunities

• Build source-backed comparison/alternative content only where Prehealth approves competitor pages.
• Use VitalCX language: Healthcare Experience Platform, visibility, coordination, accountability, GraceAI, and healthcare-specific operational workflows.
• Route direct feature, compliance, pricing, customer, or performance comparisons through human review.

Purpose

The Competitive Analysis Agent researches direct and indirect competitors, turns their public sources into structured intelligence, and recommends positioning and SEO/AEO opportunities for VitalCX.

First Project Supported

VitalCX Website 2.0 SEO/AEO dominance.

Required Inputs

• Competitor URLs.
• VitalCX client overview.
• VitalCX brand guide.
• Website 2.0 SEO/AEO brief.
• Current competitor notes.
• Claims/compliance rules.
• Oracle brand rubric.

Outputs

• Competitor profiles.
• Cross-competitor summary.
• Positioning white-space map.
• SEO/AEO opportunities.
• Website 2.0 page recommendations.
• Prehealth CompIntel workbook.
• Visual Brand Audit deck with competitor homepage screenshots.
• Claims requiring review.

VitalCX V1 Workflow

1. Build the VitalCX primary-company baseline from the client brain.

Workbook Field Spine

• Company Identity.
• Brand Positioning.
• Value Proposition.
• Services And Products.
• Brand Architecture.
• Key Messages And Boilerplate.
• Target Audience.
• Competitive Context.

Source Snapshot

• URL: https://fabrichealth.com/
• Date accessed: 2026-06-28
• Source ID: SRC-028
• Raw source: 01-sources/raw-urls/2026-06-28/competitors/fabric-health/homepage.md
• Homepage screenshot: 01-sources/screenshots/2026-06-28/competitors/fabric-health/homepage.png
• Role: Discovered care access competitor
• Segment: Care access platform / virtual care / enablement

Brand Positioning

Fabric Health positions around care access platform / virtual care / enablement. The captured homepage makes this visible through the lead line, product navigation, and workflow terms recorded in the source capture.

Messaging And UX Signals

• Primary headline: Intelligently connected care
• Product story: Care access platform for answers, streamlined experiences, operational/clinical efficiency, provider directory, and virtual care services.
• Visual audit note: use the captured homepage screenshot for design review and deck reference.

Source-Backed Strengths

• Clear ownership of care access platform / virtual care / enablement language.
• Public homepage provides concrete workflow terms that can inform VitalCX comparison strategy.
• Competitor is useful for SEO/AEO category mapping and Website 2.0 positioning.

Weaknesses Or Gaps

These are strategic inferences from the captured homepage, not claims about product performance.

• VitalCX should define HXP more concretely through six coordinated service areas.
• VitalCX should avoid attacking this competitor and instead clarify the category boundary.

VitalCX Website 2.0 Opportunities

• Build source-backed comparison/alternative content only where Prehealth approves competitor pages.
• Use VitalCX language: Healthcare Experience Platform, visibility, coordination, accountability, GraceAI, and healthcare-specific operational workflows.
• Route direct feature, compliance, pricing, customer, or performance comparisons through human review.

Source Snapshot

• URL: https://www.hyro.ai/
• Date accessed: 2026-06-28
• Source ID: SRC-019
• Raw source: 01-sources/raw-urls/2026-06-28/competitors/hyro/homepage.md
• Homepage screenshot: 01-sources/screenshots/2026-06-28/competitors/hyro/homepage.png
• Role: Discovered direct healthcare AI competitor
• Segment: Healthcare AI agents / patient access / call center automation

Brand Positioning

Hyro positions around healthcare ai agents / patient access / call center automation. The captured homepage makes this visible through the lead line, product navigation, and workflow terms recorded in the source capture.

Messaging And UX Signals

• Primary headline: Unburden your staff, unblock access to care
• Product story: AI agents for call center automation, scheduling, physician search, FAQ resolution, Rx management, and responsible AI.
• Visual audit note: use the captured homepage screenshot for design review and deck reference.

Source-Backed Strengths

• Clear ownership of healthcare ai agents / patient access / call center automation language.
• Public homepage provides concrete workflow terms that can inform VitalCX comparison strategy.
• Competitor is useful for SEO/AEO category mapping and Website 2.0 positioning.

Weaknesses Or Gaps

These are strategic inferences from the captured homepage, not claims about product performance.

• VitalCX should claim broader HXP orchestration across patient/care-team handoffs.
• VitalCX should avoid attacking this competitor and instead clarify the category boundary.

VitalCX Website 2.0 Opportunities

• Build source-backed comparison/alternative content only where Prehealth approves competitor pages.
• Use VitalCX language: Healthcare Experience Platform, visibility, coordination, accountability, GraceAI, and healthcare-specific operational workflows.
• Route direct feature, compliance, pricing, customer, or performance comparisons through human review.

Source Snapshot

• URL: https://www.janus-ai.com/
• Date accessed: 2026-06-28
• Source ID: SRC-026
• Raw source: 01-sources/raw-urls/2026-06-28/competitors/janus-health/homepage.md
• Homepage screenshot: 01-sources/screenshots/2026-06-28/competitors/janus-health/homepage.png
• Role: Discovered RCM specialist competitor
• Segment: Revenue cycle intelligence and automation

Brand Positioning

Janus Health positions around revenue cycle intelligence and automation. The captured homepage makes this visible through the lead line, product navigation, and workflow terms recorded in the source capture.

Messaging And UX Signals

• Primary headline: Transform Revenue Cycle Performance with JanusIQ
• Product story: AI-powered revenue cycle intelligence and automation for revenue yield, staff capacity, claims, portals, and RCM operations.
• Visual audit note: use the captured homepage screenshot for design review and deck reference.

Source-Backed Strengths

• Clear ownership of revenue cycle intelligence and automation language.
• Public homepage provides concrete workflow terms that can inform VitalCX comparison strategy.
• Competitor is useful for SEO/AEO category mapping and Website 2.0 positioning.

Weaknesses Or Gaps

These are strategic inferences from the captured homepage, not claims about product performance.

• VitalCX should connect RCM to the broader patient experience rather than treating it as a silo.
• VitalCX should avoid attacking this competitor and instead clarify the category boundary.

VitalCX Website 2.0 Opportunities

• Build source-backed comparison/alternative content only where Prehealth approves competitor pages.
• Use VitalCX language: Healthcare Experience Platform, visibility, coordination, accountability, GraceAI, and healthcare-specific operational workflows.
• Route direct feature, compliance, pricing, customer, or performance comparisons through human review.

Source Snapshot

• URL: https://www.kapture.cx/
• Date accessed: 2026-06-28
• Source ID: SRC-017
• Raw source: 01-sources/raw-urls/2026-06-28/competitors/kapture-cx/homepage.md
• Homepage screenshot: 01-sources/screenshots/2026-06-28/competitors/kapture-cx/homepage.png
• Role: Supplied direct/adjacent competitor
• Segment: Generic agentic CX / service operations platform

Brand Positioning

Kapture CX positions around generic agentic cx / service operations platform. The captured homepage makes this visible through the lead line, product navigation, and workflow terms recorded in the source capture.

Messaging And UX Signals

• Primary headline: Stop managing work. Start completing it.
• Product story: AgentOS, agent builder, human command layer, audit/calibration, and operational intelligence.
• Visual audit note: use the captured homepage screenshot for design review and deck reference.

Source-Backed Strengths

• Clear ownership of generic agentic cx / service operations platform language.
• Public homepage provides concrete workflow terms that can inform VitalCX comparison strategy.
• Competitor is useful for SEO/AEO category mapping and Website 2.0 positioning.

Weaknesses Or Gaps

These are strategic inferences from the captured homepage, not claims about product performance.

• VitalCX should contrast healthcare-specific HXP against broad agentic CX.
• VitalCX should avoid attacking this competitor and instead clarify the category boundary.

VitalCX Website 2.0 Opportunities

• Build source-backed comparison/alternative content only where Prehealth approves competitor pages.
• Use VitalCX language: Healthcare Experience Platform, visibility, coordination, accountability, GraceAI, and healthcare-specific operational workflows.
• Route direct feature, compliance, pricing, customer, or performance comparisons through human review.

Source Snapshot

• URL: https://www.kore.ai/ai-for-service/ai-for-healthcare
• Date accessed: 2026-06-28
• Source ID: SRC-025
• Raw source: 01-sources/raw-urls/2026-06-28/competitors/kore-ai-healthcare/homepage.md
• Homepage screenshot: 01-sources/screenshots/2026-06-28/competitors/kore-ai-healthcare/homepage.png
• Role: Discovered adjacent enterprise AI competitor
• Segment: Enterprise AI for service / healthcare applications

Brand Positioning

Kore.ai Healthcare positions around enterprise ai for service / healthcare applications. The captured homepage makes this visible through the lead line, product navigation, and workflow terms recorded in the source capture.

Messaging And UX Signals

• Primary headline: Streamline care. Elevate experiences.
• Product story: Healthcare AI applications for providers, payers, life sciences, appointment management, notifications, care management, RCM, billing, and claims.
• Visual audit note: use the captured homepage screenshot for design review and deck reference.

Source-Backed Strengths

• Clear ownership of enterprise ai for service / healthcare applications language.
• Public homepage provides concrete workflow terms that can inform VitalCX comparison strategy.
• Competitor is useful for SEO/AEO category mapping and Website 2.0 positioning.

Weaknesses Or Gaps

These are strategic inferences from the captured homepage, not claims about product performance.

• VitalCX should emphasize healthcare-native category ownership, not a generic agent platform with a healthcare module.
• VitalCX should avoid attacking this competitor and instead clarify the category boundary.

VitalCX Website 2.0 Opportunities

• Build source-backed comparison/alternative content only where Prehealth approves competitor pages.
• Use VitalCX language: Healthcare Experience Platform, visibility, coordination, accountability, GraceAI, and healthcare-specific operational workflows.
• Route direct feature, compliance, pricing, customer, or performance comparisons through human review.

Source Snapshot

• URL: https://www.lumahealth.io/
• Date accessed: 2026-06-28
• Source ID: SRC-023
• Raw source: 01-sources/raw-urls/2026-06-28/competitors/luma-health/homepage.md
• Homepage screenshot: 01-sources/screenshots/2026-06-28/competitors/luma-health/homepage.png
• Role: Discovered patient journey and operational AI competitor
• Segment: Operational AI / patient success platform

Brand Positioning

Luma Health positions around operational ai / patient success platform. The captured homepage makes this visible through the lead line, product navigation, and workflow terms recorded in the source capture.

Messaging And UX Signals

• Primary headline: Operational AI for: fewer calls
• Product story: Operational AI across referrals, scheduling, waitlists, registration, prep, payments, intake, communication, reminders, and document flow.
• Visual audit note: use the captured homepage screenshot for design review and deck reference.

Source-Backed Strengths

• Clear ownership of operational ai / patient success platform language.
• Public homepage provides concrete workflow terms that can inform VitalCX comparison strategy.
• Competitor is useful for SEO/AEO category mapping and Website 2.0 positioning.

Weaknesses Or Gaps

These are strategic inferences from the captured homepage, not claims about product performance.

• VitalCX should define HXP as the next layer above patient success and access automation.
• VitalCX should avoid attacking this competitor and instead clarify the category boundary.

VitalCX Website 2.0 Opportunities

• Build source-backed comparison/alternative content only where Prehealth approves competitor pages.
• Use VitalCX language: Healthcare Experience Platform, visibility, coordination, accountability, GraceAI, and healthcare-specific operational workflows.
• Route direct feature, compliance, pricing, customer, or performance comparisons through human review.

Category Landscape

VitalCX is positioned as a Healthcare Experience Platform: the operational layer between patients and care teams across scheduling, triage, referrals, outreach, medical records, and revenue cycle management.

Differentiators VitalCX Should Defend

• Healthcare Experience Platform, not generic CX software.
• Full operational middle, not only AI agents or contact center automation.
• Scheduling, triage, referrals, outreach, medical records, and RCM as one coordinated experience.
• GraceAI as healthcare-specific intelligent technology.
• Visibility and accountability across patient-care team interactions.
• Operational excellence as patient care.

Source Snapshot

• URL: https://www.notablehealth.com/
• Date accessed: 2026-06-28
• Source ID: SRC-022
• Raw source: 01-sources/raw-urls/2026-06-28/competitors/notable/homepage.md
• Homepage screenshot: 01-sources/screenshots/2026-06-28/competitors/notable/homepage.png
• Role: Discovered direct healthcare automation competitor
• Segment: Healthcare AI platform / access, RCM, care operations

Brand Positioning

Notable positions around healthcare ai platform / access, rcm, care operations. The captured homepage makes this visible through the lead line, product navigation, and workflow terms recorded in the source capture.

Messaging And UX Signals

• Primary headline: The AI Platform purpose-built for healthcare
• Product story: AI agents for patient access, RCM, care operations, intake, registration, referrals, and repetitive work.
• Visual audit note: use the captured homepage screenshot for design review and deck reference.

Source-Backed Strengths

• Clear ownership of healthcare ai platform / access, rcm, care operations language.
• Public homepage provides concrete workflow terms that can inform VitalCX comparison strategy.
• Competitor is useful for SEO/AEO category mapping and Website 2.0 positioning.

Weaknesses Or Gaps

These are strategic inferences from the captured homepage, not claims about product performance.

• VitalCX should differentiate healthcare experience from administrative automation.
• VitalCX should avoid attacking this competitor and instead clarify the category boundary.

VitalCX Website 2.0 Opportunities

• Build source-backed comparison/alternative content only where Prehealth approves competitor pages.
• Use VitalCX language: Healthcare Experience Platform, visibility, coordination, accountability, GraceAI, and healthcare-specific operational workflows.
• Route direct feature, compliance, pricing, customer, or performance comparisons through human review.

Source-Backed Category Move

VitalCX should own the operational middle of healthcare: the high-volume interactions and handoffs that determine whether patients experience care as coordinated or fragmented.

Competitive Read

The market is converging around AI agents, patient access automation, contact-center automation, and operational AI. Competitors are credible in their lanes, but none of the captured competitors uses VitalCX's exact HXP framing across scheduling, triage, referrals, outreach, medical records, and RCM.

1. Everything Between Patients And Care

Use this as the emotional and operational category anchor.

2. Operational Excellence Is Patient Care

Turn scheduling, triage, referrals, outreach, records, and RCM into patient-experience moments.

3. Healthcare-Specific AI, Not Generic Agent Hype

GraceAI should be explained through safe workflow support, patient/care-team clarity, and accountability.

4. The Connected Workflow Advantage

Competitors often lead with one dominant lane: AI agents, patient access, communication, contact center, RCM, or hospital ops. VitalCX should show the connected layer.

Source Snapshot

• URL: https://www.qventus.com/
• Date accessed: 2026-06-28
• Source ID: SRC-027
• Raw source: 01-sources/raw-urls/2026-06-28/competitors/qventus/homepage.md
• Homepage screenshot: 01-sources/screenshots/2026-06-28/competitors/qventus/homepage.png
• Role: Discovered healthcare operations competitor
• Segment: Hospital operations AI automation

Brand Positioning

Qventus positions around hospital operations ai automation. The captured homepage makes this visible through the lead line, product navigation, and workflow terms recorded in the source capture.

Messaging And UX Signals

• Primary headline: Automate hospital operations with AI teammates
• Product story: AI teammates for hospital operations, margins, capacity, surgical growth, discharge, and productivity.
• Visual audit note: use the captured homepage screenshot for design review and deck reference.

Source-Backed Strengths

• Clear ownership of hospital operations ai automation language.
• Public homepage provides concrete workflow terms that can inform VitalCX comparison strategy.
• Competitor is useful for SEO/AEO category mapping and Website 2.0 positioning.

Weaknesses Or Gaps

These are strategic inferences from the captured homepage, not claims about product performance.

• VitalCX should separate HXP from hospital operations automation by centering patient/care-team handoffs.
• VitalCX should avoid attacking this competitor and instead clarify the category boundary.

VitalCX Website 2.0 Opportunities

• Build source-backed comparison/alternative content only where Prehealth approves competitor pages.
• Use VitalCX language: Healthcare Experience Platform, visibility, coordination, accountability, GraceAI, and healthcare-specific operational workflows.
• Route direct feature, compliance, pricing, customer, or performance comparisons through human review.

Source Snapshot

• URL: https://sierra.ai/
• Date accessed: 2026-06-28
• Source ID: SRC-018
• Raw source: 01-sources/raw-urls/2026-06-28/competitors/sierra-ai/homepage.md
• Homepage screenshot: 01-sources/screenshots/2026-06-28/competitors/sierra-ai/homepage.png
• Role: Supplied direct/adjacent competitor
• Segment: Generic AI agent customer experience platform

Brand Positioning

Sierra AI positions around generic ai agent customer experience platform. The captured homepage makes this visible through the lead line, product navigation, and workflow terms recorded in the source capture.

Messaging And UX Signals

• Primary headline: Better customer experiences. Built on Sierra.
• Product story: AI agents for customer experience across channels, personalization, customer data, trust, and reliability.
• Visual audit note: use the captured homepage screenshot for design review and deck reference.

Source-Backed Strengths

• Clear ownership of generic ai agent customer experience platform language.
• Public homepage provides concrete workflow terms that can inform VitalCX comparison strategy.
• Competitor is useful for SEO/AEO category mapping and Website 2.0 positioning.

Weaknesses Or Gaps

These are strategic inferences from the captured homepage, not claims about product performance.

• VitalCX should define healthcare-specific workflows instead of competing on generic AI-agent polish.
• VitalCX should avoid attacking this competitor and instead clarify the category boundary.

VitalCX Website 2.0 Opportunities

• Build source-backed comparison/alternative content only where Prehealth approves competitor pages.
• Use VitalCX language: Healthcare Experience Platform, visibility, coordination, accountability, GraceAI, and healthcare-specific operational workflows.
• Route direct feature, compliance, pricing, customer, or performance comparisons through human review.

Source Snapshot

• URL: https://www.talkdesk.com/call-center-solutions/healthcare/
• Date accessed: 2026-06-28
• Source ID: SRC-024
• Raw source: 01-sources/raw-urls/2026-06-28/competitors/talkdesk-healthcare/homepage.md
• Homepage screenshot: 01-sources/screenshots/2026-06-28/competitors/talkdesk-healthcare/homepage.png
• Role: Discovered adjacent platform competitor
• Segment: Healthcare contact center / CX automation

Brand Positioning

Talkdesk Healthcare positions around healthcare contact center / cx automation. The captured homepage makes this visible through the lead line, product navigation, and workflow terms recorded in the source capture.

Messaging And UX Signals

• Primary headline: A purpose-built healthcare contact center solution for providers and payers.
• Product story: Healthcare contact center, Healthcare Experience Cloud, CX automation, AI agents, appointment scheduling, patient identification, and omnichannel outreach.
• Visual audit note: use the captured homepage screenshot for design review and deck reference.

Source-Backed Strengths

• Clear ownership of healthcare contact center / cx automation language.
• Public homepage provides concrete workflow terms that can inform VitalCX comparison strategy.
• Competitor is useful for SEO/AEO category mapping and Website 2.0 positioning.

Weaknesses Or Gaps

These are strategic inferences from the captured homepage, not claims about product performance.

• VitalCX should position as the healthcare experience operating layer beyond the contact center.
• VitalCX should avoid attacking this competitor and instead clarify the category boundary.

VitalCX Website 2.0 Opportunities

• Build source-backed comparison/alternative content only where Prehealth approves competitor pages.
• Use VitalCX language: Healthcare Experience Platform, visibility, coordination, accountability, GraceAI, and healthcare-specific operational workflows.
• Route direct feature, compliance, pricing, customer, or performance comparisons through human review.

Snapshot

The VitalCX market is not a simple two-competitor field. Kapture CX and Sierra AI are useful broad AI/CX benchmarks, but the higher-priority SEO/AEO and positioning risk comes from healthcare-native AI agent, patient access, patient communication, operational AI, RCM, and hospital-operations platforms.

Category Battle

• Broad CX/AI platforms say: better customer experiences through AI agents.
• Healthcare AI-agent platforms say: automate patient access, scheduling, support, and repetitive work.
• Patient access platforms say: unify and automate patient journeys.
• RCM and hospital-operations platforms say: improve operational performance, capacity, and revenue.
• VitalCX should say: healthcare experience is created through coordinated operational moments between patients and care teams.

Positioning White Space

VitalCX should own: Everything between patients and care. That territory is broader than a voice agent, more healthcare-native than generic AI/CX, and more patient-experience led than RCM or hospital operations automation.

Recommended Website 2.0 Moves

1. Put the HXP definition above the fold.

Risks And Unknowns

• Pricing, packaging, and integration specifics for VitalCX remain unknown.
• Any HIPAA/compliance claims need approval.
• Competitor claims are based on public homepage captures and should be refreshed before publication.
• Hyro, Assort, Notable, Luma, Artera, and Talkdesk are likely more important than Kapture/Sierra for healthcare-specific SEO/AEO.

Kapture CX

Source: https://www.kapture.cx

Apparent Positioning

AI-powered customer experience/customer support platform across multiple industries.

VitalCX Contrast

VitalCX should be framed as healthcare-specific, built around patient-care team workflows rather than generic customer support operations.

Website 2.0 Content Implication

Create pages and answer blocks around:

• Healthcare Experience Platform vs customer experience platform.
• Patient access automation vs customer support automation.
• Healthcare workflow orchestration vs generic ticket/service automation.

Sierra AI

Source: https://sierra.ai

Apparent Positioning

AI-agent platform for customer experience across channels and industries.

Overview

Score every VitalCX creative asset before it moves into client review, publishing, or the

Dimensions and Weights

Score each dimension 0: weight. Total ≥ 80 passes. Any automatic-fail condition caps the

Automatic Fail Conditions

• Invented healthcare, compliance, performance, clinical, pricing, or customer-result claims (10-oracle-instructions/claims-compliance.md).
• Metrics copied from mockups/Figma into final output without proof-point approval (03-brand/master-brand-guide.md 2026 addendum).
• Emoji in final output (03-brand/brand-non-negotiables.md).
• Wrong palette, typography, or logo treatment (03-brand/design-tokens.json).
• Reviewer cannot identify which brain file or source informed the asset (03-brand/brand-non-negotiables.md).

Machine Block

palette:

• "warm/golden photography treatments"
• "complex gradients as a primary UI device"
• "decorative patterns or textures outside the approved V-frame system"
• "unsupported HIPAA, outcome, savings, speed, retention, or satisfaction claims"
• "off-palette colors"
• "substitute typefaces"

Known Open Conflicts (do not resolve silently)

Deck headings currently use New Spirit (deck harvest,

Overview

This process teaches the VitalCX brain from real creative work without letting raw drafts, competitor references, or inspiration sources become approved brand canon by accident.

What Counts As Creative

• Website pages, sections, wireframes, prototypes, screenshots, HTML, or Figma exports.
• Social posts, ads, carousels, banners, thumbnails, and campaign concepts.
• Sales decks, PDFs, one-pagers, pitch decks, and enablement materials.
• Videos, motion tests, storyboards, scripts, and image/video generations.
• Competitor screenshots, category examples, swipe references, and strategy articles.
• Internal Prehealth drafts, prompts, outputs, revisions, and client feedback.

Required Intake Steps

1. Create an asset folder using the date and a short slug.

Metadata Tags

Use consistent tags so Oracle can retrieve patterns later.

Promotion Rules

Raw inspiration never becomes brand truth automatically. It can be promoted only as one of these:

Inspiration Safety Rule

The agent may extract principles from external or competitor creative, but must not copy the execution. Every inspiration note must answer:

• What is the underlying strategic or design principle?
• Why does it matter for VitalCX?
• What should VitalCX do differently to make it ownable?
• What risk would appear if we copied it too closely?

Overview

The inspiration loop turns reviewed creative into better briefs, prompts, and brand-system decisions.

Loop

flowchart LR

What The Agent Learns

The agent should learn principles, not copy surface-level references.

Inspiration Board Entry Standard

Each approved inspiration entry must include:

• Asset ID.
• Preview path or URL.
• Source type.
• Tags.
• What works.
• Why it matters for VitalCX.
• How to adapt it.
• What not to copy.

Drift Detection

Every 10 reviewed creative records, check whether the same off-brand correction keeps appearing.

Creative Memory Boundary

The inspiration loop is not a dumping ground. Oracle should retrieve only approved inspiration entries for future creative generation unless the operator explicitly asks to inspect raw drafts or rejected references.

Overview

This loop lets Oracle create, score, revise, and version VitalCX creative internally until the work reaches the required quality threshold. The team should see the best version, not every rough pass.

Default Loop Behavior

1. Load the required brand, source, project, and claims context.

Threshold Presets

If no work type is specified, use client review asset as the default threshold for client-facing work and internal concept for exploratory internal work.

When To Stop And Ask The User

Do not interrupt the user during normal revisions. Ask for help only if:

• The asset cannot pass because source material is missing.
• The asset contains a claim that requires human/legal/client approval.
• The brief conflicts with approved VitalCX brand rules.
• Two consecutive revision rounds do not improve the score.
• The maximum self-revision count is reached without passing.
• The requested output would require inventing facts, proof, screenshots, customer names, or performance data.

Rubric Loop Ledger

Target threshold: 4.25

Share Packet

When the loop passes, share:

• Final asset or recommended version.
• Weighted score and target threshold.
• One-paragraph rationale for why it passed.
• Top 3 improvements made across versions.
• Remaining watchouts, if any.
• Link to the review file.

Do

• Use Vital Blue confidently.
• Pair Fields headlines with Albert Sans body.
• Use the "V" frame as the primary graphic device.
• Keep layouts spacious and calm.
• Make healthcare operations feel human.
• Use custom two-tone icons when available.
• Use source-backed copy and approved claims.

Don't

• Do not use emoji.
• Do not use unapproved prototype metrics.
• Do not use generic AI visual language.
• Do not use all-caps display headlines.
• Do not use heavy shadows or busy decoration.
• Do not use warm golden photo treatments.
• Do not use Lucide/custom fallback icons without flagging the substitution.

Logos

Available logo families:

• VitalCX full horizontal logo.
• VCX shorthand logo.
• VXN logo.
• Vital Experience Network horizontal and stacked marks.

Fonts

• Fields: ExtraLight through Black.
• Fields Display: Regular through Black.
• Albert Sans: ExtraLight through ExtraBold, with italic variants in uploads.

Preview Cards

The design system includes preview HTML for:

• Brand graphic treatment.
• Brand icons.
• VitalCX logos.
• Sub-brand logos.
• Primary, secondary, grayscale, and semantic colors.
• Buttons, chips, inputs.
• Spacing, radii, shadows.
• Type display, body, scale, and pairings.

UI Kit

Website prototype includes:

• Fixed navigation.
• Hero section.
• Solutions grid.
• GraceAI spotlight.
• Platform services tabs.
• Testimonial block.
• Metrics and values.
• CTA/demo form.

Visual Personality

Clean, spacious, precise, healthcare-credible, warm, and human. The system should feel premium and operationally calm without becoming sterile.

Primary Blues

• Vital Blue #0063FF: core brand blue.
• Deep Indigo #0051CF: hover states, dark surfaces, depth.
• Ocean Navy #003181: maximum depth.
• Soft Sky #A3C7FF: light accents and tints.
• Air Blue #D8E7FF: soft surfaces/background tints.
• Clear Blue #EBF2FF: lightest blue tint.

Secondary Palette

Secondary colors are contextual support colors, never dominant.

• Mint #B1FFEF
• Lilac #D4C5DD
• Aqua #88E4FE
• Sand #EDE1C5
• Soft Mint #EEFDFA
• Soft Lilac #F4EAFA
• Soft Aqua #D2F5FF
• Light Sand #F9F5EA

Neutrals

• Black #1C1A19
• Charcoal #575A66
• Drift #9DA2B3
• Mist #BCC0CC
• Lavender Gray #D2D5E0
• Border #E5E7F2
• Paper #F8F8FB
• White #FFFFFF

Typography Direction

• Headlines/key messages: Fields or Fields Display.
• Body/UI/forms/captions: Albert Sans.
• Headlines use sentence case and generous scale.
• Eyebrows use uppercase, small size, and tracking.
• Button labels use Title Case.

Layout And Composition Rules

• Clean, spacious layouts.
• Left-aligned hierarchy by default.
• Strong blue accents.
• Generous white space and 80px page gutters on desktop.
• Use Paper surfaces for secondary sections.
• Cards and image containers use 22px radius.
• Large display cards may use 32px radius.
• Inputs use 12px radius.

Priority

Website 2.0 should define the Healthcare Experience Platform category before broader AI-agent and healthcare automation competitors capture the answer space.

Answer Blocks To Build

• What is a Healthcare Experience Platform?
• How is HXP different from a healthcare contact center?
• How is HXP different from healthcare AI agents?
• What workflows should a Healthcare Experience Platform support?
• How does patient access automation improve healthcare experience?
• Where does revenue cycle management fit into patient experience?

Goal

Make Website 2.0 the authority layer for VitalCX's Healthcare Experience Platform category.

Phase 1: Category Foundation

Create pages that teach search engines, answer engines, buyers, and internal teams what VitalCX is.

• Homepage.
• Healthcare Experience Platform explainer.
• GraceAI page.
• Healthcare workflow automation overview.
• Patient access automation page.

Phase 2: Workflow Authority

Create workflow pages for the six core service areas:

• Scheduling.
• Triage.
• Referrals.
• Outreach.
• Medical records.
• Revenue cycle management.
• Direct answer block.
• Problem framing.

Phase 3: Audience Authority

Create audience pages:

• Hospitals.
• Health systems.
• Clinics/providers.
• RCM companies.
• Urgent care.

Phase 4: Competitive Authority

Create factual, respectful comparison pages:

• VitalCX vs Kapture CX.
• VitalCX vs Sierra AI.
• Healthcare Experience Platform vs customer experience platform.
• Healthcare AI agents vs generic AI agents.

Phase 5: AEO/FAQ Hub

Build a structured answer hub for questions like:

• What is a Healthcare Experience Platform?
• How does AI improve patient access?
• What is closed-loop referral management?
• How can healthcare organizations automate medical records workflows?
• What is healthcare revenue cycle automation?
• How is healthcare AI different from generic customer service AI?

Overview

Machine-facing scoring rubric for every Oracle-generated VitalCX output. Structure

1. Brand fidelity (25)

• [ ] Vital Blue #0063FF primary; Deep Indigo #0051CF hover; Ocean Navy #003181 depth, byte-exact hex, 03-brand/design-tokens.json
• [ ] Tints/neutrals from the token set only (Soft Sky #A3C7FF, Air Blue #D8E7FF, Clear Blue #EBF2FF, Black #1C1A19, Charcoal #575A66, Drift #9DA2B3, Paper #F8F8FB, White #FFFFFF), 03-brand/design-tokens.json
• [ ] Secondary set (Mint/Lilac/Aqua/Sand + soft variants) supportive, never dominant, 01-sources/raw-uploads/vitalcx-design-system/README.md
• [ ] Fields / Fields Display for display; Albert Sans for body/UI, 03-brand/design-tokens.json (typography.family); 03-brand/brand-non-negotiables.md
• [ ] Logos unmodified from assets/logos/ SVG set, 01-sources/raw-uploads/vitalcx-design-system/assets/logos/
• [ ] V-frame is the only graphic device; no gradients-as-device, no warm/golden photo treatment, 03-brand/master-brand-guide.md (Do-Not-Use)

2. Voice & tone (20)

• [ ] Traits present: confident, warm, authoritative, precise, humane, clinically credible, 03-brand/master-brand-guide.md (Personality Traits)
• [ ] Contains no emoji, 03-brand/voice-messaging.md (Avoid)
• [ ] Contains no corporate jargon / bloated enterprise-speak, 03-brand/voice-messaging.md (Avoid)
• [ ] Contains no generic AI hype, 03-brand/voice-messaging.md (Avoid)
• [ ] Contains no casual slang, 03-brand/voice-messaging.md (Avoid)
• [ ] Contains no unsupported superlatives, 03-brand/voice-messaging.md (Avoid)
• [ ] Sentence-case headlines; uppercase tracked eyebrows; Title Case buttons, 03-brand/voice-messaging.md (Casing)
• [ ] Tagline exact when used: "Customer experience is vital. And nothing is more vital than healthcare.", 03-brand/master-brand-guide.md

3. Layout & craft (15)

• [ ] Spacing from five-tier token scale (4, 200px), 03-brand/design-tokens.json (spacing)
• [ ] Radii from 8/12/22/32/pill only, 03-brand/design-tokens.json (radius)
• [ ] 1440px max width, 80px gutter (24px small) for page work, 03-brand/design-tokens.json (layout)
• [ ] Component rules: pill buttons, arrow-circle primary CTA, 12px inputs, 22px flat cards, 01-sources/raw-uploads/vitalcx-design-system/README.md
• [ ] Template slot compliance where a template applies, 03-brand/templates/{vertical}/

4. Message clarity (20)

• [ ] Advances "Only Global Healthcare Experience Platform" positioning, 03-brand/master-brand-guide.md (Category Claim)
• [ ] Audience: hospitals, health systems, clinics/providers, RCM, 03-brand/master-brand-guide.md (Positioning Statement)
• [ ] Names the operational work: scheduling, triage, referrals, outreach, medical records, RCM, 03-brand/master-brand-guide.md
• [ ] Connects operations to patient/care-team experience, 03-brand/master-brand-guide.md (Messaging Pillars)
• [ ] CTA present when required, approved Title Case label, 03-brand/voice-messaging.md (Casing)

5. Claim safety (10)

• [ ] No HIPAA/outcome/savings/speed/retention/satisfaction claims unless approved, 10-oracle-instructions/claims-compliance.md
• [ ] Quantitative/testimonial claims only from 05-offers-sales/proof-points.md, cited, 10-oracle-instructions/claims-compliance.md
• [ ] No prohibited claims (clinical/cost guarantees; GraceAI never diagnoses/prescribes/decides care), 10-oracle-instructions/claims-compliance.md
• [ ] Unsupported claims marked blocked, visibly, never smoothed into final copy, 10-oracle-instructions/claims-compliance.md (Workflow)

Overview

Use these instructions whenever a Prehealth teammate asks Oracle to review, score, ingest, or learn from VitalCX creative.

Required Context Load

Before reviewing creative, read:

Review Behavior

• Inspect the uploaded creative directly when possible. For images, review the actual image. For decks, videos, or websites, create or inspect representative screenshots.
• Treat the current brand guide as canon unless an approved change exists.
• Score every asset using 08-creative-system/creative-review-rubric.md.
• Separate objective brand violations from subjective creative preferences.
• Do not rewrite creative until the review identifies the source-backed issue.
• Do not promote raw inspiration into canon.
• Never copy competitor or external inspiration. Translate it into a VitalCX principle.

Autonomous Rubric Loop

When asked to create or improve work, do not show the first draft by default. Run the rubric loop first:

Output Requirements

Every creative review must include:

• Decision: approve, minor revisions, major revisions, or reject/redo.
• Weighted score.
• Target threshold and final version number if the rubric loop was used.
• Scorecard with evidence and required fixes.
• Version ledger showing the scores and revision focus for each internal pass.
• Highest-risk issues first.
• Brand-system notes: what works, what drifts, what should be reused.
• Inspiration capture recommendation.

Learning Loop

After scoring, classify the asset:

Default Role

Act as a Prehealth strategist and creative operator working from the approved VitalCX Oracle Brain.

Approved Sources

• 00-admin/source-register.md
• 01-sources/extracted-notes.md
• 02-foundation/client-overview.md
• 03-brand/master-brand-guide.md
• 03-brand/voice-messaging.md
• 03-brand/brand-non-negotiables.md
• 04-audience/audience-icp.md
• 05-offers-sales/offers-sales-context.md

Context Priority Order

1. Approved brain files.

Do Rules

• Position VitalCX as a Healthcare Experience Platform.
• Treat Website 2.0 as a VitalCX client project, not an Oracle app.
• Tie platform value to visibility, coordination, accountability, clarity, and patient experience.
• Use confident, warm, authoritative, precise language.
• Make healthcare operations feel human and consequential.
• Use Fields/Fields Display for headlines and Albert Sans for body/UI in visual artifacts.
• Use Vital Blue #0063FF as the core brand color.
• Use the "V" frame as the primary graphic device when a graphic system is needed.

Don't Rules

• Do not invent VitalCX facts.
• Do not borrow context from another Prehealth client.
• Do not use emoji in final outputs.
• Do not use metrics or testimonials outside 05-offers-sales/proof-points.md as fact without review.
• Do not claim GraceAI diagnoses, prescribes, or makes clinical decisions.
• Do not use generic AI hype or bloated enterprise-speak.
• Do not create public-facing work from unapproved claims unless clearly marked draft.

Ask A Human When

• The output needs an approved website URL, sales claim, metric, testimonial, pricing, integration detail, or compliance/legal statement.
• The request depends on competitor research.
• The request asks for a final client-facing artifact using source-present but unapproved metrics.

Safe Claims

Safe when used without additional quantitative proof:

• VitalCX is positioned as a Healthcare Experience Platform.
• VitalCX focuses on patient-care team interactions.
• The platform covers scheduling, triage, referrals, outreach, medical records, and revenue cycle management.
• GraceAI is positioned as intelligent technology purpose-built for healthcare.
• The brand emphasizes visibility, coordination, accountability, clarity, and patient experience.

V1-Approved Quantitative And Testimonial Claims

The claims in 05-offers-sales/proof-points.md are approved for V1 use when cited to the uploaded design system.

Claims Requiring Citation Or Reapproval

• HIPAA compliance.
• Performance improvements outside 05-offers-sales/proof-points.md.
• Patient satisfaction gains outside 05-offers-sales/proof-points.md.
• Hold-time reductions outside 05-offers-sales/proof-points.md.
• No-show reductions outside 05-offers-sales/proof-points.md.
• Clean claim rate outside 05-offers-sales/proof-points.md.
• Client retention outside 05-offers-sales/proof-points.md.
• Number of organizations served outside 05-offers-sales/proof-points.md.

Prohibited Claims

Prohibited unless separately approved:

• Guarantees of clinical outcomes.
• Guarantees of cost reduction or revenue lift.
• Claims that AI replaces clinical judgment.
• Claims that imply GraceAI diagnoses, prescribes, or makes care decisions.
• Any quantified claim outside the V1-approved proof-points file without client validation.

Legal Or Compliance Workflow

1. Identify the claim.

Sensitive Topics

• HIPAA
• Clinical triage
• AI in patient interactions
• Medical records
• Billing, denial management, prior authorization
• Patient satisfaction and outcomes
• Health system testimonials

Client Brain

The client brain is the source of truth for one client. It contains context, sources, brand rules, offers, audiences, competitors, proof points, claims rules, and agent instructions.

Client Projects

Client projects are deliverables or workstreams for a specific client.

• Website 2.0 SEO/AEO dominance.
• Sales enablement.
• Social content calendar.
• Ads and landing pages.
• Video scripts.
• Strategy docs.

Reusable Oracle Apps

Reusable Oracle apps are cross-client tools Prehealth will build later around repeatable skills.

• PowerPoint/deck generation app.
• Social media content creation app.
• Website strategy/copy app.
• SEO/AEO strategy app.
• Sales enablement app.
• Video script app.
• Image generation and creative direction app.
• Strategy document app.

Rule

Do not call a client project an app.

• "VitalCX Website 2.0 project"
• "Future website strategy app"
• "Future social content app"
• "Future PowerPoint app"

Internal Oracle Hosting

The VitalCX brand style guide should become an internal Oracle module, not a standalone external artifact.

• Oracle / Clients / VitalCX / Brand System
• Future route: /clients/vitalcx/brand-system
• Google Business SSO.
• Client-level permissions.
• Version state.
• Source traceability.
• Brand rubric connection.
• Skill context injection.

Overview

This loop keeps the VitalCX brain learning from new blogs, articles, reports, competitor updates, healthcare AI trends, client meetings, and performance results.

Purpose

Oracle should not treat onboarding as a one-time event. Each client brain needs a living research loop that:

• Adds new external context.
• Connects research to the client's positioning, audience, offers, SEO/AEO, creative, and claims.
• Separates raw source material from approved client truth.
• Promotes useful insights into project briefs, content ideas, strategy documents, and performance learnings.

Loop Steps

1. Capture the source.

Promotion Rules

Research does not become approved client truth automatically.

Cadence

• Weekly: add new client, competitor, and category sources.
• Biweekly: connect research findings to active projects.
• Monthly: review stale claims, SEO/AEO opportunities, and competitor shifts.
• Quarterly: promote reusable category learnings into the central PreHealth Oracle Brain.

Agent Behavior

When Oracle ingests research, it must output:

• Source summary.
• Key claims and whether they are safe to use.
• Client relevance.
• Connected brain files.
• Recommended promotions.
• Ideas generated.
• Open questions.
• Expiration or recheck date when the source is time-sensitive.

Overview

Use this map to decide where new research, articles, blogs, meetings, and performance learnings should connect inside the VitalCX brain.

Connection Rule

Every new source should create at least one connection, but not every connection becomes canon. Use this path:

Connection Note Format

Insight:

Healthcare Experience Platform

A Healthcare Experience Platform coordinates the operational work between patients and care teams, including scheduling, triage, referrals, outreach, medical records, and revenue cycle management.

Healthcare AI Agents

AI agents used in healthcare workflows to automate or assist patient access, support, scheduling, outreach, intake, billing, or operational tasks.

Patient Access Automation

Automation that helps patients find, schedule, confirm, change, or complete access-related steps in care.

Operational AI

AI applied to workflow execution, staff productivity, capacity, communication, and operational follow-through.

Website 2.0 AEO Questions

• What is a Healthcare Experience Platform?
• How is a Healthcare Experience Platform different from a healthcare contact center?
• How is a Healthcare Experience Platform different from healthcare AI agents?
• What workflows should a Healthcare Experience Platform support?
• How does patient access automation improve healthcare experience?
• How does referral management affect patient experience?
• Where does revenue cycle management fit into patient experience?
• What is GraceAI?

Review Rule

Answers should be short, source-backed, and approval-safe. Avoid HIPAA, performance, clinical, or ROI claims unless approved.

Patient Experience Happens In The Handoffs

VitalCX should make the case that patient experience is created in operational moments: scheduling, triage, referrals, outreach, records, billing, and follow-through.

HXP Is Bigger Than An AI Agent

Competitors often lead with AI agents. VitalCX should use GraceAI as part of the story, but the larger category is the Healthcare Experience Platform.

Operational Excellence Is Patient Care

Website 2.0 should connect operational reliability to the experience patients and care teams actually feel.

Scheduling

Draft explainer needed.

Triage

Draft explainer needed.

Referrals

Draft explainer needed.

Outreach

Draft explainer needed.

Medical Records

Draft explainer needed.

Revenue Cycle Management

Draft explainer needed.

Layer Model

Website 2.0 is not an Oracle app. It is the first VitalCX client project.

• Client projects: client-specific deliverables inside one client brain. For VitalCX, Website 2.0 SEO/AEO dominance is the first project.
• Reusable Oracle apps: cross-client tools Prehealth will build later around repeatable skills, such as PowerPoint generation, social media content creation, strategy docs, video scripts, image generation, and sales…

Future Reusable Oracle Apps

These are not VitalCX projects. They are platform capabilities to build later across clients:

• PowerPoint/deck generation app.
• Social media content creation app.
• Website strategy/copy app.
• SEO/AEO strategy app.
• Sales enablement app.
• Video script app.
• Image generation and creative direction app.
• Strategy document app.

First VitalCX Project Workflow

Start with a Website 2.0 SEO/AEO project workflow that uses:

• 01-sources/upload-ingestion-process.md
• 02-foundation/website-2-0-seo-aeo-brief.md
• 03-brand/voice-messaging.md
• 06-content-social/content-social-system.md
• 07-market-competitors/market-competitors.md
• 07-market-competitors/competitive-analysis-agent-brief.md
• 08-creative-system/visual-motion-system.md
• 10-oracle-instructions/claims-compliance.md

Oracle Product Direction

The current VitalCX brand guide is a prototype for the internal Oracle Brand System module.

• Oracle / Clients / VitalCX / Brand System
• Future app route: /clients/vitalcx/brand-system

Attendees

• Prehealth:
• Client:
• Other:

Overview

This board stores approved creative patterns and lessons for VitalCX. It should help the team create better work without copying competitor or third-party execution.

Approved Inspiration

No approved entries yet. Add entries only after a creative review has been completed.

Review Later

No pending entries yet.

Rejected Lessons

No rejected lessons yet.

Overview

Use this file to log articles, podcasts, newsletters, analyst notes, and industry research that should influence VitalCX strategy.

Ingestion Prompt

When adding a strategy article, Oracle should extract:

• One-sentence thesis.
• Three useful insights.
• Relevant buyer/category language.
• Potential VitalCX application.
• Risks or claims that should not be repeated.
• Suggested destination folder.

Overview

Performance data should update the VitalCX brain after every meaningful campaign, content, website, PR, sales, or SEO/AEO result.

Loop

result captured -> learning intake -> interpretation -> brain connection -> next test -> performance follow-up

What Gets Captured

• Website analytics.
• SEO/AEO ranking and answer visibility.
• Paid media performance.
• Organic social performance.
• Email performance.
• Sales deck or one-pager performance.
• PR pickup and backlink quality.
• Creative test results.

Required Output

Every performance learning should produce:

• What happened.
• Why it likely happened.
• What it teaches us about the audience, offer, creative, copy, channel, or timing.
• What to repeat.
• What to stop.
• What to test next.
• Which brain files should be updated.

Promotion Rule

Performance learnings become stronger context than opinions, but they still need review. Promote only after the result is understood and the source is documented.

Monthly Review

Once per month, review all performance learnings and update:

• 06-content-social/content-pillars.md
• 09-campaigns-performance/
• 14-ideas-insights/idea-board.md
• Active project briefs in 15-projects-roadmaps/
• Central PreHealth patterns if the learning is reusable across clients