Abstract: An analysis is performed on first and second product information to determine a relationship between a first product and a second product. In response to a first notification from a first backend system, a first message is transmitted to a mobile device of the user indicating that the change of a first activity is needed. It is determined whether a modification of a second activity is needed based on the relationship information of the first product and the second product and in response to determining that the modification of the second activity is needed, a second message is transmitted to the mobile device, indicating a possible modification of the second activity and offering a list of one or more options to modify the second activity. A live communications session is established between the user and a support agent of the server to discuss the possible modification of the second activity.

Abstract: An analysis is performed on first and second product information to determine a relationship between a first product and a second product. In response to a first notification from a first backend system, a first message is transmitted to a mobile device of the user indicating that the change of a first activity is needed. It is determined whether a modification of a second activity is needed based on the relationship information of the first product and the second product and in response to determining that the modification of the second activity is needed, a second message is transmitted to the mobile device, indicating a possible modification of the second activity and offering a list of one or more options to modify the second activity. A live communications session is established between the user and a support agent of the server to discuss the possible modification of the second activity.

Abstract: An analysis is performed on first and second product information to determine a relationship between a first product and a second product. In response to a first notification from a first backend system, a first message is transmitted to a mobile device of the user indicating that the change of a first activity is needed. It is determined whether a modification of a second activity is needed based on the relationship information of the first product and the second product and in response to determining that the modification of the second activity is needed, a second message is transmitted to the mobile device, indicating a possible modification of the second activity and offering a list of one or more options to modify the second activity. A live communications session is established between the user and a support agent of the server to discuss the possible modification of the second activity.

Abstract: After successfully authenticating a user of a mobile device, products that have been registered with the server are determined. For each of the registered products, a list of support options available to the user is determined for a corresponding registered product, the list of support options including a live support option and a self-support option. For the self-support option available to the corresponding registered product, articles associated with the corresponding registered product are identified that have been published in an online publication forum. For the live support option available a list of communication options is determined that is available for the user to establish a live communication session with a support agent. A personalized page to the mobile device to be displayed at a display of the mobile device, listing the registered products. Each product is associated with the support options available.

Abstract: An analysis is performed on first and second product information to determine a relationship between a first product and a second product. In response to a first notification from a first backend system, a first message is transmitted to a mobile device of the user indicating that the change of a first activity is needed. It is determined whether a modification of a second activity is needed based on the relationship information of the first product and the second product and in response to determining that the modification of the second activity is needed, a second message is transmitted to the mobile device, indicating a possible modification of the second activity and offering a list of one or more options to modify the second activity. A live communications session is established between the user and a support agent of the server to discuss the possible modification of the second activity.

Abstract: After successfully authenticating a user of a mobile device, products that have been registered with the server are determined. For each of the registered products, a list of support options available to the user is determined for a corresponding registered product, the list of support options including a live support option and a self-support option. For the self-support option available to the corresponding registered product, articles associated with the corresponding registered product are identified that have been published in an online publication forum. For the live support option available a list of communication options is determined that is available for the user to establish a live communication session with a support agent. A personalized page to the mobile device to be displayed at a display of the mobile device, listing the registered products. Each product is associated with the support options available.

Abstract: According to one aspect, a request is received at a services application programming interface (API) of a support center from a user for support services of a product provided by a client of the support center. In response to the request, one or more articles associated with the product are identified that have been published in an online publication forum, where the articles have been extracted from a knowledgebase (KB) based on a support history of the product maintained by the support center. A list of support options is presented to the user, including a first one-touch button to contact an agent of the support center and a link to the one or more articles of the publication forum to allow the user to attempt finding a solution to the product without having to contact the agent of the support center.

Abstract: According to one aspect, in response to a request from a mobile application running at a mobile device of a customer, a personalized page is transmitted to the mobile application, the personalized page including a list of products retrieved from a customer profile of the customer. Each of the products is associated with one or more communications channels preferred by an associated client, which are retrieved from the client database. A live support request is received from the mobile application initiated from a selected product of the personalized page, the live support request including a selection selecting one of the preferred communications channels listed on the personalized page. A live communication session is established between the customer and a support agent using a selected communications channel for live support services to the customer concerning the selected product.

