Book a demo

Cut patent&paper research from weeks to hours with PatSnap Eureka AI!

Try now
WebSock Global Strategies v. Zendesk — WebSocket Patent Dispute | PatSnap
Explore in Eureka
Case ID1:24-cv-01003
FiledAug 2024
ClosedOct 2024
Patent Litigation

WebSock Global Strategies v. Zendesk: Stipulated Dismissal in 34 Days

WebSock Global Strategies, LLC asserted US7756983B2 — a patent covering symmetrical bi-directional communication — against customer experience platform Zendesk, Inc. in Delaware. The parties reached a stipulated dismissal with prejudice against all claims in just 34 days, suggesting rapid settlement or licensing resolution before substantive litigation began.

Resolution time
34days
34 days — well below the median district court patent case lifespan of 2–3 years
Patents asserted
1
US7756983B2 — symmetrical bi-directional (WebSocket) communication technology
Outcome
Case Dismissed
All claims dismissed with prejudice; counterclaims dismissed without prejudice
Cost ruling
Each Party Bears
No fee shift — each party bears its own costs, expenses, and attorneys’ fees
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

A 34-day patent dispute over WebSocket communication technology

On August 30, 2024, WebSock Global Strategies, LLC filed suit against Zendesk, Inc. in the U.S. District Court for the District of Delaware before Judge Jennifer L. Hall, asserting infringement of US7756983B2. The patent-in-suit covers symmetrical bi-directional communication — technology foundational to real-time web communication protocols such as WebSocket. Zendesk, a leading customer support and engagement platform, was identified as the accused infringer, with its real-time messaging and live-chat infrastructure likely within scope of the asserted claims.

The case resolved on October 3, 2024 — just 34 days after filing — via a joint stipulation of dismissal under Federal Rule of Civil Procedure 41(a)(1)(A)(ii). All claims against Zendesk were dismissed with prejudice, foreclosing any future re-filing of the same claims by WebSock. Notably, Zendesk’s counterclaims were dismissed without prejudice, preserving Zendesk’s ability to refile those claims independently. Each party agreed to bear its own legal costs, with no fee-shifting order entered.

The speed of resolution — 34 days, before any substantive motion practice or claim construction — strongly suggests the parties reached a private agreement, most likely a license or covenant not to sue, shortly after the complaint was served. The mutual cost-bearing arrangement is consistent with a negotiated settlement rather than a one-sided capitulation. The public record does not disclose any financial terms or licensing conditions, and the asymmetric prejudice terms (with-prejudice for claims, without-prejudice for counterclaims) is a pattern commonly associated with structured licensing exits.

Case at a glance
Case no.1:24-cv-01003
DefendantZendesk, Inc.
CourtDelaware
JudgeJennifer L. Hall
FiledAugust 30, 2024
ClosedOctober 3, 2024
Duration34 days
OutcomeCase Dismissed
Verdict causeInfringement Action
BasisCase Dismissed
Prior Art Intelligence
See what prior art exists on this patent.
Eureka scans millions of patents and papers to surface prior art that may have invalidated these claims before costly litigation begins.
Check Prior Art
Case data sourced from PACER / Delaware District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Case Dismissed in 34 days

34 days — well below the median district court patent case lifespan of 2–3 years

Case timeline: Complaint filed AUG 30 2024, SEP–OCT — 34 days total Horizontal timeline showing the three key events in WebSock Global Strategies, LLC v Zendesk, Inc. from filing to resolution. Source: PACER, Delaware District Court. AUG 30 2024 Complaint filed Pre-trial proceedings OCT 3 2024 Case Dismissed 34 DAYS TOTAL
Dismissal terms

Stipulated dismissal with prejudice: what the terms mean for each party

Legal mechanism

Rule 41(a)(1)(A)(ii) stipulated dismissal explained

A Rule 41(a)(1)(A)(ii) dismissal is a court-approved stipulation signed by all parties — no judicial merits ruling is made. Dismissal ‘with prejudice’ on the plaintiff’s claims operates as a final adjudication on the merits under res judicata, permanently barring WebSock from re-asserting the same claims against Zendesk based on US7756983B2. This is the standard mechanism used to formally close cases following a private settlement or licensing agreement.

Consent dismissal — no merits ruling
Plaintiff outcome

