IP Library Granted Patent US 12,273,310
Granted Patent B2
US 12,273,310 · App. 17/677,915 · Granted Apr 8, 2025

Systems and methods for intelligent delivery of communications

Inventors: Dennis Reil (Großheide, DE); Frank Steffen (Hamburg, DE); Martin Richter (Edewecht, DE)
Assignee: OPEN TEXT HOLDINGS, INC.
H04L51/212G06N20/00G06Q30/0281H04L51/234
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,273,310
App. No.
17/677,915
Granted
Apr 8, 2025
Kind
B2
Abstract

Systems, methods and products for intelligent delivery of communications, where a machine learning engine is trained to identify an output channel for delivery of a communication based on received context information and intended recipient information and to route the communication to the selected channel. An intelligent delivery task in a communication flow model is performed by the machine learning engine, which receives customer/recipient data such as age, region, gender, etc., and context data such as communication type, time of day, working hours, etc., and uses this data to determine which of a set of different channels is likely to be most effecting for sending the communication to the recipient. A user therefore does not have to build a complex static communication flow, but simply adds an intelligent delivery task to the flow. The output channel is dynamically selected and may vary for different recipients and communications.

Claims (76)

1. An intelligent delivery system comprising:

an intelligent delivery server configured to execute a self-learning machine learning engine which is trained to identify one of a plurality of output connectors for delivery of a communication based on received context information, intended recipient information, and previously collected event information indicating a delivery of a previous communication, wherein the plurality of output connectors are coupled to the intelligent delivery server;

one or more input connectors coupled to the intelligent delivery server, wherein the one or more input connectors coupled to the intelligent delivery server receive input data for the communication, wherein the received input data comprises:

intended recipient information; and

context information;

a flow model configured to:

access stored information of the previously collected event information based on the received input data;

generate a communication flow for a communication using the received input data, wherein a type of communication is determined by the received input data;

wherein the flow model is further configured to:

receive, in real-time, user input modifying the flow model during execution of the flow model, and in response to the real-time user input, dynamically modify the communication flow during execution of the flow model;

wherein the intelligent delivery server selects a different one of the plurality of output connectors for delivery of the communication based on the type of communication, context information associated with the communication, and the real-time user input modifying the flow model; and

route, by the intelligent delivery server the communication to the selected different one of the plurality of output connector for delivery of the communication.

2. The system of claim 1 , further comprising:

an event collector coupled to the plurality of output connectors and configured to collect event information associated with delivery of the communication by the selected one of the output connectors;

an event database coupled to the event collector and configured to store event information collected by the event collector.

3. The system of claim 2 , further comprising a delivery tracker configured to receive event information from the event database, the delivery tracker configured to track delivery of the communication via the selected one of the output connectors, the delivery tracker further configured to provide delivery information to the machine learning engine.

4. The system of claim 3 , wherein the machine learning engine is configured to receive delivery information from the delivery tracker, the machine learning engine configured to self-learn based on the received delivery information and to thereby adapt the training of the machine learning engine to identify output connectors for delivery of communications.

5. The system of claim 1 , wherein the intelligent delivery system is implemented in a customer communications management system, the communications management system comprising:

an input queue configured to store data for generation of communications for delivery to corresponding recipients;

an orchestration server coupled to receive communications from the input queue; and

wherein the flow model is for processing of the communication, the flow model executed by the orchestration server;

wherein the intelligent delivery server machine is coupled to the orchestration server and configured to perform an intelligent delivery task of the flow model.

6. The system of claim 1 , wherein the communication comprises a common communication directed to two different recipients, wherein intelligent delivery server selects different ones of the output connectors for delivery of the common communication based on differences in recipient information associated with the different recipients.

7. The system of claim 1 , wherein the communication is one of two or more communications directed to a single recipient, wherein the intelligent delivery server selects different ones of the plurality of output connectors for delivery of the two or more communications based on differences in context information associated with the two or more communications.

8. A method for intelligent delivery of communications, the method comprising:

executing a self-learning machine learning engine on an intelligent delivery server, the machine learning engine trained to identify one of a plurality of output connectors for delivery of a communication based on received context information, intended recipient information, and previously collected event information indicating a delivery of a previous communication, wherein the plurality of output connectors are coupled to the intelligent delivery server;

