CROSS CHANNEL REAL TIME AWARENESS FRAMEWORK

• US 20130185176A1
• Filed: 01/18/2012
• Published: 07/18/2013
• Est. Priority Date: 01/18/2012
• Status: Active Grant

• Current Assignee: Cellco Partnership, Inc. (Verizon Communications Inc.)
• Original Assignee: Cellco Partnership, Inc. (Verizon Communications Inc.)
• Inventors: ANCHALA, Arvindeep Singh
• Granted Patent: US 9,384,490 B2
• Time in Patent Office: Days
• US Class Current: 705/27.1
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 30/0619 Neutral agent
• CPC Class Codes: G06Q 30/0641 Shopping interfaces

Abstract

Techniques and equipment for enabling a cross-channel real time awareness framework for capturing and storing transaction data in real time for a user via an interface in a first channel of an enterprise are disclosed. The stored transaction data are made accessible to a second channel of the enterprise for processing transaction requests received from the user via an interface in the second channel, and, if desired, modify an interactive process flow associated with the interface in the second channel.

Claims

1. A computer-implemented method, comprising:

providing an automated service interface at a device of a user through a first channel of an enterprise having a plurality of channels, the automated service interface including a plurality of user interface elements enabling the user to initiate at least one transaction related to a product or service offered to the user by the enterprise;

detecting user interaction with at least one user interface element from the plurality of user interface elements of the automated service interface;

capturing transaction data in real time for the user based on the detected user interaction with the automated service interface of the first channel; and

sharing in real time the transaction data captured for the user in the first channel with at least one second channel of the enterprise, the captured transaction data being shared in association with a unique global identifier identifying the user across the plurality of channels of the enterprise, wherein the shared transaction data is used by the second channel for processing a transaction request from the user in the second channel.

2. The method of claim 1, wherein the sharing step comprises:

storing the captured transaction data to a data store of the enterprise, the captured transaction data stored in association with the unique global identifier identifying the user across the plurality of channels of the enterprise; and

activating a data service for enabling the stored transaction data to be used by the second channel of the enterprise for processing the transaction request from the user in the second channel.

3. The method of claim 1, wherein the captured transaction data includes a record of the user'"'"'s interactions with the plurality of user interface elements of the automated service interface of the first channel.

4. The method of claim 3, wherein at least one user interface element from the plurality of user interface elements is encoded with an activity identifier associated with the user interface element of the automated service interface, and the capturing step further comprises:

receiving a beacon signal including the activity identifier associated with the user interface element; and

storing in a data store of the enterprise the activity identifier from the received beacon signal as part of the record of user interactions in association with the unique global identifier associated with the user

5. The method of claim 1, wherein the processing of the transaction request received from the user in the second channel of the enterprise comprises:

determining whether to modify at least a portion of an interactive process flow of the second channel based on the transaction data for the user captured in the first channel; and

in response to determining to modify the portion of the interactive process flow, providing a customized version of the interactive process flow based on the captured transaction data for the user, the customized version of the interactive process flow having customized options or prompts for the user relative to a default version of the interactive process flow.

6. The method of claim 5, wherein providing the customized version of the interactive process flow includes at least one of:

presenting a fewer number of options in the customized version of the interactive process flow relative to the default version of the interactive process flow,

presenting an option or notice from the default version of the interactive process flow in a more emphasized manner, or

presenting a new option or prompt that is related to the transaction initiated by the user in the first channel and that is not part of the default version of the interactive process flow that otherwise would be presented to the user.

7. The method of claim 5, wherein in response to determining that the transaction request from the user in the second channel is being made in order to complete the transaction initiated in the first channel, the customized version of the interactive process flow provided to the user in the second channel includes options enabling the user to complete the transaction initiated in the first channel.

8. The method of claim 5, further comprising:

capturing initial conversion metrics for the default version of the interactive process flow, based on a first set of transaction requests from the user and other enterprise users using the default version of the interactive process flow in the second channel of the enterprise;

capturing new conversion metrics for the customized version of the interactive process flow, based on a second set of transaction requests from the user and the other enterprise users using the customized version of the interactive process flow;

comparing the initial conversion metrics with the new conversion metrics; and

determining whether the customized version of the interactive process flow produces improved conversion metrics based on the comparison.

9. The method of claim 1, wherein the transaction request from the user in the second channel of the enterprise is a confirmation request for confirming completion of the transaction initiated by the user in the first channel.

10. The method of claim 1, wherein the unique global identifier is an identifier associated with an account for the user in the enterprise.

11. The method of claim 1, wherein the capturing step further comprises:

determining whether the unique global identifier is available at the user'"'"'s device to identify the user when the transaction data is captured; and

at least one of;

in response to determining that the unique global identifier is not available at the user'"'"'s device, generating the unique global identifier for the user, and storing the generated unique global identifier at the user'"'"'s device; and

in response to determining that the unique global identifier is available at the user'"'"'s device, determining whether the unique global identifier at the user'"'"'s device is valid based on an expiration date associated with the unique global identifier, generating a new unique global identifier for the user in response to determining that the unique global identifier at the user'"'"'s device is not valid, and replacing the unique global identifier at the user'"'"'s device with the new unique global identifier.

12. The method of claim 1, wherein the first channel is a Web channel, the unique global identifier that is available at the user'"'"'s device is stored in a cookie file for a web browser executed at the user'"'"'s device, the automated service interface of the Web channel being accessible to the user via the web browser, and the second channel is a different one of an interactive voice response channel, a handset channel, a physical retail store channel, an automated kiosk channel, a live-person chat channel, an automated chat channel or a telesales channel.

