Event planning system

• US 20050033615A1
• Filed: 02/23/2004
• Published: 02/10/2005
• Est. Priority Date: 06/22/1999
• Status: Active Grant

• Current Assignee: Lanyon Solutions, Inc. (Cvent Incorporated)
• Original Assignee: The Active Network Incorporated (Cvent Incorporated)
• Inventors: Thackeray, Raymond, Goodrich, Adam, Chang, John, Chen, Joseph, Leong, Bruce, Nguyen, Justin T., Stanovic, Hoselito
• Granted Patent: US 8,065,171 B2
• Time in Patent Office: Days
• US Class Current: 705/5
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 10/1095 Meeting or appointment
• CPC Class Codes: G06Q 20/085 involving remote charge determination or related payment systems
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/204 comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit

Abstract

An event planning process is provided for execution by a server system in a computer network including a plurality of user terminals communicatively coupled with the server system via the network. The process includes the steps of: providing an event planning graphical user interface at a user terminal, the interface enabling a user to plan an event; receiving event information input by the user, the event information indicating a scheduled event, at least one invitee to be invited to the scheduled event, and information indicative of RSVP fees required to attend the scheduled event; providing an invitation to the invitee, the invitation indicating the scheduled event and the RSVP fees, and soliciting a response to the invitation, wherein an affirmative response to the invitation requires a payment as defined by the RSVP fees; receiving RSVP status information including payment information from the invitee; and verifying the payment information. The steps of providing an invitation to the invitee and receiving RSVP status information further include: generating an invitation Web page based on the event information, the invitation Web page being accessible via the network and being operative to provide an invitation response graphical user interface for enabling the invitee to respond to the invitation; sending an invitation message to the invitee, the invitation message prompting the invitee to view the invitation Web page; and receiving input provided by the invitee via the invitation Web page, the input provided by the invitee indicating the RSVP status information.

Claims

1. An event planning process executed by a server system in a computer network including a plurality of user terminals communicatively coupled with the server system via the network, the process comprising the steps of:

providing an event planning graphical user interface at a user terminal, the interface enabling a user to plan an event;

receiving event information input by the user said event information indicating a scheduled event, at least one invitee to be invited to said scheduled event, and information indicative of RSVP fees required to attend said scheduled event;

providing an invitation to said invitee, said invitation indicating said scheduled event and said RSVP fees, and soliciting a response to said invitation, wherein an affirmative response to said invitation requires a payment as defined by said RSVP fees;

receiving RSVP status information including payment information from said invitee; and

verifying said payment information.

2. An event planning process as recited in claim 1 wherein said step of providing an event planning graphical user interface at the user terminal includes generating at least one event planning Web page that is accessible at the user terminal via the network, said event planning Web page including embedded code for providing said event planning graphical user interface.

3. An event planning process as recited in claim 1 wherein said steps of providing an invitation to said invitee and receiving RSVP status information further comprise:

generating an invitation Web page based on said event information, said invitation Web page being accessible via the network and being operative to provide an invitation response graphical user interface for enabling said invitee to respond to said invitation;

sending an invitation message to said invitee, said invitation message prompting said invitee to view said invitation Web page; and

receiving input provided by said invitee via said invitation Web page, said input provided by said invitee indicating said RSVP status information.

4. An event planning process as recited in claim 3 wherein said step of sending an invitation message to said invitee comprises sending an Email message via the network to said invitee at a second user terminal, said Email invitation including a link to said invitation Web page.

5. An event planning process as recited in claim 3 wherein the server system is communicatively coupled with a plain old telephone system, and wherein said step of sending an invitation message to said invitee comprises sending a fax invitation message to said invitee via said telephone system, said fax invitation including a universal resource locator for accessing said invitation Web page via the network.

6. An event planning process as recited in claim 3 wherein said step of sending an invitation message to said invitee comprises sending a post card to said invitee, said post card providing a universal resource locator for accessing said invitation Web page via the network.

7. An event planning process as recited in claim 1 wherein the server system is communicatively coupled with an interactive voice response system that is connected to a plain old telephone system, said interactive voice response system being configured to enable said invitee to provide said RSVP status information in response to said invitation, and wherein said RSVP status information is received at the server system via said interactive voice response system.

