METHODS AND SYSTEMS FOR BOOKING AN EVENT

• US 20150154516A1
• Filed: 12/05/2014
• Published: 06/04/2015
• Est. Priority Date: 12/02/2013
• Status: Abandoned Application

• Current Assignee: Joshua Christopher Joachim
• Original Assignee: Joshua Christopher Joachim
• Inventors: JOACHIM, JOSHUA CHRISTOPHER
• Application Number:
  US14/562,191
• Publication Number:
  US 20150154516A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 50/01 Social networking

Abstract

Embodiments disclosed herein provide systems and methods for a crowd-funding server for users to pledge to purchase tickets to an event based on a number of users that have pledged to purchase tickets for an event and the gender ratio of the users that have pledged to purchase the tickets for the event.

Claims

1. A system for crowd-funding events, the system comprising:

a profile module configured to create an account for a user on an online community;

a pledge module configured to receive a pledge to purchase a ticket to a first event, wherein the pledge to purchase the ticket to the first event is associated with the user;

an event module configured to create an entry associated with the first event, the first event including a male count, a female count, a male threshold, and a female threshold, the event module being configured to book the first event responsive to determining that the male count associated with a number of male users pledging to purchase tickets to the first event is above or equal to the male threshold and the female count associated with a number of females users pledging to purchase tickets to the first event is above or equal to the female threshold.

2. The system of claim 1, further comprising:

a group module configured to create a group of users on the online community, the group including a first number associated with male users within the group and a second number associated with female users within the group, wherein the group of users pledges to purchase tickets to the first event; and

the event module is configured to increase the male count or the female count.

3. The system of claim 2, wherein the first event includes a maximum number of males and a maximum number of females, and the event module is configured to book the first event responsive to determining the male count is above or equal to the male threshold and below or equal to the maximum number of males and the female count is above or equal to the female threshold and below or equal to the maximum number of females.

4. The system of claim 3, wherein the group is not allowed to pledge to purchase tickets to the first event when the male count would become above the maximum number of males or the female count would become above the maximum number of females.

5. The system of claim 2, wherein the event module is configured to:

create a second event, and

the pledge module is configured to receive a pledge to purchase a ticket to the second event from the group of users, wherein responsive to the second event being booked the pledge to purchase tickets to the first event associated with the group is automatically deleted, and the male count for the first event is decreased or the female count for the first event is decreased.

6. The system of claim 2, further comprising:

a waitlist module configured to place the group on a waitlist to pledge to purchase tickets to the first event responsive to determining the male count would become above a maximum number of males or the female count would become above a maximum number of females.

7. The system of claim 6, wherein the event module is configured to:

decrease the male count or the female count associated with the first event responsive to a second event being booked before the first event, wherein a second group had pledged to purchase tickets to the first event and the second event.

8. The system of claim 7, wherein the waitlist module is configured to:

remove the group from the waitlist and automatically pledge to purchase tickets to the event for the group, responsive to decreasing the male count or the female count.

9. The system of claim 6, wherein the waitlist module is configured to:

allocate a timestamp to the group responsive to placing the group on the waitlist.

10. The system of claim 9, wherein the waitlist module is configured to determine the group with the earliest timestamp responsive to decreasing the male count or the female count.

11. A method for crowd-funding events, the method comprising:

creating an account for a user on an online community;

receiving a pledge to purchase a ticket to a first event, wherein the pledge to purchase the ticket to the first event is associated with the user;

creating an entry associated with the first event, the first event including a male count, a female count, a male threshold, and a female threshold; and

booking the first event responsive to determining that the male count associated with a number of male users pledging to purchase tickets to the first event is above or equal to the male threshold and the female count associated with a number of female users pledging to purchase tickets to the first event is above or equal to the female threshold.

12. The method of claim 11, further comprising:

creating a group of users on the online community, the group including a first number associated with male users within the group and a second number associated with female users within the group, wherein the group of users pledges to purchase tickets to the first event;

increasing the male count or the female count.

13. The method of claim 12, wherein the first event includes a maximum number of males and a maximum number of females, and the method includes:

booking the first event responsive to determining that the male count is above or equal to the male threshold and below or equal to the maximum number of males and the female count is above or equal to the female threshold and below or equal to the maximum number of females.

14. The method of claim 13, further comprising:

not allowing the group to pledge to purchase tickets to the first event when the male count would become above the maximum number of males or the female count would become above the maximum number of females.

15. The method of claim 12, further comprising:

creating a second event, and

receiving a pledge to purchase a ticket to the second event from the group of users,

automatically deleting the pledge to purchase a ticket to the first event associated with the group of users responsive to the second event being booked;

decreasing the male count; and

decreasing the female count.

16. The method of claim 12, further comprising:

placing the group on a waitlist to pledge to purchase tickets to the first event responsive to determining the male count would become above a maximum number of males or the female count would become above a maximum number of females.

17. The method of claim 16, further comprising:

decreasing the male count or the female count associated with the first event responsive to a second event being booked before the first event, wherein a second group had pledged to purchase tickets to the first event and the second event.

18. The method of claim 17, further comprising:

removing the group from the waitlist; and

automatically pledging to purchase tickets to the event for the group responsive to decreasing the male and the female count.

19. The method of claim 16, further comprising:

allocating a timestamp to the group responsive to placing the group on the waitlist.

20. The method of claim 19, further comprising:

determining the group with the earliest timestamp responsive to decreasing the male count or the female count.