Abstract: A computer implemented method for scheduling a meeting includes receiving a set of input parameters as meeting constraints. The meeting input parameters include a meeting organizer attendee identifier and multiple additional meeting attendee identifiers, a duration of the meeting, and a time frame within which to schedule the meeting. Calendar data is accessed from one or more servers storing calendar data corresponding to the organizer attendee and the meeting attendees based on the respective identifiers. The accessed calendar data is processed against the received set of input parameters to identify candidate meetings. In response to no candidate meeting matching all the input parameters, at least one parameter is automatically adjusted, and new candidate meetings are identified. Candidate meeting suggestions are communicated to a meeting organizer.

Abstract: In non-limiting examples of the present disclosure, systems, methods and devices for providing cross-domain access to calendar availability are presented. A request to schedule an event may be received. The request may comprise an identity of an organizer user account, the organizer user account associated with a first domain, and an identity of an invitee user account, the invitee user account associated with a second domain. An importance level of the organizer user account to the invitee user account may be determined. A determination may be made as to whether the organizer user account has access to events in an electronic calendar associated with the invitee user account based on the importance level. One or more events that the organizer account has access to may be surfaced in an event scheduling assistant user interface associated with the organizer user account.

Abstract: In non-limiting examples of the present disclosure, systems, methods and devices for providing cross-domain access to calendar availability are presented. A request to schedule an event may be received. The request may comprise an identity of an organizer user account, the organizer user account associated with a first domain, and an identity of an invitee user account, the invitee user account associated with a second domain. An importance level of the organizer user account to the invitee user account may be determined. A determination may be made as to whether the organizer user account has access to events in an electronic calendar associated with the invitee user account based on the importance level. One or more events that the organizer account has access to may be surfaced in an event scheduling assistant user interface associated with the organizer user account.

Abstract: Techniques described herein provide contextually-aware insights into calendar events. Generally described, the techniques disclosed herein can analyze a wide variety of contextual data including, but not limited to, weather data, traffic data, location data, performance data, preference data, and scheduling data, to generate salient insights that can be automatically displayed and/or communicated to a user. Insights related to one or more calendar events may be generated in response to a discovery of a predetermined condition. A predetermined condition may be detected at the time an appointment is made or at a later time when contextual data indicates a change in one or more conditions. An insight can include a text description, an image, a graphical indicator, a generated voice, and any other suitable form of communication describing useful information regarding one or more calendar events. An insight can include ranked list of recommendations can also be displayed.

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.