Electronic meeting management system and an associated method of scheduling meetings

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This patent application claims priority to U.S. Provisional Patent Application Serial No. 60/369,913 filed Apr. 4, 2002.

BACKGROUND OF THE INVENTION

[0002] This invention relates to the electronic scheduling of meetings, and more particularly, to an electronic meeting management system and an associated method of scheduling meetings. The scheduling of meetings is a very time consuming administrative function. Meetings can include virtually any type of activity where people get together and have face-to-face interaction. This can encompass a wide variety of activities and events including, but not limited to, birthday parties, boy scout parties, girl scout parties, and so forth. The administrative aspect of scheduling meetings is especially difficult for meetings that occur at particular locations having a fixed amount of resources. For example, if someone desires to schedule a party at a retail establishment, this person must communicate with one of the few people trained and authorized to enter this information into the computer. If several people want to reserve a meeting, e.g., party, at the same time and place, there can be issues as to which party reserved first and when the information was entered. The customer or meeting attendee can be told that the time is free while another employee reserves the exact same date, time and location before the first employee can complete the transaction. This can be very detrimental to the relationship with that customer. One approach utilized by organizations, in an attempt to address this issue, is to obtain suggested dates and times from customers via phone or e-mail. This information is then directed to one particular designated employee. The problem with this system is that this employee is constantly involved with this function and when things are busy there can be a considerable lag between receiving an indication of interest and responding to any one particular customer. In addition, there may need to be considerable interaction between the customer and the employee if the desired location, date and time is already reserved. Moreover, although this administrative task is essential to the organization, it is very time consuming and repetitious. This makes it is very difficult for the employer to keep and retain quality employees. Furthermore, the customer is frustrated since he or she must spend a considerable time on the phone to determine all available options if the optimal facility, date and time has been already reserved.

[0003] The present invention is directed to overcoming one or more of the problems set forth above.

SUMMARY OF INVENTION

[0004] In one aspect of this invention, a computer system for managing a meeting utilizing at least one database associated with at least one processor is disclosed. This system includes an input mechanism that receives a selected facility, a selected date for the meeting, a number of people to attend the meeting, a portion of the day in which to schedule the meeting, and an output mechanism that retrieves from the database at least one available time and date for the meeting at the selected facility, wherein the input mechanism further includes receiving an input for one particular date, time and facility of the at least one retrieved time and date for the meeting at the selected facility and the output mechanism provides a confirmation of the selected date, time and facility for the meeting. Throughout this application, each database preferably, but not necessarily, includes a separate processor used in conjunction therewith, in addition to at least one processor.

[0005] In another aspect of this invention, a method for managing a meeting utilizing at least one database is disclosed. This method includes selecting a facility, selecting a date for the meeting, inputting a number of people to attend the meeting, selecting a portion of the day in which to schedule the meeting, retrieving from the database at least one available time and date for the meeting at the selected facility, selecting a particular time and date for the meeting at the selected facility, from the at least one retrieved time and date for the meeting, and receiving an output of a confirmation of a reserved meeting.

[0006] Still another aspect of this invention, a computer software interface that is capable of being connected to a database for managing a meeting is disclosed. This software interface includes an input that provides a facility selection, an input that provides a meeting date selection, an input that provides an attendance number for a meeting, an input that selects a portion of the day in which to schedule the meeting, an output that retrieves at least one available time and date for the meeting at the selected facility, an input that provides a selection of a particular time and date for the meeting at the selected facility, from the at least one retrieved time and date for the meeting, and an output that provides a confirmation of a reserved meeting.

[0007] These are merely three of the illustrative aspects of the present invention and should not be deemed an all-inclusive listing of the innumerable aspects associated with the present invention. These and other aspects will become apparent to those skilled in the art, in view of the following disclosure and accompanying drawings.

BRIEF DESCRIPTION OF DRAWINGS

[0008] For a better understanding of the present invention, reference may be made to the accompanying drawings in which:

[0009]FIG. 1 is a schematic diagram of a series of software programs and associated database of the present invention for a meeting management system and associated method of scheduling meetings;

[0010]FIG. 2 is a flowchart of a system management interface for an information and tracking system associated with the present invention;

[0011]FIG. 3 is a flowchart of a reservation (time blocking, e.g., “hibernation”) function for scheduled meetings at a selected facility associated with the present invention;

[0012]FIG. 4 is a flowchart of a meeting and facility status information system for a facility interface program associated with the present invention;

[0013]FIG. 5 is a flowchart of a meeting scheduling system that is electronically accessed via either a processor located at a kiosk at a facility or a processor electrically connected to a global communications network, e.g., Internet, associated with the present invention;

[0014]FIG. 6 is an exemplary screen display of a graphical user interface for accessing the system management interface for an information and tracking system associated with the present invention, as detailed in the flowchart of FIG. 2, by system users, e.g., employees;

[0015]FIG. 7 is an exemplary screen display of a graphical user interface for tracking a product or service order utilizing the system management interface for an information and tracking system associated with the present invention as detailed in the flowchart of FIG. 2;

[0016]FIG. 8 is an exemplary screen display of a graphical user interface for placing a new product or service order utilizing the system management interface for an information and tracking system associated with the present invention as detailed in the flowchart of FIG. 2;

[0017]FIG. 9 is an exemplary screen display of a graphical user interface for accessing an existing product or service order utilizing the system management interface through a log-in for an information and tracking system associated with the present invention as detailed in the flowchart of FIG. 2;

[0018]FIG. 10 is an exemplary screen display of a graphical user interface for viewing a listing of meeting attendees or customers that are scheduled to be present for at least one meeting, e.g., party, which is collected based on search criteria utilizing the system management interface for an information and tracking system associated with the present invention as detailed in the flowchart of FIG. 2;

[0019]FIG. 11 is an exemplary screen display of a graphical user interface for editing and viewing personal and household information regarding meeting attendees or customers, which is accessed by clicking an either a view or edit hyperlink as shown in FIG. 10;

[0020]FIG. 12 is an exemplary screen display of a graphical user interface for viewing. a listing of meeting attendees or customers and a history for each meeting utilizing the system management interface for an information and tracking system associated with the present invention as detailed in the flowchart of FIG. 2;

[0021]FIG. 13 is an exemplary screen display of a graphical user interface for editing and viewing information regarding a particular meeting utilizing the system management interface for an information and tracking system associated with the present invention as detailed in the flowchart of FIG. 2;

[0022]FIG. 14 is an exemplary screen display of a graphical user interface for inserting and editing information regarding meetings occurring at a facility, e.g., store, utilizing the system management interface for an information and tracking system associated with the present invention as detailed in the flowchart of FIG. 2;

[0023]FIG. 15 is an exemplary screen display of an automatically generated letter that either confirms or cancels, e.g., cancels, a proposed meeting utilizing the system management interface for an information and tracking system associated with the present invention as detailed in the flowchart of FIG. 2;

[0024]FIG. 16 is an exemplary screen display of a graphical user interface for accessing a reservation (time blocking, e.g., hibernation) function for scheduled meetings associated with the present invention by system users, e.g., employees, as detailed in the flowchart of FIG. 3;

[0025]FIG. 17 is an exemplary screen display of a graphical user interface for querying the reserved (blocked, e.g., hibernation) times based on the name of the particular party accessing the reservation (time blocking, e.g., hibernation) function for scheduled meetings associated with the present invention by system users, e.g., employees, as detailed in the flowchart of FIG. 3;

[0026]FIG. 18 is an exemplary screen display of a graphical user interface for querying the reserved (blocked, e.g., hibernation) times based on the previously reserved times (block-outs, e.g. hibernations) for scheduled meetings associated with the present invention by system users, e.g., employees, as detailed in the flowchart of FIG. 3;

[0027]FIG. 19 is an exemplary screen display of a graphical user interface for creating a reserved (blocked, e.g., hibernation) time for a scheduled meeting, e.g., party, associated with the present invention by system users, e.g., employees, as detailed in the flowchart of FIG. 3;

[0028]FIG. 20 is an exemplary screen display of a graphical user interface for deleting a reserved (blocked, e.g., hibernation) time for a scheduled meeting, e.g., party, associated with the present invention by system users, e.g., employees, as detailed in the flowchart of FIG. 3;

[0029]FIG. 21 is an exemplary screen display of a graphical user interface for accessing a meeting and facility status information system by a user, e.g., employee, at a facility as detailed in the flowchart of FIG. 4. This exemplary screen display of a graphical user interface includes an introduction/home page for the network accessible by employees, e.g., “Bearnet”;

[0030]FIG. 22 is an exemplary screen display of a graphical user interface for accessing meetings, e.g., parties, based on a predetermined period of time, e.g., the current week, of meetings occurring at a particular facility for a user at that facility, as detailed in the flowchart of FIG. 4;

[0031]FIG. 23 is an exemplary screen display of a graphical user interface for accessing detailed information regarding a particular meeting, e.g., party, occurring at a particular facility for a user at that facility, as detailed in the flowchart of FIG. 4;

[0032]FIGS. 24A, 24B and <b>24</b>C are an exemplary screen display of a graphical user interface for providing background information regarding scheduling a meeting, e.g., party, occurring at a particular facility by a meeting attendee or customer;

[0033]FIGS. 24D and 24E are an exemplary screen display of a graphical user interface for scheduling a meeting, e.g., party, occurring at a particular facility by a meeting attendee or customer located at that facility's computer as detailed in the flowchart of FIG. 5 including a preferred facility, a preferred date, a preferred portion of the day, a number of meeting attendees or customers and an average age of the meeting attendees or customers;

[0034]FIGS. 25A and 25B are an exemplary screen display of a graphical user interface for selecting a preferred date and time for a meeting, e.g., party, occurring at a particular facility by a meeting attendee or customer located at that facility's computer terminal, e.g., kiosk, as detailed in the flowchart of FIG. 5;

[0035]FIGS. 26A and 26B are an exemplary screen display of a graphical user interface for designating the occasion for an meeting, e.g., party, occurring at a particular facility for a meeting attendee or customer located at that facility's computer terminal, e.g., kiosk, as detailed in the flowchart of FIG. 5;

[0036]FIGS. 27A, 27B, <b>27</b>C, <b>27</b>D and <b>27</b>E are an exemplary screen display of a graphical user interface for providing additional informational input from a meeting attendee or customer regarding a meeting, e.g., party, occurring at a particular facility for a meeting attendee or customer located at that facility's computer as detailed in the flowchart of FIG. 5;

[0037]FIGS. 28A, 28B, <b>28</b>C and <b>28</b>D are an exemplary screen display of a graphical user interface for receiving confirmation of a reserved meeting, e.g., party, occurring at a particular facility by a meeting attendee or customer located at that facility's computer as detailed in the flowchart of FIG. 5;

[0038]FIG. 29 is an exemplary screen display of a graphical user interface for providing additional marketing information and contacts for a meeting attendee or customer utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. 5 for scheduling a meeting, e.g., party;

