Abstract: A meeting assignment conflict, between two meetings, a, is detected, because a meeting organizer is attempting to assign a given conference room to a second meeting, when it is already assigned to a first meeting. It is determined whether a number of participants in the first meeting is small enough to be accommodated by a different conference room. If so, the first meeting is automatically reassigned to the different conference room, and the second meeting is assigned to the given conference room.

Abstract: Techniques of intelligent management of calendar items in computing systems are disclosed herein. In one embodiment, a calendar server can be configured to determine whether to accept a requested meeting utilizing a decision tree pre-configured at the server by a service provider. The decision tree contains one or more hierarchical decision nodes individually comparing one or more of parameters provided by a meeting requester to a corresponding criterion previously provided by the service provider. The calendar server can also be configured to invoke an application identified in the decision tree and provide results of the invoked application to the meeting requester in lieu of accepting the requested meeting.

Abstract: A meeting assignment conflict, between two meetings, a, is detected, because a meeting organizer is attempting to assign a given conference room to a second meeting, when it is already assigned to a first meeting. It is determined whether a number of participants in the first meeting is small enough to be accommodated by a different conference room. If so, the first meeting is automatically reassigned to the different conference room, and the second meeting is assigned to the given conference room.

Abstract: Techniques of intelligent management of calendar items in computing systems are disclosed herein. In one embodiment, a calendar server can be configured to determine whether to accept a requested meeting utilizing a decision tree pre-configured at the server by a service provider. The decision tree contains one or more hierarchical decision nodes individually comparing one or more of parameters provided by a meeting requester to a corresponding criterion previously provided by the service provider. The calendar server can also be configured to invoke an application identified in the decision tree and provide results of the invoked application to the meeting requester in lieu of accepting the requested meeting.

Abstract: Variety of approaches to manage an interaction with an organization based on a work period are described. A productivity service initiates operation(s) to manage an interaction with the organization upon determining an initial work period of the organization. Upon receiving a status update associated with an asset of the organization, a determination is made on whether the status update affects the initial work period. In response to a determination that the status update affects the initial work period, the initial work period of the organization is modified based on the status update. The modified work period is provided to a stakeholder entity.

Abstract: Variety of approaches to propagate a do not disturb state are described. A hosted service initiates operations to propagate the do not disturb state upon determining a user's state to be the do not disturb state based on receiving a direct user input or an inference from user associated data. The do not disturb state is exposed to an application consumed by a user and other application consumed by other user. The hosted service provides the application and the other application. A behavior of the application is configured based on the do not disturb state. Upon expiration of the do not disturb state, the behavior of the application is reverted.

Abstract: Techniques described herein provide mechanisms for generating contextually-aware scheduling exceptions. In some configurations, when a scheduling conflict is detected, the techniques disclosed herein can utilize contextual data from a number of resources to determine if a scheduling exception can be made. The contextual data can include preferences, such as preferences of a service provider or a customer, that define criteria and/or goals. The techniques disclosed herein prioritize customers based on the contextual data and provide different scheduling options for customers and other entities based on a priority associated with individual customers. When there is a conflict between two or more calendar events, a scheduling exception can be made for some customers and a scheduling conflict can be made for other customers depending on one or more priorities associated with the customers.

Abstract: Techniques described herein provide resource-based auto completion for data entry fields of a graphical user interface. In some configurations, the techniques disclosed herein utilize input data and contextual data from a number of resources to select and display text entry candidates for assisting users in populating one or more data entry fields. For example, the input data can include an indication of a service category or a topic and other data defining a calendar event. The contextual data can be related to service providers and customers including, data defining a prior work history between two or more entities, commute projections, scheduling conflicts, preferences, and other data, such as traffic data and weather data. Data indicating a lifetime value of a customer or provider can also be utilized to select text entry candidates.