Intake · Triage · Evidence · Counsel Handoff

Not a lawyer. Built to prepare better lawyer handoffs.

LawyerBot is the intake front door for digital-asset disputes across the eCorp network. When a demand arrives, it captures the facts in a structured form, classifies the threat, assembles the evidence checklist, and prepares an attorney-ready packet — so that when a matter reaches licensed counsel, counsel starts on the merits instead of on a blank page.

How intake works Not a law firm

The problem it solves

Most domain matters are lost in the first 72 hours — to disorganization, not to the merits.

A senior asset holder receives a demand and reacts: forwards a PDF, writes an emotional reply, misplaces the original correspondence, lets the clock run. By the time counsel is engaged, the record is scattered and momentum is gone. LawyerBot standardizes that first response so every matter arrives at counsel clean, complete, and consistent.

What LawyerBot is — and is not

IS: a structured intake, triage, and document-assembly workflow that prepares materials for review by licensed counsel.

IS NOT: a lawyer, legal advice, or a substitute for counsel. It does not opine on the merits or create an attorney-client relationship.

The intake pipeline

Capture. Structured intake of the asset, owner/controller, registrar, creation date, current use, and the incoming demand.

Classify. The threat is matched to a known pattern (see the taxonomy below), which sets the default response posture.

Checklist. A pattern-specific evidence checklist is generated — exactly what to collect and preserve.

Assemble. Facts, timeline, and evidence index are compiled into a non-admission packet stored in LegalServer.

Route. When legal judgment is required, the prepared packet is handed to licensed counsel and experts via EsquireNet.

Threat classification taxonomy

Intake matches each matter to a pattern. The pattern sets the default posture — always reviewed against the specific record before anything is sent.

Threat pattern	What it usually means	Default first response
Transfer demand on a senior asset	A later brand wants a domain it does not have priority over	Reject transfer; document senior use; request factual support
Trademark claim ignoring prior use	Filing date postdates the domain's use	Build creation/use chronology; preserve RDNH posture
UDRP notice	Formal proceeding initiated	Route to counsel immediately; preserve all communications
Broker / acquisition approach	Often a precursor to a later demand	Log the approach; it can become evidence of acknowledgment
Logo / color / confusion allegation	Surface-similarity claim	Side-by-side comparison; fact-check the demand's assertions
Email / actual-confusion event	Mail meant for the claimant reached the senior domain	Preserve as evidence the claimant adopted into a prior identity

The evidence checklist it builds

For every matter, LawyerBot generates a collection list — the documents that turn a position into a record:

Registrar records, WHOIS/registration history, and creation date.

All demand letters, emails, broker notes, and prior correspondence.

Internet Archive (Wayback) captures and continuous-use evidence.

USPTO records: the claimant's filing and claimed first-use dates.

Screenshots, specimens, and any actual-confusion communications.

Triage outcomes

Hold. Low-intent or unsupported demand — document and monitor, no escalation yet.

Document. Build the record and a non-admission response position for review.

Escalate. Formal proceeding or litigation risk — route to counsel via EsquireNet now.

The attorney handoff packet

What counsel receives from LawyerBot is a prepared file, not a blank slate — which shortens engagement and reduces cost.

Matter summary

Asset, owner/controller, registrar, creation date, current operating use.

Factual timeline

Prior use, claimant first-use, filing dates, and the demand sequence.

Evidence index

Registration records, Wayback captures, correspondence, USPTO records.

Posture

Reserved rights, RDNH/bad-faith preservation, requested factual support — for counsel review.

Questions, answered

Does LawyerBot give legal advice?
No. It organizes facts and prepares materials for licensed counsel. It does not opine on the merits or form an attorney-client relationship.

What should I do the moment a demand arrives?
Preserve everything and start intake. Do not delete correspondence, and avoid an off-the-cuff reply before the record is assembled.

Who actually handles the legal work?
Licensed attorneys and experts engaged through EsquireNet, working from the prepared packet.

Not a law firm. Not legal advice.

LawyerBot.com is an intake, triage, and document-preparation workflow within the eCorp network. It is not a law firm, does not provide legal advice, does not create an attorney-client relationship, and does not replace licensed counsel. Classifications and checklists are operational aids; the facts of each matter control, and matters requiring legal judgment are routed to qualified attorneys through EsquireNet.com.