IP Library Granted Patent US 12,335,205
Granted Patent B2
US 12,335,205 · App. 17/964,906 · Granted Jun 17, 2025

Automated interactive communication trigger in message distribution

Inventors: Anthony Saia (Chandler, AZ); Seth Miller (Mesa, AZ); Spencer Lund (Scottsdale, AZ); Ryan Lepinski (Portland, OR); Brandon O'Halloran (Omaha, NE); Armando Spataro (Chandler, AZ); Daniel Seidel (San Francisco, CA)
Assignee: Airship Group, Inc.
H04L51/02H04L51/04H04L51/216H04W4/029
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,335,205
App. No.
17/964,906
Granted
Jun 17, 2025
Kind
B2
Abstract

A message management server may receive selections, from a message publisher, to build a message series. The message series includes one or more messages and a live chat triggering condition. The message management server may generate a message series preview of the message series. The message series preview includes a simulation of a message in the message series. The message management server may receive a command from the message publisher to launch the message series. The message management server may transmit at least one of the messages in the message series to an end user. The message management server may determine that the live chat triggering condition is met. The message management server may launch a live chat based on the live chat triggering condition being met. The live chat connects the end user to a natural person agent.

Claims (43)

1. A system, comprising:

a graphical user interface configured to:

receive selections, from a message publisher, to build a message series, the message series comprising one or more messages and a live chat triggering condition; and

generate a message series preview of the message series, the message series preview comprising a simulation of a message in the message series, the message series comprising a first message and a second message, the first message to be sent via a software development kit (SDK) incorporated in a mobile application, the SDK being a first channel, the second message to be sent via a second channel; and

a message management server in communication with the graphical user interface, the message management server comprising a processor and memory storing instructions, the instructions, when executed by the processor, cause the processor to:

receive a command from the message publisher to launch the message series;

transmit, via at least the first channel and the second channel, the first message and the second message in the message series to an end user;

determine that the live chat triggering condition is met; and

launch a live chat based on the live chat triggering condition being met, the live chat launched in the mobile application by the SDK, the SDK establishing a third channel different from the first channel or the second channel, the third channel connecting the end user to a natural person agent in the live chat.

2. The system of claim 1 , wherein one of the messages in the message series is sent to the mobile application installed in a user device of the end user and the live chat is operated inside the mobile application.

3. The system of claim 1 , wherein launching the live chat causes the end user to switch to a third-party messaging platform.

4. The system of claim 1 , wherein the live chat triggering condition corresponds to a real life event and the message management server determines that the live chat triggering condition is met by receiving a notification regarding the real life event.

5. The system of claim 1 , wherein at least one of the messages in the message series is sent to the mobile application installed in a user device of the end user and the live chat triggering condition corresponds to an action performed by user with the mobile application.

6. The system of claim 1 , wherein the live chat triggering condition is associated with a geolocation detected.

7. The system of claim 1 , wherein the natural person agent is associated with the message publisher and chat messages in the live chat are forwarded to the message management server to allow the message publisher to access the chat messages.

8. The system of claim 1 , wherein the live chat is launched through the end user clicking a deep link that directs the user end to a live chat feature of the mobile application.

9. The system of claim 1 , wherein the live chat is launched after an in-application message is sent via the mobile application and the live chat is part of a native feature of the mobile application enabled by the SDK.

10. The system of claim 1 , wherein one of the messages in the message series is sent through the software development kit (SDK) associated with the mobile application installed in a user device of the end user and the live chat is part of a feature of the SDK.

11. The system of claim 1 , wherein the one or more messages in the message series are sent to the end user via a plurality of channels, and wherein the instructions, when executed, further cause the processor to:

determine an event of the end user associated with the live chat triggering condition;

determine a channel associated with the event; and

provide information of the channel to the natural person agent.

12. The system of claim 1 , wherein the message series includes a tag associated with the live chat triggering condition, the tag specified by the message publisher, and the live chat matches natural person agent based on the tag.

13. The system of claim 1 , wherein the live chat allows the natural person agent to specify one or more automated chat messages to be sent to the end user.

14. The system of claim 1 , wherein the natural person agent participates in the live chat through a live chat interface that is operated by the message management server.

15. A computer-implemented method, comprising:

receiving selections, from a message publisher, to build a message series, the message series comprising one or more messages and a live chat triggering condition;

generating a message series preview of the message series, the message series preview comprising a simulation of a message in the message series, the message series comprising a first message and a second message, the first message to be sent via a software development kit (SDK) incorporated in a mobile application, the SDK being a first channel, the second message to be sent via a second channel;

receiving a command from the message publisher to launch the message series;

transmitting, via at least the first channel and the second channel, the first message and the second message in the message series to an end user;

determining that the live chat triggering condition is met; and

launching a live chat based on the live chat triggering condition being met, the live chat launched in the mobile application by the SDK, the SDK establishing a third channel different from the first channel or the second channel, the third channel connecting the end user to a natural person agent in the live chat.