[0039]FIGS. 29A and 29B are an exemplary screen display of a graphical user interface for scheduling a meeting, e.g., party, occurring at a particular facility by a meeting attendee or customer utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. <b>5</b> including a preferred facility, a preferred date, a preferred portion of the day, a number of meeting attendees or customers and an average age of meeting attendees or customers;

[0040]FIG. 30 is an exemplary screen display of a graphical user interface for selecting a preferred date and time or an alternative date and time for a meeting, e.g., party, occurring at a particular facility by a meeting attendee or customer utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. 5;

[0041]FIG. 31 is an exemplary screen display of a graphical user interface for designating the occasion for a meeting, e.g., party, occurring at a particular facility by a meeting attendee or customer utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. 5;

[0042]FIGS. 32A, 32B and <b>32</b>C are an exemplary screen display of a graphical user interface for providing informational input from a meeting attendee or customer regarding an alternative example of a meeting, e.g., party, occurring at a particular facility for a meeting attendee or customer utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. 5;

[0043]FIGS. 33A and 33B are an exemplary screen display of a graphical user interface that provides an output of frequently-asked questions regarding the meeting, e.g., party, as well as how to schedule the meeting, e.g., party, utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. 5;

[0044]FIG. 34 is an exemplary screen display of a graphical user interface that provides an address, contact information, telephone numbers, potential food providers, with a map with directions for a selected facility that is having the meeting, e.g., party, for a meeting attendee or customer utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. 5;

[0045]FIG. 35 is an exemplary screen display of a graphical user interface that provides an input for a facility, e.g., store, to ascertain the food service providers associated with a particular facility, e.g., store, for a meeting attendee or customer utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. 5.

[0046]FIG. 36 is an exemplary screen display of a graphical user interface that provides contact information regarding the food service providers associated with a particular facility, e.g., store, selected by meeting attendee or customer through the graphical user interface shown in FIG. 35 utilizing a global computer network, e.g., Internet;

[0047]FIG. 37 is an exemplary display of a written form for providing information that can be utilized in a storybook or certificate by a meeting attendee or customer utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. 5;

[0048]FIG. 38 is an exemplary screen display of a graphical user interface for allowing the user to create invitations or thank you cards related to a meeting, e.g., party, occurring at a particular facility by a meeting attendee or customer utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. 5;

[0049]FIG. 39 is an exemplary screen display of a graphical user interface for allowing the user to provide information in order to create invitations related to a meeting, e.g., party, occurring at a particular facility by a meeting attendee or customer utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. 5;

[0050]FIG. 40 is an exemplary screen display of a graphical user interface for allowing the user to customize invitations, such as coloration and layout, related to a meeting, e.g., party, occurring at a particular facility by a meeting attendee or customer utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. 5;

[0051]FIG. 41 is an exemplary screen display of a graphical user interface for allowing the user to provide information in order to create thank you cards related to a meeting, e.g., party, occurring at a particular facility by a meeting attendee or customer utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. 5;

[0052]FIG. 42 is an exemplary screen display of a graphical user interface for allowing the user to customize thank you cards, such as coloration and layout, related to a meeting, e.g., party, occurring at a particular facility by a meeting attendee or customer utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. 5;

[0053]FIGS. 43A and 43B is an exemplary screen display of a graphical user interface for allowing the user to provide information in order to create e-mail invitations related to a meeting, e.g., party, occurring at a particular facility by a meeting attendee or customer utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. 5; and

[0054]FIG. 44 is an exemplary screen display of a graphical user interface for sending, confirming and potentially changing an e-mail invitation related to a meeting, e.g., party, occurring at a particular facility by a meeting attendee or customer utilizing a global computer network, e.g., Internet, as detailed in the flowchart of FIG. 5.

DETAILED DESCRIPTION OF THE INVENTION

[0055] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. For example, the invention is not limited in scope to the particular type of industry application depicted in the figures, a particular type of software language, or to particular conventions regarding software designations. In other instances, well-known methods, procedures, and components have not been described in detail so as not to obscure the present invention. A processor referred to herein can be a single processor or a whole series of processors. The preferred method of communication for this invention is through a global computer network, e.g., Internet, however, there are numerous mechanisms for electronic communication that might suffice for this present invention.

[0056] Referring now to the drawings, and initially to FIG. 1, which is a contextual schematic of the electronic meeting management system of the present invention that is generally indicated by numeral <b>10</b>. There is a database <b>12</b> that preferably provides access to five (5) different software programs. These software programs include a system management interface program <b>14</b>, a reservation (time blocking, e.g., hibernation) interface program <b>16</b> for a facility, a facility interface program <b>18</b>, a meeting scheduling interface program <b>20</b> accessible from a remote location utilizing a global computer network, e.g., Internet, and a meeting scheduling interface program <b>22</b> accessible from a facility, e.g., store, from a processor located at the facility's kiosk or similar type of access and display. A wide variety of electronic communication mechanisms can be utilized to link these interface programs <b>14</b>, <b>16</b>, <b>18</b>, <b>20</b> and <b>22</b> to a database <b>12</b>, with the preferred mechanism being a global computer network, e.g., Internet. The database <b>12</b> can be associated with one main processor or series of multiple processors. The separation of the functional features associated with the present invention into five (5) interface programs <b>14</b>, <b>16</b>, <b>18</b>, <b>20</b> and <b>22</b> is merely for illustration only and select features from these programs <b>14</b>, <b>16</b>, <b>18</b>, <b>20</b> and <b>22</b> can be combined, eliminated, augmented or further segregated depending on the specific application that is involved.

[0057] In the description of flowcharts, the functional explanation marked with numerals in angle brackets, &lt;nnn&gt;, will refer to the flowchart blocks bearing that number. Referring now to FIG. 2, the first step in accessing the system management interface <b>14</b>, as is also shown in FIG. 1, is for the user, e.g., employee, at a facility, e.g., store, to login into the system of the present invention &lt;<b>30</b>&gt;. As shown on the exemplary graphical interface screen display for the login function shown in FIG. 6 and generally indicated by numeral <b>31</b>, this can include an organizational logo <b>32</b>, an input for the user's, e.g., employee's, name <b>34</b>, the user's, e.g., employee's, password <b>36</b>, and a pushbutton <b>38</b> for submitting the user's, e.g., employee's, name and the user's, e.g., employee's, password to the system of the present invention. There is a disclaimer for this system that indicates that the system is for “Authorized Use Only”, which is generally indicated by numeral <b>33</b>.

[0058] The second step in the system management interface <b>14</b> is a system management main interface screen &lt;<b>40</b>&gt; as shown in FIG. 2. As shown on the exemplary graphical interface screen display shown in FIG. 7 and generally indicated by numeral <b>42</b>, this can include an organizational logo <b>44</b>, a first hyperlink for building a custom product <b>46</b>, a second hyperlink for selecting complementary items for a selected product, e.g., clothing and accessories, <b>48</b>, a third hyperlink for custom designing a product to be shipped as a gift <b>50</b>, a fourth hyperlink to a listing of select products <b>51</b>, a fifth hyperlink to a listing of limited edition products <b>52</b>, a sixth hyperlink to a specific series of products <b>54</b>, a seventh hyperlink for products that include a contribution to a charity with a purchase of each product, e.g., World Wildlife Fund, <b>55</b>, an eighth hyperlink for gift certificates <b>56</b>, a ninth hyperlink to a privacy policy associated with the system of the present invention <b>57</b> and a second logo and informational display <b>60</b>. There is a tenth hyperlink that directs the user to the system's current home page <b>62</b>, an eleventh hyperlink that provides an e-mail function <b>64</b> that directs correspondence from the user to the system of the present invention, a twelfth hyperlink that provides news to the user about the organization for the system <b>66</b> of the present invention and a thirteenth hyperlink that provides information to the user regarding a complimentary product <b>68</b>.

[0059] The first function in the system management interface <b>14</b> is an order tracking function &lt;<b>70</b>&gt; as shown in FIG. 2. This is illustrated on the exemplary graphical interface screen display <b>42</b>, shown in FIG. 7, with the selection of the “order tracking” function is generally indicated by numeral <b>71</b> and accomplished through a drop-down selector input <b>72</b>. There is a heading <b>74</b> and a logo <b>76</b> present on the interface screen display <b>42</b>.

[0060] The order number is provided by the user through a data input <b>78</b>. There is a graphical interface pushbutton input <b>80</b> for entering the order number in order to track the order associated with the order number provided in data input <b>78</b>. The graphical interface screen display <b>42</b> also includes an output for shipping/order fulfillment information <b>82</b>.

[0061] There is a second collection of hyperlinks that is generally indicated by numeral <b>90</b>. This includes a fourteenth hyperlink to a calendar feature <b>3001</b>, a fifteenth hyperlink to a listing of e-mail addresses <b>3003</b>, a sixteenth hyperlink to facility, e.g., store, locations <b>3005</b>, a seventeenth hyperlink that provides news to the user about the organization for the system of the present invention <b>3007</b>, an eighteenth hyperlink to direct the user to product safety information <b>3009</b>, a nineteenth hyperlink to direct the user to a privacy statement or policy <b>3011</b>, and a twentieth hyperlink that allows the user to contact the system of the present invention <b>3013</b>. This is in addition to general information, e.g., address, copyright, phone number, <b>83</b> regarding the organization associated with the system of the present invention.

[0062] The second function in the system management interface <b>14</b> is a product or service order creation function &lt;<b>90</b>&gt; as shown in FIG. 2. As shown on the exemplary graphical interface screen display <b>92</b> shown in FIG. 8, this includes a series of drop-down selector inputs and data inputs that are generally indicated by numeral <b>94</b>. This can include as illustrative, but nonlimiting, examples: a pushbutton input for promotional codes <b>96</b>; an input <b>98</b> for a stock keeping unit “sku” or keyword with associated pushbutton <b>100</b>; an input for a zip code to determine the closest facility, e.g., store, <b>106</b>; and an associated pushbutton <b>108</b>, a drop-down selector input for gift certificates or cards <b>107</b>; a drop-down selector input for electronic gift certificates or cards <b>107</b> that can be sent via e-mail and include a account number and a personal identification number (PIN) number; a drop-down selector input for specific products <b>110</b>; a drop-down selector input for limited edition products <b>112</b>; a drop-down selector input for a special series of products <b>114</b>; a drop-down selector input for series of products that are directed to products that include a donation to charity and/or promote important issues <b>116</b>. In addition, there can be a drop-down selector input indicating the occasion for the purchase includes a particular type of birthday celebration <b>118</b>, a drop-down selector input indicating the occasion for the purchase is that the person receiving the product is desired to get well <b>120</b>, a drop-down selector inputs indicating the occasion for the purchase is that the person receiving the product is to be congratulated <b>122</b>, and a drop-down selector input indicating the occasion for the purchase is that the person receiving the product has a new baby <b>124</b>. These are merely illustrative examples of the innumerable reasons for purchasing a product or service.

[0063] An illustrative picture of a product includes that indicated by numeral <b>131</b> with an input to provide the desired quantity <b>132</b> with a pushbutton <b>134</b> to add the product to a basket of selected items for purchase. This invention could just as easily be applied to the rendering of services by the organization of the present invention rather than the purchasing of goods.

