IP Library Patent Application 18661261
Patent Application
App. No. 18/661,261

SYSTEMS AND METHODS RELATED TO CUSTOMER AUTHENTICATION OF INCOMING TELEPHONE CALLS FROM AGENTS

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 None
App. No.
18/661,261
Abstract

A method of verifying that incoming telephone calls to respective customers originate from a business entity known to the customers that includes: receiving data transmitted from a customer application on a first customer device that notifies of a triggering event occurring; generating a business-side version of the verification code for use in association with the first authentication attempt; generating, by the first customer device, a customer-side version of the verification code for use in association with the first authentication attempt; generating a user interface showing the customer-side version of the verification code; and transmitting the generated business-side version of the verification code to a first agent device for authenticating that the first telephone call originates from a first business entity by enabling a comparison verifying that the customer-side version and the business-side version of the verification code are equal.

Claims (52)

1 . A method of verifying that incoming telephone calls to respective customers originate from a business entity known to the customers, the method comprising the steps of:

transmitting, from one or more servers associated with the business entity, a customer application to a customer device of each of the customers for installation on the customer device, wherein the customer application identifies the business entity associated therewith and is configured to:

determine an occurrence of a triggering event signaling an authentication attempt for authenticating a telephone call to a one of the customers;

generate, in response to determining the occurrence of the triggering event, a customer-side version of a verification code for use in each authentication attempt; and

generate a user interface on the customer device that displays the generated customer-side version of a verification code;

performing an authentication process in relation to each authentication attempt, wherein, when described in relation to an exemplary first authentication attempt related to authenticating that a first telephone call initiated from a first agent device by an agent to a first customer device associated with a first customer originates from a first business entity, the authentication process comprises the steps of:

receiving, by a verification module disposed within the one or more servers, data transmitted from the customer application on the first customer device that notifies of the triggering event occurring;

generating, by the verification module, a business-side version of the verification code for use in association with the first authentication attempt;

generating, by the customer application on the first customer device, the customer-side version of the verification code for use in association with the first authentication attempt;

generating, by the customer application on the first customer device for display on the first customer device, the user interface showing the customer-side version of the verification code;

transmitting, by the one or more servers, the generated business-side version of the verification code to the first agent device for authenticating that the first telephone call originates from the first business entity by enabling a comparison verifying that the customer-side version of the verification code and the business-side version of the verification code are equal.

2 . The method of claim 1 , wherein the customer application comprises a software token, and the customer device comprises a smart phone.

3 . The method of claim 2 , wherein the customer-side version of the verification code comprises a one-time password generated by the software token.

4 . The method of claim 2 , wherein the software token of the customer application and the verification module on the one or more servers associated with the business entity each comprises a shared secret key that is used by the software token of the customer application and the verification module to generate the customer-side version of the verification code and the business-side version of the verification code, respectively.

5 . The method of claim 4 , wherein the customer application is further configured to:

generate a user interface on the customer device that displays a selectable portion that instructs the customer to select the selectable portion when the customer wants to generate the customer-side version of the verification code for authenticating a given telephone call.

6 . The method of claim 5 , wherein the triggering event comprises receiving input indicating selection of the selectable portion.

7 . The method of claim 4 , wherein the triggering event comprises an expiration of a recurring countdown such that the verification code is generated periodically and usable until a current one of the recurring countdown expires.

8 . The method of claim 4 , wherein the triggering event comprises an activation of the customer application.

9 . The method of claim 4 , wherein the data transmitted from the customer application on the first customer device that notifies of the triggering event occurring further includes a customer identifier for the first customer.

10 . The method of claim 9 , wherein the authentication process further comprises the step of:

identifying, based on the customer identifier, the first agent device from among a plurality of such agent devices as being the particular agent device that is conducting the first telephone call with the first customer.

11 . The method of claim 10 , wherein the authentication process further comprises the step of:

generating, in response to identifying the first agent device as the particular agent device conducting the first telephone call, a user interface on the first agent device displaying the business-side version of the verification code.

12 . The method of claim 9 , wherein the authentication process further comprises the steps of:

providing, in response to identifying the first agent device as the particular agent device conducting the first telephone call, audio data for generating automated speech communicating the business-side version of the verification code; and

generating the automated speech during the first telephone call so to communicate the business-side version of the verification code to the first customer.

13 . The method of claim 4 , wherein the customer application is further configured to place an order for a product or service offered by the business entity.

14 . A system for verifying that incoming telephone calls to respective customers originate from a business entity known to the customers, the system comprising:

a processor; and

a memory storing instructions which, when executed by the processor, cause the processor to perform the steps of:

transmitting, from one or more servers associated with the business entity, a customer application to a customer device of each of the customers for installation on the customer device, wherein the customer application identifies the business entity associated therewith and is configured to:

determine an occurrence of a triggering event signaling an authentication attempt for authenticating a telephone call to a one of the customers;

generate, in response to determining the occurrence of the triggering event, a customer-side version of a verification code for use in each authentication attempt; and

generate a user interface on the customer device that displays the generated customer-side version of a verification code;

performing an authentication process in relation to each authentication attempt, wherein, when described in relation to an exemplary first authentication attempt related to authenticating that a first telephone call initiated from a first agent device by an agent to a first customer device associated with a first customer originates from a first business entity, the authentication process comprises the steps of:

receiving, by a verification module disposed within the one or more servers, data transmitted from the customer application on the first customer device that notifies of the triggering event occurring;

generating, by the verification module, a business-side version of the verification code for use in association with the first authentication attempt;

generating, by the customer application on the first customer device, the customer-side version of the verification code for use in association with the first authentication attempt;

generating, by the customer application on the first customer device for display on the first customer device, the user interface showing the customer-side version of the verification code; and

transmitting, by the one or more servers, the generated business-side version of the verification code to the first agent device for authenticating that the first telephone call originates from the first business entity by enabling a comparison verifying that the customer-side version of the verification code and the business-side version of the verification code are equal.

15 . The system of claim 14 , wherein the customer application comprises a software token, and the customer device comprises a smart phone.

16 . The system of claim 15 , wherein the customer-side version of the verification code comprises a one-time password generated by the software token.

17 . The system of claim 16 , wherein the software token of the customer application and the verification module on the one or more servers associated with the business entity each comprises a shared secret key that is used by the software token of the customer application and the verification module to generate the customer-side version of the verification code and the business-side version of the verification code, respectively.

18 . The system of claim 17 , wherein the customer application is further configured to:

generate a user interface on the customer device that displays a selectable portion that instructs the customer to select the selectable portion when the customer wants to generate the customer-side version of the verification code for authenticating a given telephone call;

wherein the triggering event comprises receiving input indicating selection of the selectable portion.

19 . The system of claim 17 , wherein the triggering event comprises an expiration of a recurring countdown such that the verification code is generated periodically and usable until a current one of the recurring countdown expires.

20 . The system of claim 17 , wherein the data transmitted from the customer application on the first customer device that notifies of the triggering event occurring further includes a customer identifier for the first customer; and

wherein the authentication process further comprises the step of:

identifying, based on the customer identifier, the first agent device from among a plurality of such agent devices as being the particular agent device that is conducting the first telephone call with the first customer; and

generating, in response to identifying the first agent device as the particular agent device conducting the first telephone call, a user interface on the first agent device displaying the business-side version of the verification code.

Assignments (2)
SUPPLEMENT TO SECURITY AGREEMENT Recorded May 1, 2025
From: GENESYS CLOUD SERVICES, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 071146/0687 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 14, 2024
From: SHAKED, DAN
To: GENESYS CLOUD SERVICES, INC.
Reel/Frame 067406/0489 →