Part 1 overview from The AI Contact Center Handbook by Sho Shimoda. Available on Amazon.
Why Part 1 exists
Before you can lead a transformation, you have to be able to describe — honestly, without slides, in language a CFO will accept — what you are actually leading a transformation away from, what you are leading it toward, and why the technology underneath it changed in a way that makes the transformation possible now instead of five years ago.
That is what Part 1 does. It is the map. Chapter 1 names the trap. Chapter 2 shows the architecture that replaces it. Chapter 3 explains the intelligence that finally makes the architecture worth switching to. Read together, the three chapters give a leader a defensible answer to the two questions every board eventually asks: "What are we changing?" and "Why now?"
The three chapters, in one paragraph each
A legacy contact center is not a legacy technology — it is a legacy operating model, held in place by three reinforcing structures: the on-premises phone infrastructure, the pre-cloud CRM, and the workforce that has adapted to both. Each is defensible on its own. The trap is the way they hold each other up. Chapter 1 names the trap, quantifies the taxes it collects (on agents, on customers, on the P&L), and walks through why every failed CRM modernization gets killed by the same three obstacles: data, integration, and humans, in that order.
Read the Chapter 1 walkthrough →Three acronyms describe three historical starting points — internal collaboration (UCaaS), customer-facing contact center (CCaaS), and developer communications APIs (CPaaS). The interesting story is not any of the three. It is the way all three are sprinting into each other's territory and collapsing into a single, cloud-native platform that runs the whole communications surface of the enterprise. Chapter 2 explains why that convergence is happening now, which vendors are on which side of the trend, and what a leader needs to understand about the coming "one vendor instead of three" pitch before it lands on the desk.
Read the Chapter 2 walkthrough →A chatbot answers. An agent acts. The word "agentic" has been on every vendor slide since 2024, but the technical distinction it points at is real and testable: a system that can accept a goal, reason about how to reach it, call tools to actually do things, and observe the result well enough to adjust its plan. Chapter 3 draws the line between real agentic systems and the pretenders (rules-based IVRs, workflow engines, retrieval chatbots), walks through the three ingredients (language model + tools + memory) that separate them, and lays out the seven design principles that separate production systems from failed pilots.
Read the Chapter 3 walkthrough →What Part 1 buys you
| If you are… | Part 1 gives you… |
|---|---|
| A CX or contact center leader making the case for change | A defensible narrative for the board — three chapters that answer "what are we changing" and "why now" in language a CFO accepts. |
| A CIO or CTO with a vendor selection ahead of you | The vocabulary to sit through the UCaaS/CCaaS/CPaaS pitch cycle and see through the marketing to the architectural convergence underneath. |
| A CX ops or workforce leader planning the next 24 months | A grounded picture of what shifts in the operating model and what stays, so you can staff and plan against reality instead of hype. |
| A consultant or investor tracking the space | A working framework for how to distinguish real agentic capability from the products that inherited the word by osmosis. |
What comes next
Part 2 — The Front Line — leaves the landscape and enters the operational shifts: intent design, tool orchestration, and the redesign of the human agent role for exception handling. Once the map from Part 1 is in your head, Part 2 is where the day-to-day contact center starts to look different.