receiving, by the intelligent delivery server via one or more input connectors coupled to the intelligent delivery server, wherein the one or more input connectors coupled to the intelligent delivery server receives input data for the communication flow, wherein the received input data comprising;

the context information; and

intended recipient information; and

accessing, by a flow model, stored information of the previously collected event information based on the received input data;

generating, by the flow model, the communication flow using the received input data, wherein a type of communication is determined by the received input data;

receiving, in real-time, user input modifying the flow model during execution of the flow model, and in response to the real-time user input, dynamically modifying the communication flow by the flow model during execution of the flow model;

selecting, by the intelligent delivery server, a different one of the plurality of output connectors for delivery of the communication based on the type of communication, context information associated with the communication, and the real-time user input modifying the flow model;

routing, by the intelligent delivery server, the communication to the selected different one of the plurality of output connector for delivery of the communication.

9. The method of claim 8 , further comprising:

collecting, by an event collector coupled to the plurality of output connectors, event information associated with delivery of the communication by the selected one of the output connectors;

storing, in an event database coupled to the event collector, the event information collected by the event collector;

receiving, by a delivery tracker, the event information from the event database;

tracking, by the delivery tracker, delivery of the communication via the selected one of the output connectors; and

providing, by the delivery tracker, delivery information to the machine learning engine;

receiving, by the machine learning engine, the delivery information from the delivery tracker; and

self-learning, by the machine learning engine, based on the received delivery information and thereby adapting the training of the machine learning engine to identify output connectors for delivery of communications.

10. The method of claim 8 , implementing the intelligent delivery system in a customer communications management system, including:

storing, by an input queue, communications for delivery to corresponding recipients;

receiving, by an orchestration server, communications from the input queue; and

executing, by the orchestration server, a flow model for processing of the communication;

performing, by the intelligent delivery server machine which is coupled to the orchestration server, an intelligent delivery task of the flow model.

11. The method of claim 8 , wherein the communication comprises a common communication directed to two different recipients, the method further comprising selecting, by the intelligent delivery server different ones of the output connectors for delivery of the common communication based on differences in recipient information associated with the different recipients.

12. The method of claim 8 , wherein the communication is one of two or more communications directed to a single recipient, the method further comprising selecting, by the intelligent delivery server, different ones of the plurality of output connectors for delivery of the two or more communications based on differences in context information associated with the two or more communications.

13. A computer programming product for communication management and delivery, comprising:

a non-transitory storage medium comprising computer instructions that when loaded into a memory of a processor, the processor performing:

executing a self-learning machine learning engine on an intelligent delivery server, the machine learning engine trained to identify one of a plurality of output connectors for delivery of a communication based on received context information, intended recipient information, and previously collected event information indicating a delivery of a previous communication, wherein the plurality of output connectors are coupled to the intelligent delivery server;

receiving, by the intelligent delivery server via one or more input connectors coupled to the intelligent delivery server, wherein the one or more input connectors coupled to the intelligent delivery server receives input data for the communication flow, wherein the received input data comprising;

the context information; and

intended recipient information; and

accessing, by a flow model, stored information of the previously collected event information based on the received input data;

generating, by the flow model, the communication flow using the received input data, wherein a type of communication is determined by the received input data;

receiving, in real-time, user input modifying the flow model during execution of the flow model, and in response to the real-time user input, dynamically modifying the communication flow by the flow model during execution of the flow model;

selecting, by the intelligent delivery server, a different one of the plurality of output connectors for delivery of the communication based on the type of communication, context information associated with the communication, and the real-time user input modifying the flow model;

routing, by the intelligent delivery server, the communication to the selected different one of the plurality of output connector for delivery of the communication.

14. The computer program product of claim 13 , the processor further performing:

collecting, by an event collector coupled to the plurality of output connectors, event information associated with delivery of the communication by the selected one of the output connectors;

storing, in an event database coupled to the event collector, the event information collected by the event collector;

receiving, by a delivery tracker, the event information from the event database,

tracking, by the delivery tracker, delivery of the communication via the selected one of the output connectors;

providing, by the delivery tracker, delivery information to the machine learning engine;

receiving, by the machine learning engine, the delivery information from the delivery tracker; and

self-learning, by the machine learning engine, based on the received delivery information and thereby adapting the training of the machine learning engine to identify output connectors for delivery of communications.

15. The computer program product of claim 13 , the processor further performing:

