How Should You Keep Takedown Case IDs and Ticket Numbers?
Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team
The short answer
In the case, not in email. Every channel returns an identifier — the registrar's ticket, the host's case, Meta's and the marketplaces' case IDs — and each packet checklist tells you to keep it because later filings cite it. Record each ID against its target's case the day it arrives, and the whole campaign stays one thread: escalation-ready, exportable, and immune to inbox archaeology.
What is keeping ticket numbers and case IDs?
A ticket number or case ID is a channel's handle for your filing — the registrar checklist calls the registrar's ticket the thing to keep and cite in host and platform reports, and the marketplace checklist keeps case IDs because repeat offenders are escalated by case history. Collectively, the IDs are the connective tissue of a multi-channel takedown.
What is keeping ticket numbers and case IDs?
A ticket number or case ID is a channel's handle for your filing — the registrar checklist calls the registrar's ticket the thing to keep and cite in host and platform reports, and the marketplace checklist keeps case IDs because repeat offenders are escalated by case history. Collectively, the IDs are the connective tissue of a multi-channel takedown.
Detection starts with the free scan on TakedownCoop's home page. From your one genuine domain, the scanner builds the candidate set an impersonator would plausibly register — typosquats made by deleting, transposing, duplicating or substituting letters, homoglyph lookalikes, affix combinations, and TLD swaps — and tests each candidate against live DNS. That order matters for keeping ticket numbers and case IDs: generation first, evidence second, and nothing is called a hit until DNS or a certificate log says it is real.
How the scan ranks and records it
The results are ranked, not dumped. The scanner's own priority scores put a resolving lookalike with a certificate at 90 and one without at 80, registered-but-dormant names at 50 or 40 depending on whether a certificate exists, and CT-only discoveries at 35 or 30. Certificate Transparency evidence is filtered for relevance — shared certificates carrying unrelated names are not treated as evidence against your brand — and any check that could not be performed is reported as exactly that, never converted into a reassuring claim.
Six filings, one thread of numbers
A real campaign generates IDs faster than memory holds them: a registrar ticket, a host case, a Meta case per ad variant, a Google trademark report, a listing ID per marketplace report, an app-store inquiry. Scattered across inboxes and browser tabs, they are trivia. Assembled against the case — each ID on its target, each target under one brand — they become the pattern evidence that turns a reviewer's 'another complaint' into 'a repeat offender with a file'.
TakedownCoop's structure is built for that assembly: cases per target, a timeline per case, and an export that carries the sequence out as JSON or CSV when a processor, insurer or a client's board asks what was done. The discipline required from you is tiny and absolute — when an ID arrives, it goes in the case that day. Every checklist in the packet generator ends with some version of that instruction because every escalation begins with it.
A worked example, end to end
A fictional furniture brand, Hartwood at hartwood.com, fights a campaign across five channels in one month and collects seven identifiers: registrar ticket HW-1102, a host case, three Meta case IDs for three ad variants, and two marketplace case IDs. All seven sit on the campaign's cases. When the seller relists in month two, the new marketplace filing quotes both prior case IDs and the registrar ticket — and is actioned as a repeat-offender escalation, with no time lost digging through anyone's sent folder.
Turning evidence into a filing
Evidence only helps if it arrives in the shape the channel expects. TakedownCoop's packet generator produces one packet per channel — registrar, host, Meta, Google Ads, marketplace, app store — each with that channel's own subject line and filing checklist, built on the same evidence block: genuine brand, lookalike domain, detection method, DNS and CT evidence, and priority. Packets are a Pro feature ($49/mo; Agency $99/mo covers multiple client brands), and they are prepared for the brand owner or their authorised agent to file.
- Record each ticket or case ID against its target's case the day it arrives
- Note which channel issued it and which filing it answers
- Cite the registrar ticket in host and platform filings, as the registrar checklist instructs
- Quote prior case IDs in every repeat filing — history is the escalation
- Export the timeline when you need the whole thread in one document
After you file: tracking the case
The follow-through is where most takedowns quietly die, so the product tracks it as a case. States run from evidence collected through packet built, submitted and provider response, to resolved — and a case can be re-opened as reappeared when monitoring finds the same threat back. Submitted and provider-response states are recorded as holder attestations, honestly labelled, while a verified resolution needs a re-scan showing the target is gone. The recheck after submission is set at seven days.
Where efforts like this usually go wrong
The commonest failure with keeping ticket numbers and case IDs is treating it as a message instead of a case. A report typed from memory, sent from the wrong account, missing its ticket number within the week — each is a small thing, and together they are why impersonators outlast brands that were right about everything. The artefacts exist to remove memory from the loop: the evidence block is generated, not recalled; the checklist is written for the channel, not improvised; the case holds the IDs, not an inbox thread nobody can find in month two.
There is also a sequencing mistake: acting on the loudest artefact instead of the highest-priority one. A furious customer message about a dormant name feels urgent; a quiet scan result showing a live, certified clone is urgent. The priority score exists to arbitrate exactly that conflict — 90 before 40, live before loud — and the teams that follow it spend their filing hours where the money is actually leaving.
Keeping it from coming back
Impersonators rotate, so a one-off filing is a snapshot, not a solution. Monitoring re-scans the domain, and when a known threat reappears the case re-opens and its packet regenerates. Pair that with the verified-genuine page — a public page where customers can confirm they are dealing with the real brand — and the timeline export (JSON and CSV) that processors and insurers ask for, and keeping ticket numbers and case IDs stops depending on whoever happens to notice the fake next.
Frequently asked questions
Which ID matters most?
The registrar's ticket number — the packet checklist names it as the citation host and platform reports should carry.
I lost an ID in email. Recoverable?
Channels can usually re-issue from the filing account, but the lesson stands: the case, not the inbox, is the system of record from the next filing onward.
Do IDs expire in usefulness?
No — case history is precisely how repeat offenders are escalated, and old IDs are the history.
Can Agency clients see their IDs organised per brand?
Yes — cases and packets are per brand on Agency, so each client's thread stays separate and exportable.
Keep exploring
TakedownCoop home — run the free brand scan · All TakedownCoop guides · Pricing — Free, Pro and Agency · Get a license key · Takedown cases · My street (dashboard) · Terms · Privacy · Ingenious AI — all platforms
Related guides
- How Should You Take Evidence Screenshots for a Takedown?
- How Do You Export an Evidence Timeline as JSON or CSV?
- Who Needs an Evidence Timeline — and Why Processors and Insurers?
- How Do Priority Scores Rank Lookalike Hits?
- How Do You Write a Takedown Subject Line That Gets Read?
- What Trademark Evidence Should You Attach to a Takedown?