US 12,379,903 B2
Campaign message flow builder
Alexander Colin Meyer, Chicago, IL (US); Gerardo Díaz De La Serna Formoso, Mexico City (MX); Gideon Daniel VanRiette, Chicago, IL (US); James Quinlan, Richmond, VA (US); Joy Taylor Kaufman, Durham, NC (US); Kameron Ahler, Colorado, CO (US); Lauren Leia Rouse, Nashville, TN (US); and Vishak Swaminathan Visvanathan, Brooklyn, NY (US)
Assigned to Stodge Inc., Scottsdale, AZ (US)
Filed by Stodge Inc., Scottsdale, AZ (US)
Filed on Aug. 16, 2023, as Appl. No. 18/234,857.
Application 18/234,857 is a continuation of application No. 18/330,244, filed on Jun. 6, 2023.
Application 18/330,244 is a continuation of application No. 17/964,825, filed on Oct. 12, 2022, granted, now 11,709,660, issued on Jul. 25, 2023.
Prior Publication US 2024/0126514 A1, Apr. 18, 2024
Int. Cl. G06F 8/34 (2018.01); G06F 9/54 (2006.01)
CPC G06F 8/34 (2013.01) [G06F 9/543 (2013.01)] 28 Claims
OG exemplary drawing
 
1. A system for providing message campaign services in cooperation with an application builder platform comprising one or more computers on which are stored instructions operable to cause the application builder platform to operate as a backend component of an application controlled by an application operator, and wherein the application builder platform:
is operable to communicate events to the system, and
is operable to send to the system notifications describing events that are each associated with a respective one of a plurality of end users;
the system comprising:
a message management platform, wherein the message management platform:
is separate from and operates independently of the application builder platform; and
is one or more computers on which are stored instructions operable to cause the platform to perform actions comprising:
receiving, through a user interface, from an application operator, a definition of a campaign, the campaign being a message flow plan, the campaign including (i) two or more messages, (ii) multiple flow plan steps, and (iii) an instruction to launch the message flow plan, wherein the multiple flow plan steps are connected to each other to define the campaign, and each of a plurality of the multiple flow plan steps are associated with a respective particular message of the campaign,
wherein the campaign is defined by the application operator to be distributed to multiple end users, the campaign comprising target recipient criteria for selecting a group of two or more end user subscribers to receive messages from the message flow plan, subscribers being subscribers to messages from the application operator,
wherein the target recipient criteria comprise characteristics of end users who are to receive an initial message of the campaign,
wherein the definition of the campaign includes a definition of the message flow for the campaign that (a) begins with the initial message for each subscriber satisfying the target recipient criteria and (b) specifies further messages to be transmitted in the campaign, and
wherein the definition of the campaign specifies a scheduled start of the campaign, the scheduled start being specified by the application operator;
receiving from the application builder platform notifications describing events that are each associated with a respective one of a plurality of end users;
storing, before the scheduled start of the campaign, for multiple end users that are subscribers, subscriber events, the subscriber events being events that are described in the notifications and are associated with the subscribers; and
identifying, at the scheduled start of the campaign and based on one or more of the previously stored subscriber events as of the scheduled start of the campaign, two or more subscribers as target subscribers that satisfy the target recipient criteria, and starting the message flow plan of the campaign and sending the initial message to the target subscribers at the scheduled start of the campaign.