[0064] As also shown on the exemplary graphical interface screen display <b>92</b> shown in FIG. 8, there is a series of pushbuttons that can include a first pushbutton <b>134</b> for ordering a new product or service, a second pushbutton <b>136</b> for viewing or tracking an order for a product or service, a third pushbutton <b>138</b> that directs the user to shipping information, a fourth pushbutton <b>132</b> that directs the user to a webpage for the organization associated with the system of the present invention and a fifth pushbutton <b>146</b> that directs the user to purchase additional components for the products, e.g., sound generating devices <b>146</b>. There may also be an additional pushbutton that directs the user back to the main or home page of the system associated with the present invention (not shown) as indicated by process step &lt;<b>40</b>&gt; on FIG. 2.

[0065] The third function in the system management interface <b>14</b> is a mail label generation and printing function &lt;<b>150</b>&gt; as shown in FIG. 2. As shown on the exemplary graphical interface screen display <b>92</b>, illustrated in FIG. 8, this is accomplished with a “print label” pushbutton <b>152</b>. This includes information from the following data input/outputs that includes a customer's or meeting attendee's first name input <b>154</b>, a customer's or meeting attendee's last name input <b>156</b>, a customer's or meeting attendee's home phone number input <b>158</b>, a customer's or meeting attendee's other phone number input <b>160</b>, a customer's or meeting attendee's facsimile number input <b>162</b>, a customer's or meeting attendee's e-mail address input <b>164</b>, a customer's or meeting attendee's first address line input <b>166</b>, a customer's or meeting attendee's second address line input <b>168</b>, a customer's or meeting attendee's city input <b>170</b>, a customer's or meeting attendee's state drop-down selector input <b>172</b>, a customer's or meeting attendee's zip code input <b>174</b>, and a customer's or meeting attendee's facility location name from a drop-down selector input <b>176</b>, which may include other identifying information including the state and the city for the facility.

[0066] The fourth function in the system management interface <b>14</b> is to create a new meeting attendee or customer in the system of the present invention with associated household information through input function &lt;<b>180</b>&gt; as shown in FIG. 2. As shown on the exemplary graphical interface screen display <b>92</b>, illustrated in FIG. 8, this is accomplished with a “add guest” pushbutton <b>182</b> for inputting new meeting attendees/customers or a “new call” pushbutton <b>184</b> for receiving new input from the phone call regarding a meeting attendee or customer. This includes providing information from the following, previously described, data input/outputs that includes a customer's or meeting attendee's first name input <b>154</b>, a customer's or meeting attendee's last name input <b>156</b>, a customer's or meeting attendee's home phone number input <b>158</b>, a customer's or meeting attendee's other phone number input <b>160</b>, a customer's or meeting attendee's facsimile number input <b>162</b>, a customer's or meeting attendee's e-mail address input <b>164</b>, a customer's or meeting attendee's first address line input <b>166</b>, a customer's or meeting attendee's second address line input <b>168</b>, a customer's or meeting attendee's city input <b>170</b>, a customer's or meeting attendee's state drop-down selector input <b>172</b>, a customer's or meeting attendee's zip code input <b>174</b>, and a customer's or meeting attendee's facility location name from a drop-down selector input <b>176</b>, which may include other identifying information including the state and the city for the facility.

[0067] The fifth function in the system management interface <b>14</b> is to view details of an existing order of products or services &lt;<b>200</b>&gt;, as shown in FIG. 2. As also shown on the exemplary graphical interface screen display <b>202</b>, illustrated in FIG. 9, this selection of the “view existing” function from a drop-down selector input <b>72</b>, then reveals information regarding a specific order (not shown). In this case, if after a predetermined time, the session will timeout requiring the re-inputting of the user name <b>204</b>, password <b>206</b> with a login pushbutton <b>208</b>.

[0068] The sixth function in the system management interface <b>14</b> is an input function &lt;<b>210</b>&gt; that allows a user, e.g., employee to be able to search for a meeting attendee or customer, as shown in FIG. 2. Also, as shown on the exemplary graphical interface screen display <b>212</b> shown in FIG. 10, this is accomplished with a “find guest” pushbutton <b>214</b> to find a specific meeting attendee or customer on the system of the present invention. Therefore, any information provided in the previously described data inputs that are shown on FIG. 9 can be searched independently or together to search for a particular meeting attendee or customer. This includes, but is not limited to, a customer's or meeting attendee's first name input <b>154</b>. Preferably, a customer's or meeting attendee's e-mail address can be searched through input <b>164</b>. Moreover, other input can be searched including a customer's or meeting attendee's first address line input <b>166</b>, a customer's or meeting attendee's second address line input <b>168</b>, a customer's or meeting attendee's city input <b>170</b>, a customer's or meeting attendee's zip code input <b>174</b>.

[0069] The output provided by the search is in column form is generally indicated by the seventh function &lt;<b>230</b>&gt; on FIG. 2. Also, as shown on the exemplary graphical interface screen that is generally indicated by numeral <b>212</b> in FIG. 10. This includes a column for the meeting attendee's or customer's name <b>218</b>, a column for the meeting attendee's or customer's full address <b>220</b>, and a column for the meeting attendee's or customer's phone and facsimile number <b>222</b>. Each meeting attendee or customer has an edit hyperlink <b>240</b> or a view hyperlink <b>242</b> that directs the user to the eighth and ninth functions &lt;<b>244</b>&gt; and &lt;<b>246</b>&gt;, respectively, which allows the user to either edit or view the meeting attendee's or customer's information and edit or view the meeting attendee's or customer's household information. When the edit hyperlink <b>240</b> is selected, the user is directed to the exemplary graphical interface screen that is generally indicated by numeral <b>248</b> in FIG. 11.

[0070] Under the heading of “Guest Information” <b>250</b>, where a guest is either a customer or meeting attendee, is an output for an identification number <b>252</b>, an input for a first name of the meeting attendee or customer <b>254</b>, an input for a last name of the meeting attendee or customer <b>256</b>, an input for a full name of the meeting attendee or customer <b>258</b>, an input for a nickname of the meeting attendee or customer <b>260</b>, an input for a work phone of the meeting attendee or customer <b>262</b>, an input for another phone number of the meeting attendee or customer <b>264</b>, an input for an e-mail address of the meeting attendee or customer <b>266</b>, an input for a birth date of the meeting attendee or customer <b>268</b>, a drop-down selector input of the gender of the meeting attendee or customer <b>270</b>, a drop-down selector input for the language of the meeting attendee or customer <b>272</b>, a drop-down selector input for whether or not an e-mail can be sent to this meeting attendee or customer <b>274</b>, and a pushbutton input to update information <b>276</b> and a pushbutton input to print a label <b>278</b> directed to this meeting attendee or customer.

[0071] Under the heading of “household information” <b>280</b> is an output for an identification number <b>282</b>, an input for a first line of an address for the household of the meeting attendee or customer <b>284</b>, an input for a second line of an address for the household of the meeting attendee or customer <b>286</b>, an input for a city for the household of the meeting attendee or customer <b>288</b>, a drop-down selector input for the state for the household of the meeting attendee or customer <b>290</b>, an input for a zip code for the household of the meeting attendee or customer <b>292</b>, an input for a home phone for the household of the meeting attendee or customer <b>294</b>, an input for a facsimile number for a household of the meeting attendee or customer <b>296</b>, a drop-down selector input for whether or not mail can be sent to this guest or customer <b>298</b>, a pushbutton input to create a new household for a meeting attendee or customer <b>300</b> and a pushbutton input to update household information for a meeting attendee or customer <b>302</b>.

[0072] Also, as shown on the exemplary graphical interface screen that is generally indicated by numeral <b>216</b> in FIG. 10, the view hyperlink <b>242</b> also directs the user to a tenth function &lt;<b>310</b>&gt; on FIG. 2, which is a listing of all scheduled meetings or events for that particular meeting attendee or customer, which is generally indicated by numeral <b>312</b> on FIG. 12. There is a first column that includes a date and time for the meeting or event, e.g., party, <b>314</b> where every entry, e.g., specific meeting or event date and time such as that indicated by the numeral <b>315</b>, is a hyperlink to an edit screen that is generally indicated by numeral <b>350</b> on FIG. 13. The second column on the exemplary graphical interface screen <b>312</b>, illustrated in FIG. 12, is a description of the meeting <b>316</b>, e.g., “in-store party” indicated by numeral <b>317</b>. The third column on the exemplary graphical interface screen <b>318</b>, illustrated in FIG. 12, is a representation, e.g., numerical, of a meeting attendee or customer indicated by numeral <b>319</b>. The fourth column on the exemplary graphical interface screen <b>312</b>, illustrated in FIG. 12, is the date and time that comments regarding a meeting, e.g., party, are inputted into the system <b>320</b>, e.g., “Jan. 27, 2002, 12:29:27 PM”, which is indicated by numeral <b>321</b>. Finally, the fifth column on the exemplary graphical interface screen <b>212</b>, illustrated in FIG. 12, is for comments regarding a particular meeting, e.g., party, <b>322</b>, e.g., “Created New Party <b>323</b>.” Examples of comments for the meeting can include “cancellation”, “time changes”, “reactivation”, and so forth.

[0073] Under the first column that includes a date and time for the meeting <b>314</b> where every entry, e.g., the entry indicated by numeral <b>315</b>, is a hyperlink to an edit screen that is generally indicated by numeral <b>350</b> on FIG. 13, which is the eleventh function &lt;<b>351</b>&gt; on FIG. 2. There is an output for an identification number for a particular meeting, e.g., party, <b>360</b>, an output number for a facility, e.g., store identification information, e.g., number, <b>362</b>, an input for a starting date and time <b>364</b>, an input for an ending date and time <b>366</b>, a drop-down selector input for the occasion <b>368</b>, an input for the status of a particular meeting attendee or customer, e.g., guest of honor, <b>370</b>, an input for the age of the selected meeting attendee or customer, e.g., guest of honor, <b>372</b>, an input for the number of meeting attendees or customers, e.g., guests, <b>374</b>, an input for the price per meeting attendee or customer, e.g., guest, <b>376</b>, an input for an average age for most of the meeting attendees or customers, e.g., guests, <b>378</b>.

[0074] For the received deposit, the amount that will be spent on the meeting is provided in input <b>380</b>, a drop-down selector input is provided for the type of payment <b>382</b>, a drop-down selector input is provided for the reason as to why a deposit is not required <b>384</b>, an input for the date of an invoice for a deposit <b>386</b> is provided as well as an input for the number of an invoice for the deposit <b>388</b>.

[0075] For an actual refund that is issued, the amount of the refund is provided in input <b>390</b>, the date the refund is issued is provided in input <b>392</b>, the number of the invoice for the refund is provided in input <b>394</b> and the type of refund that is issued is provided in input <b>396</b>. There is a scroll-down data field input <b>398</b> for any new comments that are associated with the meeting or a refund of a deposit.

