Rights and contracts
Who owns customer-written support tickets and chat messages?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Customer-written support tickets and chat messages usually have split ownership: the customer may hold copyright in original text it wrote, while your company holds the ticket record, your agents' replies and whatever license your terms grant. Whether you can license the archive depends less on ownership than on that contract license and on privacy law.
Key takeaways
- Rights in a support ticket split three ways: copyright in the words, contract rights to use them and privacy rights of the people named.
- Short routine messages may carry little or no copyright, while longer original descriptions can belong to the customer or the customer's employer.
- Replies written by employed agents are usually company work; replies by outsourced agents depend on the outsourcing contract.
- The license in your terms of service or subscription agreement usually decides what you may do with customer-written text.
- Removing personal details addresses privacy, not copyright or contract limits.
Why is ownership the wrong single question?#
Ownership of a support ticket is the wrong single question because one ticket bundles material with different rights holders. A Zendesk or Intercom conversation can hold a customer's original description, an agent's reply, an internal note, a macro your team wrote, an attached screenshot and system metadata such as timestamps, tags and satisfaction ratings.
General counsel usually gets further with three narrower questions: who holds copyright in each piece of text, what license the company has to use it, and what privacy obligations attach to the people named in it. The answers can differ within the same conversation, and a decision about the archive is really a decision about each layer.
Who usually holds rights in each part of a ticket?#
Rights in a ticket usually follow who wrote each part and under which agreement. The table is a starting map; specific contracts and facts can change any row.
| Part of the record | Who usually holds copyright | What usually controls reuse |
|---|---|---|
| Customer's original message | The writer, or the writer's employer if written on the job | Your terms of service, subscription agreement and any feedback clause |
| Short routine messages | Possibly no one, if too brief or functional to be original | Contract and privacy terms still apply |
| Agent replies and internal notes | The company, when agents are employees acting in their role | Company policy, and the outsourcing contract for external agents |
| Macros, help articles and canned replies | The company, or whoever drafted them under contract | Authorship records and any content license |
| Attachments and screenshots | Often a third party: the customer, its vendors or a software maker | Usually excluded unless reviewed one by one |
| Tags, timestamps, status and ratings | Usually facts, not protected expression | Contract, privacy terms and the helpdesk vendor's export terms |
Does a customer own copyright in the messages it writes?#
A customer can own copyright in a support message when the text is original expression rather than a short functional statement. A detailed bug report that walks through a workflow in the customer's own words is more likely to qualify than a message saying the export button is broken.
In B2B support the writer is usually an employee of the customer, so any copyright typically sits with the customer company under work-made-for-hire principles rather than with the individual. That matters because the customer company is also the party to your subscription agreement, so the contract it signed usually governs what you may do with that text.
Even where the terms are silent, a customer who writes in usually grants at least an implied license to use the message to answer it and run the support relationship. Whether that implied license reaches licensing the text to an outside developer is far less certain, which is why buyers ask for a clear license chain. Copyright in individual messages is seldom the deciding issue on its own, and counsel should not read thin copyright as permission; contract and privacy limits apply regardless of how original the words are.
What do your contracts usually say about support content?#
Your contracts usually decide the practical answer, because they set the license the customer granted when it wrote in. Review the master subscription agreement or online terms, the data processing agreement, any feedback clause and the support policy, in the versions that applied when each conversation happened. The clauses to read closely are these.
- Definition of customer data: whether it covers support communications or only content uploaded into the product.
- License grant: whether customer data may be used solely to deliver the service or for improvement too, and whether improvement plausibly reaches training models for others.
- Feedback clause: many agreements give the vendor broad rights in suggestions, but feedback is rarely defined to include whole conversations.
- Confidentiality: whether support content counts as the customer's confidential information.
- Negotiated terms: enterprise customers may have narrowed reuse rights or added no-AI-training clauses.
Where does privacy law come in?#
Privacy law comes in because support conversations name real people: the writer, colleagues they copy in, end customers of your customer, and sometimes payment or account details pasted into the thread. Those rights belong to the individuals and do not move with copyright or with your contract.
Privacy preparation strips names, emails, phone numbers, account numbers and similar identifiers from structured fields and free text alike, before anything leaves the company. Preparation answers the privacy question only; it cannot create a license that the contract withholds, and it does not change who wrote the words.
How do you turn the three answers into a licensing scope?#
A licensing scope comes from combining the copyright, contract and privacy answers for each layer of the archive, then choosing the narrowest route that still gives a buyer useful records. Most companies end up with a tiered package rather than an all-or-nothing decision.
Outsourced support teams need their own check. If a business process outsourcer wrote replies under its own agreement, confirm that the agreement assigns or licenses that work to you and does not restrict reuse of the conversations it handled.
| Layer | Usually include when | Usually hold back when |
|---|---|---|
| Company-authored replies and notes | Agents were employees, or the outsourcing contract assigns their work | Notes quote confidential customer material that cannot be removed |
| Customer-written messages | Terms or an amendment grant the license and privacy preparation is complete | Terms limit use to providing support, or a no-reuse clause applies |
| Resolution metadata | Fields describe outcomes rather than identify people | Tags or custom fields hold names or account numbers |
| Attachments | Each file is reviewed and belongs to the company | Files belong to customers or other third parties |
Illustrative: sorting a scheduling software company's helpdesk archive#
Illustrative: a fictional B2B scheduling software company has kept years of Zendesk tickets and Intercom chats from operations managers at its customers, mostly cleaning and field service firms. A model developer wants resolved conversations to train a support agent.
Counsel maps the archive against three versions of the company's terms. None clearly grants rights to license customer-written text to an outside developer, and several enterprise accounts have negotiated no-reuse clauses. Attachments are excluded across the board because many contain customers' own documents.
The company scopes the first package around material it authored: agent replies, internal notes, macros and resolution metadata such as category, time to resolve and outcome, all de-identified. Customer-written messages are added only for accounts that sign a short amendment describing the use plainly.
How SourceX approaches authored content#
SourceX records authorship and the license chain during the Rights step of the SourceX five-step transaction, one record family at a time. Customer-written text, company-authored replies and attachments are scoped separately, and the first conversation covers systems and metadata, not files.
The findings go into the SourceX Evidence Packet, where provenance, licensing rights, permitted use, the privacy record and release authorization are recorded layer by layer. A buyer can then tell which parts of a conversation were licensed, and on what basis.
Frequently asked questions
Do our helpdesk vendor's terms affect who owns the tickets?
Usually not ownership, but they can affect access. Helpdesk providers generally treat account content as the customer's, while their terms govern exports, API use and retention. Check your plan's export limits and the vendor's documentation before scoping an archive, and confirm whether older conversations are still retrievable.
Does anonymizing customer messages solve the copyright issue?
No. Removing names and identifiers addresses privacy, but the words themselves are unchanged, so any copyright and contract limits remain. Summarizing customer text can reduce the issue, but it also changes what a buyer receives, so agree the approach with the buyer and with counsel.
What about chats with consumers rather than business users?
Consumer conversations shift more weight to privacy and consumer protection law. Individuals write in their own right, terms are usually click-through, and state privacy laws give consumers rights over their personal information. Many suppliers limit licensing to business-user conversations, or to company-authored replies, for that reason.
Who owns recordings and transcripts of support calls?
Recorded calls add a layer: consent rules under federal and state wiretap laws, and the voice itself as personal information. Transcripts inherit the same contract and copyright questions as chats. Treat recordings as their own record family, with a consent review of their own, rather than folding them into the ticket archive.
Are internal notes safe to license because customers never see them?
Internal notes are company-authored, which simplifies copyright, but they often quote customer messages, name individuals and include candid remarks about accounts. They still need privacy preparation and a review for the customer's confidential information before release.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.