implementing the intelligent delivery system in a customer communications management system, including:

storing, by an input queue, communications for delivery to corresponding recipients;

receiving, by an orchestration server, communications from the input queue; and

executing, by the orchestration server, a flow model for processing of the communication; and

performing, by the intelligent delivery server machine which is coupled to the orchestration server, an intelligent delivery task of the flow model.

16. The computer program product of claim 13 , wherein the communication comprises a common communication directed to two different recipients, the processor further performing selecting, by the intelligent delivery server different ones of the output connectors for delivery of the common communication based on differences in recipient information associated with the different recipients.

17. The computer program product of claim 13 , wherein the communication is one of two or more communications directed to a single recipient, the processor further performing selecting, by the intelligent delivery server, different ones of the plurality of output connectors for delivery of the two or more communications based on differences in context information associated with the two or more communications.

Assignments (2)
MERGER Recorded Jun 23, 2026
From: OPEN TEXT HOLDINGS, INC.
To: OPEN TEXT INC.
Reel/Frame 075054/0766 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 31, 2022
From: REIL, DENNIS; STEFFEN, FRANK; RICHTER, MARTIN
To: OPEN TEXT HOLDINGS, INC.
Reel/Frame 059455/0504 →
Continuity (1)
Related Publication 20230269210A1 · Aug 24, 2023
References Cited (199)
US 5181162A · Smith · 1993 [cited by applicant]
US 5299304A · Williams et al. · 1994 [cited by applicant]
US 5524250A · Chesson · 1996 [cited by applicant]
US 5713014A · Durflinger et al. · 1998 [cited by applicant]
US 5911776A · Guck · 1999 [cited by applicant]
US 5970490A · Morgenstern · 1999 [cited by applicant]
US 5995996A · Venable · 1999 [cited by applicant]
US 6012098A · Bayeh et al. · 2000 [cited by applicant]
US 6151608A · Abrams · 2000 [cited by applicant]
US 6172988B1 · Tiernan et al. · 2001 [cited by applicant]
US 6236997B1 · Bodamer et al. · 2001 [cited by applicant]
US 6243107B1 · Valtin et al. · 2001 [cited by applicant]
US 6263332B1 · Nasr et al. · 2001 [cited by applicant]
US 6275536B1 · Chen et al. · 2001 [cited by applicant]
US 6324568B1 · Diec · 2001 [cited by applicant]
US 6336124B1 · Alam et al. · 2002 [cited by applicant]
US 6336139B1 · Feridun et al. · 2002 [cited by applicant]
US 6338074B1 · Poindexter · 2002 [cited by applicant]
US 6397232B1 · Cheng-Hung et al. · 2002 [cited by applicant]
US 6484178B1 · Bence, Jr. et al. · 2002 [cited by applicant]
US 6587972B1 · Baird et al. · 2003 [cited by applicant]
US 6623529B1 · Lakritz · 2003 [cited by applicant]
US 6643701B1 · Aziz · 2003 [cited by applicant]
US 6668254B2 · Matson et al. · 2003 [cited by applicant]
US 6748020B1 · Eifrig et al. · 2004 [cited by applicant]
US 6782379B2 · Lee · 2004 [cited by applicant]
US 6810429B1 · Walsh et al. · 2004 [cited by applicant]
US 6816871B2 · Lee · 2004 [cited by applicant]
US 6877156B2 · Osborne et al. · 2005 [cited by applicant]
US 7043687B2 · Knauss et al. · 2006 [cited by applicant]
US 7054952B1 · Schwerdtfeger et al. · 2006 [cited by applicant]
US 7055096B2 · Namioka · 2006 [cited by applicant]
US 7127520B2 · Ladd et al. · 2006 [cited by applicant]
US 7143087B2 · Fairweather · 2006 [cited by applicant]
US 7213249B2 · Loo et al. · 2007 [cited by applicant]
US 7216163B2 · Sinn · 2007 [cited by applicant]
US 7225256B2 · Villavicencio · 2007 [cited by applicant]
US 7257600B2 · Matson et al. · 2007 [cited by applicant]
US 7284235B2 · Nachmanson et al. · 2007 [cited by applicant]
US 7302678B2 · Bohlmann et al. · 2007 [cited by applicant]
US 7308399B2 · Fallen-Bailey et al. · 2007 [cited by applicant]
US 7461403B1 · Libenzi et al. · 2008 [cited by applicant]
US 7478402B2 · Christensen et al. · 2009 [cited by applicant]
US 8380830B2 · Ladd et al. · 2013 [cited by applicant]
US 8788699B2 · Kitagata · 2014 [cited by applicant]
US 8825627B1 · Indukuri · 2014 [cited by applicant]
US 8914809B1 · Cohen · 2014 [cited by applicant]
US 9047146B2 · Ladd et al. · 2015 [cited by applicant]
US 9237120B2 · Cohen · 2016 [cited by applicant]
US 9400703B2 · Ladd et al. · 2016 [cited by applicant]
US 10210028B2 · Ladd · 2019 [cited by applicant]
US 10496458B2 · Ladd et al. · 2019 [cited by applicant]
US 10534843B2 · Smith et al. · 2020 [cited by applicant]
US 10606921B2 · Lorensson · 2020 [cited by applicant]
US 10846739B1 · Hahn · 2020 [cited by applicant]
US 10904102B2 · Smith · 2021 [cited by applicant]
US 10922158B2 · Ladd · 2021 [cited by applicant]
US 11106856B2 · Lorensson · 2021 [cited by applicant]
US 11263383B2 · Smith · 2022 [cited by applicant]
US 11360833B2 · Ladd · 2022 [cited by applicant]
US 11362908B2 · Smith · 2022 [cited by applicant]
US 11398218B1 · Haslam · 2022 [cited by applicant]
US 11481537B2 · Smith · 2022 [cited by applicant]
US 11586800B2 · Lorensson · 2023 [cited by applicant]
US 11699020B2 · Smith · 2023 [cited by applicant]
US 11811617B2 · Smith · 2023 [cited by applicant]
US 11829702B2 · Lorensson · 2023 [cited by applicant]
US 11888793B2 · Reil · 2024 [cited by applicant]
US 12099794B2 · Lorensson · 2024 [cited by applicant]
US 12204843B2 · Smith · 2025 [cited by applicant]
US 12229490B2 · Smith · 2025 [cited by applicant]
US 20010047369A1 · Aizikowitz et al. · 2001 [cited by applicant]
US 20010056362A1 · Hanagan et al. · 2001 [cited by applicant]
US 20020059076A1 · Grainger · 2002 [cited by applicant]
US 20020065848A1 · Walker · 2002 [cited by applicant]
US 20020083124A1 · Knox · 2002 [cited by applicant]
US 20020083205A1 · Leon et al. · 2002 [cited by applicant]
US 20020165975A1 · Abbott · 2002 [cited by applicant]
US 20030023336A1 · Kreidler et al. · 2003 [cited by applicant]
US 20030065623A1 · Corneil et al. · 2003 [cited by applicant]
US 20030085902A1 · Vogelaar et al. · 2003 [cited by applicant]
US 20030192036A1 · Karkare · 2003 [cited by applicant]
US 20030204429A1 · Botscheck · 2003 [cited by applicant]
US 20040056787A1 · Henry · 2004 [cited by applicant]
US 20040133635A1 · Spriestersbach · 2004 [cited by applicant]
US 20040143738A1 · Savage · 2004 [cited by applicant]
US 20050071150A1 · Nasypny · 2005 [cited by applicant]
US 20050160086A1 · Haraguchi et al. · 2005 [cited by applicant]
US 20050209990A1 · Ordille · 2005 [cited by applicant]
US 20050240876A1 · Myers et al. · 2005 [cited by applicant]
US 20060064467A1 · Libby · 2006 [cited by applicant]
US 20060095511A1 · Munarriz et al. · 2006 [cited by applicant]
US 20060233108A1 · Krishnan · 2006 [cited by applicant]
US 20060271390A1 · Rich · 2006 [cited by applicant]
US 20070083425A1 · Cousineau · 2007 [cited by applicant]
US 20070201654A1 · Shenfield · 2007 [cited by applicant]
US 20070204058A1 · Ladd et al. · 2007 [cited by applicant]
US 20070233555A1 · Fourrage · 2007 [cited by applicant]
US 20070283364A1 · Deininger · 2007 [cited by applicant]
US 20080319813A1 · du Preez · 2008 [cited by applicant]
US 20090064175A1 · Taylor et al. · 2009 [cited by applicant]
US 20090150501A1 · Davis · 2009 [cited by examiner]
US 20090150507A1 · Davis · 2009 [cited by examiner]
US 20090254572A1 · Redlich · 2009 [cited by applicant]
US 20100023642A1 · Ladd et al. · 2010 [cited by applicant]
US 20100325102A1 · Maze · 2010 [cited by applicant]
US 20110296048A1 · Knox · 2011 [cited by applicant]
US 20120191546A1 · Phelan · 2012 [cited by applicant]
US 20130081132A1 · Lee · 2013 [cited by applicant]
US 20130086188A1 · Mays · 2013 [cited by examiner]
US 20130275528A1 · Miner · 2013 [cited by applicant]
US 20150193808A1 · Wade · 2015 [cited by applicant]
US 20160012465A1 · Sharp · 2016 [cited by applicant]
US 20160070815A1 · Carlsson · 2016 [cited by applicant]
US 20160232143A1 · Fickenscher et al. · 2016 [cited by applicant]
US 20160162478A1 · Blassin · 2016 [cited by applicant]
US 20160253841A1 · Ur et al. · 2016 [cited by applicant]
US 20160255076A1 · Lee · 2016 [cited by applicant]
US 20170148227A1 · Alsaffar · 2017 [cited by applicant]
US 20170257486A1 · Smith · 2017 [cited by applicant]
US 20170323349A1 · Blaylock · 2017 [cited by applicant]
US 20170344526A1 · Smith · 2017 [cited by applicant]
US 20170344547A1 · Smith · 2017 [cited by applicant]
US 20170346828A1 · Lorensson · 2017 [cited by applicant]
US 20190121684A1 · Ladd et al. · 2019 [cited by applicant]
US 20200014604A1 · Smith · 2020 [cited by examiner]
US 20200117849A1 · Smith · 2020 [cited by applicant]
US 20200193082A1 · Lorensson · 2020 [cited by applicant]
US 20210365626A1 · Lorensson · 2021 [cited by applicant]
US 20220086118A1 · Jain · 2022 [cited by examiner]
US 20220164519A1 · Smith · 2022 [cited by applicant]
US 20230024774A1 · Smith · 2023 [cited by applicant]
US 20230195996A1 · Lorensson · 2023 [cited by applicant]
US 20230269206A1 · Reil · 2023 [cited by applicant]
US 20230297760A1 · Smith · 2023 [cited by applicant]
US 20240037317A1 · Lorensson · 2024 [cited by applicant]
US 20240039800A1 · Smith · 2024 [cited by applicant]
US 20240106774A1 · Reil · 2024 [cited by applicant]
WO WO200109752A2 · 2001 [cited by applicant]
WO WO2006041340 · 2006 [cited by applicant]
Office Action for U.S. Appl. No. 10/184,430, mailed Sep. 21, 2005, 12 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 11/583,369, mailed Apr. 3, 2009, 8 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 12/573,352, mailed Sep. 13, 2010, 9 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 13/092,771, mailed Jul. 20, 2011, 12 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 13/092,771, mailed Jan. 4, 2012, 13 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 13/745,096, mailed Sep. 30, 2013, 10 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 13/454,492, mailed Nov. 26, 2013, 18 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 13/745,096, mailed Jan. 15, 2014, 15 pages. [cited by applicant]
Office Action for U.S. Appl. No. 13/745,096, mailed Jul. 25, 2014, 16 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 14/638,700, mailed Mar. 26, 2015, 14 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 14/638,700, mailed Oct. 6, 2015, 13 pages. [cited by applicant]
Office Action for U.S. Appl. No. 15/174,591, mailed Feb. 3, 2017, 22 pages. [cited by applicant]
Office Action for U.S. Appl. No. 15/174,591, mailed Jul. 21, 2017, 19 pages. [cited by applicant]
Müldner, Tomasz, Robin McNeill and Jan Krzysztof Miziołek in “Secure Publishing using Schema-level Role-based Access Control Policies for Fragments of XML Documents.” Presented at Balisage: The Markup Conference 2008, M… [cited by applicant]
Office Action for U.S. Appl. No. 15/607,091, mailed Mar. 19, 2018, 8 pages. [cited by applicant]
Office Action for U.S. Appl. No. 15/607,091, mailed Nov. 28, 2018, 8 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 15/607,111, mailed Jan. 30, 2019, 55 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 15/607,036, mailed Apr. 17, 2019, 7 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 15/607,111, mailed Jul. 12, 2019, 62 pgs. [cited by applicant]
Sihem Amer-Yahia et al., A Web-Services Architecture for Efficient XML Data Exchange, 2004, Proceedings of the 20th Int'l Conf. on Data Engineering (ICDE'04), pp. 1-12. [cited by applicant]
Office Action for U.S. Appl. No. 15/607,091, mailed Sep. 17, 2019, 8 pgs. [cited by applicant]
Nord, et al., “Reviewing Architecture Documents Using Question Sets,” 2009 Joint Working IEEE/IFIP Conference on Sofrware Architecture & European Conference on Software Architecture, Sep. 2009, pp. 1-4. [cited by applicant]
Office Action for U.S. Appl. No. 15/607,091, mailed Feb. 19, 2020, 9 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 15/607,091, mailed Mar. 15, 2021, 9 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 16/708,069, mailed Jun. 14, 2021, 7 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 15/607,091, mailed Sep. 24, 2021, 9 pgs. [cited by applicant]
Thomas-Kerr, J., Burnett, I., and Ritz, C., “Format-Independent Rich Media Delivery Using the Bitstream Binding Language,” IEEE Transactions on Multimedia, vol. 10, No. 3, Apr. 2008, pp. 514-522. [cited by applicant]
Office Action for U.S. Appl. No. 17/139,759, mailed Oct. 15, 2021, 22 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 15/607,091, mailed Mar. 2, 2022, 9 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 15/607,091, mailed Jun. 14, 2022, 4 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 17/666,876, mailed Oct. 31, 2022, 6 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 17/393,270, mailed Oct. 13, 2022, 15 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 17/677,917, mailed Jan. 31, 2023, 8 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 17/666,876, mailed Feb. 23, 2023, 2 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 17/944,754 issued by the U.S. Patent and Trademark Office, mailed Jun. 23, 2023, 15 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 18/168,444, mailed Jul. 27, 2023, 12 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 17/677,917 mailed Aug. 2, 2023, 5 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 18/168,444, mailed Sep. 25, 2023, 10 pgs. [cited by applicant]
International Search Report and Written Opinion for International Patent Application No. PCT/IB2019/055367, mailed Oct. 28, 2019, 10 pgs. [cited by applicant]
Al-Fedaghi, S. et al., “Conceptual Model for Communication”, International Journal of Computer Science and Information Security, vol. 6, No. 2, 2009, 13 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 16/451,309, mailed Jun. 19, 2020, 11 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 17/147,314, mailed Sep. 21, 2021, 13 pgs. [cited by applicant]
International Preliminary Report on Patentability (IPRP) issued for International Application No. PCT/IB2019/055367, mailed Jan. 5, 2021, 6 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 17/829,056, mailed Sep. 30, 2022, 28 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 17/829,056, mailed Apr. 13, 2023, 25 pgs. [cited by applicant]
Mateja Klaric, “Mailchimp 101: How to Set up and Use the Damn Thing?,” The Writing Cooperative, May 5, 2018, 9 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 17/829,056, mailed Jul. 27, 2023, 5 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 17/829,056, mailed Sep. 26, 2023, 5 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 17/677,917, issued by the U.S. Patent and Trademark Office, Nov. 24, 2023, 5 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 17/944,754, issued by the U.S. Patent and Trademark Office, Dec. 22, 2023, 11 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 18/322,446, issued by the United States Patent and Trademark Office, mailed Apr. 18, 2024, 9 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 18/484,490 issued by the United States Patent and Trademark Office, mailed May 13, 2024, 12 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 18/484,490 issued by the United States Patent and Trademark Office, mailed Aug. 15, 2024, 13 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 18/322,446 issued by the United States Patent and Trademark Office, mailed Aug. 30, 2024, 2 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 17/944,754 issued by the United States Patent and Trademark Office, mailed Sep. 17, 2024, 4 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 18/534,082 issued by the United States Patent and Trademark Office, mailed Oct. 23, 2024, 6 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 18/484,828 issued by the United States Patent and Trademark Office, mailed Jun. 6, 2024, 19 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 18/484,828 issued by the U.S. Patent and Trademark Office, mailed Sep. 18, 2024, 5 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 18/534,082, mailed Mar. 5, 2025, 5 pgs. [cited by applicant]