The Center of CX
Subscribe
Current research complete · validated 22 September 2026

8x8

8x8, Inc. · Campbell, California, USA · Public, Nasdaq: EGHT

  • UCaaS + CCaaS
  • SMB
  • Midmarket
  • Enterprise, selected use
Request an introduction to 8x8Report an error
Compared with vendors that do the same job

Midmarket / unified-stack CCaaS

Run standard-to-moderate complexity contact centers efficiently.

Typical buyer
SMB-midmarket / distributed enterprise.
Compared on
Compared with other platforms of this kind. Lacking depth that only the largest enterprises need does not count against it unless you need that depth.
In the research's words
Do not penalize for narrower extreme-enterprise depth when not applicable.
Class status
Draft class, still being normalized

The class is context for comparison, never a quality grade. Unified UCaaS+CCaaS platform optimized around operational consolidation, global voice, strong channel economics and increasingly capable native WEM/AI. Current enterprise depth is broader than the historical value-play framing, but key AI/WEM functions still mix native and partner control planes and the best fit remains buyers who value platform consolidation over maximum bespoke control-plane depth.

Who it is sold to

  • UCaaS + CCaaS
  • SMB
  • Midmarket
  • Enterprise, selected use
  • UCaaS + CCaaS: 8x8 Work is the UC product.
  • Sizes: Enterprise means distributed enterprise, and selected global enterprise.

Where it runs: Global

Sizes, in the research's words:

  • 8x8 Contact Center: SMB, midmarket, distributed enterprise and selected global enterprise

UCaaS + CCaaS, in the research's words:

  • 8x8 Work: Organizations standardizing UC+CC on one platform

A size is the buyer size the research says the platform is sold to. Where a tag holds only for some buyers, the note says which. It describes the offer and carries no grade.

Best when

  • Use 8x8 when the buyer materially values one supplier family for UC+CC, global voice and CX operations rather than assembling multiple control planes.

    Context: Unified communications + contact center consolidation

    Why: The simplification thesis creates business value only when overlap actually disappears.

  • Use 8x8 when the buyer needs credible omnichannel, WFM and outbound without the transformation gravity of a highly bespoke enterprise program.

    Context: Cost-conscious growth / midmarket modernization

    Why: Class fit favors right-sized operating capacity over maximum feature breadth.

  • Use 8x8 when channel carry, global voice, regional operations and packaged integrations are more valuable than custom platform engineering.

    Context: Partner-led global distributed service

    Why: Partner and global operating model align to deployment/Day-2 capacity.

  • Use 8x8 when buyer wants native WFM integrated with contact center and can avoid a separate workforce license/control plane.

    Context: Native WFM modernization

    Why: Native WFM economics and operational integration can reduce stack complexity.

Take care when

  • Use caution if the proposed solution mixes native 8x8 WFM, Calabrio or Verint without an explicit control-plane/support RACI.

    Context: Mixed WEM architecture

    Why: 'WEM' can hide materially different products, contracts and support surfaces.

  • Use caution if AI Studio, Smart Assist and ICA are presented as one homogeneous native AI layer.

    Context: Mixed AI control planes

    Why: Native EAP plus Creovai/Capacity and Cognigy dependencies create different maturity, support and economics.

  • Use caution until persistent data, recordings, media, service data, AI processing and subprocessors are mapped by workload and region.

    Context: Strict sovereignty / regulated geography

    Why: Global presence is not equivalent to exact workload locality.

  • Use caution when the buyer needs hard isolation, pooled shared agents and granular client-level attribution.

    Context: BPO multi-client / shared-agent model

    Why: Named BPO proof and admin RBAC do not prove the complete operating model.

Rule it out when

  • Eliminate an 8x8-led architecture for a workload when the buyer requires the CCaaS layer itself to own durable, exception-heavy enterprise process state that cannot be proven rational.

    Context: Enterprise state/orchestration mismatch

    Why: The simplification thesis breaks when CCaaS becomes a surrogate BPM/state platform.

  • Eliminate the proposed design if contractual client isolation, locality or processing restrictions cannot be satisfied by the exact 8x8/partner components.

    Context: Mandatory isolation/locality cannot be proven

    Why: Structural policy requirements cannot be averaged away by channel or feature breadth.

  • Eliminate an over-customized 8x8 estate if the buyer cannot own APIs, partner WEM/AI, release regression and cross-vendor incident management after go-live.

    Context: Operating-capacity mismatch

    Why: Low entry complexity does not make a bespoke estate low-complexity on Day 2.

Products researched

  • 8x8 Contact Center

    CCaaS. Primary CCaaS control plane

    Release state: GA

  • 8x8 Workforce Management

    WFM. Workforce planning / scheduling / adherence

    Release state: GA

  • 8x8 Quality Management / Speech & Text Analytics

    QM / Analytics. Quality, interaction analytics, coaching

    Release state: GA

  • 8x8 AI Studio

    Agentic AI / automation. AI-agent development and runtime

    Release state: EAP

  • 8x8 Smart Assist

    Agent Assist. Human agent assist

    Release state: Limited availability

  • 8x8 Intelligent Customer Assistant (ICA)

    Conversational AI / IVA. Voice/digital self-service

    Release state: GA/partner-scope

  • 8x8 Work

    UCaaS. Adjacent UCaaS / expert collaboration control plane

    Release state: GA

  • 8x8 Engage

    CX beyond contact center. Extend service work beyond formal contact center agents

    Release state: GA

Take it further

No correction has been made to this page. Found an error? Report it. How corrections work.

How to cite

The Center of CX, "8x8: contact center platform research", validated 22 September 2026, https://www.contactcentercx.com/vendors/8x8