## TL;DR
Loop in legal the moment a ticket involves lawyers, subpoenas, data deletion or privacy requests with teeth, threats of lawsuits, or content the company might be liable for. Document facts only, route through the defined legal channel, and never promise a legal outcome to the customer. Support's job is the handoff, not the judgment.

## The query

```text
how to loop legal into a support ticket
```

## Use this when

- A customer mentions lawyers or lawsuits
- You receive a subpoena or legal-looking request
- A data deletion or privacy request has complications
- Content in a ticket could create liability

## Not for

- Giving the customer legal advice
- Writing legal responses yourself
- Deciding the company's legal position
- Handling routine privacy requests with a clear process

## Steps

### 1. Know the triggers that mean legal, not support

Mentions of attorneys or litigation, subpoenas or court orders, law enforcement requests, data deletion demands that conflict with retention obligations, defamation or IP complaints about content, and threats of public legal action. Memorize the list; hesitation here is expensive.

Expected output: agents recognize a legal trigger on sight.

### 2. Document facts, nothing else

Write down what happened, what was said, and when. No opinions, no admissions, no speculation about liability. "Customer stated they will contact an attorney on [date]" is documentation; "we are probably liable" is a problem.

Expected output: a clean factual record legal can use immediately.

### 3. Route through the defined legal channel

Legal alias, intake form, or designated contact: use the official path, not a Slack DM to someone you know. Include the ticket link, the trigger, and your factual summary. Then wait for their direction before replying to the customer.

Expected output: legal owns the response strategy from that point.

### 4. Pause the normal ticket workflow

Dont keep troubleshooting or negotiating while legal reviews. A well-meaning agent trying to "resolve" a legal situation can create commitments the company cant keep. Mark the ticket, set expectations with the customer, and hold.

Expected output: no agent action on the ticket until legal clears it.

### 5. Never promise a legal outcome

"We will delete your data by Friday" or "our lawyers will contact you" are promises you cant make. What you can say: "I have passed this to our legal team and they will respond." That is the whole script until legal gives you more.

Expected output: the customer hears process, not commitments.

## Variant phrasings

### when to escalate a support ticket to legal

Step 1. The trigger list is the escalation rule.

### handling legal threats in customer support

Steps 2 and 5. Document factually, promise nothing.

### support process for subpoenas and legal requests

Steps 3 and 4. Official channel, paused workflow.

## Why it happens

Support agents are problem-solvers, so their instinct on a legal ticket is to solve it like any other ticket: empathize, negotiate, resolve. But legal situations run on different rules, where a friendly concession can become a binding commitment. The handoff exists because the skills that make a great agent are the wrong skills for a legal matter.

## Edge cases

- The customer is bluffing about lawyers: treat it as real anyway. Bluff or not, the trigger list doesnt have a bluff exception.
- Law enforcement contacts support directly: route to legal immediately, do not provide data. Even urgent-sounding requests go through legal first.
- The request conflicts with the customer's own interest: still route it. Support doesnt adjudicate; legal does.
- Legal is slow to respond: one polite follow-up with the ticket age and customer impact. Then keep holding; do not freelance a response.
- Routine privacy requests: if there is a documented self-serve process, use it. Legal only enters when the request is disputed, complex, or adversarial.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_FkfKbr3oTMzImRsjx1muaA