16. The computer-implemented method of claim 15 , wherein one of the messages in the message series is sent to a mobile application installed in a user device of the end user and the live chat is operated inside the mobile application.

17. The computer-implemented method of claim 15 , wherein one of the messages in the message series is sent through a software development kit (SDK) associated with a mobile application installed in a user device of the end user and the live chat is part of a feature of the SDK.

18. The computer-implemented method of claim 15 , wherein at least one of the messages in the message series is sent to a mobile application installed in a user device of the end user and the live chat triggering condition corresponds to an action performed by user with the mobile application.

19. The computer-implemented method of claim 15 , wherein the live chat is launched through the end user clicking a deep link that directs the user end to a live chat feature of a mobile application.

20. A non-transitory computer-readable medium configured to store computer code comprising instructions, the instructions, when executed by one or more processors, cause the one or more processors to perform step comprising:

receiving selections, from a message publisher, to build a message series, the message series comprising one or more messages and a live chat triggering condition;

generating a message series preview of the message series, the message series preview comprising a simulation of a message in the message series, the message series comprising a first message and a second message, the first message to be sent via a software development kit (SDK) incorporated in a mobile application, the SDK being a first channel, the second message to be sent via a second channel;

receiving a command from the message publisher to launch the message series;

transmitting, via at least the first channel and the second channel, the first message and the second message in the message series to an end user;

determining that the live chat triggering condition is met; and

