Services (CX)
The Services (CX) domain tests how you position and use Cisco Customer Experience offerings: CX Cloud, Success Tracks, Business Critical Services, High-Value Services, Solution Support, and reactive TAC support across the lifecycle. Expect situational items asking which service fits a customer need, what an entitlement actually covers, and how telemetry-driven insights are produced.
Structure of the portfolio
- CX Cloud: the digital platform that aggregates install-base telemetry, cases, advisories, and success milestones into one view.
- Success Tracks: tiered lifecycle programs covering adopt, support, and optimize phases; higher tiers add named advisors, proactive engagements, and deeper analytics than what ships with an eligible purchase.
- Business Critical Services: high-touch, proactive engagement with named experts for high-risk or fast-changing environments.
- High-Value Services: design, implementation, and optimization engagements, frequently delivered by partners.
- Solution Support: single point of accountability across the products that make up a solution, including multi-vendor scenarios.
- TAC: reactive break/fix. Hardware warranty covers replacement, not software updates or design help.
Answering service questions
Match the ask to the motion: active outage to TAC or Solution Support; recurring risk to Business Critical Services; adoption gaps to Success Tracks advisory; design or migration help to High-Value Services. Entitlements follow contracts per device and per software, and CX Cloud insight quality depends on onboarding and telemetry consent - without it, inventory and advisories are incomplete.
Worked example
A customer running SD-WAN, ISE, and firewalls has had three P1 outages in six months and wants to know why. Reasoning: TAC resolves each incident but does not perform cross-product trend analysis. Solution Support provides one owner across the solution during incidents. The proactive answer is Business Critical Services: a named architect, risk reviews, and CX Cloud analytics over the install base, combining advisories with the incident history to find the systemic cause. So recommend BCS for the "why" and Solution Support as the reactive backstop - not another case.
Traps that cost marks
- Promising software updates under hardware warranty.
- Assuming Success Tracks entitlements are identical for every purchase.
- Using TAC as a design or architecture service.
- Overlooking onboarding and telemetry consent, then trusting a partial CX Cloud inventory.
- Confusing partner-delivered High-Value Services with Cisco-delivered Business Critical Services.