Data library
Company email archives for AI.
Quick answer
Sometimes, but email is one of the most sensitive types of business data. A company can license email only where it owns the records, its policies and contracts allow it, and every person's details are removed. In practice, buyers often prefer narrow, well-defined sets — such as shared support or sales inboxes — over whole mailboxes. Personal, legal, HR and privileged messages are excluded.
What's included#
- Shared inbox threads (support, sales, operations)
- Message order, timestamps and reply structure
- Outcome of the thread (resolved, quote sent, order placed)
- Attachments only where cleared separately
Where it typically lives
How AI developers use it#
- Training assistants to draft business replies
- Evaluating how AI handles multi-message conversations
- Teaching models to triage and route requests
Preparation and privacy#
- Remove names, addresses, phone numbers and signatures
- Replace customer and company names with stand-ins
- Drop messages with legal advice, HR or medical content
- Keep thread structure so replies still make sense
What's usually left out#
- Personal mailboxes of individual employees
- Legal, HR, board and privileged communications
- Messages from regions or customers whose contracts forbid sharing
- Attachments that haven't been reviewed separately
How it's packaged#
- Threads as ordered message lists with roles (customer, staff)
- A data sheet listing inboxes, years covered and thread count
What makes it valuable#
- Clear business purpose for each inbox
- Complete threads with a visible outcome
- Consistent removal of personal details
Starting with a sample#
- A small set of cleaned threads from one shared inbox, approved by you
How SourceX approaches it#
Preparation requirements are agreed with you before any work begins, and the approved dataset is delivered only after an executed agreement and your explicit authorization of buyer access.
Industries with this data
Datasets built from this data
Dataset specs AI labs can request through SourceX, sourced to spec from businesses like yours.
- Customer and revenueCustomer support ticket datasetsA customer support ticket dataset is a de-identified export of real support cases: the customer's messages, agent replies, internal notes, escalations,…TextStructured records
- Customer and revenueContact center call recordings and transcriptsA contact center call recording dataset is a collection of recorded customer service and support calls, usually with speaker-labeled, time-aligned…AudioTextStructured records
- Customer and revenueSales CRM pipeline historiesA sales CRM dataset is a record of how deals actually moved through a company's pipeline: opportunities with their stage changes, close-date pushes and…Structured recordsText
- Customer and revenueSales call recordings and transcriptsA sales call transcript dataset is a set of recorded sales conversations, such as discovery calls, product demos and negotiations, with speaker-attributed…AudioTextStructured records
Typical fields#
- Record ID (pseudonymous)
- Created and closed timestamps
- Category or type
- Request or input text
- Ordered steps or actions
- Outcome or resolution
- Role of each actor (not identity)
Sample record
Illustrative · fictional
- record_id
- rec_8f21c0
- created / closed
- 2023-04-11 → 2023-04-12
- category
- Billing question
- request
- Customer [NAME] asks why invoice [ID] was charged twice.
- steps
- 1. Checked payment log 2. Found duplicate 3. Issued refund
- outcome
- Resolved · refund issued
- actors
- customer, agent_tier1
What buyers look for#
- Complete start-to-finish records
- Consistent fields over years
- Clear, labeled outcomes
- Low duplication
- Work done by skilled professionals
- Edge cases and failures, not only successes
Personal details removed#
- Names
- Email addresses
- Phone numbers
- Postal addresses
- Account, customer and order numbers
- Government IDs
- Payment details
- Health information
- IP addresses and device IDs
- Credentials, keys and hostnames
How buyers test it#
- Sample review by buyer researchers
- Residual personal-data scan
- Duplicate and leakage check against public data
- Label and outcome accuracy spot-check
- Rights and consent documentation review
Rules that may apply
Federal Wiretap Act 18 U.S.C. 2511
Applies to recorded calls and intercepted communications; some states require all-party consent. Assessed deal by deal.
California Consumer Privacy Act Cal. Civ. Code 1798.100 et seq.
May apply where records include personal information of California residents and the business meets the law's thresholds. Assessed deal by deal.
Reviewer note: applicability is confirmed with counsel for each deal. Not legal advice.
All data types · Issue resolution histories · Internal knowledge bases · Project records
Frequently asked questions
Can we license employees' personal mailboxes?
We generally advise against it. Shared, business-purpose inboxes are much easier to clear and more useful to buyers.
Do we need employee consent?
It depends on your policies and state law. Your counsel should confirm before any email is included.
Related resources
- SolutionWhat is AI evaluation data?
- SolutionHow AI developers source data
- IndustryBPO & contact centers data
- IndustryRecruiting & staffing data
- DataInternal knowledge bases
- QuestionShould companies sell or license their data?
- QuestionCan CRM data be licensed?
- InsightCan you license spreadsheets and financial models to AI companies?
- InsightCan you license training materials and course content to AI companies?
- InsightCan I limit licensing to evaluation only?
- DataWorkflow data
- GlossaryDataset
See if your company qualifies
A short company assessment. No data uploads are needed.