WebSock cannot refile these infringement claims against Zendesk

With the claims dismissed with prejudice, WebSock Global Strategies has permanently surrendered its right to pursue US7756983B2 infringement against Zendesk in any future action. This is a significant concession, typically made in exchange for a licensing payment or other commercial consideration not disclosed in the public record. WebSock retains the patent and may continue asserting it against other defendants — the with-prejudice bar applies only to Zendesk.

Claims barred — Zendesk-specific
Defendant outcome

Zendesk’s counterclaims survive — dismissed without prejudice

Zendesk’s counterclaims were dismissed without prejudice, meaning Zendesk retains the ability to refile them independently. This asymmetric structure — plaintiff’s claims out with prejudice, defendant’s counterclaims out without prejudice — is consistent with a negotiated exit where Zendesk preserved optionality, potentially including the right to challenge patent validity in a future IPR or declaratory judgment action if circumstances change.

Counterclaims preserved
Commercial implications

US7756983B2 remains live — risk for other real-time communication platforms

The with-prejudice dismissal resolves only Zendesk’s exposure. US7756983B2 remains in force and WebSock retains full enforcement rights against the broader market. Any SaaS platform, messaging provider, or customer engagement tool relying on WebSocket or symmetrical bi-directional communication protocols should assess FTO exposure. The rapid resolution here suggests the patent may carry licensing leverage, making proactive clearance analysis advisable for similarly situated companies.

Patent remains enforceable
Legal analysis based on PACER docket records for case 1:24-cv-01003 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffWebSock Global Strategies, LLCCompanyPatent assertion entity — holder of US7756983B2 covering WebSocket bi-directional communicationSearch in Eureka ↗
DefendantZendesk, Inc.CompanyZendesk, Inc. — cloud-based customer service and engagement platformSearch in Eureka ↗
Plaintiff counselAntranig N. GaribianAttorneyCounsel for WebSock Global Strategies, LLCSearch in Eureka ↗
Plaintiff law firmGaribian Law Offices, PCLaw FirmRepresenting WebSock Global Strategies, LLCSearch in Eureka ↗
Defendant counselJeremy Douglas AndersonAttorneyCounsel for Zendesk, Inc.Search in Eureka ↗
Defendant counselLance E. Wyatt , Jr.AttorneyCounsel for Zendesk, Inc.Search in Eureka ↗
Defendant counselNeil J. McNabnayAttorneyCounsel for Zendesk, Inc.Search in Eureka ↗
Defendant law firmFish & Richardson PCLaw FirmRepresenting Zendesk, Inc.Search in Eureka ↗
Presiding judgeJudge Jennifer L. HallJudgeDelaware District CourtSearch in Eureka ↗
Official verdict

Official order — verbatim text

“Pursuant to Federal Rule of Civil Procedure 41(a)(1)(A)(ii), the parties hereby stipulate to dismiss all claims against ZENDESK, INC. WITH PREJUDICE and all counterclaims against WEBSOCK GLOBAL STRATEGIES LLC WITHOUT PREJUDICE. Each party shall bear its own costs, expenses, and attorneys’ fees.”
Source: PACER Docket, Case 1:24-cv-01003, Delaware District Court

The stipulation’s phrasing is precise and commercially significant. Dismissal of plaintiff’s claims ‘with prejudice’ under Rule 41(a)(1)(A)(ii) has the legal effect of a final judgment on the merits — WebSock is permanently barred from re-asserting these specific infringement claims against Zendesk. The separate treatment of Zendesk’s counterclaims, dismissed ‘without prejudice,’ preserves Zendesk’s invalidity and non-infringement positions for future use. The mutual cost-bearing clause eliminates any inference of a clear winner, pointing instead to a negotiated commercial resolution.

PACER case 1:24-cv-01003 · Public docket record Explore in Eureka ↗
Patent at issue

US7756983B2 — Symmetrical Bi-Directional Web Communication

Publication No.US7756983B2
Application No.US12/109198
Patent details
ProductSymmetrical bi-directional real-time web communication protocols
Cited in actionAugust 30, 2024

US7756983B2, filed under application number US12/109198, covers symmetrical bi-directional communication — the foundational technology enabling persistent, full-duplex connections between web clients and servers, commonly implemented as WebSocket protocol. The B2 grant designation confirms the patent issued after examination and likely amendment. This class of technology underpins real-time features across SaaS platforms: live chat, push notifications, collaborative editing, and customer support messaging infrastructure.

