	US 12,067,587 B2
	System and methods for using enhanced QR codes in a call to action
Steve Doumar, Fort Lauderdale, FL (US); and David Teodosio, Guilford, CT (US)
Assigned to TAPTEXT LLC, Coral Springs, FL (US)
Filed by TapText llc, Coral Springs, FL (US)
Filed on Sep. 12, 2022, as Appl. No. 17/943,118.
Application 17/943,118 is a continuation in part of application No. 17/875,402, filed on Jul. 27, 2022.
Application 17/875,402 is a continuation of application No. 17/349,659, filed on Jun. 16, 2021, granted, now 11,488,188.
Application 17/943,118 is a continuation in part of application No. 17/409,841, filed on Aug. 24, 2021.
Application 17/409,841 is a continuation in part of application No. 17/360,731, filed on Jun. 28, 2021.
Application 17/360,731 is a continuation in part of application No. 17/229,251, filed on Apr. 13, 2021.
Application 17/360,731 is a continuation in part of application No. 17/085,931, filed on Oct. 30, 2020, granted, now 11,055,736, issued on Jul. 6, 2021.
Application 17/229,251 is a continuation in part of application No. 16/693,275, filed on Nov. 23, 2019, granted, now 11,270,354, issued on Mar. 8, 2022.
Application 17/943,118 is a continuation in part of application No. 17/351,321, filed on Jun. 18, 2021, granted, now 11,201,965, issued on Dec. 14, 2021.
Application 17/351,321 is a continuation of application No. 17/349,659, filed on Jun. 16, 2021, granted, now 11,488,188.
Application 17/349,659 is a continuation of application No. 17/348,660, filed on Jun. 15, 2021, granted, now 11,232,471.
Application 17/348,660 is a continuation of application No. 17/344,695, filed on Jun. 10, 2021, granted, now 11,354,691, issued on Jun. 7, 2022.
Application 17/344,695 is a continuation of application No. 17/229,251, filed on Apr. 13, 2021.
Application 17/229,251 is a continuation in part of application No. 17/209,474, filed on Mar. 23, 2021.
Application 17/209,474 is a continuation in part of application No. 17/208,059, filed on Mar. 22, 2021, granted, now 11,562,407.
Application 17/208,059 is a continuation in part of application No. 17/191,977, filed on Mar. 4, 2021.
Application 17/191,977 is a continuation in part of application No. 17/190,260, filed on Mar. 2, 2021, granted, now 11,532,020.
Application 17/190,260 is a continuation in part of application No. 17/153,426, filed on Jan. 20, 2021, abandoned.
Claims priority of provisional application 63/350,415, filed on Jun. 9, 2022.
Claims priority of provisional application 63/040,610, filed on Jun. 18, 2020.
Claims priority of provisional application 63/025,287, filed on May 15, 2020.
Claims priority of provisional application 63/022,190, filed on May 8, 2020.
Claims priority of provisional application 62/994,219, filed on Mar. 24, 2020.
Claims priority of provisional application 62/965,626, filed on Jan. 24, 2020.
Claims priority of provisional application 62/963,568, filed on Jan. 21, 2020.
Claims priority of provisional application 62/963,368, filed on Jan. 20, 2020.
Claims priority of provisional application 62/963,379, filed on Jan. 20, 2020.
Claims priority of provisional application 62/940,607, filed on Nov. 26, 2019.
Claims priority of provisional application 62/904,568, filed on Sep. 23, 2019.
Claims priority of provisional application 62/883,360, filed on Aug. 6, 2019.
Claims priority of provisional application 62/879,862, filed on Jul. 29, 2019.
Claims priority of provisional application 63/211,496, filed on Jun. 16, 2021.
Claims priority of provisional application 63/166,391, filed on Mar. 26, 2021.
Claims priority of provisional application 63/154,357, filed on Feb. 26, 2021.
Prior Publication US 2022/0414698 A1, Dec. 29, 2022
Int. Cl. H04M 1/64 (2006.01); G06F 16/955 (2019.01); G06F 21/32 (2013.01); G06F 21/62 (2013.01); G06K 7/14 (2006.01); G06K 19/06 (2006.01); G06N 20/00 (2019.01); G06Q 10/0631 (2023.01); G06Q 30/016 (2023.01); G06Q 30/0201 (2023.01); G06Q 30/0207 (2023.01); H04M 3/523 (2006.01); H04M 3/527 (2006.01); H04M 3/533 (2006.01); G06Q 30/0251 (2023.01)

CPC G06Q 30/0207 (2013.01) [G06F 16/9554 (2019.01); G06F 16/9558 (2019.01); G06F 21/32 (2013.01); G06F 21/6245 (2013.01); G06K 7/1417 (2013.01); G06K 19/06037 (2013.01); G06N 20/00 (2019.01); G06Q 10/06315 (2013.01); G06Q 30/016 (2013.01); G06Q 30/0201 (2013.01); H04M 3/523 (2013.01); H04M 3/527 (2013.01); H04M 3/53308 (2013.01); H04M 3/53333 (2013.01); G06F 2221/2139 (2013.01); G06Q 30/0267 (2013.01)]

14 Claims

1. A system for using enhanced quick-response (“QR”) codes in a call to action, comprising:

a computing device comprising a memory, a processor, and a non-volatile data storage device;

a database stored on the non-volatile data storage device, the database comprising identifiers for a plurality of tokens and automation rules for each of the tokens;

a positioning server comprising a first plurality of programming instructions stored in the memory which, when operating on the processor, causes the computing device to:

place a call to action element comprising a first token on an Internet website or embed the call to action in a message communication, the call to action comprising an enhanced QR code, the enhanced QR code further comprising:

a QR code comprising a set of call to action instructions configured to generate, when scanned, a pre-filled first short message service (SMS) or multimedia message service (MMS) message on a mobile device, the SMS or MMS message comprising an identifier for the call to action element; and

a plurality of QR enhancements;

wherein the QR enhancements are selected from: a customized shape, embedded image content, or a nested QR code;

a media server comprising a second plurality of programming instructions stored in the memory which, when operating on the processor, causes the computing device to:

receive the first pre-filled SMS message or the first pre-filled MMS message from the mobile device;

capture the phone number of the mobile computing device from the first pre-filled SMS message or the first pre-filled MMS message;

send the identifier for the call to action to a token manager with a request for verification of the token and a request for rules associated with the token;

receive verification of the token and a rule associated with the token;

initiate an action to be taken based on the rule; and

a token manager comprising a third plurality of programming instructions stored in the memory which, when operating on the processor, causes the computing device to:

receive the identifier for the call to action;

verify, using the identifier, that the token associated with the identifier matches a same token stored in the database;

retrieve from the database the rule associated with the token; and

send the verification and the rule to the media server.