Automated Section 2(d) Conflict Alerts
Every morning, WebRun opens Alt Legal, reads new Section 2(d) watch hits against your clients' marks, captures each conflicting application, drafts a client alert email in Gmail left unsent for review, and posts your team a Slack summary of what surfaced.
How do I alert clients about conflicting trademark applications automatically?
Every morning, WebRun opens Alt Legal, reads new Section 2(d) watch hits against your clients' marks, and matches each conflicting application to the affected client. It drafts a client alert email in Gmail, leaves it unsent for an attorney to review, and posts your team a Slack summary so close conflicts surface fast without any message going out unapproved.
- Conflicting filings surface the morning they hit the watch
- Client alerts are drafted for review, never sent unattended
- Short opposition windows get an attorney's eyes first
Built for trademark attorneys · brand protection teams · IP law firms · in-house IP counsel
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.altlegal.comin a real browser with your saved login - no setup, no API keys. -
1
Alt Legal - read Section 2(d) watch hits
altlegal.com
WebRun opens Alt Legal to read new Section 2(d) watch hits. - Open Alt Legal and review new Section 2(d) trademark watch hits
- Capture each conflicting application, its owner, classes, and how close it sits to the client's mark
- Match each hit to the affected client and their registered mark
Done when Every new watch hit is captured and matched to the affected client.
-
2
Gmail - draft the client alert
gmail.com
WebRun drafts the client alert and leaves it unsent for review. - Draft a clear client alert that names the conflicting application and the client's affected mark
- Summarise the overlap and outline the options, such as watching, opposing, or contacting the applicant
- Leave the email saved as a draft for an attorney to review. Never send a conflict alert to the client on its own
Done when A client alert sits drafted and unsent for each affected mark.
-
3
Slack - post the watch summary
slack.com
WebRun posts the day's Section 2(d) watch summary to Slack. - Post an internal summary of the new watch hits, grouped by client
- Flag the closest conflicts and any with a short opposition window first
- Link each item to the drafted alert so an attorney can review and send
Done when The team has today's Section 2(d) watch summary in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it email clients about a conflict on its own?
No. WebRun drafts the client alert in Gmail and leaves it unsent for an attorney to review and send. No conflict alert reaches a client until a person approves both the finding and the wording.
How does it know which filings conflict?
WebRun reads the Section 2(d) trademark watch hits Alt Legal already surfaces, then matches each flagged application to the affected client and mark, so you review real watch results rather than a fresh guess.
Can it flag a short opposition window?
Yes. WebRun highlights conflicts with a near opposition or response deadline first in the Slack summary, so time-sensitive filings get an attorney's eyes before the window closes.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.