A client data export needs an agreed scope and a way to verify completeness. A folder of recordings does not explain pending work, action outcomes, configuration versions, or the relationships between records.
Define what the client needs and is authorized to receive: configuration, call metadata, approved summaries, media, action ledgers, pending requests, and billing evidence where applicable. Keep vendor-supported export limits visible.
Preserve relationships and meanings
Include stable identifiers, timestamps with time-zone meaning, status definitions, schema or field descriptions, and links or references between calls and resulting actions. Label unknown outcomes and missing assets rather than presenting an incomplete export as complete.
Exclude other clients' data and secrets. A credential reference may be useful in the asset register, but raw tokens should move only through the approved secure access process where required.
Work through a fictional service exit
A client requests its last ninety days of call outcomes and all open requests. The export includes the agreed period, action references, current pending queue, and a manifest of media included or unavailable.
Staff reconcile the open requests separately and assign owners. The export is delivered through the agreed controlled route, and the recipient verifies it can read the files and identify unresolved work before the old dashboard access ends.
| Export check | Required evidence |
|---|---|
| Client scope | Only authorized records and assets |
| Period | Explicit cutoff and date interpretation |
| Completeness | Manifest, counts, and missing-item notes |
| Relationships | Call, request, and remote action links |
| Delivery | Authorized recipient and access controls |
Separate export from deletion
Exporting does not automatically determine what the agency or vendors must retain or delete. Follow the agreed policy and applicable professional requirements with appropriate advice, including backups, replicas, scheduled reports, and downloaded copies where relevant.
A broad export improves portability but increases preparation and data-handling work. A smaller purpose-specific package may be easier to use. Agree on the intended recipient and future operation before choosing formats and scope.
Review client offboarding for the phone routing and pending-action transition around the export.
Questions about offboarding exports
Should every transcript be included by default?
Use the approved scope and purpose. More personal content is not automatically more useful.
Can an export promise full provider portability?
Only describe supported formats and verified import capabilities. Exported data may not recreate every vendor feature.
What should the completion record contain?
Scope, cutoff, manifest, known omissions, delivery recipient, verification, pending-work ownership, and separate retention or deletion actions.