[0076] There is a click-on input <b>400</b> to cancel the meeting, e.g., party. A listing of comments associated with a particular meeting, e.g., party, <b>402</b> is displayed, which includes a first column for the date and time the comment is entered <b>404</b>, a second column for the name of the user, e.g., employee, that entered the comment <b>406</b>, a third column for the scope of the comment <b>408</b>, e.g., facility or store, and a fourth column that is the text of the comment <b>410</b>.

[0077] The right side of the edit screen that is generally indicated by numeral <b>350</b> on FIG. 13 includes a click-on indication as to whether that person has attended a meeting in the past or merely went to a facility without attending a meeting <b>412</b>, a click-on indication as to whether all meeting attendees or customers would be utilizing a product or service <b>414</b>. There is a drop-down selector input for a group that the meeting attendee or customer is a member <b>416</b> as well as input for a particular organization that the meeting attendee or customer is a member <b>418</b> and an input for an identification number input <b>420</b>. Moreover, there is an input for a tax identification number for the specific organization <b>422</b>. There is a click-on input as to whether a discount form <b>424</b> is required, an input for the percentage of discount that has been approved <b>426</b> and an input for a promotional code <b>428</b>. There is a drop-down selector input <b>430</b> to indicate the origination of the request, e.g., store, for the meeting <b>430</b>. There is a pushbutton <b>432</b> that saves the information on this edit screen <b>350</b>. In addition, there is pushbutton <b>434</b> that allows the user to printout a confirmation letter. As shown on the exemplary graphical interface screen that is generally indicated by numeral <b>480</b> in FIG. 15, the user can generate form letters to cancel or confirm meetings as shown by the twelfth function &lt;<b>482</b>&gt; on FIG. 2.

[0078] Also, from the main interface screen &lt;<b>40</b>&gt;, as shown in FIG. 2, the system user can view meetings by facility, e.g., store through the thirteenth function &lt;<b>450</b>&gt; and this same screen can allow the user to add a new meeting through the fourteenth function &lt;<b>452</b>&gt; by clicking on an open time. The exemplary graphical interface screen display is shown in FIG. 14 and is generally indicated by numeral <b>454</b>, this includes a drop-down selector input for the time period or portion of the day for each meeting displayed <b>456</b>, and an output for the specific facility name <b>458</b>, e.g., store, that is displayed. There is a column for the time <b>460</b>, and a column for each day of the week Sunday <b>462</b>, Monday <b>464</b>, Tuesday <b>466</b>, Wednesday <b>468</b>, Thursday <b>470</b>, Friday <b>472</b> and Saturday <b>474</b>, respectively. By clicking on an open time that has the word “new” such as that indicated by numeral <b>476</b>, a new meeting can be inputted by the user, e.g., employee. As indicated by the meeting listed by numeral <b>455</b>, double booking of a facility may be permitted as an optional feature.

[0079] Referring now to FIG. 3, the first step in reserving a facility, which is otherwise described as a time blocking function, e.g., “hibernation”, for a meeting, e.g., party, is for the user, e.g., administrator, to login into the facility reservation interface program <b>16</b> of the present invention &lt;<b>500</b>&gt;, as is also shown in FIG. 1. As shown on the exemplary graphical interface screen display for the login function shown in FIG. 16 and generally indicated by numeral <b>502</b>, this includes an organizational logo <b>504</b>, an input for the employee's or user's name <b>506</b>, an input for the employee's or user's password <b>508</b>, and a pushbutton <b>510</b> for submitting the employee's or user's name and the employee's or user's password to this software function of the system associated with the present invention. There may be an optional disclaimer to emphasize the fact that the facility reservation interface program <b>16</b> is for “Authorized Use Only” as indicated by numeral <b>509</b>.

[0080] The second step in the time blocking function for a meeting, e.g., hibernation, interface program <b>16</b> is a main interface screen &lt;<b>512</b>&gt; as shown in FIG. 3. As shown on the exemplary graphical interface screen display in FIG. 17 and generally indicated by numeral <b>514</b>, this includes an optional organizational logo and trademark <b>516</b>, a first hyperlink for going to a home page <b>518</b>, a second hyperlink to going to a “help desk” type of function <b>520</b> for assistance with the system of the present invention, a third hyperlink for directing the user, e.g., employee, to a feedback function <b>522</b> regarding the system of the present invention and a fourth hyperlink for directing the user, e.g., employee, to a search function <b>524</b> of the system of the present invention.

[0081] There is an output for a date for a meeting that is generally indicated by numeral <b>526</b>. There is a click-on input <b>528</b> to indicate that a single date is desired to be reserved (blocked-out, e.g., hibernation) for a meeting as well as a date input <b>530</b> for typing in a particular date or a calendar input function <b>532</b> that converts a selected date on a graphical representation of a calendar to a date that is automatically fed into the date input <b>530</b>. There is a click-on input <b>534</b> to indicate that a range of dates are desired to be reserved (blocked-out, e.g., hibernation) for meetings as well as a starting date input <b>536</b> for typing in a particular starting date or a calendar input function <b>538</b> that converts a selected date on a graphical representation of a calendar to a date that is automatically fed into the starting date input <b>536</b> as well as a ending date input <b>540</b> for typing in a particular ending date or a calendar input function <b>542</b> that converts a selected date on a graphical representation of a calendar to a date that is automatically fed into the ending date input <b>540</b>.

[0082] There is an output for a time to reserve (block-out, e.g., hibernate) for a meeting that is generally indicated by numeral <b>544</b>. There is a click-on input <b>546</b> to indicate the earliest operating start time when the facility, e.g., store can be reserved for a meeting, e.g. party, and by a click-on input <b>548</b> for a specific time when a facility, e.g., store is reserved (blocked-out, e.g., hibernation). There is a drop-down selector input <b>550</b> for inputting this specific starting time to indicate when the facility, e.g., store is reserved. There is a click-on input <b>552</b> to indicate the closing time or latest time a facility, e.g., store can be reserved for a meeting or a click-on input <b>554</b> for a specific time when a facility, e.g., store can no longer be reserved or “blocked-out.” There is a drop-down selector input <b>556</b> for inputting this specific ending time when a facility, e.g., store, is no longer reserved or blocked-out, e.g. hibernating.

[0083] There is an output to indicate the specific facilities, e.g., stores, that are to be blocked out or reserved, e.g. hibernating, for a meeting, e.g., party, that is generally indicated by numeral <b>561</b>. There is a first click-on input <b>560</b> to indicate that a single facility, e.g., store, is to be blocked-out or reserved, e.g., hibernating. There is a drop-down selector input <b>566</b> for finding a listing of facilities, e.g., stores. There is a second click-on input <b>562</b> for reserving or “blocking-out”, e.g., hibernating, a group of facilities, e.g., stores, with an associated drop-down selector input <b>568</b> that identifies specific groupings of facilities, e.g., stores. Finally, there is a third click-on input <b>564</b> that allows the user to reserve or “block-out” all of the facilities simultaneously. There is an input <b>570</b> for providing a description involving the reasons for the reservation or blocking-out, e.g., “hibernation”, of the facility, e.g., store.

[0084] As shown on the exemplary graphical interface screen display shown in FIG. 17 and generally indicated by numeral <b>580</b>, there is a listing of all meetings, e.g., parties, for the selected dates, times and facilities, e.g., stores, based on a user query which is the function described in the third process step &lt;<b>600</b>&gt;, on FIG. 3, based on clicking a “view parties” pushbutton <b>578</b> as shown on FIG. 17. This output listing <b>580</b> is arranged in columns including a facility, e.g., store, number <b>582</b>, a facility, e.g., store, name <b>584</b>, a city where the facility, e.g., store, is located <b>586</b>, a state where the facility, e.g., store, is located <b>588</b>, the start time for the meeting, e.g., party, <b>590</b>, the end time for the meeting, e.g., party, <b>592</b>, the type of meeting, e.g., party, <b>594</b> and the number of guests or attendees for the meeting, e.g., party <b>596</b>.

[0085] As shown on the exemplary graphical interface screen display shown in FIG. 18 and generally indicated by numeral <b>581</b>, there is a listing of all reserved times or blocked-out time periods, e.g., hibernations, for the selected dates, times and facilities, e.g., stores based on a user query which is the function described in the fourth process step &lt;<b>602</b>&gt;, on FIG. 3, based on clicking a “view hibs” (view hibernations otherwise known as block-outs or reservations) pushbutton <b>576</b> as shown on FIG. 18. This listing <b>580</b> is arranged in columns including a number for a facility, e.g., store, <b>582</b>, a name for a facility, e.g., store, <b>584</b>, a city where the facility, e.g., store, is located <b>586</b>, a state where the facility, e.g., store, is located <b>588</b>, the start time for the meeting, e.g., party, <b>590</b>, the end time for the meeting, e.g., party, <b>592</b>, the type of meeting, e.g., party <b>594</b> and the number of guests or attendees for the meeting, e.g., party <b>596</b>. If the “view hibs” (view hibernations otherwise known as block-outs or reservations) pushbutton <b>576</b> is selected, the number of attendees or guests should equal zero (0). This occurs when the facility, e.g., store, is closed for parties, but open for another purpose, e.g., retail sales.

[0086] The exemplary graphical interface screen display shown in FIG. 19 that is generally indicated by numeral <b>606</b>, provides the function for the user to create a reservation or a blocking-out of a facility(s), e.g., store(s) based on a function described in the fifth process step &lt;<b>608</b>&gt;, in FIG. 3, based on clicking a “hibernation” pushbutton <b>574</b>, as shown on FIG. 19. There is a graphical output indicating that the process for reserving or blocking-out a facility or facilities has commenced and when it is completed <b>610</b>.

[0087] The exemplary graphical interface screen display shown in FIG. 20 that is generally indicated by numeral <b>614</b>, provides the function for the user to cancel or delete a reservation or a blocking-out of a facility(s), e.g., store(s) based on a function described in the sixth process step &lt;<b>612</b>&gt;, in FIG. 2, based on clicking a “delete hib” or “delete hibernation” pushbutton <b>572</b>, as shown on FIG. 20. There is a graphical output indicating that the process for removing the reservation or blocking-out of a facility or facilities has commenced and when it is completed <b>616</b>.

[0088] Referring now to FIGS. 1 and 4, an interface utilized by a user at a particular facility, e.g., store, is generally indicated by numeral <b>18</b>. As shown in FIG. 4 in process step &lt;<b>701</b>&gt; and on the exemplary graphical user interface shown on FIG. 21, the first functional graphical interface screen display allows the user at a particular facility, e.g., store, to be able to obtain pertinent information as to the operation of the facility, e.g., store, as generally indicated by numeral <b>700</b>. As shown on FIG. 21, there is a series of hyperlinks that provide access for the user, e.g., employee, to a variety of informational features including, but not limited to, organizational news <b>708</b>, a customer experience survey <b>710</b>, organizational performance data <b>712</b>, communication cards to other users, e.g., employees <b>714</b>, special product listings <b>715</b>, coupon utilization <b>716</b>, product or service locator <b>718</b>, common or preferred forms utilized by the organization associated with the system of the present invention <b>720</b>, calendar of meetings, e.g., parties, for the organization <b>722</b>, planograms or graphical representations of organizational data <b>724</b>, cash register closing information and monetary data <b>726</b>, organizational reports <b>728</b>, technical auditing functions <b>730</b>, a system troubleshooting function <b>732</b> associated with the system of the present invention and an user, e.g., employee, contact for assistance <b>734</b>.

