Invalidity dossier

US 12438978

Systems and methods for resuming online abandoned journeys

Current assignee: IQX Corp

Added 9/25/2026, 12:00:19 AM

At a glanceActive PTAB challengeNo litigation on fileSoftware Technology & Computing Systems (T)

Active provider: DeepSeek · deepseek-v4-flash

Auto-generating section 1 of 7: Litigation summary…

Each section takes ~30-60s with web-search grounding. Keep this tab open — sections will fill in below as they complete.

Patent summary

Title, assignee, inventors, filing/issue dates, abstract, and a plain-language overview of the claims.

✓ Generated

I'll search for this specific patent number across sources, including USPTO and CAFC 2026 docket references.

Let me verify with additional targeted searches, including CAFC docket and any litigation references.

Found litigation references. Let me investigate the IQX Corp. enforcement activity and confirm which patents are at issue.

US Patent 12,438,978 — Summary

Bibliographic Data (as verified)

Field Value
Patent number US 12,438,978 B2
Title "Systems and methods for resuming online abandoned journeys"
Inventors Sacha Spindler; Aidan Wright
Assignee IQX Corp (original assignee also IQX Corp.)
Application number US 19/192,732
Filing date 2025-04-29
Issue/grant date 2025-10-07
Pre-grant publication US 2025/0274544 A1 (published 2025-08-28)
Earliest priority date 2018-09-27 (US provisional 62/737,315)
Anticipated expiration 2039-09-25
Status Active
Primary classifications H04M 1/72403, H04M 1/7243, H04M 1/72436, H04M 1/72445; H04W 12/06, H04W 4/12, H04W 4/14, H04W 4/20

Continuity (per the front matter): This patent is a continuation of Ser. No. 18/984,041 (filed Dec. 17, 2024), itself a continuation of Ser. No. 18/896,197 (filed Sep. 25, 2024), which is a continuation-in-part of Ser. No. 18/483,670 (filed Oct. 10, 2023), a continuation of Ser. No. 18/193,163 (filed Mar. 30, 2023), a continuation of Ser. No. 17/279,188 (filed Mar. 24, 2021; U.S. National Stage of PCT/US19/52847, filed Sep. 25, 2019), claiming benefit of provisional 62/737,315 (Sep. 27, 2018). The Google Patents timeline also lists a later family member, application 19/324,477 → US 2026/0012531 A1 (dated 2025-09-10).

Sources: https://patents.google.com/patent/US12438978/en ; corroborating family/description pages for the pre-grant publication at https://patents.justia.com/patent/20250274544 and https://www.patents-review.com/a/20250274544-systems-methods-resuming-online-abandoned-journeys.html ; assignee/portfolio listing at https://www.ipqwery.com/ipowner/en/owner/ip/[2495953](/patent/2495953)-iqx-corp.html


Abstract (verbatim, as published)

"Systems and methods are described for receiving a request to provide content to at least one authorized recipient; generating a customized message comprising at least one action associated with the content; causing transmission of the customized message to a mobile computing device associated with the at least one authorized recipient, requesting authorization data corresponding to the at least one authorized recipient; responsive to receiving the requested authorization data: verifying that the authorization data correlates to an identity of the at least one authorized recipient or an identity of the mobile computing device; determining a classification of the at least one authorized recipient; and generating a Rich Communication Service (RCS) message comprising the content; and scheduling, using a machine learning model and based on the determined classification, delivery of the RCS message to the mobile computing device."

Note the label/reality mismatch worth flagging: the title emphasizes resuming online abandoned journeys, but the abstract and independent claims are drafted more broadly around RCS messaging, silent-network authentication, and ML-based send-time/classification. The abandonment-resumption subject matter is carried mainly in the specification (Figs. 15–18) and in dependent claims.


Plain-Language Overview of the Independent Claims

The patent recites three independent claims — a method claim, a system claim, and a computer-readable storage medium claim. All three share the same core workflow; the differences are in claim type and in the vocabulary used for the end user ("authorized recipient," "service subscriber," or "authorized recipient or subscriber") and for the actionable element ("action" in the method/system claims vs. "link" in the medium claim).

Independent Claim 1 — Computer-implemented method (core workflow):

  1. Receive a request to provide content to at least one authorized recipient.
  2. Generate a customized message that includes at least one action associated with that content (e.g., a link/button).
  3. Transmit the customized message to a mobile computing device belonging to the authorized recipient.
  4. After the user selects the action, the system requests authorization data for that recipient.
  5. If authorization data is received, the system (a) verifies that the data correlates to the recipient's identity or the mobile device's identity, (b) determines a classification of the recipient based on that identity, and (c) generates an RCS message containing the content.
  6. Schedules delivery of the RCS message using a machine learning model and based on the determined classification.

In plain terms: a marketing/transaction message with a clickable action is sent by text; the click triggers an identity check; the verified user is sorted into a tier; and an AI model decides when to push the follow-up rich (RCS) message to that tier.

Independent System Claim — "Automated messaging subscription and distribution system":
A processor + memory system performing the same steps, but reciting "service subscriber" instead of "authorized recipient," requesting "subscription data" upon action selection, and generating the RCS message "based on the determined classification."