13. The method of claim 12, wherein the transaction data captured for the user in the Web channel corresponds to an interactive process flow for completing a transaction, and the interactive process flow is presented to the user as a sequence of web pages via the web browser.

14. The method of claim 13, further comprising:

identifying web pages from the sequence of web pages that were browsed by the user via the web browser, based on the captured transaction data associated with the transaction; and

assigning a weight to each of the web pages browsed by the user, wherein a relatively greater weight is assigned to browsed web pages appearing later in the sequence of web pages, the later-appearing web pages corresponding to later steps for completing the transaction, wherein web pages appearing earlier in the sequence may be assigned a weight having a zero or non-zero value.

15. A method, comprising:

interacting with a consumer via network communications from a first system associated with a first channel of an enterprise offering goods or services, the first system providing a first type of user interface for the consumer in the first channel, the first type of user interface implementing an interactive process flow having a plurality of steps for the consumer to perform in order to initiate and complete a transaction for a purchase of a good or service offered by the enterprise;

storing transaction data related to one or more of the plurality of steps of the interactive process flow performed by the consumer via the first type of user interface in the first channel;

receiving at a second system associated with a second channel of the enterprise via network communications, and within a predetermined period of time following the interaction with the consumer via the first type of user interface in the first channel, a communication request from the consumer via a second type of user interface provided by the second system;

upon receiving the request at the second system of the second channel, retrieving the stored transaction data about the one or more steps of the interactive process flow performed by the consumer in the first channel; and

interacting with the consumer in the second channel via the second type of user interface provided by the second system based on the retrieved transaction data, wherein at least a portion of the interaction with the consumer via the second type of user interface in the second channel is responsive to the retrieved transaction data about the one or more steps of the interactive process flow that the consumer performed in the first channel.

16. A system, comprising:

a first system coupled to a network and configured to interact with a user for an enterprise offering goods or services, the first system also being configured to provide a first channel with a first type of user interface for the user;

a second system coupled to a network and configured to interact with the user for the enterprise, the second system also being configured to provide a second channel with a second type of user interface for the user;

at least one database accessible to a processor of the first system and a processor of the second system;

wherein the first system is further configured to;

provide the first type of interface at a device of a user through the first channel of the enterprise, the first type of interface including a plurality of user interface elements enabling the user to initiate at least one transaction related to a purchase of one or more of the goods or services offered by the enterprise;

detect user interaction with at least one user interface element from the plurality of user interface elements of the automated service interface;

capture transaction data in real time for the user based on the detected user interaction with the automated service interface of the first channel;

store the captured transaction data from the first channel to a data store in the enterprise, the captured transaction data stored in association with a unique global identifier identifying the user across the channels of the enterprise; and

activate a data service for providing the stored transaction data to the second system; and

wherein the second system is further configured to;

receive a transaction request from the user via the second type of user interface in the second channel; and

process the received transaction request from the user based on the stored transaction request corresponding to the transaction initiated in the first channel.

17. The system of claim 16, wherein the first type of interface is an automated interface.

18. The system of claim 16, wherein the captured transaction data includes a record of the user'"'"'s interactions with the automated service interface of the first channel.

19. The system of claim 16, wherein the second system is further configured to:

upon reception of the transaction request from the user in the second channel of the enterprise, determine whether to modify at least a portion of an interactive process flow associated with the second type of interface for the second channel, based on the stored transaction data for the user.

20. The system of claim 19, wherein the second system is further configured to, in response to determining to modify the portion of the interactive process flow, provide a customized version of the interactive process flow based on the captured transaction data for the user, the customized version of the interactive process flow having customized options or prompts for the user relative to a default version of the interactive process flow.

21. The system of claim 16, wherein the unique global identifier is an identifier associated with an account for the user in the enterprise.

22. The system of claim 16, wherein the first system is further configured to:

determine whether the unique global identifier is available at the user'"'"'s device to identify the user when the transaction data is captured; and

at least one of;

in response to determining that the unique global identifier is not available at the user'"'"'s device, generate the unique global identifier for the user, and store the generated unique global identifier at the user'"'"'s device;

or

in response to determining that the unique global identifier is available at the user'"'"'s device;

determine whether the unique global identifier at the user'"'"'s device is valid based on an expiration date associated with the unique global identifier;

generate a new unique global identifier for the user in response to determining that the unique global identifier at the user'"'"'s device is not valid; and

replace the unique global identifier at the user'"'"'s device with the new unique global identifier.

23. The system of claim 16, wherein the first channel is a Web channel, the unique global identifier that is available at the user'"'"'s device is stored in a cookie file for a web browser executed at the user'"'"'s device, the first type of interface of the Web channel being accessible to the user via the web browser, and the second channel is a different one of an interactive voice response channel, a handset channel, a physical retail store channel, an automated kiosk channel, a live-person chat channel, an automated chat channel or a telesales channel.

24. The system of claim 23, wherein the transaction data captured for the user in the Web channel corresponds to an interactive process flow for completing a transaction, and the interactive process flow is presented to the user as a sequence of web pages via the web browser.

25. The system of claim 24, wherein the first system is further configured to:

identify web pages from the sequence of web pages that were browsed by the user via the web browser, based on the captured transaction data associated with the transaction; and

assign a weight to each of the web pages browsed by the user, wherein a relatively greater weight is assigned to browsed web pages appearing later in the sequence of web pages, the later-appearing web pages corresponding to later steps for completing the transaction, wherein web pages appearing earlier in the sequence may be assigned a weight having a zero or non-zero value.