8. An event planning process as recited in claim 1 wherein:

said step of providing an event planning graphical user interface at the user terminal includes a step of providing a plurality of invitation templates each being associated with a different type of event and having at least one associated graphical image;

said step of receiving event information includes receiving information indicative of a selected one of said templates; and

said step of generating an invitation Web page includes generating an invitation Web page based on said selected template, said invitation Web page displaying said associated graphical image.

9. An event planning process as recited in claim 1 wherein:

said step of providing an event planning graphical user interface at the user terminal includes providing access to an address book associated with the user, said address book including a list of contacts and associated contract addresses;

said step of receiving event information includes receiving information indicative of selected ones of said contacts; and

said step of providing an invitation includes providing invitations to said selected contacts.

10. An event planning process as recited in claim 3 wherein said step of providing an event planning graphical user interface includes prompting the user to indicate whether said scheduled event is to be listed in a public events directory, and wherein said event information indicates whether said scheduled event is to be listed in the public events directory, and further comprising the step of:

if said event information indicates that said scheduled event is to be listed in the public events directory, providing a link to said invitation Web page from a home page Web page that is accessible via the network, said invitation Web page allowing anyone who accesses said invitation Web page to RSVP for said scheduled event.

11. An event planning process as recited in claim 1 wherein said step of providing an event planning graphical user interface includes prompting the user to indicate a schedule for sending reminders to invited guests, and further comprising the step of sending reminder messages to said invitees in accordance with said schedule.

12. An event planning process as recited in claim 3 wherein:

said step of providing an event planning graphical user interface includes prompting the user to specify a question for said invitee;

said event information specifies said question;

said invitation Web page is further operative to provide invitation response graphical user interface components enabling said invitee to provide a response to said question; and

said step of receiving invitee user input via said invitation Web page includes receiving information indicative of said response.

13. An event planning process as recited in claim 12 wherein said invitation Web page is further operative to enable other invitees to view said response if the user has selected an option of enabling said other invitees to view said response.

14. An event planning process as recited in claim 3 wherein said invitation Web page is further operative to enable said invitee to view information indicating other invitees associated with the planned event, and RSVP status information associated with each of said other invitees.

15. An event planning process as recited in claim 3 wherein invitees may post messages and comments regarding the event on said invitation Web page.

16. An event planning process as recited in claim 15 wherein said user may specify that all of said posted messages and comments may be viewed only by said user.

17. An event planning process as recited in claim 3 wherein said step of providing an event planning graphical user interface includes prompting the user to indicate whether said invitee may forward said invitation to other people.

18. An event planning process as recited in claim 1 wherein said step of providing an event planning graphical user interface includes prompting the user to indicate ticket pricing information indicating a price of at least one type of ticket being offered for admission to said scheduled event, and further comprising a step of determining convenience fees to be paid to administrators of the server system based on sales of said tickets to said invitees.

19. An event planning process as recited in claim 18 wherein said event information provided by said user indicates whether said convenience fees are to be paid from proceeds of ticket sales, or whether said convenience fees are to be passed on to said invitees.

20. An event planning process as recited in claim 2 further comprising the steps of:

providing an event summary Web page to the user terminal, the event summary Web page enabling the user to select from at least one previously planned event;

receiving user input from said user via said event summary Web page, said user input indicating a selected one of the previously planned events;

generating event summary information associated with the selected event, said event summary information including RSVP status information associated with each of the invitees for selected event; and

transmitting said event summary information to said user terminal.

21. An event planning process as recited in claim 3 wherein said invitation Web page provides an invitation response graphical user interface enabling said invitee to select “

maybe”

as an said RSVP status response.

22. An event planning process as recited in claim 1 wherein said step of providing an event planning graphical user interface includes prompting the user to specify a maximum number of invitees.

23. An event planning process as recited in claim 2 further comprising the steps of:

providing an event report Web page to the user terminal, the event report Web page enabling the user to select from at least one previously planned event;

receiving user input from said user via said event report Web page, said user input indicating a selected one of the previously planned events;

