A new role in Customer Success

The CX Engineer

The person who directs agents across every customer segment, the way a manager once directed people.

Book a demo

The role

What a CX Engineer does

Humans direct, agents execute. People keep the relationships, the judgment and the revenue calls. Agents run the repeatable work across every account, every day.

  1. 01 Agents

    Directs agents, not tasks

    Decides which agents run on which accounts, what they watch for, and which actions wait for a human.

  2. 02 Outcomes

    Owns outcomes across the whole book

    Adoption, renewal readiness, expansion and risk, across every segment rather than one CSM's accounts.

  3. 03 Background

    Often promoted out of CS Ops or RevOps

    A sharp operator who already knows the data, the playbooks and the systems.

The org chart

How the org changes

The CX Engineer sits beside the Head of CS and directs agents for every segment. Each segment keeps the shape that suits it.

The CX-Engineer effect shown as an org chart. A CRO sits above a Head of CS. A CX Engineer promoted from Ops directs agents for every segment: Enterprise CSMs with agents assisting, Mid-Market carrying a bigger book, and a pooled, agent-run long tail at one to thousands. The takeaway on the slide reads that you do not add CSMs to cover more accounts; one CX Engineer dedicates agents to the tedious work, so each team carries far more and the long tail runs pooled
Tap to open the chart full size.
  • Enterprise

    Named CSMs · agents assist

    Keeps its named CSMs, who own the relationships and the hard calls. Agents handle the administrative work underneath them.

  • Mid-Market

    Same team · bigger book

    Keeps the same team, and each person carries a bigger book.

  • Long tail

    Pooled · agent-first · 1 : thousands

    Runs pooled and agent-first, at one to thousands, with guidance shaped to each customer instead of a one-size-fits-all cadence.

You don't add CSMs to cover more accounts.

One CX Engineer dedicates agents to the tedious work, so each team carries far more and the long tail runs pooled.

The agents

What a CX Engineer runs

Two motions on every account across the lifecycle, plus the signals from outside your own data.

Proactive Drive outcomes forward.
  • Onboard Time to value
  • Adopt Adoption & growth
  • Renew Renewal readiness
  • Expand Expansion pipeline
Reactive Protect outcomes when risk surfaces.
  • Onboard Stalled onboarding
  • Adopt Early risk
  • Renew Churn signals
  • Expand Buying signals
External Events beyond your own data, factored into every account's health.
  • Exec changes
  • Funding rounds
  • Layoffs
  • M&A

In production

Teams already working this way

Merge

10K+

agent runs per week across customer accounts

Ocrolus

8×

faster QBR prep with unified account context

Ocrolus

184 hrs

handed back to the Ocrolus team every week

Read the Ocrolus story →

Becoming a CX Engineer

The skills that carry over

The role is new, but most of what it asks for is already part of senior CS work.

  1. You know the book and the playbooks.

    Which accounts need what, and when, is the judgment agents are pointed with.

  2. You can describe a workflow in plain English.

    Describe a process and Sonora builds the agent for it. No engineers, no roadmap wait.

  3. You can judge what agents should do, and what needs a human.

    Agents run on their own for low-risk work; approval stays on the critical calls.

The first CX Engineer Hackathon October 7, 2026 · New York · with Ocrolus Build and deploy agents that run a book of business, live in Sonora. About the hackathon →

Humans direct, agents execute

Direct agents across your whole book.

We'll stand Sonora up on your data and show you the agents running live.