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:
De acuerdo con un aspecto, se recibe de un usuario una petición, en una interfaz programadora de aplicación (API) de servicios de un centro de apoyo, para servicios de apoyo de un producto. Se genera una primera lista de uno o más canales de comunicación que están disponibles para que el usuario se ponga en contacto con un agente del centro de apoyo, con base en una segunda lista de uno o más canales de comunicación preferidos por el usuario, y una tercera lista de uno o más canales de comunicación preferidos por un vendedor asociado con el producto. Se trasmite la primera lista de uno o más canales de comunicación a través de la API, al usuario. En respuesta a una selección de un canal de comunicación de la primera lista, se establece una sesión de comunicación entre el usuario y el agente a través del canal de comunicación seleccionado para dar servicios de apoyo del producto a nombre del vendedor.
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, 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 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, 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:
A service center receives a request from a remote device for a live support session of a product supported by the service center, where the service center provides support services for a plurality of products on behalf of a plurality of product providers. In response to the request, the service center determines one or more preferred agents that are known to a user of the remote device and transmits information representing the preferred agents to the remote device to allow the user to select one of the preferred agents for the live support session. In response to a user selection of an agent, a communications session is established between the user and the selected agent to enable the selected agent to provide live support.
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.