[0089] An illustrative, but nonlimiting, feature found on the exemplary graphical interface screen display <b>700</b> shown on FIG. 21, includes product distribution information that is generally indicated by numeral <b>740</b>. This includes an estimated time of arrival for a shipment of product(s) or service(s) <b>742</b>, an outslip number associated with that particular shipment <b>744</b> and a bill of lading number <b>746</b> that is also associated with that particular shipment. There is a pushbutton <b>748</b> that allows the user, e.g., employee, to view all distribution information with an output for all pending outslips that the facility user is tracking <b>750</b>.

[0090] Another illustrative, but nonlimiting, feature found on the exemplary graphical interface screen display <b>700</b> shown on FIG. 21, allows the user, e.g., employee, at a particular facility, e.g., store, to view pertinent organizational news <b>752</b>. This includes a pushbutton <b>754</b> that allows the user to view all organizational news associated with the organization for the system of the present invention.

[0091] Yet another illustrative, but nonlimiting, feature found on the exemplary graphical interface screen display <b>700</b> shown on FIG. 21, allows the user at a particular facility, e.g., store, to view all meetings, e.g., parties, scheduled at a particular facility <b>760</b>. There is a first pushbutton that allows the user to view all meetings, e.g., parties, scheduled for a predetermined time period, e.g., the current week, <b>762</b> and second pushbutton to print-out to view all meetings, e.g., parties, scheduled for another predetermined time period, e.g., today, <b>764</b>. There is a hyperlink <b>766</b> to view all recent changes to the currently scheduled meetings, e.g., parties.

[0092] Still another illustrative, but nonlimiting, feature found on the exemplary graphical interface screen display <b>700</b> shown on FIG. 21, allows the user at a particular facility, e.g., store, to view an operational hint or receive advice utilized in operating the facility, e.g., store, <b>768</b>. There is a pushbutton <b>770</b> that allows the user to view all operational hints located on the system associated with the present invention.

[0093] It is another illustrative, but nonlimiting, feature found on the exemplary graphical interface screen display <b>700</b> shown on FIG. 21, allows the user at a particular facility, e.g., store, to access a variety of forms <b>772</b> that are listed in a series of hyperlinks. Illustrative, but nonlimiting, examples include gift certificate reports <b>774</b>, employee reviews <b>776</b>, employee bonus calculations <b>778</b>, and so forth.

[0094] Upon clicking of the pushbutton <b>762</b> takes the user to the screen that is generally indicated by numeral <b>780</b> on FIG. 22, which is also indicated by second process step &lt;<b>702</b>&gt; on FIG. 4. On the exemplary graphical interface screen display <b>780</b>, as shown in FIG. 22, there is a graphical representation of a calendar for a predetermined time period, e.g., month <b>782</b>. Underneath this calendar <b>782</b> is a heading <b>784</b> that lists a particular facility name, e.g., store. This may also include the location and/or grouping for the facility. There is a table of scheduled meetings, e.g. parties, which is generally indicated by numeral <b>801</b>. From left to right, there is a column for the time in predetermined increments or portions of the day <b>786</b>, e.g., one (1) hour, and the days of the week including Sunday <b>788</b>, Monday <b>790</b>, Tuesday <b>792</b>, Wednesday <b>794</b>, Thursday <b>796</b>, Friday <b>798</b> and Saturday <b>800</b>. If meetings, e.g., parties, are scheduled on a particular day at a particular time period, there is a hyperlink, e.g., <b>802</b>, which provides some basic information and then allows the user, e.g., employee, to hyperlink to obtain additional information. This basic information may include the number of attendees, average age of attendees, type of meeting, e.g., party. Under the table of scheduled meetings <b>801</b>, there is a second heading <b>804</b> that also, like the first heading <b>784</b>, lists the particular facility, e.g., store. At the bottom of this exemplary graphical interface screen display <b>780</b> is a listing of new meetings, e.g., parties, that have been recently scheduled that is generally indicated by numeral <b>805</b>. There is a column with an indication and logo that the scheduled meeting, e.g., party, is newly scheduled <b>806</b>, a column of hyperlinks that lists the date and time for each scheduled meeting, e.g., party, <b>808</b> that directs the user, e.g., employee to additional information, a column for the primary attendee or customer attending the scheduled meeting, e.g., party, <b>810</b>, a column for information regarding the scheduled meeting, e.g., party, such as the number of people attending as well as average age of the attendees <b>817</b>, and a column for the type of event or meeting, e.g., birthday party, <b>814</b>. There is an additional column <b>815</b> to alert the user, e.g., employee, that an event or meeting is cancelled <b>815</b>.

[0095] When any of the numerous hyperlinks for additional information, e.g., <b>802</b>, <b>808</b> and so forth, are clicked, the system directs the user to detailed information regarding a scheduled meeting, e.g., party, such as that generally indicated by numeral <b>820</b> on the exemplary graphical user interface shown on FIG. 23 as well as the fourth process step &lt;<b>704</b>&gt; on FIG. 4.

[0096] Examples of the type of information found on this additional information screen <b>820</b> can include an identification number of the particular scheduled meeting, e.g., party, <b>822</b>, the starting date and time for the scheduled meeting, e.g., date, <b>824</b>, the occasion for the particular scheduled meeting, e.g., party, <b>826</b>, the contact name for the particular scheduled meeting, e.g., name, <b>828</b>, the contact's address for the particular scheduled meeting, e.g., party, <b>830</b>, the home phone number for the contact for the particular scheduled meeting, e.g., party, <b>832</b>, the work phone number for the contact for the particular scheduled meeting, e.g., party, <b>834</b>, the designated guest of honor for the particular scheduled meeting, e.g., party, <b>836</b>, the gender of the guest of honor for the meeting, e.g., party <b>837</b>, an indication as to whether the meeting, e.g., party, is a surprise <b>839</b>, the number of guests for the particular scheduled meeting, e.g., party, <b>838</b>, the price per guest for the particular scheduled meeting, e.g., party, <b>840</b>, the age of most guests for the particular scheduled meeting, e.g., party, <b>842</b>, the amount of deposit for the scheduled meeting, e.g., party, <b>844</b> and the payment type for deposit, <b>846</b> associated with the particular scheduled meeting, e.g., party, the amount of refund issued <b>848</b>, the date the refund was issued <b>850</b>, an invoice number associated with a refund <b>852</b>, the type of refund provided <b>854</b>, a data entry field for a new comment <b>856</b>, the name of the organization having the particular scheduled meeting, e.g., party, <b>858</b>, the identification number for the organization having the particular scheduled meeting, e.g., party, <b>860</b>, the tax identification number for the organization having the particular scheduled meeting, e.g., party, <b>862</b>, an output as to whether a discount form is needed <b>864</b>, an output as to a percentage of discount that is approved by the organization associated with the system of the present invention <b>866</b> and an output for a promotional code <b>868</b>.

[0097] There is a pushbutton input <b>870</b> to save any newly inputted information. Also, there is a listing of comments <b>872</b> on the bottom of this exemplary graphical user interface screen <b>820</b>. This includes a column for the date <b>874</b>, the user, e.g., employee, who created the comment <b>876</b> and the text of the comment <b>878</b>.

[0098] Referring now to FIG. 5, the actual scheduling of a meeting, e.g., party, by a customer can be accomplished by at least two, illustrative but nonlimiting methods. The first method is to make the reservation at a processor located at a kiosk at the facility, e.g., store, which is a software program indicated by numeral <b>22</b> on FIG. 1. The second method is through a processor that is electrically connected to global computer network, e.g., Internet, which is a software program indicated by numeral <b>20</b> on FIG. 1.

[0099] As shown in FIGS. 24A, 24B, <b>24</b>C, there is first a graphical user interface that is generally indicated by numeral <b>6100</b> and provides meeting, e.g., party, background planning information regarding the scheduling of a meeting, e.g., party, <b>6102</b>. This is also indicated as process step &lt;<b>1109</b>&gt; on FIG. 5. As before, there is the pushbutton <b>910</b> that allows the meeting attendee or customer to return to a main graphical user interface. This graphical user interface screen <b>6100</b> can also be accessed from hyperlink <b>6740</b> on FIG. 29. As shown in FIG. 24C, there is a first hyperlink to schedule a meeting, e.g., party, <b>6104</b>, a second hyperlink to obtain ancillary services, e.g., food service, for the meeting, e.g., party, <b>6106</b>. There is also a third hyperlink that also allows the user to schedule a meeting, e.g., party, <b>6108</b> and also provides a phone number to accomplish this same task. Again, the feature that may be present is a listing of marketing information that lists the Internet website, e.g., www.buildabear.com, for the organization as well as promotes other services or features provided by the organization <b>6110</b>.

[0100] As shown in FIGS. 24D and 24E, the first step in the process for scheduling a meeting, e.g., party by a meeting attendee or customer at a computer located at a kiosk at the facility, e.g., store, as shown in FIG. 5 by process step &lt;<b>900</b>&gt;, is through an exemplary graphical user interface that is generally indicated by numeral <b>902</b>. There is a hyperlink that directs the meeting attendee or customer to frequently asked questions regarding the system <b>904</b>. This directs the user to the exemplary graphical interface shown on FIGS. 33A and 33B that is generally indicated by numeral <b>2400</b>. There is explanatory material regarding the scheduling process provided as output that is indicated by numeral <b>906</b>. There is a pushbutton <b>910</b> that allows the meeting attendee or customer to return to a main graphical user interface.

[0101] As shown in FIG. 24E, there is a drop-down selector input <b>914</b> for inputting a specific facility, e.g., store. There is an input <b>916</b> for providing the desired date for the meeting, e.g., party. There is a pushbutton <b>918</b> that allows the customer or meeting attendee to go to a calendar and select a particular date, which is then fed into the date input <b>916</b>.

[0102] As also shown in FIG. 24E, there is a click-on input <b>920</b> for desired portions of the day, e.g., daytime, afternoon or evening. There is an input <b>922</b> for the number of people who will attend the meeting, e.g., party, and an input <b>924</b> for the average age of the people who will attend the meeting, e.g., party. Once this information is inputted, there is a “continue” pushbutton <b>926</b> that performs a function &lt;<b>901</b>&gt;, as shown on FIG. 5, to query available meetings, e.g., parties, and reserve at least one date and time for a meeting, e.g., party, as pending as well as directing the meeting attendee or customer to the next stage in the process. Another feature that may be present is a listing of marketing information that lists the Internet website, e.g., www.buildabear.com, for the organization as well as promotes other services or features provided by the organization <b>6110</b>.

