Abstract: A method and apparatus for autonomous container management configuration changes to container clusters during runtime and autonomous configuration-based release orchestration. A release manager manages a staggered feature release that includes staggers, stagger order, and container clusters included in each stagger. A logging service manages logs generated by the container clusters and/or app containers. An update service determines container management configuration changes based on analysis of data provided by the logging service. A shared engine attempts to implement instructions provided by the release manager and the update service at different times. The release manager receives an indication of success or failure of the attempted deployment of the feature release to the current stagger. The release manager, responsive to the indication of success or failure, determines to perform one of a plurality of actions, including attempting to deploy the feature release to the next stagger, and rolling back.

Abstract: A method and apparatus for autonomous release orchestration that supports staggered releases across a plurality of container clusters. A representation of a risk level for a current release is obtained. Based on the risk level, a set of one or more attributes of a stagger configuration is determined. An attempt to deploy the current release to the plurality of container clusters in accordance with the stagger configuration is caused.

Abstract: A method and apparatus for autonomous configuration-based release orchestration that supports staggered feature releases across a plurality of container clusters. A release seeking goal is obtained. An unprocessed stagger is selected as a current stagger based on a stagger order. The current stagger is processed by attempting to cause a deployment of the feature release to the container clusters in the current stagger, receiving an indication of success or failure of the attempted deployment, and determining whether to roll back the current stagger based on the indication. A determination is made whether the release seeking goal can still be met. If the release seeking goal can no longer be met, a release level rollback is caused, and otherwise the selecting, processing, and determining is repeated for the next unprocessed stagger based on the stagger order.

Abstract: A method and apparatus for autonomous configuration-based release orchestration. A first engine obtains stagger configuration data that includes an indication of container clusters in each stagger and a stagger order, selects a current stagger based on the order, and attempts to deploy the feature release to the current stagger by causing an app config update to be sent to a second engine within each container cluster of the current stagger, and receives an indication of success or failure of the attempted deployment of the feature release to the current stagger. Responsive to the indication of success or failure, the first engine performs one of a plurality of actions that include attempting to deploy the feature release to a next one of the staggers according to the order responsive to the indication indicating success, and causing a roll back of the current stagger responsive to the indication indicating failure.

Abstract: Methods and systems are provided for providing an insights page. When data identifying a party of a call is received, a customer relationship management (CRM) application can be launched at a computing device without any further user input, and records that are potentially relevant to the call and that are to potentially be included as part of an insights page of the CRM application can be automatically determined. Some of the records are automatically determined by analyzing CRM information using artificial intelligence technologies. The records can then be ranked in a priority order according to relevance from most relevant to least relevant. The insights page can then be caused to be displayed at a user interface of the computing device without user input with at least some of the records displayed in the priority order as relevant records.

Abstract: Methods and systems are provided for providing an insights page. When data identifying a party of a call is received, a customer relationship management (CRM) application can be launched at a computing device without any further user input, and records that are potentially relevant to the call and that are to potentially be included as part of an insights page of the CRM application can be automatically determined. Some of the records are automatically determined by analyzing CRM information using artificial intelligence technologies. The records can then be ranked in a priority order according to relevance from most relevant to least relevant. The insights page can then be caused to be displayed at a user interface of the computing device without user input with at least some of the records displayed in the priority order as relevant records.

Abstract: Embodiments of the present disclosure relate to detecting and mitigating errors associated with software pull requests such as software deployment packages. The embodiments include identifying a failure of a pull request, identifying a system error associated with the failure, determining a failure mitigation process based on the failure and the system error, and executing the failure mitigation process to resolve the failure. The errors can be classified as system errors, user errors or planned downtime. The failure mitigation process can include generating an alert associated with the identified system error, updating a status of the pull request, re-evaluating the failure after a predetermined period of time, and retrying deployment of the pull request using an exponential retry process.

Abstract: Among other things, embodiments of the present disclosure relate to detecting and mitigating errors associated with software pull requests (PRs). Other embodiments may be described or claimed.

Abstract: Methods and systems are provided for implementing session synchronization to synchronize applications at different user systems (e.g., mobile device, laptop, desktop, tablet) of a particular user. This platform level solution can maintain session information received any number of different user systems of the particular user and share this collective session information with each of the other user systems as session-synchronization information that can be used, at any user system of that user, to ensure that when that user switches from using one user system to another user system that applications at the “new” user system being switched to are synchronized with any other applications that were most recently in use at all of the other user systems of that user.

Abstract: An intelligent transcription and automated record generation system and method are provided in which a record identification module can identify, based on call data from a video call, a record in a customer relationship management (CRM) database that is relevant to the video call. An image recognition and video extraction module can process a video stream that includes video information from the video call to extract relevant portions of the video information that are relevant to the record as extracted video information. A record updater module can automatically modify the record at the CRM database to include at least part of the extracted video information as part of the record.

