Abstract: Context information, indicative of a tenant's engagement with a multi-tenant service, is obtained. An engagement state for the tenant is determined and the context information, and engagement state, are correlated to an issue to be addressed. A user experience is conducted, based upon the likely issue to be addressed.

Abstract: Tenant engagement signals are exposed to third party systems through an application programming interface (API). The third parties acquire the signals through the API, surface them, and launch workflows based on the tenant engagement signals acquired, in order to assist the tenant in the on-boarding process.

Abstract: An issue is identified based on corresponding information indicative of steps taken in an on-boarding process and a velocity of transition through the steps. The issue is matched against an agent based on agent capabilities exposed by the agent. The issue and corresponding information are routed to the agent.

Abstract: An issue is identified based on corresponding information indicative of steps taken in an on-boarding process and a velocity of transition through the steps. The issue is matched against an agent based on agent capabilities exposed by the agent. The issue and corresponding information are routed to the agent.

Abstract: An issue is identified based on corresponding information indicative of steps taken in an on-boarding process and a velocity of transition through the steps. The issue is matched against an agent based on agent capabilities exposed by the agent. The issue and corresponding information are routed to the agent.

Abstract: An issue is identified based on corresponding information indicative of steps taken in an on-boarding process and a velocity of transition through the steps. The issue is matched against an agent based on agent capabilities exposed by the agent. The issue and corresponding information are routed to the agent.

Abstract: Context information, indicative of a tenant's engagement with a multi-tenant service, is obtained. An engagement state for the tenant is determined and the context information, and engagement state, are correlated to an issue to be addressed. A user experience is conducted, based upon the likely issue to be addressed.

Abstract: Tenant engagement signals are exposed to third party systems through an application programming interface (API). The third parties acquire the signals through the API, surface them, and launch workflows based on the tenant engagement signals acquired, in order to assist the tenant in the on-boarding process.

Abstract: An issue is identified based on context information and a state of engagement of a user. The issue is matched against an agent based on agent capabilities exposed by the agent. Feedback information is used to generate a reputation metric for the agent.

Abstract: Technologies for enabling real-time support for requests (e.g., onboarding requests, support requests, managing requests, troubleshooting requests, etc.) based at least in part on contextual data are described. The technologies described can receive a request associated with a product and/or a service and determine contextual data associated with the request. The contextual data can define a status of an application associated with the product and/or the service. Additionally, the technologies described can include determining support providers for supporting the request based partly on the contextual data and generating task data associated with the request. The task data can include the contextual data.

Abstract: Technologies for enabling support providers to integrate into a support application and provide real-time support for requests based at least partly on authorizations associated with the support providers are described. The technologies described can access authentication data associated with support providers. The technologies described can receive a request associated with a product and/or a service and determine contextual data associated with the request. The technologies described can determine authorization data associated with support providers, determine support providers for supporting the request based partly on the contextual data, determine that the support providers are authorized to receive the request, and generate task data associated with the request.

Abstract: A data store is distributed between a server and a client. The distributed data store includes global data. A transformation is applied to the global data to generate client-specific data based on the global data. The client-specific data is stored on the client which uses the client-specific data to perform tasks relating to the client-specific data.

Abstract: A data store is distributed between a server and a client. The distributed data store includes global data. A transformation is applied to the global data to generate client-specific data based on the global data. The client-specific data is stored on the client which uses the client-specific data to perform tasks relating to the client-specific data.