Abstract: A state client is configured to allow a user to specify a meeting-specific state, such as that the user is running late for a meeting, checked in to the meeting, or unable to attend the meeting. A state service stores data identifying the user's meeting-specific state. The state service also responds to requests for the state of the user. In one implementation, when such a request is received, the state service determines whether the user is an invitee to the same meeting as the user requesting the state. If not, the state service returns a general-purpose state indicator for the user. If both users are invitees to the same meeting, the state service returns the meeting-specific state indicator, which may then be displayed by a state client.

Abstract: Various technologies pertaining to instant messaging are described herein. A persistent instant messaging group is created, wherein the persistent instant messaging group comprises a plurality of members and persists over a plurality of instant messaging sessions. Instances of an instant messaging application are installed on mobile telephones, and the instant messaging application is used to transmit instant messages between members of the persistent instant messaging group. Messages directed towards offline members of the persistent instant messaging group are transmitted to such members when they come online.

Abstract: Various technologies pertaining to instant messaging are described herein. A persistent instant messaging group is created, wherein the persistent instant messaging group comprises a plurality of members and persists over a plurality of instant messaging sessions. Instances of an instant messaging application are installed on mobile telephones, and the instant messaging application is used to transmit instant messages between members of the persistent instant messaging group. Messages directed towards offline members of the persistent instant messaging group are transmitted to such members when they come online.

Abstract: A state client is configured to allow a user to specify a meeting-specific state, such as that the user is running late for a meeting, checked in to the meeting, or unable to attend the meeting. A state service stores data identifying the user's meeting-specific state. The state service also responds to requests for the state of the user. In one implementation, when such a request is received, the state service determines whether the user is an invitee to the same meeting as the user requesting the state. If not, the state service returns a general-purpose state indicator for the user. If both users are invitees to the same meeting, the state service returns the meeting-specific state indicator, which may then be displayed by a state client.

Abstract: A meeting lifecycle management service manages various aspects of a meeting lifecycle. An indication of a newly scheduled meeting is received at the meeting lifecycle management service, and information related to the meeting is managed, via the meeting lifecycle management service, prior to the meeting, during the meeting, and after the meeting.

Abstract: Architecture that facilitates the ability to trigger the capture and storing of meeting state (or context) by way of a single user interaction (a “one-click” operation), referred to herein as a bookmark operation, and then to store and access the state for subsequent use. The state is captured relative to a point of reference, such as time, user, keywords, and reference to a document, for example. Thus, all state elements such as meeting activities, participants, and content (e.g., audio, video, images, text, documents, etc.). The bookmark assigned to the state at a particular reference can be selected to rehydrate all the state elements captured and associated with that bookmark (e.g., getting back to the point in the meeting to perceive a relevant portion of a document, part of the meeting video, or other recorded feed), as well as all other allowed state elements.

Abstract: Various technologies pertaining to instant messaging are described herein. A persistent instant messaging group is created, wherein the persistent instant messaging group comprises a plurality of members and persists over a plurality of instant messaging sessions. Instances of an instant messaging application are installed on mobile telephones, and the instant messaging application is used to transmit instant messages between members of the persistent instant messaging group. Messages directed towards offline members of the persistent instant messaging group are transmitted to such members when they come online.

Abstract: A system described herein includes a receiver component that receives a request to create a persistent messaging group for an instant messaging application, wherein the request includes an indication of one or more entities that are desired to be members of the persistent messaging group. The system further includes a group creator component that creates the persistent messaging group based at least in part upon the received group creation request, wherein the persistent messaging group is persisted over multiple instant messaging sessions.

Abstract: A system described herein includes a receiver component that receives a request to create a persistent messaging group for an instant messaging application, wherein the request includes an indication of one or more entities that are desired to be members of the persistent messaging group. The system further includes a group creator component that creates the persistent messaging group based at least in part upon the received group creation request, wherein the persistent messaging group is persisted over multiple instant messaging sessions.

Abstract: A system described herein includes a receiver component that receives a request to create a persistent messaging group for an instant messaging application, wherein the request includes an indication of one or more entities that are desired to be members of the persistent messaging group. The system further includes a group creator component that creates the persistent messaging group based at least in part upon the received group creation request, wherein the persistent messaging group is persisted over multiple instant messaging sessions.

Abstract: A system described herein includes a receiver component that receives a request to create a persistent messaging group for an instant messaging application, wherein the request includes an indication of one or more entities that are desired to be members of the persistent messaging group. The system further includes a group creator component that creates the persistent messaging group based at least in part upon the received group creation request, wherein the persistent messaging group is persisted over multiple instant messaging sessions.