- CRM alignment: Salesforce · Dynamics · ServiceNow
- Incumbent economics: Sunk contracts, upgrade credits
- Regulated constraints: Healthcare · PCI · residency
- Geographic coverage: Regions, PSTN, languages
- Outcome: two-vendor shortlist, scored bake-off
The five layers you are actually buying
Telephony and routing (the CCaaS), the automation and orchestration layer, the knowledge and retrieval layer, the agent desktop surface, and the analytics and QA layer. Vendors bundle these differently, which is why feature-by-feature comparison produces nonsense. Score by layer, and be explicit about which layers you intend to keep swappable.
Scoring criteria that separate vendors
Six criteria carry the decision: quality of the evaluation tooling, depth of write-back integration into your CRM and core systems, transparency of the audit trail on tool calls, latency under real concurrency, data residency and retention controls, and the commercial model's behaviour as volume grows. Conversation design tooling and prebuilt intent libraries — the demo's centrepiece — rarely change the outcome.
Integration reality check
Ask every vendor to complete one real write-back transaction against your sandbox during evaluation: create a case, update an order, post a claim note. This single test eliminates more shortlists than any RFP section. Read-only assistants are commodity; the ability to act is what you are paying for.
Total cost including inference
Model four lines beyond licence: per-conversation inference, integration build and maintenance, evaluation and QA tooling, and the run team. Inference cost per contained conversation should be modelled at three volume scenarios — automation economics that work at pilot volume can invert at peak.
Build, buy or layer
Buy packaged automation for commodity intents on commodity data. Layer a platform such as Kore.ai, Amazon Bedrock or Azure AI Foundry when the differentiating workflow runs on your own data and needs to outlive your current CCaaS contract. Build in-house only where the workflow is a competitive asset and you have a standing platform team to run it.
- Score by layer, not by feature list — vendors bundle the five layers differently
- Evaluation tooling, write-back depth and audit trail carry the decision
- Make every vendor complete one real write-back in your sandbox
- Model inference cost at three volume scenarios, not at pilot volume
Questions leaders ask us
- What should we score when evaluating call center automation software?
- Evaluation tooling quality, depth of write-back integration, audit-trail transparency on tool calls, latency under real concurrency, data residency and retention controls, and how the commercial model behaves as volume grows.
- Should call center automation come from our CCaaS vendor?
- Only if you are prepared to re-platform the automation when you re-platform the contact center. Most enterprises keep the automation and orchestration layer separate so it survives CCaaS change and can run across multiple platforms at once.
- What costs do buyers usually miss?
- Per-conversation inference at peak volume, integration maintenance, evaluation and QA tooling, and the standing run team. Licence is rarely the largest line by year two.