From a competitive intelligence standpoint, US7756983B2 sits at the intersection of foundational web infrastructure and high-value SaaS product features. Any platform offering real-time user-facing communication — customer support tools, collaboration software, live commerce, IoT dashboards — potentially falls within the assertion scope. The fact that WebSock targeted Zendesk, whose entire product suite depends on real-time agent-customer interaction, signals that the patent holder views enterprise SaaS as its primary enforcement market. Competitors in this space should treat this patent as an active enforcement risk.

Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Freedom to operate

Should your product team run an FTO against US7756983B2?

Any company building or acquiring products that rely on persistent, full-duplex web connections — WebSocket-based chat, real-time notifications, live support widgets, or collaborative SaaS tools — should treat US7756983B2 as a material FTO risk. The fact that WebSock successfully extracted a with-prejudice settlement from Zendesk in under 40 days demonstrates that the patent carries practical enforcement leverage. R&D teams integrating WebSocket or similar bi-directional communication layers should document design-arounds and review whether their architecture falls within the asserted claims.

PatSnap Eureka’s FTO Search Agent can map US7756983B2’s independent claims against your product architecture, surface relevant prior art that could support an IPR petition, and benchmark WebSock’s assertion history across the patent litigation database. For in-house IP teams at SaaS companies with real-time communication features, running a targeted FTO now — before receiving a demand letter — is materially cheaper than litigation entry. Eureka’s claim-charting tools and prosecution history analysis modules provide the fastest path to a defensible clearance opinion.

PatSnap Eureka FTO Search

Run a freedom-to-operate analysis on US7756983B2 to assess your product’s exposure

Run FTO in Eureka →
Related litigation

Similar WebSocket and bi-directional communication patent cases

Comparable patent infringement actions asserting real-time bi-directional communication IP in Delaware District Court and related federal venues.

🔍
Access 40+ similar cases in PatSnap Eureka
WebSock Global Strategies, LLC patent enforcement history, Delaware case history, WebSock Global Strategies, LLC’s full IP portfolio, and comparable case analysis
WebSocket patent casesDelaware PAE actionsReal-time comms IP disputesSaaS platform infringement suits
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the real-time communication IP landscape

A 34-day exit with asymmetric prejudice terms is rarely accidental — it points to deliberate IP monetisation strategy around WebSocket infrastructure.

Speed of resolution suggests a licensing play, not litigation on the merits

Cases that settle in under 40 days — before any motion practice — typically reflect a licensing demand served alongside or shortly after the complaint. WebSock’s entity name and single-patent assertion pattern are consistent with a patent monetisation strategy targeting real-time communication infrastructure. Zendesk’s quick resolution likely reflects a cost-benefit calculus favouring a licence over protracted litigation.

Asymmetric prejudice terms are a hallmark of structured licensing exits

The with-prejudice/without-prejudice split — plaintiff’s claims gone permanently, defendant’s counterclaims preserved — is a deliberate drafting choice. It signals Zendesk negotiated protective optionality: if the licence terms are breached or if WebSock pursues further action, Zendesk retains the ability to challenge the patent’s validity through its preserved counterclaims or a fresh IPR petition.

🔒
Full strategic analysis in PatSnap Eureka
Unlock gated analysis on WebSocket patent assertion strategy and Delaware District Court enforcement trends for real-time communication IP.
Prosecution history flagsIPR vulnerability scoreSerial assertion risk
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

WebSock v Zendesk — key questions answered

Still have questions? PatSnap Eureka can answer them instantly from patent and litigation data. Ask Eureka ↗
PatSnap Eureka

Monitor WebSocket patent enforcement before the next demand letter arrives

US7756983B2 is active and its holder has demonstrated willingness to litigate. Run a targeted FTO and set up portfolio monitoring in PatSnap Eureka to stay ahead of assertion risk across your real-time communication product stack.

Ask anything about this case.
PatSnap Eureka searches patents and litigation data to answer instantly.
Powered by PatSnap Eureka
Link copied to clipboard

Related Litigation Cases

Help us improve this page

Found incorrect or outdated information? Let us know and we'll get it fixed.