# US 2009/0276498 A1 · Specifying during meeting establishment when respondents are to be prompted for attendance intentions

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2009/0276498 A1
- Document ID: US20090276498A1
- Status: Published application
- Kind: A1
- Application number: 12/114,547
- Filed: 2008-05-02
- Published: 2009-11-05
- Earliest claimed: 2008-05-02
- Assignees: International Business Machines Corporation
- Inventors: RUTHIE D. LYLE; ULYSSES LAMONT CANNON
- Web page: https://patentgrep.com/patent/US20090276498A1

## CPC

- G06Q 10/109: Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A meeting initialization request for a meeting can be identified. The meeting initialization request can specify a prompt time for attendance intentions. A programmatic trigger, referred to as a prompt trigger, can be established for the prompt time. A firing of this prompt trigger can occur when a current time equals the prompt time. At this time, at least one potential attendee for the meeting can be determined. A set of potential attendees is typically defined by the meeting initiator within the meeting initialization request. An intention message can be sent to the determined potential attendee responsive to a firing of the programmatic trigger. This intention message can be sent at a time close to the prompt time. The intention message can prompt the potential attendee to indicate whether the potential attendee intends to attend the meeting.

## Claims

### Claim 1

A method for delayed meeting intention response comprising:
identifying a meeting initialization request for a meeting, wherein said meeting initialization request specifies a prompt time for attendance intentions;
establishing a programmatic trigger for the prompt time, referred to as the prompt trigger;
firing the prompt trigger when a current time equals the prompt time;
determining at least one potential attendee of the meeting; and
sending an intention message to the determined potential attendee responsive to a firing of the prompt trigger, wherein said intention message prompts the potential attendee to indicate whether the potential attendee intends to attend the meeting.

### Claim 2 (depends on 1)

The method of claim 1, wherein the meeting initialization request is received during a meeting initialization time, wherein the prompt time is a user configured time having a date and time established by a meeting initiator who completed the meeting initialization request.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
receiving user input entered into a prompt element of a user interface, wherein said user interface is one used to establish a new meeting time, a plurality of meeting participants, a meeting title, and other meeting attributes, wherein the input entered into the prompt element defines the prompt time.

### Claim 4 (depends on 1)

The method of claim 1, wherein the sending comprises at sending an email message to email addresses of at least a portion of the at least one determined potential attendees.

### Claim 5 (depends on 1)

The method of claim 1, wherein the meeting initialization request is received by meeting management software, where said meeting management software stores meeting specifics from the meeting initialization request in a data store comprising a plurality of meeting records, wherein each of said meeting record comprises a primary key for a meeting event, an attribute for meeting time, and an attribute for prompt time.

### Claim 6 (depends on 1)

The method of claim 1, wherein said meeting initialization request comprises a tally time for the meeting, said method further comprising:
establishing a programmatic trigger for the tally time, referred to as the tally trigger;
firing the tally trigger when a current time equals the tally time;
compiling metrics from a plurality of responses from potential attendees; and
creating from these compiled metrics an expected attendance report, which is made available to at least one party designated as authorized by an meeting initiator of the meeting initialization request, wherein the meeting initialization request is received during a meeting initialization time, wherein the prompt time is a user configured time having a date and time established by the meeting initiator who completed the meeting initialization request, wherein the tally time is a user configured time having a date and time established by the meeting initiator.

### Claim 7

A method for summarizing intention responses comprising:
identifying a meeting initialization request for a meeting, wherein the meeting initialization request specifies a tally time for the meeting;
establishing a programmatic trigger for the tally time;
firing the programmatic trigger when a current time equals the tally time;
compiling metrics from a plurality of responses from potential attendees; and
creating from these compiled metrics an expected attendance report, which is made available to at least one party designated as authorized by an initiator of the meeting initialization request.

### Claim 8 (depends on 7)

The method of claim 7, wherein the tally time is a user configured time having a date and time established by the meeting initiator.

### Claim 9 (depends on 7)

