Call Center OutsourcedPowered by StealthAgents

Call Center Outsourced evidence brief · Desk review · Published

How should a contact center audit the subprocessors that touch call data?

A subprocessor audit that inventories the data path, checks the contract chain, tests change notice, and keeps evidence current.

How should a contact center audit the subprocessors that touch call data? editorial illustration
On this page
  1. Key stats
  2. Key takeaways
  3. Question and scope
  4. What the evidence supports
  5. Inventory every subprocessor
  6. Trace the data path
  7. Check the contractual chain
  8. Test the change-notification clause
  9. Collect annual evidence
  10. Limits and review
  11. Put this into a support lane
  12. Related operating guides
  13. FAQs
  14. Sources

Key stats

  • 2.67 million U.S. customer service representative jobs in 2025 (BLS)
  • $21.53 median hourly wage in May 2025 (BLS)
  • 289,500 projected annual openings, 2025 to 2035 (BLS)

Key takeaways

  • Inventory every vendor that can touch audio, text, or metadata.
  • Trace one call end to end and note the retention period at each step.
  • Check that the client's data terms bind each subprocessor in writing.
  • Test the change-notification path with a real question.

Question and scope

This brief asks how a contact center should audit the subprocessors that touch call data. The population is an outsourced queue that uses a telephony platform, a transcription vendor, a quality tool, and a workforce system. The unit is one subprocessor and the data path it supports. The analysis covers inventory, contract flow, change notice, and evidence. The list should name the purpose and the data type, not only the company.

The scope excludes a full security certification of every vendor. It also excludes the client's own systems unless they connect to the queue. The audit should show where customer data goes and who can reach it. Write the scope in the client agreement so the review does not expand into an open-ended investigation. A named scope makes the audit repeatable; It also lets the client compare the vendor's list with its own records.

What the evidence supports

The NIST Privacy Framework asks organizations to understand data flows and the parties involved. ISO 18295 places contact-center processes within a managed system. ISO 9001 supports documented information and supplier control. None of these sources gives a universal subprocessor list or a single audit frequency. They support a documented chain rather than a verbal assurance; the client's contract and privacy terms set the minimum.

The evidence favors a data-path view over a vendor-name view. A subprocessor may receive audio, text, metadata, or only a summary. The risk depends on what it receives and how long it keeps it. Map the data type to each vendor before judging the control. A short list with clear paths is more useful than a long list with no detail.

A useful test is to ask each vendor what data it would receive if the queue sent only a call identifier. If the answer is a full recording, the path is broader than the contract suggests. Record the answer and compare it with the data-flow map. The gap is the audit finding, not the vendor's reputation. A clear question often reveals more than a long questionnaire.

Inventory every subprocessor

List every subprocessor that can access call data, including the ones added by another vendor. A telephony provider may use a separate recording store or a transcription engine. Include the purpose, the data type, the location, and the contract owner. Do not rely on the vendor's marketing page for the list. Ask for the current list in writing and date it; A list without a date cannot support an audit.

Check the list against the systems the agents actually use. A tool that appears in the browser may send data to a third party the contract does not name. Review the network logs and the integration list. If a system is used but not listed, add it before the audit continues. The gap is a finding, not a paperwork issue; name the owner who will close the gap and the date.

Trace the data path

Trace one customer call from the phone system through every vendor that touches it. Record where the audio is stored, where the transcript is created, and where the quality score is kept. Note the retention period at each step. The trace shows whether a deletion request can actually be honored across the chain. A diagram is useful only when it matches the live configuration.

Repeat the trace for a chat or email contact if the queue handles them; the data path may differ from the voice path. A vendor that never sees voice may still receive personal data in a ticket. Record the differences instead of assuming one map covers every channel. The client should see the map before approving a new tool. A new integration can change the path without changing the contract.

Include the backup and archive paths in the trace. A vendor may delete the live copy while a backup still holds the recording for months. The deletion test should cover every copy the client would expect to be removed. If a backup cannot be reached, say so and let the client decide. That limit belongs in the audit report, because silence can look like a completed deletion.

Check the contractual chain

Check that the client's data terms flow down to each subprocessor. The vendor should have a written agreement that covers confidentiality, security, retention, and breach notice. A general services contract may not be enough. Ask for the clause that binds the subprocessor, not only the vendor's promise to the client. The clause should name the data type and the purpose; It should also say what happens when the relationship ends.

Record any gap between the client's terms and the subprocessor's obligations. A vendor that cannot accept the client's audit or deletion terms is a risk the client must see. Do not paper over the gap with a side letter that the client has not approved. Escalate the decision to the contract owner. The queue should not sign away a client obligation on its own.

Test the change-notification clause

Test the change-notification clause with a real question. Ask the vendor how it informs the queue when it adds a subprocessor or changes a data location. A clause that requires notice is only useful if someone receives it. Name the person who monitors the notices and the time allowed to object. A shared inbox with no owner is not a control.

Record the last notice the vendor sent and what the queue did with it. If no notice exists, ask for the current list and compare it with the contract. A silent change is a finding even when the new vendor is reputable. Review the notice path when the vendor changes its account team. The control should survive a personnel change on either side.

Ask what notice the queue receives when a vendor changes its own subcontractor. The answer may be a portal update that no one watches. Name the person who checks the portal and how often. A notice that no one reads does not satisfy the clause. The check should be on a calendar, not on memory, and the result should be logged.

Collect annual evidence

Collect evidence once a year and after any material change. The evidence can include the subprocessor list, the contract clauses, a recent security report, and the deletion test. Do not accept a certificate as proof that the data path is correct. The certificate covers a scope that may not match the queue; read the scope statement before relying on the report. A report for a different service tells the client very little.

Keep the evidence with the client file and note the date of each item. If a vendor refuses to provide a document, record the refusal and the reason. The client can then decide whether to accept the risk. Do not describe a missing document as compliant because the vendor is well known. The audit is about evidence, not reputation; A short evidence index makes the file usable at renewal.

Limits and review

This method cannot certify a subprocessor's security or guarantee that a data path is complete. It also cannot resolve a contract dispute between the client and the vendor. The queue can inventory, trace, and document. State those limits in the report so the client does not mistake a list for an assurance. The client's legal and privacy owners decide what risk is acceptable.

Review the inventory when a tool is added, replaced, or retired; recheck the data map after a platform migration. Sample one deletion request each year to see whether the chain works. Update the contract owner when a vendor changes hands. A subprocessor list is a living record, not a one-time attachment. The review should end with one owner and one date; that habit keeps the record current between formal audits.

Keep a short list of open findings with an owner and a due date. Review it at the next client meeting rather than waiting for the annual audit. A finding that stays open for a year is a decision the client has not made. Say that plainly and record the response. The list should show the risk, not only the task.

Put this into a support lane

Bring the current vendor list, one contract clause, and the last data-flow trace so the review can test the chain end to end.

Review the subprocessor inventory

FAQs

How often should the subprocessor list be reviewed?

At least annually and after any material change, such as a new integration or a platform migration. The review should name an owner and a date.

Is a vendor security certificate enough evidence?

No. The certificate may cover a different scope. The queue should also check the subprocessor list, the contract clauses, and a deletion test.

Sources

  1. NIST Privacy Framework
  2. ISO 18295-1:2017 Customer contact centres
  3. ISO 9001:2015 Quality management systems
  4. GAO-20-283G: Assessing Data Reliability
  5. NIST Special Publication 800-92: Guide to Computer Security Log Management