[0103] As shown in FIG. 29, there is a graphical user interface that is generally indicated by numeral <b>6310</b> that can provide information (general or specific) regarding a potential meeting, e.g., party <b>6312</b>. This is also indicated by process step &lt;<b>1101</b>&gt; on FIG. 5. Moreover, there is a hyperlink that directs the customer to frequently asked questions <b>1024</b>, <b>1018</b> regarding the system that is indicated by process step &lt;<b>1100</b>&gt; on FIG. 5. This directs the user to the exemplary graphical user interface screen generally indicated by numeral <b>2400</b> as shown on FIGS. 33A and 33B to provide the written output information in question and answer format <b>2401</b>.

[0104] In addition, there are a series of hyperlinks that are generally indicated by numeral <b>1101</b> on FIG. 5. As shown in FIG. 29, there is a hyperlink <b>1021</b> for obtaining food service that is indicated by process step &lt;<b>1102</b>&gt; on FIG. 5, hyperlink <b>1019</b> for providing invitations to the meeting, e.g., party, that is indicated by process step &lt;<b>1106</b>&gt; on FIG. 5, a hyperlink <b>1020</b> for providing thank-you cards for the meeting, e.g., party, that is indicated by process step &lt;<b>1104</b>&gt; on FIG. 5 and a hyperlink <b>1022</b> for planing a story or certificate, e.g., birth certificate, that can be utilized in conjunction with the meeting, e.g., party, by a customer utilizing a global computer network, e.g., Internet that is indicated by process step &lt;<b>1108</b>&gt; on FIG. 5. This story or certificate involves the inputting of data fields that are outputted within text files to provide a customized story or certificate. There is also a hyperlink that directs the user to information regarding the scheduling of a meeting, e.g., party, &lt;<b>1109</b>&gt;, which is shown by graphical user interface <b>6100</b> shown on FIGS. 24A, 24B and <b>24</b>C. This can be in the form of a process checklist for planning a meeting, e.g., party.

[0105] Referring now to FIGS. 29A and 29B, the first step in the process for scheduling a meeting, e.g., party, by a meeting attendee or customer at a computer on a global computer network, e.g., Internet, as shown in FIG. 5 by process step &lt;<b>900</b>&gt;, is through an exemplary graphical user interface that is generally indicated by numeral <b>1000</b>. This process step is virtually identical to that performed by a meeting attendee or customer at a computer located at a kiosk at the facility, e.g., store. There is explanatory material regarding the scheduling process provided as output that is indicated by numeral <b>1002</b> that is identical to the explanatory material regarding the scheduling process provided as output that is indicated by numeral <b>906</b> in FIG. 24D.

[0106] There is a drop-down selector input <b>1004</b> for inputting a specific facility, e.g., store that is identical to drop-down selector input <b>914</b> shown on FIG. 24E. There is an input <b>1006</b> for providing the desired date for the meeting, e.g., party, that is identical to input <b>916</b> shown on FIG. 24E. There is a pushbutton <b>1008</b> that allows the meeting attendee or customer to go to a calendar and select a particular date, which is then fed into the input <b>1006</b> that is identical to pushbutton <b>918</b> shown on FIG. 24E. There is a click-on input <b>1010</b> for desired portions of the day, e.g., daytime, afternoon or evening, that is identical to click-on input <b>920</b> shown on FIG. 24E. There is an input <b>1012</b> for the number of people who will attend the meeting, e.g., party, and an input <b>1014</b> for the average age of the people who will attend the meeting, e.g., party, that is identical to inputs <b>922</b> and <b>924</b> shown on FIG. 24E. Once this information is inputted, there is a “continue” pushbutton <b>1016</b> that performs a function &lt;<b>901</b>&gt;, as shown on FIG. 5, to query available meetings, e.g., parties, and reserve at least one meeting, e.g., party, as pending as well as directing the user to the next stage in the process that is identical to the “continue” pushbutton <b>926</b> shown on FIG. 24E.

[0107] In addition, at the top of the exemplary graphical interface screen <b>1000</b>, shown on FIG. 29A, is a exemplary logo <b>1030</b>, a hyperlink for purchasing products <b>1032</b>, a hyperlink <b>1034</b> for directs to this same graphical interface screen <b>1000</b> for scheduling a meeting, e.g., party, a hyperlink for gift certificates, gift cards and e-mail gift cards <b>6200</b>, a hyperlink for gift items <b>6201</b>, a hyperlink for purchasing products <b>1038</b>, a hyperlink for obtaining complementary products <b>6202</b>, a hyperlink for ancillary product-related activity, e.g., computer games, screen savers, cards, contests, e-mails and other associated activities, <b>1036</b>, a hyperlink to looking at all of the customer, e.g., guest services for facilities, e.g. locations, <b>1040</b>, a hyperlink for all employment opportunities for the organization <b>1042</b> associated with the system of the present invention and a hyperlink that directs the user to a graphical user interface (not shown) that provides general information about the organization <b>1046</b> associated with the system of the present invention. There is an additional hyperlink <b>6602</b> to the organization's home page. There are also a series of hyperlinks that complement the meeting, e.g., party, scheduling functions generally indicated by numeral <b>6750</b>. There is a first hyperlink <b>6744</b> that directs the user to the to the graphical user interface that is generally indicated by numeral <b>6310</b> that can provide information (general or specific) regarding a potential meeting, e.g., party <b>6312</b>, as shown in FIG. 29. A second hyperlink <b>6742</b> directs the user to this same graphical interface screen <b>1000</b> for scheduling a meeting, e.g., party. A third hyperlink <b>6740</b> directs the user to the graphical user interface that is generally indicated by numeral <b>6100</b> and provides meeting, e.g., party, background planning information regarding the scheduling of a meeting, e.g., party, <b>6102</b>, as shown in FIGS. 24A, 24B, and <b>24</b>C. A fourth hyperlink <b>6760</b> for providing invitations to the meeting, e.g., party, that is indicated by process step &lt;<b>1106</b>&gt; on FIG. 5, as well as for providing thank-you cards for the meeting, e.g., party, that is indicated by process step &lt;<b>1104</b>&gt; on FIG. 5. There is a fifth hyperlink <b>1021</b> for obtaining foodservice that is indicated by process step &lt;<b>1102</b>&gt; on FIG. 5. A sixth hyperlink <b>1022</b> is for planning a story or certificate, e.g., birth certificate, that can be utilized in conjunction with the meeting, e.g., party, by a customer utilizing a global computer network, e.g., Internet that is indicated by process step &lt;<b>1108</b>&gt; on FIG. 5. There are two graphical interface hyperlinks <b>6702</b> and <b>6704</b> that allow shopping for products or services online and determine the location of facilities, e.g., stores, respectively.

[0108] In addition, there are hyperlinks to additional features. This can include a hyperlink <b>6706</b> to another graphical user interface screen (not shown) that illustrates to the user what goods or services are purchased in a shopping basket so that a user can see what has been purchased and check-out or keep shopping. Another hyperlink <b>6710</b> is an e-mail function that directs the user to a graphical user interface screen (not shown) to either subscribe or unsubscribe to an e-mail list to receive information from the organization associated with the system. Still another hyperlink <b>6710</b> is to a “wish list” that directs the user to go to a graphical user interface screen (not shown) that allows user to list desired goods or services so that others can purchase for them as a gift or some other purpose. There is also a “help” hyperlink <b>6712</b> that directs the user to a graphical user interface screen (not shown) that allows the user to obtain technical assistance in utilizing the system.

[0109] Referring now to FIG. 25A, the next step in the process for a customer at a computer located at a kiosk at the facility, e.g., store, is to schedule a meeting, e.g., party, as shown in FIG. 5 by process step &lt;<b>1200</b>&gt;, is through an exemplary graphical user interface that is generally indicated by numeral <b>929</b>, is that the available times for the meeting, e.g., party, are displayed on an exemplary graphical user interface that is generally indicated by numeral <b>910</b>. The desired date and time can be selected through click-in inputs that are shown by numerals <b>920</b>, <b>922</b>, <b>924</b>, <b>926</b>, <b>928</b> and <b>930</b>, respectively, with the date and time associated with click-on input <b>932</b> selected in this illustrative, but nonlimiting, example.

[0110] Referring now to FIG. 25B, which is the bottom portion of the same graphical user interface screen shown in FIG. 25A, the desired date and time is unavailable so that the user can view alternative times and dates, as shown by process step &lt;<b>1200</b>&gt; in FIG. 5 is through an exemplary graphical user interface that is generally indicated by numeral <b>929</b>. There is instructive verbiage regarding this feature that is generally indicated by numeral <b>934</b>. There are a series of click-on inputs where examples include seven days earlier with the same desired time range <b>938</b>, the previous day with the same desired time range <b>940</b>, the next day with the same desired time range <b>942</b>, and another time range for the same desired day <b>944</b>. Any of a wide variety of mathematical offsets can be utilized with this feature. There is a pushbutton <b>946</b> for continuing the process once an alternative, click-on input is selected and another pushbutton <b>948</b> to quit the process. Again, the feature that may be present is a listing of marketing information that lists the Internet website, e.g., www.buildabear.com, for the organization as well as promotes other services or features provided by the organization <b>950</b>.

[0111] As shown in FIG. 30, the next step in the process for scheduling an meeting, e.g., party, by a customer at a computer on a global computer network, e.g., Internet, as shown in FIG. 5 by process step &lt;<b>1200</b>&gt;, is through an exemplary graphical user interface that is generally indicated by numeral <b>1400</b>. This process step is virtually identical to that performed by a meeting attendee or customer at a computer located at a kiosk at the facility, e.g., store. The available times for the meeting, e.g., party, are displayed is on an exemplary graphical user interface, that is generally indicated by numeral <b>1402</b>, where the desired date and time can be selected by click-in inputs that are shown by numerals <b>1404</b>, <b>1406</b>, <b>1408</b>, <b>1410</b>, <b>1412</b>, <b>1414</b>, <b>1416</b>, <b>1418</b>, with the date and time associated with click-on input <b>1404</b> selected in this illustrative, but nonlimiting, example. There is a pushbutton <b>1420</b> that directs the user to the next step in the process <b>1420</b>. Also, alternative dates and times can be selected as generally indicated by numeral <b>1430</b>. There is instructive verbiage regarding this feature that is generally indicated by numeral <b>1431</b>. There are a series of click-on inputs where examples include seven days earlier with the same desired time range <b>1432</b>, seven days later with the same desired time range <b>1434</b>, the previous day with the same desired time range <b>1436</b>, the next day with the same desired time range <b>1437</b>, and another time range for the same desired day <b>1438</b>. Any of a wide variety of mathematical offsets can be utilized with this feature. There is a pushbutton <b>1440</b> for continuing the process once an alternative, click-on input is selected and another pushbutton <b>1442</b> to quit the process.