Abstract: According to one aspect, in response to a request from a mobile application running at a mobile device of a customer, a personalized page is transmitted to the mobile application, the personalized page including a list of products retrieved from a customer profile of the customer. Each of the products is associated with one or more communications channels preferred by an associated client, which are retrieved from the client database. A live support request is received from the mobile application initiated from a selected product of the personalized page, the live support request including a selection selecting one of the preferred communications channels listed on the personalized page. A live communication session is established between the customer and a support agent using a selected communications channel for live support services to the customer concerning the selected product.

Abstract: According to one aspect, a first request is received at a services application programming interface (API) of a support center from a first user for a first product provided by a first client. A second request is received at the services API of the support center from a second user for a second product provided by a second client. A first knowledgebase (KB) associated with the first client and a second KB associated with the second client are identified. A third KB that contains information common to the first product and the second product is identified. The first KB and the third KB are enabled to be accessible by a first agent assigned to provide support services of the first product. The second KB and the third KB are enabled to be accessible by a second agent assigned to provide support services of the second product.

Abstract: According to one embodiment, a request is received at a support center a request from a user for registering a product, where the request includes a machine-readable code that uniquely represents the product. In response to the request, the product is identified and product information is compiled based on the machine-readable code without requiring the user to specifically provide the product information. The product information of the identified product is stored in a user asset store associated with the user, where the product information stored in the user asset store is utilized subsequently for supporting identified product.

Abstract: According to one aspect of the invention, it is determined, at a support center, a relationship between a first product provided by a first vendor and a second product provided by a second vendor. The first and second products have been purchased by a user via a purchasing facility associated with a client of the support center. In response to a first event received from the client or the first vendor indicating a change of the first product, a first message is transmitted to the user on behalf of the client notifying the user the change of the first product. A second message is automatically transmitted to the user offering a support service of a possible change of the second product in view of the relationship between the first and second products, without requiring the user to initiate a request for the support service.

Abstract: According to one aspect, a request is received at a services application programming interface (API) of a support center from a user for support services of a product. A first list of one or more communication channels that are available for the user to contact an agent of the support center is generated based on a second list of one or more communication channels preferred by the user and a third list of one or more communication channels preferred by a vendor associated with the product. The first list of one or more communication channels is transmitted via the service API to the user. In response to a selection of a communication channel from the first list, a communication session is established between the user and the agent via the selected communication channel for providing support services of the product on behalf of the vendor.

Abstract: According to one aspect, a first request is received at a services application programming interface (API) of a support center from a first user for a first product provided by a first client. A second request is received at the services API of the support center from a second user for a second product provided by a second client. A first knowledgebase (KB) associated with the first client and a second KB associated with the second client are identified. A third KB that contains information common to the first product and the second product is identified. The first KB and the third KB are enabled to be accessible by a first agent assigned to provide support services of the first product. The second KB and the third KB are enabled to be accessible by a second agent assigned to provide support services of the second product.

Abstract: According to one aspect, a request is received at a support services application programming interface (API) of a support center that provides support services to a plurality of products of a plurality of vendors, where the request is received from a user for support services of a product. In response to the request, a case identifier (ID) is instantly generated that uniquely identifies a current instant support services session associated with the user for supporting the product. A touch plan is dynamically created representing an instance of the support services session, where the touch plan is identified and tracked by the case ID. A communication session is established between an agent and the user to allow the agent to provide support services to the user based on the touch plan.

Abstract: According to one aspect, a request is received at a services application programming interface (API) of a support center from a user for support services of a product provided by a client of the support center. In response to the request, one or more articles associated with the product are identified that have been published in an online publication forum, where the articles have been extracted from a knowledgebase (KB) based on a support history of the product maintained by the support center. A list of support options is presented to the user, including a first one-touch button to contact an agent of the support center and a link to the one or more articles of the publication forum to allow the user to attempt finding a solution to the product without having to contact the agent of the support center.