launching a live chat based on the live chat triggering condition being met, the live chat launched in the mobile application by the SDK, the SDK establishing a third channel different from the first channel or the second channel, the third channel connecting the end user to a natural person agent in the live chat.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 13, 2025
From: SAIA, ANTHONY; LEPINSKI, RYAN; O'HALLORAN, BRANDON; SPATARO, ARMANDO; SEIDEL, DANNY
To: AIRSHIP GROUP, INC.
Reel/Frame 070495/0866 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 13, 2025
From: MILLER, SETH
To: URBAN AIRSHIP, INC.
Reel/Frame 070504/0606 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 13, 2025
From: LUND, SPENCER
To: URBAN AIRSHIP, INC.
Reel/Frame 070504/0670 →
CHANGE OF NAME Recorded Mar 13, 2025
From: URBAN AIRSHIP, INC.
To: AIRSHIP GROUP, INC.
Reel/Frame 070513/0364 →
SECURITY INTEREST Recorded Jul 1, 2024
From: AIRSHIP GROUP, INC.; APPTIMIZE, LLC
To: RUNWAY GROWTH FINANCE CORP.
Reel/Frame 068099/0779 →
Continuity (2)
Provisional Application 63256214 · Oct 15, 2021
Related Publication 20230122680A1 · Apr 20, 2023
References Cited (78)
US 5873106A · Joseph · 1999 [cited by applicant]
US 6230309B1 · Turner et al. · 2001 [cited by applicant]
US 7669177B2 · Gerber et al. · 2010 [cited by applicant]
US 7881439B1 · Cohn · 2011 [cited by examiner]
US 8065600B2 · Chorv et al. · 2011 [cited by applicant]
US 8380803B1 · Stibel · 2013 [cited by examiner]
US 8494077B2 · Haustein · 2013 [cited by examiner]
US 8543577B1 · Ben-Artzi · 2013 [cited by examiner]
US 9351193B2 · Raleigh et al. · 2016 [cited by applicant]
US 9485177B2 · Tung et al. · 2016 [cited by applicant]
US 9602661B2 · Rauenbuehler et al. · 2017 [cited by applicant]
US 9621735B2 · Ting et al. · 2017 [cited by applicant]
US 9635057B2 · Bone et al. · 2017 [cited by applicant]
US 9654581B2 · Pollack et al. · 2017 [cited by applicant]
US 9911290B1 · Zalewski et al. · 2018 [cited by applicant]
US 9959551B1 · Schermerhorn · 2018 [cited by examiner]
US 10200486B2 · Herrick et al. · 2019 [cited by applicant]
US 10732782B1 · Krivopaltsev et al. · 2020 [cited by applicant]
US 11232465B2 · Orr et al. · 2022 [cited by applicant]
US 20040183838A1 · Lahiri · 2004 [cited by applicant]
US 20060284878A1 · Zimmer · 2006 [cited by applicant]
US 20060294199A1 · Bertholf · 2006 [cited by applicant]
US 20070005717A1 · LeVasseur et al. · 2007 [cited by applicant]
US 20090167553A1 · Hong et al. · 2009 [cited by applicant]
US 20100287566A1 · Hauser · 2010 [cited by applicant]
US 20110264996A1 · Norris · 2011 [cited by applicant]
US 20120227000A1 · McCov et al. · 2012 [cited by applicant]
US 20120260209A1 · Stibel · 2012 [cited by examiner]
US 20130019182A1 · Gil et al. · 2013 [cited by applicant]
US 20130173734A1 · Oteiza Lacalle · 2013 [cited by examiner]
US 20130212487A1 · Cote · 2013 [cited by applicant]
US 20130219307A1 · Raber et al. · 2013 [cited by applicant]
US 20140006129A1 · Heath · 2014 [cited by examiner]
US 20140100669A1 · Hammack et al. · 2014 [cited by applicant]
US 20140258055A1 · Wolfe et al. · 2014 [cited by applicant]
US 20140273915A1 · Corley · 2014 [cited by examiner]
US 20140282218A1 · Kaufman et al. · 2014 [cited by applicant]
US 20150049157A1 · Krishnamoorthy · 2015 [cited by examiner]
US 20150049160A1 · Krishnamoorthy · 2015 [cited by examiner]
US 20150049164A1 · Krishnamoorthy · 2015 [cited by examiner]
US 20150112990A1 · van Os · 2015 [cited by examiner]
US 20150160931A1 · Glazer et al. · 2015 [cited by applicant]
US 20150161088A1 · Kamada · 2015 [cited by applicant]
US 20150193537A1 · Cierniak · 2015 [cited by examiner]
US 20150212984A1 · Bowden · 2015 [cited by examiner]
US 20150229592A1 · Rathod · 2015 [cited by applicant]
US 20150350068A1 · Tung et al. · 2015 [cited by applicant]
US 20160007198A1 · Lacey et al. · 2016 [cited by applicant]
US 20160012465A1 · Sharp · 2016 [cited by examiner]
US 20160066273A1 · Prats · 2016 [cited by applicant]
US 20160110083A1 · Kranendonk · 2016 [cited by examiner]
US 20160150021A1 · Britt et al. · 2016 [cited by applicant]
US 20160328715A1 · Gideoni · 2016 [cited by examiner]
US 20170041742A1 · Toksvig et al. · 2017 [cited by applicant]
US 20170142191A1 · Caldwell · 2017 [cited by examiner]
US 20170193851A1 · McNichol et al. · 2017 [cited by applicant]
US 20170279759A1 · Liden · 2017 [cited by examiner]
US 20170282736A1 · Goei · 2017 [cited by applicant]
US 20180084111A1 · Pirat et al. · 2018 [cited by applicant]
US 20180156925A1 · Johns · 2018 [cited by examiner]
US 20190108585A1 · Caldwell · 2019 [cited by examiner]
US 20200127951A1 · Shah · 2020 [cited by examiner]
US 20200404390A1 · Lieberman · 2020 [cited by examiner]
US 20210281528A1 · Orr et al. · 2021 [cited by applicant]
KR 101545285B1 · 2015 [cited by applicant]
PCT International Search Report and Written Opinion, PCT Application No. PCT/US2020/044901, dated Nov. 6, 2020, ten pages. [cited by applicant]
Boltclock, “Revision—Stack Overflow,” https://stackoverflow.com/revisions/8426901/2, 1 page, Dec. 8, 2011. [cited by applicant]
European Patent Office, Extended European Search Report and Opinion, EP Patent Application No. 20162248.7, dated Jun. 25, 2020, nine pages. [cited by applicant]
Extended European Search Report, European Application No. 15739969.2, dated Aug. 30, 2017, 12 pages. [cited by applicant]
Leiva, L., “Ace: An Adaptive CSS Engine for Web Pages and Web-based Applications,” WWW2012 Developer Track, Apr. 2012, pp. 1-4. [cited by applicant]
Leiva, L., “Interaction-based user interface redesign,” Proceedings of the 2012 ACM International Conference on Intelligent User Interfaces, Feb. 2012, pp. 311-312. [cited by applicant]
PCT International Search Report and Written Opinion, PCT Application No. PCT/US15/11986, dated Apr. 9, 2015, 9 pages. [cited by applicant]
United States Office Action, U.S. Appl. No. 14/506,990, dated Jan. 12, 2017, 24 pages. [cited by applicant]
United States Office Action, U.S. Appl. No. 14/506,990, dated Jun. 15, 2018, 12 pages. [cited by applicant]
United States Office Action, U.S. Appl. No. 14/506,990, dated Nov. 16, 2017, 22 pages. [cited by applicant]
United States Office Action, U.S. Appl. No. 16/381,590, filed Aug. 20, 2020, 11 pages. [cited by applicant]
W3C, “Selectors API Level 1,” Feb. 21, 2013, eight pages, [Online] [Retrieved on Jun. 12, 2020] Retrieved on the Internet <URL: https://www.w3.org/TR/selectors-api/>. [cited by applicant]
W3SCHOOLS, “CSS Selector Reference,” https://www.w3schools.com/cssref/css_selectors.asp, 9 pages, Jan. 1, 2014. [cited by applicant]