[0112] If a particular date and time for the meeting, e.g., party, cannot be selected as determined by the query found in process step &lt;<b>1201</b>&gt;, the process returns to process step &lt;<b>900</b>&gt;, as shown in FIG. 5 to allow the meeting attendee or customer to re-input desired dates and times. If a particular date and time for the meeting, e.g., party, can be selected as determined by the query found in process step &lt;<b>1201</b>&gt;, shown in FIG. 5, by the meeting attendee or customer at a computer located at a kiosk at the facility, e.g., store, then the system is directed to the exemplary graphical user interface that is generally indicated by numeral <b>940</b> on FIGS. 26A and 26B, which is also indicated as process step &lt;<b>1202</b>&gt; on FIG. 5. This process step releases dates and times for meetings, e.g., parties, that were not selected and the date and time <b>942</b>, the location <b>944</b>, the number of people attending the meeting, e.g., party, <b>946</b> and the average age of the people attending the meeting, e.g., party, <b>948</b> is outputted. There is a drop-down selector input <b>950</b> for the purpose or type of meeting, e.g., party. There is a pushbutton <b>952</b> that directs the user to the next step in the process. There is also a pushbutton <b>954</b> for starting the process over and a pushbutton <b>955</b> for quitting or cancelling the process.

[0113] Also, if a particular date and time for the meeting, e.g., party, cannot be selected as determined by the query found in process step &lt;<b>1201</b> &gt;, the process returns to process step &lt;<b>900</b>&gt;, as shown in FIG. 5 for the meeting attendee or customer utilizing a processor that is electrically connected to a global computer network, e.g., Internet to allow the meeting attendee or customer to re-input desired dates and times. If a particular date and time for the meeting, e.g., party, can be selected as determined by the query found in process step &lt;<b>1201</b>&gt;, shown in FIG. 5, by the meeting attendee or customer at a processor located at located on an global computer system, e.g., Internet, is directed to the exemplary graphical user interface indicated by numeral <b>1500</b> on FIG. 31, which is also indicated as process step &lt;<b>1202</b>&gt; on FIG. 5. This process step releases dates and times for meetings, e.g., parties, which were not selected. The date and time <b>1502</b>, the location <b>1504</b>, the number of people attending the meeting, e.g., party, <b>1506</b>, and the average age of the people attending the meeting, e.g., party, <b>1508</b>. There is a drop-down selector input for the purpose of indicating the type of meeting, e.g., girl scout, boy scout, birthday party, <b>1510</b>. There is a pushbutton <b>1520</b>, which directs the user to the next step in the process. There is also a pushbutton <b>1530</b> for starting the process over and a pushbutton <b>1540</b> for quitting or canceling the process. There is a printed disclaimer regarding a refundable deposit <b>1524</b>.

[0114] Upon selection of a particular type of meeting, e.g., party, the meeting attendee or customer at a computer located at a kiosk at the facility, e.g., store is directed to the exemplary graphical user interface that is generally indicated by numeral <b>1600</b> on FIGS. 27A, 27B and <b>27</b>C, which is also indicated as process step &lt;<b>1204</b>&gt; on FIG. 5. As shown in FIG. 27A, there is a listing of information including contact information, additional information regarding the meeting, e.g., party, as well as customer service information and a deposit <b>1602</b>. The selected date and time for the meeting, e.g., party, is displayed as indicated by numeral <b>1604</b>. The selected location for the meeting, e.g., party, is displayed as indicated by numeral <b>1606</b> on FIG. 27B. There is a statement of website location <b>1608</b> for going to a map of the location of the facility, e.g., store. This directs the meeting attendee or customer to the exemplary screen display indicated by numeral <b>2000</b>, as shown on FIG. 34. There is an output for the number of meeting attendees or customers who will attend the meeting, e.g., party, <b>1610</b> and an output for the average age of the meeting attendees or customers who will attend the meeting, e.g., party, as indicated by numeral <b>1612</b>. The occasion of the meeting, e.g., party, is indicated by numeral <b>1614</b>, e.g., birthday party, girl scout party, boy scout party, and so forth. For the “birthday party” example on FIG. 27B, the guest of honor's name is provided in input <b>1615</b> and the age of the guest of honor is provided in input <b>1617</b>.

[0115] There is an input for the approximate price to be paid for each guest at the meeting, e.g., party, as indicated by numeral <b>1620</b> on FIG. 27B. The first name of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1622</b>. The last name of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1624</b> on FIG. 27C. The e-mail address of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1626</b>. The daytime phone number of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1628</b>. The evening phone number of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1630</b>. A first address line of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1632</b> and a second address line of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1634</b>. The city of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1636</b>. A drop-down selector input for the state of the person reserving the meeting, e.g., party, is provided as indicated by numeral <b>1638</b>. The postal zip code of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1640</b>. The logos from credit or debit card companies that are accepted for providing a deposit is indicated by numeral <b>1642</b> on FIG. 27C. There is an input for a credit or debit card number <b>1644</b> followed by a expiration month <b>1646</b> and expiration year <b>1648</b> for the credit card as shown on FIG. 27C, respectively.

[0116] There is an input for a promotional code <b>1650</b> from an e-mail, direct mail or coupon as shown on FIG. 27D, respectively. There is also a request for additional customer service information from the customer. Examples include a click-on input regarding as to whether the customer has ever been to a facility, e.g., store <b>1652</b>, a click-on input as to whether all meeting attendees or customers attending the meeting, e.g., party, will be purchasing products <b>1654</b>. There is an input <b>1655</b> to indicate the number of meeting attendees or customers purchasing products when the number is less than all of the customers attending a particular meeting, e.g., party.

[0117] There is a click-on input <b>1656</b> shown on FIG. 27E, which is for whether or not the customer would like to be placed on a mailing list. There is also a click-on input <b>1658</b>, which is for whether or not the customer would like to be placed on an e-mail list. There is a pushbutton <b>1660</b> that directs the user to the confirmation page. There is also a pushbutton to start the process over as indicated by numeral <b>1662</b> and a pushbutton to quit or cancel the process as shown by numeral <b>1664</b>. The contact information and deposit can be received in the store electronically. There is an icon or emblem <b>1661</b> that indicates that this is a secure website. The information may be encrypted utilizing 128-bit encryption technology such as that provided by VERISIGN®. VERISIGN® is a federally registered trademark of Verifone, Inc., having a place of business at 4988 Great America Parkway, Santa Clara, Calif. 95054. An example of a type of organization that utilizes VERISIGN® encryption technology to receive credit or debit card payments is www.surepay.com, operated by SurePay L. P., having a place of business at 225 Broad Hollow Road, Melville, N.Y. 11746. Another illustrative, but nonlimiting, feature may include a drop-down input <b>1659</b> so that the user, e.g., customer, can indicate how he or she heard about the system associated with the present invention.

[0118] Another illustrative, but nonlimiting example of another type of meeting is that a party for a scout troop. Upon selection of this particular type of meeting, e.g., scout troop party, the customer or meeting attendee at a computer that is connected to a global computer network, e.g., Internet, is directed to the exemplary graphical user interface that is generally indicated by numeral <b>1800</b> on FIG. 32A, which is also indicated as process step &lt;<b>1204</b>&gt; on FIG. 5. This step provides an output of information regarding the reservation process <b>1802</b> on FIG. 32A. The selected date and time for the meeting, e.g., party, is displayed as indicated by numeral <b>1804</b>. The selected location for the meeting, e.g., party, is displayed as indicated by numeral <b>1806</b>. There is a hyperlink <b>1808</b> for going to a map of the location of the facility, e.g., store. This directs the meeting attendee or customer to the exemplary screen display indicated by numeral <b>2000</b>, as shown on FIG. 34. There is an output for the number of meeting attendees or customers who will attend the meeting, e.g., party, <b>1810</b> and an output for the average age of the meeting attendees or customers who will attend the meeting, e.g., party, as indicated by numeral <b>1812</b>. The occasion of the meeting, e.g., party, is indicated by numeral <b>1814</b>, e.g., scout troop meeting. As also shown on FIG. 32A, the council for the scout troop is provided in a drop-down selector input <b>1816</b> and the scout troop identification number is provided in input <b>1818</b>. There is verbiage regarding tax exempt status <b>1819</b> and an address to mail verification of tax exempt status indicated by numeral <b>1817</b> on FIG. 32B.

[0119] There is an input for the approximate price to be paid for each guest at the meeting, e.g., party, as indicated by numeral <b>1820</b> on FIG. 32B. The first name of the person reserving the meeting, e.g., party is provided by the input as indicated by numeral <b>1822</b>. The last name of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1824</b>. The e-mail address of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1826</b>. The daytime phone number of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1828</b>. The evening phone number of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1830</b>. A first address line of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1832</b> and a second address line of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1834</b>. The city of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1836</b>. A drop-down selector input for the state of the person reserving the meeting, e.g., party, is provided as indicated by numeral <b>1838</b>. The postal zip code of the person reserving the meeting, e.g., party, is provided by the input as indicated by numeral <b>1840</b>. The logos from credit or debit card companies that are accepted for providing a deposit is indicated by numeral <b>1842</b>. There is an input for a credit or debit card number <b>1844</b>. There is a drop-down selector input <b>1846</b> for inputting the month for the credit card expiration date and a drop down input <b>1848</b> for the year of the credit card expiration date. There is an input for a promotional code <b>1850</b>. There is also a request for additional customer service information from the customer. Examples include a click-on input regarding as to whether the customer has ever been to a facility, e.g., store, <b>1852</b> shown on FIG. 32B, a click-on input as to whether all meeting attendees or customers attending the meeting, e.g., party, will be purchasing products <b>1854</b> shown on FIG. 32C. There is a drop-down selector input <b>1855</b> to indicate the number of meeting attendees or customers purchasing products when the number is less than all of the customers attending a particular meeting, e.g., party.

[0120] There is a click-on input <b>1856</b>, which is for whether or not the customer would like to be placed on a mailing list. There is also a click-on input <b>1858</b>, which is for whether or not the customer would like to be placed on an e-mail list. There is a pushbutton <b>1860</b> that directs the user to the confirmation page. Another illustrative, but nonlimiting, feature may include a drop-down input <b>1859</b> so that the user, e.g., customer, can indicate how he or she heard about the system associated with the present invention. There is a hyperlink icon <b>1861</b> representing the provider of encryption technology, e.g., VERISIGN®. This will direct the user to specific information regarding the security provided by the organization associated with the system of the present invention. This information may be encrypted utilizing 128-bit encryption technology such as that provided by VERISIGN®. VERISIGN® is a federally registered trademark of Verifone, Inc., having a place of business at 4988 Great America Parkway, Santa Clara, Calif. 95054. An example of a type of organization that utilizes VERISIGN® encryption technology to receive credit or debit card payments is www.surepay.com, operated by SurePay L. P., having a place of business at 225 Broad Hollow Road, Melville, N.Y. <b>1174</b>.

[0121] There is also a pushbutton to start the process over as indicated by numeral <b>1862</b> and a pushbutton to quit or cancel the process as shown by numeral <b>1864</b>, as shown on FIG. 32C. This process step is shown on FIG. 5 by numeral &lt;<b>1206</b>&gt;. There is a query as to whether this credit or debit card information is rejected as process step &lt;<b>1207</b>&gt;. If the answer to the query is affirmative, the process returns to process step &lt;<b>1204</b>&gt; and if the answer to the query is negative, the process goes to display a confirmation of the meeting, e.g., party &lt;<b>1208</b>&gt;.

