Voice AI RACI: programme governance that survives quarter two
- VP / COO
- CX directors
- Procurement / IT-Sec
Most voice AI programmes have a launch RACI and no operating RACI. The launch RACI gets the platform live; the operating RACI keeps it useful. The two are different documents owned by different people, and the second one is what determines whether the programme exists in a year.
Why voice AI breaks the standard contact-centre RACI
A traditional contact-centre RACI assigns clear ownership of channels (CX), technology (IT), and compliance (Legal / Risk). Voice AI sits across all three in a way that previous self-service technologies did not. Prompts and flows are an operational asset (CX), the model and integration layer is engineering (IT), the data and decisioning are subject to GDPR and the EU AI Act (Legal / DPO), and the platform contract creates new third-party risk obligations (Procurement / IT-Sec).
Treating any one of these as the primary owner produces a programme that the others cannot work with. The defensible pattern is shared accountability with explicit decision rights, written down before launch and reviewed every quarter.
The fifteen recurring decisions to assign upfront
These are the decisions that recur, often unannounced, in every voice AI programme. Each one needs an A (accountable, single name), supporting Rs (responsible), and explicit Cs and Is. Leaving any of them unassigned means the decision will be taken by whoever escalates loudest.
| Decision | A (Accountable) | R (Responsible) | C (Consulted) | I (Informed) |
|---|---|---|---|---|
| Add or retire a use case (intent) | CX Director | Conversation Designer, Engineering Lead | DPO, Compliance, Procurement | Sponsor, Vendor |
| Change to prompt or flow in production | Conversation Owner (CX Ops) | Conversation Designer | QA Lead | Engineering, Sponsor |
| Change to integration with a system of record | Engineering Lead | Integration Engineer, System Owner | CX Ops, Security | Sponsor, Vendor |
| Model provider change (e.g. swap underlying LLM) | Engineering Lead | Architect, Vendor | DPO, Security, Compliance, Procurement | Sponsor, CX Director |
| Sub-processor addition or removal | DPO | Procurement, Vendor | Security, Legal | Sponsor, CX Director |
| Containment-rate target by intent | CX Director | Operations Manager | Finance, Sponsor | Vendor, Engineering |
| Escalation path or vulnerable-customer route change | Compliance Lead | CX Ops, Conversation Designer | DPO, Customer Vulnerability SME | Sponsor |
| Recording and retention policy | DPO | Compliance, IT | Legal, CX Ops | Sponsor, Vendor |
| DPIA refresh trigger | DPO | Compliance, Engineering | Procurement, CX Ops | Sponsor |
| EU AI Act classification change | DPO | Compliance, Legal | Engineering, CX Ops | Sponsor |
| PCI scope-affecting change | Security Lead | Engineering, Compliance | QSA, Vendor | Sponsor |
| Commercial model renegotiation | Procurement | Finance, CX Director | Legal, Sponsor | Vendor |
| Incident or near-miss response | Engineering Lead | Incident Manager, Vendor | DPO, Compliance, CX Ops | Sponsor, Executive |
| Kill-switch or rollback decision | CX Director | Engineering, Operations | Sponsor, Compliance | Vendor |
| Quarterly programme review | Sponsor | CX Director, Engineering Lead, DPO, Procurement | Finance, Legal | Executive |
The accountable owner of the operating model
Across every successful enterprise voice AI deployment, one role exists that is sometimes missing from the launch project: the Conversation Owner. This is the named individual in CX Operations who owns the prompt, flow, and intent taxonomy in production, has authority to change them on a defined cadence, and is measured on the operating outcomes (containment, CSAT, re-contact) rather than on engineering velocity.
If this role does not exist, every change becomes an engineering ticket and the deployment stagnates at the version that shipped at launch. The Conversation Owner sits in CX Ops, not in IT, and has tooling (a controlled editor with diff review, staging, and one-click rollback) that lets them make changes without writing code.
Cadences that hold the programme together
Three regular meetings, each with a named chair and a published agenda, are the minimum operating cadence. Drop any of them and the programme drifts.
- Weekly operations review (45 minutes) — CX Ops chair, Engineering and QA attend. Reviews production metrics, escalation cases, and the change queue.
- Monthly platform review (60 minutes) — Engineering Lead chair, Vendor attends. Reviews platform health, model performance, integration incidents, and the vendor roadmap.
- Quarterly programme review (90 minutes) — Sponsor chair, all RACI Accountables attend. Reviews outcomes against targets, RACI accuracy (do the decisions in the last quarter map to the document?), DPIA and compliance posture, and the next-quarter roadmap.
What the RACI does not include
The RACI is silent on commercial relationship management beyond renegotiation. It is silent on routine vendor communication. It is silent on PR and external communication about the programme. These belong to the sponsor and the communications function and are deliberately kept out of the operating RACI so that engineering and CX Ops can run the programme without being interrupted by external coordination.
Similarly, the RACI does not own brand voice or tone-of-voice decisions on the AI's outputs. Those belong to Marketing / Brand, who is consulted on conversation design but is not in the operating chain. Mixing brand decisions into the operating RACI is how voice AI programmes acquire six-week approval cycles for prompt changes.
Open your current voice AI project plan. Find the fifteen decisions in the table above. Mark how many have a single named Accountable today. The unmarked rows are next week's governance backlog.
- Voice AI sits across CX, IT, Legal, and Procurement — single-owner RACIs do not work.
- Fifteen recurring decisions need a named Accountable before launch, not after the first incident.
- The Conversation Owner role in CX Ops is the most frequently missing role and the most operationally damaging gap.
- Three cadences — weekly ops, monthly platform, quarterly programme — are the minimum that holds the programme together.
- Review the RACI every quarter; workarounds are evidence the document is wrong, not that the team is undisciplined.
Frequently asked questions
- Who should be the Sponsor — CX, IT, or the COO?
- Whoever owns the P&L the programme is justified against. In customer-service-led deployments that is usually the CX Director or VP. In efficiency-led deployments it is more often the COO. The wrong answer is to put sponsorship in IT — voice AI is an operating change, not a technology refresh.
- Does the vendor sit on the RACI?
- The vendor appears as Responsible on platform-change decisions and as Consulted on roadmap and incident decisions, but is not Accountable for anything. Accountability that leaves the enterprise creates a governance gap that auditors and regulators will identify.
- How often should the RACI itself be reviewed?
- Every quarter, as part of the programme review. The test is simple: did the decisions taken in the last quarter map cleanly to the document, or did people work around it? Workarounds are evidence the RACI is wrong, not evidence the team is undisciplined.
- What is the most common gap in voice AI RACIs?
- The Conversation Owner role. The launch RACI usually has Engineering owning everything, then the launch project ends and nobody is named for the operational ownership of prompts and flows. Six months later the deployment has not changed since launch and nobody can say why.
Terms used in this guide
- Voice AI— Voice AI is software that answers the phone, understands what the caller wants, and takes action — not just a smarter IVR.
Lewis Crook — 20 years in enterprise technology, from FTSE 100 voice deployments to over a million AI-handled minutes a month across Asia-Pacific. Buyer, builder, and now working with CX leaders on enterprise voice AI. Writes The Voice AI Brief. Connect on LinkedIn. More about Lewis.
Related guides
Plus the Voice AI Readiness Diagnostic in the welcome email.
Welcome email includes the Voice AI Readiness Diagnostic. No second list, no extra form.