Abstract: Systems and methods managing interaction between one of a plurality of advisors and a client. Client intent is determined based upon request details indicating a category of interest to the client. One of a plurality of advisors is selected to advise the client based, at least in part, upon the category and the client intent. The client is added to a sales pipeline of the selected advisor, and the selected advisor is prompted, at intervals, to interact with the client. The workload of each advisor is managed. The selected advisor is also prompted to generate and send a curation to the client. The systems and methods also provides e-commerce card fraud protection using conventional transaction processing methodology by including a random code in a pending transaction for the card and finalizing the transaction with the card provider when the code is correctly returned by the client.

Abstract: Systems and methods managing interaction between one of a plurality of advisors and a client. Client intent is determined based upon request details indicating a category of interest to the client. One of a plurality of advisors is selected to advise the client based, at least in part, upon the category and the client intent. The client is added to a sales pipeline of the selected advisor, and the selected advisor is prompted, at intervals, to interact with the client. The workload of each advisor is managed. The selected advisor is also prompted to generate and send a curation to the client. The systems and methods also provides e-commerce card fraud protection using conventional transaction processing methodology by including a random code in a pending transaction for the card and finalizing the transaction with the card provider when the code is correctly returned by the client.

Abstract: Systems and methods managing interaction between one of a plurality of advisors and a client. Client intent is determined based upon request details indicating a category of interest to the client. One of a plurality of advisors is selected to advise the client based, at least in part, upon the category and the client intent. The client is added to a sales pipeline of the selected advisor, and the selected advisor is prompted, at intervals, to interact with the client. The workload of each advisor is managed. The selected advisor is also prompted to generate and send a curation to the client. The systems and methods also provides e-commerce card fraud protection using conventional transaction processing methodology by including a random code in a pending transaction for the card and finalizing the transaction with the card provider when the code is correctly returned by the client.

Abstract: In an example embodiment, a submission of confidential data is received from a user via a first computerized user interface. An identification of the user is obtained, and details regarding the submission are stored in a submission table. Then a request to display, to the user, statistical information derived from confidential data from users other than the user, is received from a second computerized user interface. Based on information stored in the submission table, a determination is made that the request to display, to the user, statistical information derived from confidential data from users other than the user should be granted. In response to the determining, the statistical information derived from confidential data from users other than the user is displayed via the second computerized user interface.

Abstract: In an example embodiment, confidential data submitted by a user and one or more attributes of the user are obtained from one or more submission tables in a confidential information database. It is then determined that the one or more attributes of the user correspond to a first slice. In response to the determining, a count associated with the first slice is incremented. The count associated with the first slice is compared with a first threshold. In response to a determination that the count associated with the first slice transgresses the first threshold, the confidential data and the one or more attributes are added to a backend queue. Then, extraction, transformation, and loading (ETL) of the confidential data in the backend queue is performed and the confidential data is placed in an ETL table, in the confidential information database corresponding to the first slice.

Abstract: In an example embodiment, a submission of confidential data is received from a user. A first service is queried using an identification of the user to obtain a member profile corresponding to the user in a social networking service. One or more primary attribute values are identified from the member profile. The one of the primary attribute values are used to query a second service to obtain a derived attribute value corresponding to the one or more primary attribute values. The confidential data, one or more of the primary attribute values, and the derived attribute value are stored in a first submission table in a confidential information database. Then the one or more of the primary attribute values and the derived attribute value are used to classify the user into one or more slices.

Abstract: In an example embodiment, a submission of confidential data is received from a user. Then, the confidential data is encrypted using a first public key generated as part of a first public key-first private key pair. The encrypted confidential data is stored in a first column of a first submission table in a confidential information database. An identification of the user is encrypted using a second public key different than the first public key, the second public key generated as part of a first public key-first private key pair. Then, the encrypted identification of the user is stored in a second submission table in the confidential information database. The first private key is provided to a first component to decrypt the confidential information, without providing the second private key to the first component.

Abstract: In some embodiments, the disclosed subject matter involves an entity routing service to route user requests for an application service to a particular data center based on the user's entity status. The user's entity status is defined by at least the application service requested, and may include the user's organization, geographic area and other criteria. The routing may be effected at the frontend application server level rather than at the backend. Other embodiments are described and claimed.