[0122] Upon the clicking of the pushbutton <b>1660</b> on FIG. 27E or pushbutton <b>1860</b> on FIG. 32C, the customer at a computer located at a kiosk at the facility, e.g., store is directed to the exemplary graphical user interface that is generally indicated by numeral <b>2100</b> on FIGS. 28A, 28B, <b>28</b>C and <b>28</b>D, which is also indicated as process step &lt;<b>1208</b>&gt; on FIG. 5 to receive a confirmation of the reservation of the meeting, e.g., party. This includes an indication that the meeting, e.g., party, has been confirmed <b>2102</b> that that an additional e-mail confirmation may be received by the user without any additional confirmation. An additional phone number is provided as shown in FIG. 28A. An e-mail confirmation is listed on FIG. 5 as process step &lt;<b>1210</b>&gt;.

[0123] Referring now to FIG. 28B, additional verbiage on the meeting, e.g., party may be provided <b>2103</b>. The details regarding the date and time of the meeting, e.g., party, <b>2104</b>, the location of the meeting, e.g., party, <b>2106</b> and the occasion for the meeting, e.g., party including the name of the guest of honor and the guest of honor's age <b>2108</b>.

[0124] Referring now to FIG. 28C, the user, e.g., customer who has booked the meeting, e.g., party, is listed along with his or her address, work phone number, home phone numbers and e-mail address including indication that a confirmation e-mail was sent to that e-mail address.

[0125] This is followed by an invoice <b>2112</b> that indicates a credit card charge has been made with the number of guests and the price limit per guest.

[0126] Referring now to FIG. 28D, additional information is provided <b>2113</b> including, but not limited to, the deductibility of the deposit from the expenses of the meeting, e.g., party is listed as well as information as how to cancel the meeting, e.g., party, including time limits and contact phone numbers. The method of payment and information regarding stamps/coupons can also be provided. There may be additional marketing information <b>2117</b> that lists the Internet website, e.g., www.buildabear.com, for the organization as well as promotes other services or features provided by the organization such as invitations, cards, food suppliers, location maps, and so forth.

[0127] The feature of finding the location of a facility, e.g., store, that may be optimal for the meeting or event, which is accessible through hyperlink <b>6704</b> on FIG. 31 includes inputting desired states or zip codes, providing an output of facilities, e.g., stores in that area. One of the outputted facilities, e.g., stores, can be selected. This will direct the user to a graphical output screen that is generally indicated by numeral <b>2100</b> on FIG. 34. In addition to a map of the facility, e.g., store, additional information can include an address, telephone numbers, hours of operation, directions to the facility, e.g., store, potential food suppliers. The user can either book or reserve a meeting or event at this facility, e.g., store, or apply for employment through additional hyperlinks.

[0128] The feature of ascertaining food providers for a particular facility, e.g., store, location that may be optimal for the meeting or event, which is accessible through hyperlink <b>1021</b> on FIG. 31 includes a graphical user interface screen that is generally indicated by numeral <b>5100</b> on FIG. 35. There is some written information regarding the use of food providers that is generally indicated by numeral <b>5102</b>. This is followed by a drop-down input <b>5104</b> that allows the user to select a particular facility, e.g., store. The user than clicks on a graphical user interface pushbutton to go to the graphical user interface screen indicated by numeral <b>5200</b> on FIG. 36. This provides a listing of potential food providers/suppliers for a particular facility, e.g., store <b>5202</b>. This includes a column that lists the particular food providers <b>5210</b>, a column of contact personnel associated with each food provider <b>5212</b> and a column of phone numbers associated with each contact person <b>5214</b>. There is a graphical user interface pushbutton <b>5206</b> that allows the user to transfer back to the previous screen <b>5100</b> on FIG. 35.

[0129] The previously referenced hyperlink <b>1022</b>, as shown in FIG. 31, for planing a story or certificate, e.g., birth certificate, that can be utilized in conjunction with the meeting, e.g., party, by a customer utilizing a global computer network, e.g., Internet that is indicated by process step &lt;<b>1108</b>&gt; on FIG. 5. The user is directed to a screen that allows the user to printout a form that is generally indicated by numeral <b>7102</b> on FIG. 37. There is an line for a customer or guest name <b>7104</b>, a line for the customer's or guest's address <b>7106</b>, a line for the customer's or guest's city <b>7108</b>, a line for the customer's or guest's state <b>7110</b>, a line for the customer's or guest's zip code <b>7112</b>, a line for the customer's or guest's date of birth <b>7106</b> and a line for the customer's or guest's e-mail address <b>7116</b>. This information can be utilized to create a personalized story or certificate for the guest or customer.

[0130] The previously reference hyperlink <b>6760</b>, as shown on FIG. 31, for providing invitations to the meeting, e.g., party, that is indicated by process step &lt;<b>1106</b>&gt;, on FIG. 5, as well as for providing thank-you cards for the meeting, e.g., party, that is indicated by process step &lt;<b>1104</b>&gt;, on FIG. 5, directs the user to the graphical user interface that is generally indicated by numeral <b>4000</b> on FIG. 38. This graphical user interface screen <b>4000</b> includes instructional verbiage <b>4050</b> and well as a graphical user interface pushbutton <b>4070</b> to obtain additional help or assistance.

[0131] There is a first hyperlink <b>4010</b> and a second hyperlink <b>4030</b> that directs the user to a graphical user interface screen for generating invitations for a meeting or event, e.g., birthday party. Although each hyperlink <b>4010</b> and <b>4030</b> directs the user to a different graphical design, one illustrative, but nonlimiting, example includes the graphical user interface screen <b>8100</b>, shown on FIG. 39, that provides an input for the guest of honor for the meeting, e.g., party <b>8102</b> and the type of meeting, e.g., birthday party <b>8104</b>. There is a graphical user interface pushbutton <b>8106</b> that allows the user to create invitations by directing the user to the graphical user interface screen indicated by numeral <b>8110</b> on FIG. 40. On graphical user interface screen <b>8110</b>, there is a graphical user interface pushbutton <b>8120</b> to obtain instructions regarding creation of invitations, a color palette <b>8118</b> for coloring the invitations, a graphical user interface pushbutton <b>8121</b> for determining the form of the invitation <b>8113</b> that allows the user to select a full page invitation <b>8112</b>, a quarter fold invitation with one pet page <b>8114</b> and invitation postcards with four per page <b>8116</b>. The invitation can be made all white by clicking on the graphical user interface pushbutton <b>8122</b>. There is also the ability to start the coloring process over by the user clicking on the graphical user interface pushbutton <b>8124</b>.

[0132] There is a third hyperlink <b>4020</b> and a fourth hyperlink <b>4040</b> that directs the user to a graphical user interface screen for generating thank-you cards to individuals that have attended a meeting or event, e.g., birthday party. Although each hyperlink <b>4020</b> and <b>4040</b> directs the user to a different graphical design, one illustrative, but nonlimiting, example includes the graphical user interface screen <b>8200</b>, shown on FIG. 41, that provides an input for the name of the person sending the thank you cards for attending the meeting or event, e.g., birthday party, <b>8202</b>. There is a graphical user interface pushbutton <b>8204</b> that allows the user to create thank you cards by directing the user to the graphical user interface screen indicated by numeral <b>8205</b> on FIG. 42. On graphical user interface screen <b>8205</b>, there is a graphical user interface pushbutton <b>8206</b> to obtain instructions regarding creation of thank you cards, a color palette <b>8224</b> for coloring the thank you cards, a graphical user interface pushbutton <b>8216</b> for determining the form of the thank you card <b>8208</b> that allows the user to select a full page thank you card <b>8210</b>, a quarter fold thank you card with one per page <b>8212</b> and thank you postcards with four per page <b>8214</b>. The invitation can be made all white by clicking on the graphical user interface pushbutton <b>8218</b>. There is also the ability to start the coloring process over by the user clicking on the graphical user interface pushbutton <b>8220</b>.

[0133] There is a fifth hyperlink <b>4050</b> that directs the user to a graphical user interface screen for generating e-mail invitations for a meeting or event, e.g., birthday party. Referring now to FIGS. 43A and 43B, there are two graphical user interface pushbuttons to select a design for an e-mail invitation <b>8302</b> and <b>8340</b> from a wide assortment of different designs for various occasions. On illustrative, but nonlimiting, design is indicated by numeral <b>8303</b>. There is a typed-in input <b>8306</b> for the name of the guest of honor for the meeting or event, a typed-in input <b>8307</b> for the occasion of the meeting or event, a typed-in input <b>8308</b> for a first line of a street address for the name of the guest of honor for the meeting or event, a typed-in input <b>8310</b> for a second line of a street address for the name of the guest of honor for the meeting or event, a typed-in input <b>8312</b> for a city, state and zip code for the name of the guest of honor for the meeting or event, a drop-down input <b>8314</b> for the name of the facility, e.g., store that will host the meeting or event, a typed-in input <b>8316</b> for the date of the event, a typed-in input <b>8318</b> for the time of the event, a typed-in input <b>8320</b> for the date when an indication of whether the person receiving the e-mail will be attending the meeting or event (RSVP). There is a drop-down input <b>8321</b> for the number of recipients for this particular e-mail and a drop-down input <b>8322</b> to provide the time for delivery, e.g., now or a wide selection of dates. There is an input <b>8324</b> to indicate the name of the person being invited to the meeting or event and an input <b>8326</b> to provide that person's e-mail address. There is an input <b>8328</b> to indicate the name of the person providing the invitation to the meeting or event and an input <b>8330</b> for that person's e-mail address.

[0134] There is an input to provide an additional text message <b>8332</b> that can be augmented by graphical artwork <b>8334</b>. There is a click-on input <b>8336</b> to request an indication that the e-mail card has been picked-up by a recipient and another click-on input <b>8338</b> to provide the person sending the invitation a copy of the invitation that was sent to the recipient. There are two graphical user interface pushbuttons <b>8304</b> and <b>8342</b>, respectively, that allow the user to preview the e-mail that is being sent prior to transmission. Upon clicking on the preview function <b>8304</b> or <b>8342</b>, the user is directed to the graphical user interface screen indicated by numeral <b>8400</b> on FIG. 44. This includes information on the person sending and receiving the e-mail, transmission date, whether recipient notification information is provided to sender and whether a copy is provided to the sender. There are two graphical user interface pushbuttons <b>8404</b> and <b>8408</b>, respectively, for transmitting the e-mail and a graphical user interface pushbutton <b>8406</b> that allows the user to make changes to the e-mail prior to transmission.

[0135] Although the preferred embodiment of the present invention and the method of using the same has been described in the foregoing specification with considerable details, it is to be understood that modifications may be made to the invention, which do not exceed the scope of the appended claims and modified forms of the present invention done by others skilled in the art to which the invention pertains will be considered infringements of this invention when those modified forms fall within the claimed scope of this invention.