generating event report information associated with the selected event, said event report information including RSVP fee status information associated with each of the invitees for selected event; and

transmitting said event report information to said user terminal.

24. An event planning process as recited in claim 18 further comprising the steps of:

providing an event report Web page to the user terminal, the event report Web page enabling the user to select from at least one previously planned event;

receiving user input from said user via said event report Web page, said user input indicating a selected one of the previously planned events;

generating event report information associated with the selected event, said event report information including RSVP fee status information and convenience fee information associated with said selected event; and

transmitting said event report information to said user terminal.

25. An event planning process as recited in claim 1 wherein each of said invitees is a member of an organization.

26. A server system operative to execute an event planning process in a computer network including a plurality of user terminals communicatively coupled with the server system via the network, the process comprising the steps of:

providing an event planning graphical user interface at a user terminal, the interface enabling a user to plan an event;

receiving event information input by the user, said event information indicating a scheduled event, at least one invitee to be invited to said scheduled event, and information indicative of RSVP fees required to attend said scheduled event;

providing an invitation to said invitee, said invitation indicating said scheduled event and said RSVP fees, and soliciting a response to said invitation, wherein an affirmative response to said invitation requires a payment as defined by said RSVP fees;

receiving RSVP status information including payment information from said invitee; and

verifying said payment information.

27. A server system as recited in claim 26 wherein said step of providing an event planning graphical user interface at the user terminal includes generating at least one event planning Web page that is accessible at the user terminal via the network, said event planning Web page including embedded code for providing said event planning graphical user interface.

28. An event planning process as recited in claim 26 wherein said steps of providing an invitation to said invitee and receiving RSVP status information further comprise:

generating an invitation Web page based on said event information, said invitation Web page being accessible via the network and being operative to provide an invitation response graphical user interface for enabling said invitee to respond to said invitation;

sending an invitation message to said invitee, said invitation message prompting said invitee to view said invitation Web page; and

receiving input provided by said invitee via said invitation Web page, said input provided by said invitee indicating said RSVP status information.

29. An event planning process as recited in claim 28 wherein said step of sending an invitation message to said invitee comprises sending an Email message via the network to said invitee at a second user terminal, said Email invitation including a link to said invitation Web page.

30. An event planning process as recited in claim 28 wherein the server system is communicatively coupled with a plain old telephone system, and wherein said step of sending an invitation message to said invitee comprises sending a fax invitation message to said invitee via said telephone system, said fax invitation including a universal resource locator for accessing said invitation Web page via the network.

31. An event planning process as recited in claim 28 wherein said step of sending an invitation message to said invitee comprises sending a post card to said invitee, said post card providing a universal resource locator for accessing said invitation Web page via the network.

32. An event planning process as recited in claim 26 wherein the server system is communicatively coupled with an interactive voice response system that is connected to a plain old telephone system, said interactive voice response system being configured to enable said invitee to provide said RSVP status information in response to said invitation, and wherein said RSVP status information is received at the server system via said interactive voice response system.

33. An event planning process as recited in claim 26 wherein:

said step of providing an event planning graphical user interface at the user terminal includes a step of providing a plurality of invitation templates each being associated with a different type of event and having at least one associated graphical image;

said step of receiving event information includes receiving information indicative of a selected one of said templates; and

said step of generating an invitation Web page includes generating an invitation Web page based on said selected template, said invitation Web page displaying said associated graphical image.

34. An event planning process as recited in claim 26 wherein:

said step of providing an event planning graphical user interface at the user terminal includes providing access to an address book associated with the user, said address book including a list of contacts and associated contract addresses;

said step of receiving event information includes receiving information indicative of selected ones of said contacts; and

said step of providing an invitation includes providing invitations to said selected contacts.

35. An event planning process as recited in claim 28 wherein said step of providing an event planning graphical user interface includes prompting the user to indicate whether said scheduled event is to be listed in a public events directory, and wherein said event information indicates whether said scheduled event is to be listed in the public events directory, and further comprising the step of:

if said event information indicates that said scheduled event is to be listed in the public events directory, providing a link to said invitation Web page from a home page Web page that is accessible via the network, said invitation Web page allowing anyone who accesses said invitation Web page to RSVP for said scheduled event.

