A CX outsourcing statement of work (SOW) is the document that turns a sales promise into daily operations. It defines which customer interactions the provider handles, how performance is measured, what happens when something changes and how either side exits. Get it right and your nearshore team runs like an extension of your own. Get it wrong and you will spend the first year arguing about what was “included.”
This guide is for operations directors, CX leaders and VPs of customer support who are about to sign, or renegotiate, a managed support or team extension engagement. It covers the structure, the clauses that matter most, the mistakes experienced buyers avoid and a checklist you can take into your next vendor meeting.
TL;DR
- The SOW defines the tactical work. The Master Services Agreement (MSA) governs the long-term relationship, liability and indemnity. You need both, and they must fit together.
- Define deliverables and activities separately, with acceptance criteria a third party could evaluate.
- Replace “best efforts” language with measurable SLAs, a stated measurement method and a termination trigger for chronic failure.
- In healthcare, legal and financial services, attach the data protection terms (a BAA for protected health information, a DPA where privacy law applies) and ban use of your data to train AI models.
- Add a formal change order process and an exit plan before you sign, not after the first dispute.
Table of Contents
- SOW, MSA and everything around them
- What a CX outsourcing SOW should contain
- Scope: say what the team does and what it never touches
- Service levels that can be enforced
- Compliance clauses for healthcare, legal and financial services
- Staffing, language and training requirements
- Change orders: protect the budget and the service
- Governance and escalation
- Transition in, transition out
- Common mistakes buyers make
- Why the market makes this worth the effort
- Our perspective on writing a CX SOW
- Turning the SOW into a working program
- Pre-signing checklist
- FAQ
- Sources
SOW, MSA and everything around them
Most US outsourcing deals use an umbrella structure. According to Practical Law’s overview of US outsourcing, the predominant structure is a master services agreement with statements of work beneath it. The division of labor is simple:
| Document | What it covers | Changes how often |
|---|---|---|
| MSA | Liability, indemnity, confidentiality, term, dispute resolution, data protection terms | Rarely |
| SOW | Scope, volumes, hours, staffing, KPIs, fees, acceptance, timelines | As the program evolves |
| Addenda (BAA, DPA, security schedule) | Regulatory and security obligations | When regulations or systems change |
The state procurement guidance on drafting an SOW makes the same point from the buyer’s side: the SOW should reference the master agreement it sits under, and the two documents should not contradict each other. When they do, you want a clear order of precedence written in.
The practical consequence for CX: if your MSA lacks the right data protection terms, the SOW cannot repair that on its own. Check the MSA first.
What a CX outsourcing SOW should contain
A workable SOW for customer support, back-office or team extension usually runs through the same sections. Use this as your outline.
- Parties and references. Legal names, the governing MSA and its date.
- Purpose and background. A short statement of the business goal: for example, to cover after-hours patient inquiries or to handle legal intake.
- Scope of services. Channels, languages, hours, volumes, systems and tasks, plus what is explicitly out of scope.
- Deliverables and acceptance criteria. What gets produced and how you will confirm it is done.
- Staffing model. Seats, hours or managed service structure, ramp schedule, supervisor ratios, language proficiency.
- Service levels and reporting. Metrics, formulas, cadence, credits.
- Governance. Meeting rhythm, named owners, escalation path.
- Compliance and security. Data handling, access controls, training, audit rights.
- Fees and invoicing. Billing basis, rate card, what is billable and what is not.
- Change control. How scope, volumes and targets are modified.
- Transition in and out. Onboarding plan, knowledge transfer, exit assistance.
- Term and termination. Including termination for chronic service failure.
Experts quoted in the same procurement guidance describe a strong SOW as the manual for the relationship, not only a purchasing form. That framing is useful: if a new team lead at either company read only the SOW, could they run the program?
Scope: say what the team does and what it never touches
Vague scope is where most disputes start. Guidance for drafting SOWs frames ambiguity as the enemy and scope creep as the profit killer. For CX, that means writing scope at the level of the actual contact.
Instead of “provide customer support,” write something closer to this:
- Channels: inbound phone, email and chat, Monday to Friday, 7 a.m. to 7 p.m. Eastern.
- Contact types in scope: order status, returns, appointment changes, billing questions.
- Contact types out of scope: clinical advice, legal advice, refund approvals above a stated dollar threshold (escalated to your team).
- Systems: the CRM, ticketing tool and telephony platform the agents will use, and who owns licenses.
- Volume band: expected monthly contacts, with the range inside which pricing holds.
The out-of-scope list matters as much as the in-scope list. For a law practice, an agent can take intake details and schedule consultations, but should never evaluate a case. For a healthcare organization, an agent can handle scheduling and process questions but must escalate anything clinical. Write those boundaries down.
Deliverables versus activities
Procurement experts flag a recurring confusion: activities are things the provider does, deliverables are things you can inspect. A kick-off meeting or a project plan is an activity. A finalized, signed-off set of standard operating procedures is a deliverable. The state SOW drafting guidance recommends objective acceptance criteria that a third party could evaluate.
Good CX deliverables look like this:
- Documented SOPs for each contact type, signed off by your process owner.
- A completed training curriculum and a record of each agent’s completion.
- A QA scorecard, agreed in advance, with a calibration session schedule.
- A monthly performance report in an agreed format.
Service levels that can be enforced
The SLA section is where a CX SOW earns its keep. Two principles apply.
Avoid “best efforts.” Legal templates for outsourcing advise against it because it is hard to enforce. Use numbers, and define how they are measured. The LexDraft service agreement template describes outsourcing SOWs with KPIs, earn-back and a step-in right for the client on chronic SLA failure.
Define every metric. For each KPI, write four things: the formula, the data source, the measurement window and the exclusions. Typical CX metrics include:
| Metric | What to specify |
|---|---|
| Service level / speed to answer | Percentage answered within a set number of seconds, measured per interval or per month |
| First contact resolution (FCR) | How a “resolved” contact is defined and how repeat contacts are detected |
| CSAT | Survey method, sample size, response-rate floor |
| Quality score | Scorecard, sample rate, who calibrates |
| Schedule adherence and attendance | Measurement source and tolerance |
| Escalation accuracy | Share of escalations that met your criteria |
Exclusions, credits and chronic failure
Two details trip up nearshore programs in particular. First, define exclusions. If the provider’s team is in Latin America, local public holidays and scheduled maintenance windows should be handled explicitly, either as excluded time or through a holiday coverage plan, so that neither side is surprised by a credit or a staffing gap.
Second, pair service credits with a real remedy. Credits are usually the exclusive remedy for a single missed target, but buyers should insist on a termination right for chronic failure. A common drafting choice is a number of consecutive months of missed targets, often three, as described in the LexDraft template guidance. Pick the number that fits your risk tolerance and write it in.
Hours versus outcomes
Pricing basis shapes behavior. Industry analysts at Ryan Strategic Advisory describe a shift in Latin American nearshore from cost savings alone toward operational resilience and cultural alignment, with buyers moving beyond pure log-in-hour pricing toward models tied to business metrics such as FCR and CSAT.
In practice most SOWs blend the two. A per-seat or per-hour base keeps cost predictable, while a defined set of outcome metrics carries earn-back or bonus terms. If you are early in the relationship, start with a stable seat or managed service base and add outcome incentives once you trust the data.
Compliance clauses for healthcare, legal and financial services
General CX can run on a standard confidentiality clause. Regulated work cannot.
- Healthcare. If the provider will touch protected health information, HIPAA requires a Business Associate Agreement. LexDraft’s guidance notes this and recommends attaching the BAA to the contract structure. Specify who trains agents on HIPAA, how often, and how access is logged.
- Data protection law. Where GDPR or CCPA obligations apply, a Data Processing Addendum should cover processing purposes, audit rights and breach notification. The same source notes GDPR’s 72-hour notification window. Your counsel should confirm which regimes apply to your customer data.
- Legal services. Confidentiality and privilege handling should be explicit: who may access matter data, how recordings are stored and what happens on a suspected breach.
- Financial services. Spell out identity verification steps, call recording rules and escalation for suspected fraud, consistent with your own compliance program.
Put the caution where the work happens. If your SOW describes agents handling intake calls for a law firm or scheduling for a medical practice, have your compliance counsel review the annexes before signing. A BAA or DPA is not a formality.
AI usage terms
This is the clause most SOWs from two years ago lack. With AI tools showing up in agent assist, QA and summarization, state plainly which tools may be used, for which tasks and with what data. LexDraft’s research notes recommend that contracts forbid use of client confidential information to train third-party machine learning models. For legal, healthcare and financial work, make that a stated prohibition, and require advance written approval before any new AI tool touches your data.
Staffing, language and training requirements
If you are buying bilingual support, treat language ability as a contract term, not a hiring hope. The state SOW guidance suggests a defined proficiency requirement, for example C1 on the CEFR scale, because it gives you objective grounds to reject staff who do not meet it. Add how proficiency is assessed and who bears the cost of replacing an agent who falls short.
Other staffing terms worth specifying:
- Ramp schedule. Seats by week, with start dates and training completion gates.
- Supervision. Team lead ratio and named escalation contacts.
- Attrition and backfill. Maximum time to replace a departing agent, and who covers the gap.
- Dedicated versus shared. Whether agents work only on your account.
- Time zone coverage. Nearshore teams in Latin America typically overlap well with US business hours, but write the exact schedule down. For more on why, see our piece on how nearshore reduces communication gaps in CX.
Change orders: protect the budget and the service
Every CX program changes. Volumes rise, a new product launches, a channel is added. Experts consistently point to the missing formal change order process as a common cause of scope creep that destabilizes both budget and service quality, as the state procurement guidance explains.
A usable change clause covers:
- Who can request a change, by name or role.
- How it is submitted, in writing, with a description of impact on scope, staffing, SLAs and fees.
- Response time, for example a fixed number of business days for the provider’s estimate.
- Approval authority on both sides.
- Effective date and what happens to SLAs during the transition period.
Also define flex bands. If monthly volume can move 15 percent either way without a change order, say so, and say what pricing applies beyond that. For seasonal ecommerce and retail programs, this single clause often saves the most friction. Our guide on team extension strategy for scaling nearshore CX goes deeper on scaling models.
Governance and escalation
A SOW without a governance section describes a program nobody is managing. Include:
- Weekly operational review between the provider’s operations manager and your support lead: volumes, backlog, quality issues.
- Monthly business review: SLA performance, trends, improvement actions.
- Quarterly strategic review: roadmap, headcount, technology changes.
- Escalation ladder: tiers, named contacts, response times and a path to executives for unresolved issues.
Write who owns each artifact. Dashboards with no owner decay within a quarter.
Transition in, transition out
The LexDraft guidance cited above specifically lists detailed transition-in and transition-out plans as part of a BPO SOW. Both matter.
Transition in should cover knowledge transfer sessions, SOP creation, system access provisioning, shadowing, a pilot phase and go-live criteria. Make go-live conditional on the acceptance criteria you wrote earlier.
Transition out should cover data return and deletion, documentation handover, a defined assistance period and how fees work during wind-down. You hope never to use it. You will be glad it exists if you do.
Common mistakes buyers make
- Treating the SOW as an attachment. It is the operating manual. Involve the people who will run the program.
- Counting activities as deliverables. Define outputs you can inspect.
- Skipping the out-of-scope list. Silence invites scope creep.
- Using unmeasurable service language. If a clause cannot be tested, it cannot be enforced.
- Ignoring regulated-data terms until legal review. Raise HIPAA, privacy and AI terms in the first call.
- Forgetting holidays and time zones. Nearshore is a strength, but only when coverage is written down.
- No exit plan. Negotiating exit terms after a dispute is the worst moment to do it.
Why the market makes this worth the effort
The US customer care center industry generated $11.6 billion in revenue in 2025, according to IBISWorld, with a 1.6% rise that year after a stretch of decline and stagnation. Buyers have many providers to choose from, which gives you leverage to ask for precise terms. A provider that welcomes a detailed SOW is usually a provider confident in how it operates.
Our perspective on writing a CX SOW
We see the SOW as the first operational deliverable of the engagement, not the last legal step. When we scope a program with a healthcare organization or a law practice, we start from the contact types, the escalation boundaries and the metrics that matter to your leadership, then work backward to seats, schedules and training.
Three convictions shape how we approach it:
- Specific beats comprehensive. A two-page scope that names every contact type is more useful than twenty pages of boilerplate.
- Measure what the customer feels. Resolution and satisfaction should sit next to speed and cost in every scorecard.
- Plan for change. Volumes move, products launch, regulations shift. A clean change process keeps the relationship from straining.
Cultural alignment and bilingual quality are things we believe should show up in the document as requirements, not in a sales deck as adjectives. If a vendor will not put a standard in writing, ask why.
— Daniela
Turning the SOW into a working program
If you are scoping managed support, team extension or back-office work, we can help you draft the operational sections with you: contact types, SOPs, staffing and reporting. Healthcare teams can look at our healthcare CX operations offering for managed customer support and patient support with SOP management. Law practices can review our legal intake and back-office support services, including intake handling, scheduling, client follow-ups and managed legal team extension. For a broader view, see our CX and managed team extension services, or read how to select a nearshore CX partner before you issue an RFP.
Pre-signing checklist
Before you sign, confirm each of the following in writing:
- The SOW references the correct MSA and states which document controls in a conflict.
- Scope lists channels, languages, hours, contact types and exclusions.
- Each deliverable has acceptance criteria someone outside the project could verify.
- Every SLA has a formula, a data source, a window and exclusions.
- “Best efforts” language is replaced by numbers.
- Chronic failure triggers a termination right.
- BAA, DPA and security annexes are attached where relevant.
- AI tools are listed, and training on your data is prohibited.
- Language proficiency is a contractual standard.
- Change orders follow a documented process with named approvers.
- Transition-in and transition-out plans are attached.
FAQ
What does SOW mean in CX outsourcing?
SOW stands for statement of work. In CX outsourcing it is the document that describes the specific services the provider will deliver: channels, contact types, staffing, service levels, fees and timelines. It usually sits beneath a master services agreement that holds the legal terms.
What is the difference between an SOW and an SLA?
The SLA is a part of the SOW, or a schedule attached to it, that sets measurable performance targets such as speed to answer, first contact resolution and CSAT. The SOW is broader: it also covers scope, deliverables, staffing, governance, fees and change control.
Do I need a BAA in my SOW for healthcare support?
If the provider will create, receive, maintain or transmit protected health information on your behalf, HIPAA requires a Business Associate Agreement. It is typically attached to or referenced by the master agreement, and the SOW should point to it. Have your compliance officer or healthcare counsel confirm the exact structure for your organization.
Should I pay per seat, per hour or per outcome?
It depends on how predictable your volume is and how mature your measurement is. Per-seat or per-hour pricing gives cost certainty, while outcome-linked terms align incentives around metrics like FCR and CSAT. Many buyers combine a stable base with a limited set of outcome incentives.
How do I stop scope creep in an outsourced support program?
List out-of-scope contact types, set volume bands and require a written change order for anything outside them. Name who can approve changes on both sides, and review the scope in your monthly business review so drift is caught early.
Sources
- Drafting or Reviewing a Statement of Work, State of Iowa
- Free Service Agreement Template, LexDraft
- Customer Care Centers in the US Industry Analysis, 2025, IBISWorld
- America and the Nearshore: 2025, Ryan Strategic Advisory
- Outsourcing: United States Overview, Practical Law
- Drafting Statements of Work and Service Level Expectations, Council on Pharmacy Standards
