Abstract: An omni-channel adapter receives a request to create a communication session for a customer. Based on the request, the omni-channel adapter selects a channel-specific orchestrator. The request is modified, or a new request is generated, to suit the selected channel-specific orchestrator. The channel-specific request is sent to the channel-specific orchestrator. In response, the channel-specific orchestrator creates the communication session. Further communications between the customer and the channel-specific orchestrator may also be intermediated by the omni-channel adapter, which may maintain state information about the communication session. For example, a unique identifier may be generated by the omni-channel adapter or the channel-specific orchestrator for the communication session. A request by the customer to add an additional device to the communication session may include the identifier of the session.

Abstract: A method of intelligently handling routing requests in a computerized customer engagement environment is disclosed. Access to an API for processing a routing request in the customer engagement environment is provided. The API includes a handler for the routing request. The handler includes parameters for specifying a routing attribute and a proficiency. The proficiency corresponds to the routing attribute. The routing attribute and the proficiency are received via the parameters of the handler. An agent in the customer engagement environment is recommended to invite to a channel associated with the routing request. The recommending is based on a matching of the agent to the routing attribute and the proficiency corresponding to the routing attribute.

Abstract: A method of managing a set of interactions associated with one or more computerized systems is disclosed. An API for managing an interaction detail record associated with an interaction of the set of interactions is provided. Based on one or more parameters being received from one or more client systems of a plurality of client systems via one or more event handlers, updating of one or more values of one or more user-defined attributes stored in the interaction detail record is performed. Based on the performing of the updating of the one or more values of the one or more user-defined attributes, one or more event handlers for providing the one or more values of the one or more user-defined attributes to the one or more client systems are invoked.

Abstract: A method of processing one or more interactions using a timeline is disclosed. Data pertaining to a plurality of omnichannel interactions is stored in a timeline record in real-time when each of the plurality of interactions occurs. Each of the plurality of interactions is associated with one or more topics and an identifier of an end customer. A request for a subset of the data that corresponds to an additional interaction of the end customer is received via an API. The subset identified in one or more parameters of the API. In response to the request, the subset of the data is provided for surfacing in a graphical user interface such that one or more representatives can make a determination of whether to accept an invitation to process the additional interaction.

Abstract: An omni-channel adapter receives a request to create a communication session for a customer. Based on the request, the omni-channel adapter selects a channel-specific orchestrator. The request is modified, or a new request is generated, to suit the selected channel-specific orchestrator. The channel-specific request is sent to the channel-specific orchestrator. In response, the channel-specific orchestrator creates the communication session. Further communications between the customer and the channel-specific orchestrator may also be intermediated by the omni-channel adapter, which may maintain state information about the communication session. For example, a unique identifier may be generated by the omni-channel adapter or the channel-specific orchestrator for the communication session. A request by the customer to add an additional device to the communication session may include the identifier of the session.

Abstract: Systems and methods are disclosed for managing displays of notifications to a user device. A method can include determining that an event has occurred that requires a user notification. One or more user and device characteristics are analyzed to determine whether a user notification is to be displayed on the user device.

Abstract: Systems and methods are disclosed for managing displays of notifications to a user device. A method can include determining that an event has occurred that requires a user notification. One or more user and device characteristics are analyzed to determine whether a user notification is to be displayed on the user device.

Abstract: Systems and methods are disclosed for managing transmissions of notifications to user devices. A method can include determining that an event has occurred that requires a user notification. User and device characteristics are analyzed to determine that a single user device is currently in active use. The user notification is transmitted to the user device that has been determined to be in active use.

Abstract: Systems and methods are disclosed for managing transmissions of notifications to user devices. A method can include determining that an event has occurred that requires a user notification. User and device characteristics are analyzed to determine that a single user device is currently in active use. The user notification is transmitted to the user device that has been determined to be in active use.