A conversation that starts with a seat price or a platform total — “what is the per-agent number,” “just give us the bundle,” “the quote already has quality in it” — usually fails at the first unowned concurrent hour, the first integration that still sits with your team, or the first month of residual coaching, not at the first rate card. A seat price is a line item. It is not a contact center TCO worksheet.
A contact center TCO worksheet is the set of costs that actually run customer handling: named seats and concurrent seats, the connectivity the interactions ride, workforce and quality tools that are not in the base SKU, integrations that must keep context, implementation that is not a go-live slide, and the internal work that remains after the platform invoice. Two centers can buy the same seat rate and still have different concurrent peaks, different voice-path bills, different WFM and QM add-ons, and different residual owners after cutover.
The usual shortcut collapses TCO into a rate. Someone asks for a per-seat number, receives a platform total, and treats that figure as the decision. Concurrent usage is still unread. Connectivity is still “use the current internet.” Quality and workforce tools are still optional boxes on a later order. Integrations are still a logo on a slide. Implementation is still a promised week. Internal coaches, routing owners, and report builders are still unnamed. You have a seat price. You do not have a TCO worksheet.
That is why the live CCaaS meaning page starts with customer handling rather than a rate card. This note does not replace that page. It is the cost-worksheet reminder that sits beside it. When the next job is which names belong on a list, use the CCaaS providers shortlist after the worksheet rows are written, not instead of them. Score written answers on the CCaaS platform comparison. If the open question is still employee calling versus customer handling, use the UCaaS and CCaaS assessment before anyone treats a seat total as the model. If the decision is really about where the platform lives, use the live CCaaS versus on-premises page rather than treating a cheaper seat as the architecture.
What a contact center TCO worksheet is not
- It is not a seat price. A named-agent rate is one column. It is not concurrent usage, connectivity, or residual internal work.
- It is not a platform total. A bundle that “includes quality” still needs a written WFM and QM scope, not a checkbox.
- It is not a connectivity assumption. Voice, recording, and screen-pop still ride a path someone pays for and someone owns when it degrades.
- It is not an implementation week. Professional services, number moves, training, and dual-run hours are cost, not a calendar promise.
- It is not the work that disappears after go-live. Routing changes, coaching, calibration, and report ownership remain unless they are written as operated.
What to write before the rate card
- Seats and concurrent: named agents, peak concurrent, seasonal overflow, and which licenses attach to a person versus a session. A headcount is not a usage model.
- Connectivity: the voice and data path customer handling rides, what happens when that path is impaired, and whose bill carries the minutes, the DIDs, and the recording hop.
- WFM and QM: what is in the base SKU, what is an add-on, who scores, who schedules, and who still coaches after the platform invoice.
- Integrations: identity, CRM, ticketing, recording, and analytics. Name the owner and the recurring cost of each hop, not a logo.
- Implementation: discovery, build, porting, dual-run, training, and acceptance. Write hours and who pays them.
- Residual internal work: routing changes, exception queues, quality calibration, report building, and the owner who can accept them.
Questions that belong in the first meeting
Ask the incumbent or a challenger to show, not describe:
- Which costs they treated as in the seat, which they treated as concurrent or usage, and which they left as a customer responsibility sitting beside the quote.
- What WFM and QM actually include, and an example month where a coach, a calibrator, or a recording store would and would not be extra.
- Which integrations they priced as operated, and which they priced as a connector you still build and keep.
- What implementation hours they included, what they excluded, and who owns residual routing and quality work after go-live.
If those answers are a seat price and a promised platform total, you do not have a contact center TCO worksheet. You have a rate card.
What this page is not
This is not a platform ranking, not a price scorecard, and not a claim that The Data Partner already operated anyone’s contact center after a catalog view. The Data Partner is the advisor on the decision frame, not the platform and not the carrier. It is not a reprint of the live meaning page, the live shortlist, the live platform comparison, the live assessment, or the live architecture brief. Skip incentive talk and skip any suggestion that a seat price defines TCO. Write the rows. Then use the live companions, or contact The Data Partner on that packet. Broader buying questions sit on the FAQs page.