36. An event planning process as recited in claim 26 wherein said step of providing an event planning graphical user interface includes prompting the user to indicate a schedule for sending reminders to invited guests, and further comprising the step of sending reminder messages to said invitees in accordance with said schedule.

37. An event planning process as recited in claim 28 wherein:

said step of providing an event planning graphical user interface includes prompting the user to specify a question for said invitee;

said event information specifies said question;

said invitation Web page is further operative to provide invitation response graphical user interface components enabling said invitee to provide a response to said question; and

said step of receiving invitee user input via said invitation Web page includes receiving information indicative of said response.

38. An event planning process as recited in claim 37 wherein said invitation Web page is further operative to enable other invitees to view said response if the user has selected an option of enabling said other invitees to view said response.

39. An event planning process as recited in claim 28 wherein said invitation Web page is further operative to enable said invitee to view information indicating other invitees associated with the planned event, and RSVP status information associated with each of said other invitees.

40. An event planning process as recited in claim 28 wherein invitees may post messages and comments regarding the event on said invitation Web page.

41. An event planning process as recited in claim 40 wherein said user may specify that all of said posted messages and comments may be viewed only by said user.

42. An event planning process as recited in claim 28 wherein said step of providing an event planning graphical user interface includes prompting the user to indicate whether said invitee may forward said invitation to other people.

43. An event planning process as recited in claim 26 wherein said step of providing an event planning graphical user interface includes prompting the user to indicate ticket pricing information indicating a price of at least one type of ticket being offered for admission to said scheduled event, and further comprising a step of determining convenience fees to be paid to administrators of the server system based on sales of said tickets to said invitees.

44. An event planning process as recited in claim 43 wherein said event information provided by said user indicates whether said convenience fees are to be paid from proceeds of ticket sales, or whether said convenience fees are to be passed on to said invitees.

45. An event planning process as recited in claim 27 further comprising the steps of:

providing an event summary Web page to the user terminal, the event summary Web page enabling the user to select from at least one previously planned event;

receiving user input from said user via said event summary Web page, said user input indicating a selected one of the previously planned events;

generating event summary information associated with the selected event, said event summary information including RSVP status information associated with each of the invitees for selected event; and

transmitting said event summary information to said user terminal.

46. An event planning process as recited in claim 28 wherein said invitation Web page provides an invitation response graphical user interface enabling said invitee to select “

maybe”

as an said RSVP status response.

47. An event planning process as recited in claim 26 wherein said step of providing an event planning graphical user interface includes prompting the user to specify a maximum number of invitees.

48. An event planning process as recited in claim 27 further comprising the steps of:

providing an event report Web page to the user terminal, the event report Web page enabling the user to select from at least one previously planned event;

receiving user input from said user via said event report Web page, said user input indicating a selected one of the previously planned events;

generating event report information associated with the selected event, said event report information including RSVP fee status information associated with each of the invitees for selected event; and

transmitting said event report information to said user terminal.

49. An event planning process as recited in claim 43 further comprising the steps of:

providing an event report Web page to the user terminal, the event report Web page enabling the user to select from at least one previously planned event;

receiving user input from said user via said event report Web page, said user input indicating a selected one of the previously planned events;

generating event report information associated with the selected event, said event report information including RSVP fee status information and convenience fee information associated with said selected event; and

transmitting said event report information to said user terminal.

50. An event planning process as recited in claim 26 wherein each of said invitees is a member of an organization.

51. An event planning process executed by a server system in a computer network including a plurality of user terminals communicatively coupled with the server system via the network, the process comprising the steps of:

generating at least one event planning Web page that is accessible at the user terminal via the network, said event planning Web page including embedded code for providing an event planning graphical user interface;

receiving event information input by the user, said event information indicating a scheduled event, at least one invitee to be invited to said scheduled event, and information indicative of RSVP fees required to attend said scheduled event;

providing an invitation to said invitee, said invitation indicating said scheduled event and said RSVP fees, and soliciting a response to said invitation, wherein an affirmative response to said invitation requires a payment as defined by said RSVP fees;

receiving RSVP status information including payment information from said invitee; and

verifying said payment information.