Abstract: Methods and systems are provided for providing an insights page. When data identifying a party of a call is received, a customer relationship management (CRM) application can be launched at a computing device without any further user input, and records that are potentially relevant to the call and that are to potentially be included as part of an insights page of the CRM application can be automatically determined. Some of the records are automatically determined by analyzing CRM information using artificial intelligence technologies. The records can then be ranked in a priority order according to relevance from most relevant to least relevant. The insights page can then be caused to be displayed at a user interface of the computing device without user input with at least some of the records displayed in the priority order as relevant records.

Abstract: Methods and systems are provided for providing an insights page that is displayed at a user interface of a computing device in response to a call. The caller who is making a call and/or the callee that is receiving the call can be identified along with one or more relevant organizations. A customer relationship management (CRM) application can then be launched at the computing device, and relevant records that are relevant to the call can be automatically determined at a server system. The relevant records can include records that are determined to be relevant to the call from any organization that a user has access privileges to. The insights page displayed at the user interface of the computing device includes user interface elements for accessing the relevant records. Each user interface element is selectable to open a relevant record that has been determined to be relevant to the call.

Abstract: An intelligent transcription and automated record generation system and method are provided in which a record identification module can identify, based on call data from a video call, a record in a customer relationship management (CRM) database that is relevant to the video call. An image recognition and video extraction module can process a video stream that includes video information from the video call to extract relevant portions of the video information that are relevant to the record as extracted video information. A record updater module can automatically modify the record at the CRM database to include at least part of the extracted video information as part of the record.

Abstract: An intelligent transcription and automated record generation system and method are provided in which a record identification module can identify a record in a customer relationship management (CRM) database that is relevant to a call, and a voice recognition and transcription engine can process audio information from the call and transcribe voice data from the call to generate transcribed voice data. The calling party can be one or more of a caller who is making a call and a callee that is receiving the call. A record updater module can then automatically modify the record to include at least part of the transcribed voice data, and automatically add the modified record to the CRM database.

Abstract: Methods and systems are provided for implementing session synchronization to synchronize applications at different user systems (e.g., mobile device, laptop, desktop, tablet) of a particular user. This platform level solution can maintain session information received any number of different user systems of the particular user and share this collective session information with each of the other user systems as session-synchronization information that can be used, at any user system of that user, to ensure that when that user switches from using one user system to another user system that applications at the “new” user system being switched to are synchronized with any other applications that were most recently in use at all of the other user systems of that user.

Abstract: Methods and systems are provided for implementing session synchronization to synchronize applications at different user systems (e.g., mobile device, laptop, desktop, tablet) of a particular user. As will be explained in greater detail below, this platform level solution that can maintain session information received any number of different user systems of the particular user and share this collective session information with each of the other user systems as session-synchronization information that can be used, at any user system of that user, to ensure that when that user switches from using one user system to another user system that that applications at the “new” user system being switched to are synchronized with any other applications that were most recently in use at all of the other user systems of that user.

Abstract: Methods and systems are provided for implementing session synchronization to synchronize applications at different user systems (e.g., mobile device, laptop, desktop, tablet) of a particular user. As will be explained in greater detail below, this platform level solution that can maintain session information received any number of different user systems of the particular user and share this collective session information with each of the other user systems as session-synchronization information that can be used, at any user system of that user, to ensure that when that user switches from using one user system to another user system that that applications at the “new” user system being switched to are synchronized with any other applications that were most recently in use at all of the other user systems of that user.

Abstract: Ringback tone management devices, systems, and methods for supporting contacts across communication access systems are provided herein. Embodiments in the detailed description include ringback tone management devices, systems, and methods for contacts across a communication access system. As an example, the communication access system may be an enterprise access system. The embodiments provided herein allow a plurality of different client devices in the communication access system, each associated with a particular set of incoming caller identifiers, to receive a desired ringback tone. In this manner, as an example, a consistent ringback tone can be provided to the incoming caller for calls received from any of the incoming caller's communication devices based upon an incoming caller identifier. The communication access system may further include devices, systems, and methods for managing ringback tones.

Abstract: Ringtone management devices, systems, and methods for supporting contacts across communication access systems are provided herein. In one embodiment, the communication access system may be an enterprise access system. The communication access system can allow a plurality of different client devices in the enterprise access system, each associated with a particular set of incoming caller identifiers, to all be rung with an outgoing ringtone that identifies the incoming caller. In this manner, a user is provided with a consistent ringtone at each of the user's devices that identifies a particular incoming caller.

Abstract: Ringback tone management devices, systems, and methods for supporting contacts across communication access systems are provided herein. Embodiments in the detailed description include ringback tone management devices, systems, and methods for contacts across a communication access system. As an example, the communication access system may be an enterprise access system. The embodiments provided herein allow a plurality of different client devices in the communication access system, each associated with a particular set of incoming caller identifiers, to receive a desired ringback tone. In this manner, as an example, a consistent ringback tone can be provided to the incoming caller for calls received from any of the incoming caller's communication devices based upon an incoming caller identifier. The communication access system may further include devices, systems, and methods for managing ringback tones.