The method of claim 7, further comprising:
receiving user input entered into a tally element of a user interface, wherein said user interface is one used to establish a new meeting time, a plurality of meeting participants, a meeting title, and other meeting attributes, wherein the input entered into the tally element defines the tally time.

### Claim 10 (depends on 7)

The method of claim 7, further comprising:
sending the expected attendance report to the at least one party responsive to the firing of the tally trigger.

### Claim 11 (depends on 7)

The method of claim 7, wherein the meeting initialization request is received by meeting management software, where said meeting management software stores meeting specifics from the meeting initialization request in a data store comprising a plurality of meeting records, wherein each of said meeting record comprises a primary key for a meeting event, an attribute for meeting time, and an attribute for tally time.

### Claim 12 (depends on 7)

The method of claim 7, wherein said meeting initialization request comprises a prompt time for the meeting, said method further comprising:
receiving user input entered into a tally element of a user interface;
receiving user input entered into a prompt element of the user interface, wherein the user interface is one used to establish a new meeting time, a plurality of meeting participants, a meeting title, and other meeting attributes, wherein the input entered into the tally element defines the tally time, and wherein the input entered into the prompt element defines the prompt time;
establishing a programmatic trigger for the prompt time, referred to as the prompt trigger;
firing the prompt trigger when a current time equals the prompt time;
determining at least one potential attendee of the meeting; and
sending an intention message to the determined potential attendee responsive to a firing of the prompt trigger, wherein said intention message prompts the potential attendee to indicate whether the potential attendee intends to attend the meeting.

### Claim 13 (depends on 7, 8)

The method of claim 7, wherein said steps of claim 8 are steps performed automatically by at least one machine in accordance with at least one computer program having a plurality of code sections that are executable by the at least one machine, said at least one computer program being stored in a machine readable medium.

### Claim 14

A system for managing meetings that permits and establishment of at least one of a prompt time and a tally time comprising:
a meeting management software program stored in a machine usable medium configured to receive, manage, and store meeting specific information and configured to perform a plurality of programmatic actions related to the meeting specific information;
a meeting data store configured to store digitally encoded information comprising the meeting specific information used by the meeting management software program; and
a user interface of the meeting management software program comprising a meeting establishment view, said meeting establishment view comprising a plurality of interface controls for establishing specifics for a meeting, said meeting establishment view comprising a prompt time element configured to accept input defining a configurable prompt time, wherein said prompt time represents a time when potential attendees are to be presented messages to indicate whether each potential attendee intends to attend the meeting, wherein said meeting management software is configured to establish a programmatic trigger for the prompt time, referred to as the prompt trigger, and wherein the meeting management software is configured to fire the prompt trigger and is configured to perform a programmatic action related to the prompt time when a current time equals the prompt time.

### Claim 15 (depends on 14)

The system of claim 14, wherein said user interface further comprises at least one tally element, wherein the input entered into the tally element defines the tally time, wherein said tally time represent a time at which metrics from a plurality of responses from potential attendees for a meeting are to be compiled and made available to a party designated by a meeting initiator, wherein said meeting management software is configured to establish a programmatic trigger for the tally time, referred to as the tally trigger, and wherein the meeting management software is configured to fire the tally trigger and is configured to perform a programmatic action related to the tally time when a current time equals the tally time.

### Claim 16 (depends on 15)

The system of claim 15, wherein said meeting data store is configured to store a plurality of indexed database records stored in database tables, wherein one of said database tables is a meeting table that has a primary key of a meeting identifier, wherein said meeting table has an attribute defining the prompt time, and wherein said meeting table has an attribute defining the tally time.

### Claim 17 (depends on 16)

The system of claim 16, wherein the database tables are relational database management system (RDBMS) tables configured in third normal form.

### Claim 18 (depends on 14)

The system of claim 14, further comprising:
communication software stored in a machine usable medium configured to permit a user to communicate with a plurality of other users, wherein said meeting management software program and said communication software are configured to interact to automatically send messages to each potential participant of a meeting, as defined in the meeting data store, when the prompt trigger fires.