Independent Storage-Medium Claim:
A non-transitory computer-readable medium storing instructions to perform the same steps, but with "at least one link associated with the content" (rather than "action") and with the user termed "authorized recipient or subscriber."

Dependent claims add (summarized):

  • Actually delivering the RCS message per the schedule.
  • Content as a carousel of selectable options — perform a secure transaction, schedule an appointment, or resume an abandoned user journey.
  • Content rendered within a browser on the mobile device.
  • Send/receive (real-time typing) indicators in the mobile UI.
  • Sender verification of the RCS message, with an SMS warning delivered if the sender is not authorized.
  • Actions offering: perform a transaction, select a suggested response, return to a prior browsing session, or return to a prior application session.

Specification Highlights Supporting the Claims

  • Architecture: an Automated Messaging Distribution Array (AMDA) with an ML/AI decision cluster (1000a) and an AMDA subscriber vault (1000b) that sorts recipients into tier 1 buyers, tier 2 link clickers, and tier 3 bulk-send recipients, routed to a just-in-time messaging array (1000c) or bulk array (1000d) and an automated scheduler/distribution hub (1000e) supporting SMS/MMS, RCS, and OTT channels.
  • Security: a Silent Network Authentication Protocol (SNAP) layer (1100) that silently verifies network/device credentials (SIM/carrier identifiers) plus optional biometric authentication; a "hot cookie" bound to the mobile device gates access to the customized page and transaction flow.
  • Abandonment taxonomy (Figs. 15–16): session, browser, search, form, onboarding/signup, wish list, checkout, and cart abandonment; each type is recorded and the ML/AI cluster selects a follow-on message/link that returns the user to the abandoned access point.

Litigation / Docket Findings


Confidence and Uncertainty Notes

  • High confidence: patent number, title, inventors, assignee, application number, filing date, issue date, priority chain, abstract text, and the substance of the independent claims — all from the patent's own front matter and specification as published.
  • Medium confidence: the precise number of claims and the exact claim numbering of the independent claims. The text available to me reproduces the claim language in the Summary sections but does not show a numbered claim set, so I have described the three independent claims by type rather than by claim number.
  • Uncertainty — no correction made, per instruction: the application serial is presented as "US19/192,732" and the follow-on family member as "US19/324,477." These are reported literally.
  • Uncertainty: Whether US 12,438,978 is asserted in the IQX v. Intuit litigation. The publicly indexed complaint analysis references the '799 and '924 patents; I could not confirm '978's inclusion.
  • Not found/not verified: any CAFC (Federal Circuit) 2026 appellate docket, PTAB/IPR proceeding, or USPTO PatentCenter record specifically for 12,438,978 beyond the Google Patents and family sources cited. I did not independently retrieve the USPTO PatentCenter "Bibliographic Data" page for this patent, so the grant date and status are as reported by Google Patents rather than directly confirmed at USPTO.

Generated 9/25/2026, 12:01:36 AM

Cases on file (0)

Specific litigation cases in our database that name US patent 12438978. The free-form analysis below may also discuss cases beyond this list.

No cases on file mention this patent. Upload a CSV or add a case manually in Admin → Manage litigation cases.

Litigation summary

Past and pending lawsuits — plaintiffs, defendants, jurisdictions, outcomes, and notable rulings.

Not generated yet. Click Generate to call the active LLM provider with the configured prompt.

Proceedings on file (1)

All PTAB activity →

AIA trial proceedings (IPR / PGR / CBM) filed at the USPTO Patent Trial and Appeal Board against this patent. Sourced from the USPTO Open Data Portal and refreshed every six hours; each proceeding number deep-links to the PTAB E2E docket.

1 active
Pending
Filed
Sep 24, 2026
Last modified
Sep 24, 2026
Petitioner
Salesforce, Inc.
Inventor
Sacha Spindler et al

PTAB challenges

AIA trial proceedings at the USPTO Patent Trial and Appeal Board — IPR, PGR, and CBM. Petitioners, judge panels, claim-level invalidation outcomes from Final Written Decisions, and Federal Circuit appeals. The single most important defensive datapoint after litigation history.

Not generated yet. Click Generate to call the active LLM provider with the configured prompt.

Assignment history

Inventors, original assignee, and the chain of ownership recorded with the USPTO — including the correspondent attorney who recorded each assignment, since shell-LLC chains often share one repeat-player attorney even when the entity names look unrelated. Surfaces NPE / patent-troll patterns: shell-entity transfers, known asserters in the chain, repeat correspondent fingerprints, pre-litigation assignments, and bankruptcy fire-sales.

Not generated yet. Click Generate to call the active LLM provider with the configured prompt.

Prior art

Earlier patents, publications, and products that may anticipate or render the claims unpatentable.

Not generated yet. Click Generate to call the active LLM provider with the configured prompt.

Obviousness

Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.

Not generated yet. Click Generate to call the active LLM provider with the configured prompt.

Extensions

Patent term adjustments, term extensions, continuations, divisionals, family members, and expiration dates.

Not generated yet. Click Generate to call the active LLM provider with the configured prompt.

Derivative works

Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.

Not generated yet. Click Generate to call the active LLM provider with the configured prompt.

Keep exploring

Other patents in Software Technology & Computing Systems (T)

See all Software Technology & Computing Systems (T) patents →