System and method to optimize multi-conference telephony in an internet phone system

System and method to optimize multi -conference telephony in an internet phone system

The creator of the meeting selects those users to join. They then get a summary of what users are available and who is already in conference. They have the options to:

- Pull whole conference into meeting and close other meeting.

- Pull selected users from conference (with option to inform that meetings presenter)

- Pull whole meeting into current meeting and mark as merging.

- Pull whole meeting into current meeting and mark as break (meetings split after completion).

- Provisionally pull in a whole conference with required/optional members from that conference.

Presenters can also flag their conferences so that if this incident happens they can cater for it.

- Auto detail why a user has left if pulled to another conference.

- Flag critical members of the conference, so they are pulled to another it marks the presentation finished for those left.

- Members not pulled to other conference can be flagged with possible time for current meeting to resume.

- Set the level of the importance of the meeting/attendees, to push back on being pulled into another meeting.

- If you want to allow merging of your meeting with others.

  - Flag users that you need to come back if the meeting is still ongoing. Presenters on both sides can add another level of overriding other meetings based on other settings. For example ACL, Hierarchical or Social context (business social). Optionally presenters can flag the priority of the conversation/conference (eg. mission statement within first 5 mins is mandatory).

Attendees get the following options:
- informed they are being moved to a new conference or the conference is merging.

- ETA on when conference will resume if not added and primary people are removed from current conference.

- An alert that they are needed at meeting X.

Steps of system:
Creating a Meeting.

1. Host (H1) sets the date and time. H1 may also set the meeting as a priority meeting. They can set a grace period before starting (so everyone is there/setup)

2. H1 selects the invitees. They are as usual "Required", "Optional", "FYI". While selecting the users, their free time is checked vs a meeting they are attending and if H1 meeting has priority over it. Priority is defined by Business Social context of H1 vs other hosts and the required asset.

3. For the "Required" section the H1 can also select people as critical meeting assets. This means if these people do not show then the meeting cannot continue. This can be set either person by person or a group of people, or a number of people (eg. Four out of five required to show for meeting to continue). These rules can be overlapped with each other. They can also set a lead in time. For example: Required within the first 5 mins of the meeting starting. Another option is that required assets can be weighted so that some take preference over others.

4. Invites are sent out and agreed on. The system may at any poin...