US20200252442A1 - Systems and methods for electronic notetaking - Google Patents
Systems and methods for electronic notetaking Download PDFInfo
- Publication number
- US20200252442A1 US20200252442A1 US16/855,610 US202016855610A US2020252442A1 US 20200252442 A1 US20200252442 A1 US 20200252442A1 US 202016855610 A US202016855610 A US 202016855610A US 2020252442 A1 US2020252442 A1 US 2020252442A1
- Authority
- US
- United States
- Prior art keywords
- meeting
- bot
- conference system
- join
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
- H04L65/403—Arrangements for multi-party communication, e.g. for conferences
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
- H04L12/1818—Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/02—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail using automatic reactions or user delegation, e.g. automatic replies or chatbot-generated messages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
- H04L51/18—Commands or executable codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1083—In-session procedures
- H04L65/1093—In-session procedures by adding participants; by removing participants
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1096—Supplementary features, e.g. call forwarding or call holding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/20—Natural language analysis
- G06F40/205—Parsing
Definitions
- FIG. 1 illustrates a screen shot showing a main screen, according to an embodiment.
- FIG. 2 illustrates a meeting intelligence screen shot, according to an embodiment.
- FIG. 3 illustrates an add bot screen where a meeting ID is entered, according to an embodiment.
- FIG. 4 illustrates an add bot screen where a URL is entered, according to an embodiment.
- FIG. 5 illustrates how to indicate that a bot is “attending” and recording the meeting, according to an embodiment.
- FIG. 6 illustrates a system diagram, according to an embodiment.
- FIG. 1 illustrates a screen shot showing a main screen 100 , according to an embodiment.
- a live notes section 105 can be displayed where a user (e.g., Matt) can enter in notes while in an electronic conference system meeting (e.g., a phone meeting or an in-person meeting) is taking place. The time into the meeting is displayed along with the note created by the user at that time.
- a meeting summary section 110 can display information about the meeting, such as call duration (e.g., 1:12), the organizer (e.g., Matt), and the platform (e.g., ZOOM).
- any or all of the following platforms can be supported: WEBEX, ZOOM, GOTOMEETING, UBERCONFERENCE, JOIN.ME.
- any other current conferencing platform or any future conferencing platform can also be used.
- a currently viewing section 115 can comprise the participants (e.g., Matt, Abby, Ryland).
- a tag section 120 can comprise any or all of the following tags which can enable a participant to tag the meeting: Budget, Negotiation, Pricing, Intro, Next Steps, Objection, Needs, Business, Outcome, Timing, and Authority.
- a tag also called “comment tag” can be pinned to an exact moment of its creation (or a moment before its creation) within the context of the recording of the meeting and designated by the user (e.g., related to Budget, related to Pricing) so that the user can easily go back and access or replay any tagged portions of the meeting.
- Those of ordinary skill in the art will see that any other type of meeting tag can be created.
- a comment tag category that can later be associated to a specific comment tag can be created, as show in the following example code:
- a comment tag with a category id associated to it can then be inserted, as illustrated in the following example code (e.g., where the timestamp is for 10 seconds ago):
- the date can be moved to a certain time period before the comment tag is created so that the beginning of the important information is captured. This time period can be 1 second-25 seconds, or even longer.
- the above example code uses an example of saving a comment with a date of 10 seconds ago.
- a user can designate a certain time period for each of the comment tags (e.g., all tags can go back 3 seconds, or the Pricing tag can go back 2 seconds, but a Budget tag can go back 10 seconds)
- FIG. 2 illustrates a meeting intelligence screen shot 200 , according to an embodiment.
- the in-progress screen 225 can show notes from in-progress meetings.
- a search box can be provided in 230 , with tabs where the user can filter the content that is searched.
- the search tabs can comprise: all 235 , comments 240 , and title 245 .
- details date, time, duration
- organizer platform
- shared shared
- invitees attendees
- other participants comments from participants, or comment tags, or any combination thereof.
- FIG. 3 illustrates a screen shot showing an add bot screen 300 , according to an embodiment.
- a bot When a bot is added, this means that a virtual participant (e.g., that is recording the call) is present.
- FIG. 5 illustrates how to indicate that a bot is “attending” and recording the meeting. In the top right corner of FIG. 5 , an icon appears showing NOTENINJA to be a participant. This indicates that the meeting is being recorded by the bot.
- a meeting platform section 305 can allow a user to enter in a platform (e.g., ZOOM) for the bot
- a meeting title section 310 can allow a user to enter in a title for the meeting (e.g., “meeting with customer”).
- a meeting ID or URL section 315 can allow the user to enter in the meeting ID or URL.
- the pseudo-code below illustrates an example of how a bot can join a meeting by URL.
- the code below illustrates how the URL the user provides is parsed in order to find details about the meeting required to join the meeting (e.g., the meeting ID) from the URL (in this example a UBERCONFERENCE platform is used, although any platform can be used):
- Any URL can be parsed to find the meeting ID.
- the following types of URLs can be parsed:
- the code below illustrates how the meeting ID can be used to join a meeting in a web browser (using, for example, nodejs webdriver bindings for a browser):
- FIG. 3 illustrates an add bot screen where a meeting ID is entered
- FIG. 4 illustrates an add bot screen where a URL is entered.
- FIG. 6 illustrates a system diagram, according to an embodiment.
- a virtual assistant bot 605 can record any meeting that uses an electronic conference system meeting.
- a user's computer 610 e.g., a SALESLOFT user using a SALESLOFT web application
- a user can be: a sales manager, an administrator, or a participant in the electronic conference system meeting, or any other person or entity that interacts with the system.
- the comment tag module can enable adding and using comment tags, as descried above.
- the add recording bot module can enable adding a virtual participant bot to record the meeting.
- the electronic conferencing system 620 can be a connector that ties the user to the meeting and also ties the virtual assistant bot to the meeting.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
- The present application is a continuation to U.S. application Ser. No. 16/524,653 filed on Jul. 29, 2019, which claims priority to U.S. provisional Ser. No. 62/713,281, filed on Aug. 1, 2018, titled “SYSTEMS AND METHODS FOR ELECTRONIC NOTETAKING.” All of the foregoing are incorporated herein by reference in their entireties.
-
FIG. 1 illustrates a screen shot showing a main screen, according to an embodiment. -
FIG. 2 illustrates a meeting intelligence screen shot, according to an embodiment. -
FIG. 3 illustrates an add bot screen where a meeting ID is entered, according to an embodiment. -
FIG. 4 illustrates an add bot screen where a URL is entered, according to an embodiment. -
FIG. 5 illustrates how to indicate that a bot is “attending” and recording the meeting, according to an embodiment. -
FIG. 6 illustrates a system diagram, according to an embodiment. -
FIG. 1 illustrates a screen shot showing amain screen 100, according to an embodiment. Alive notes section 105 can be displayed where a user (e.g., Matt) can enter in notes while in an electronic conference system meeting (e.g., a phone meeting or an in-person meeting) is taking place. The time into the meeting is displayed along with the note created by the user at that time. Ameeting summary section 110 can display information about the meeting, such as call duration (e.g., 1:12), the organizer (e.g., Matt), and the platform (e.g., ZOOM). In some embodiments, any or all of the following platforms can be supported: WEBEX, ZOOM, GOTOMEETING, UBERCONFERENCE, JOIN.ME. Those of ordinary skill will see that any other current conferencing platform or any future conferencing platform can also be used. - A currently
viewing section 115 can comprise the participants (e.g., Matt, Abby, Ryland). Atag section 120 can comprise any or all of the following tags which can enable a participant to tag the meeting: Budget, Negotiation, Pricing, Intro, Next Steps, Objection, Needs, Business, Outcome, Timing, and Authority. A tag (also called “comment tag”) can be pinned to an exact moment of its creation (or a moment before its creation) within the context of the recording of the meeting and designated by the user (e.g., related to Budget, related to Pricing) so that the user can easily go back and access or replay any tagged portions of the meeting. Those of ordinary skill in the art will see that any other type of meeting tag can be created. - To create a tag, a comment tag category that can later be associated to a specific comment tag can be created, as show in the following example code:
-
// DB library syntax inspired by knex.js database connection library const sql =‘ insert into main.comment tags (organization id, tag name) values(:organizationld, :tagName) returning id ‘; let bindParams = { organizationId, tagName }; const conn = db.getConnection( ); const newCommentTags = await conn.raw(sql, bindParams); const {id: newTagId} = newCommentTags.rows[0]; - A comment tag with a category id associated to it can then be inserted, as illustrated in the following example code (e.g., where the timestamp is for 10 seconds ago):
-
// DB library syntax inspired by knex.js database connection library // next, using the newTagId created in the snippet above conn(‘comment’).insert({ text: /* comment text */‘’, created_at_in_milliseconds: Date.now( ) - (10 * 1000), tag_id: newTagId}) - As mentioned above, when a comment tag is created, the date can be moved to a certain time period before the comment tag is created so that the beginning of the important information is captured. This time period can be 1 second-25 seconds, or even longer. The above example code uses an example of saving a comment with a date of 10 seconds ago. In some embodiment, a user can designate a certain time period for each of the comment tags (e.g., all tags can go back 3 seconds, or the Pricing tag can go back 2 seconds, but a Budget tag can go back 10 seconds)
-
FIG. 2 illustrates a meetingintelligence screen shot 200, according to an embodiment. Several types of meeting information can be accessed. The in-progress screen 225 can show notes from in-progress meetings. A search box can be provided in 230, with tabs where the user can filter the content that is searched. The search tabs can comprise: all 235,comments 240, andtitle 245. In each in-progress meeting summary that is shown in 225, the following information can be shown: details (date, time, duration), organizer, platform, shared, invitees, attendees, other participants, comments from participants, or comment tags, or any combination thereof. -
FIG. 3 illustrates a screen shot showing an add bot screen 300, according to an embodiment. When a bot is added, this means that a virtual participant (e.g., that is recording the call) is present. For example,FIG. 5 illustrates how to indicate that a bot is “attending” and recording the meeting. In the top right corner ofFIG. 5 , an icon appears showing NOTENINJA to be a participant. This indicates that the meeting is being recorded by the bot. - A meeting platform section 305 can allow a user to enter in a platform (e.g., ZOOM) for the bot, A meeting title section 310 can allow a user to enter in a title for the meeting (e.g., “meeting with customer”). A meeting ID or URL section 315 can allow the user to enter in the meeting ID or URL. The pseudo-code below illustrates an example of how a bot can join a meeting by URL. The code below illustrates how the URL the user provides is parsed in order to find details about the meeting required to join the meeting (e.g., the meeting ID) from the URL (in this example a UBERCONFERENCE platform is used, although any platform can be used):
-
const userInput = ‘https://uberconference.com/personal_meeting_example_id’; const regex = /uberconference\.comV([a-z0-9-_.]+)/i; const matches = user_nput.match(regex); const meetingId = matches[1]; - Any URL can be parsed to find the meeting ID. For example, the following types of URLs can be parsed:
- https://global.gotomeeting.com/join/456684725
- https://app.gotomeeting.com/123456789
- https://www.gotomeeting.com/join/138906133
- https://www.gotomeet.me/RickSanchezz685
- https://zoom.us/j/561755827
- https://examplecompanydomain.zoom.us/my/examplepersonatcompany
- https://www.uberconference.com/mattnoteninja123_-_-
- https://join.me/996-967-779
- https://join.me/austin609
- https://austinboondockcities.my.webex.com/join/austin
- The code below illustrates how the meeting ID can be used to join a meeting in a web browser (using, for example, nodejs webdriver bindings for a browser):
-
const driver = new webdriver.Builder( ).build( ); const url = ‘https://www.uberconference.com/${meetingId}‘; console.log(‘LOG: doing ${meetingPlatform} url: ${url}‘); driver.get(‘https://www.uberconference.com/${meetingId}‘); -
FIG. 3 illustrates an add bot screen where a meeting ID is entered, andFIG. 4 illustrates an add bot screen where a URL is entered. -
FIG. 6 illustrates a system diagram, according to an embodiment. Avirtual assistant bot 605 can record any meeting that uses an electronic conference system meeting. A user's computer 610 (e.g., a SALESLOFT user using a SALESLOFT web application) can have installed or otherwise access acomment tag module 615 and an addrecording bot module 620. Those of ordinary skill in the art will recognize that a user can be: a sales manager, an administrator, or a participant in the electronic conference system meeting, or any other person or entity that interacts with the system. The comment tag module can enable adding and using comment tags, as descried above. The add recording bot module can enable adding a virtual participant bot to record the meeting. Theelectronic conferencing system 620 can be a connector that ties the user to the meeting and also ties the virtual assistant bot to the meeting. - While the disclosure has been described with reference to numerous specific details, one of ordinary skill in the art will recognize that the disclosure can be embodied in other specific forms without departing from the spirit of the disclosure. In addition, a number of the figures illustrate processes. The specific operations of these processes may not be performed in the exact order shown and described. The specific operations may not be performed in one continuous series of operations, and different specific operations may be performed in different embodiments. Thus, one of ordinary skill in the art would understand that the invention is not to be limited by the foregoing illustrative details, but rather is to be defined by the appended claims.
- While various embodiments have been described above, it should be understood that they have been presented by way of example and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail may be made therein without departing from the spirit and scope. In fact, after reading the above description, it will be apparent to one skilled in the relevant art(s) how to implement alternative embodiments. Thus, the present embodiments should not be limited by any of the above-described embodiments.
- In addition, it should be understood that any figures or description which highlight the functionality and advantages are presented for example purposes only. The disclosed methodology and system are each sufficiently flexible and configurable such that they may be utilized in ways other than that shown. For example, any steps or limitations in the specification, figures and claims may be done in another order than the order portrayed.
- Further, the purpose of any Abstract of the Disclosure is to enable the U.S. Patent and Trademark Office and the public generally, and especially the scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or phraseology, to determine quickly from a cursory inspection the nature and essence of the technical disclosure of the application. An Abstract of the Disclosure is not intended to be limiting as to the scope of the present invention in any way.
- Although the term “at least one” may often be used in the specification, claims and drawings, the terms “a”, “an”, “the”, “said”, etc. also signify “at least one” or “the at least one” in the specification, claims and drawings.
- Additionally, the terms “including”, “comprising” or similar terms in the specification, claims and drawings should be interpreted as meaning “including, but not limited to.”
- Finally, it is the applicant's intent that only claims that include the express language “means for” or “step for” be interpreted under 35 U.S.C. 212,
paragraph 6. Claims that do not expressly include the phrase “means for” or “step for” are not to be interpreted under 35 U.S.C. 212,paragraph 6.
Claims (3)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/855,610 US20200252442A1 (en) | 2018-08-01 | 2020-04-22 | Systems and methods for electronic notetaking |
US17/845,857 US20220321619A1 (en) | 2018-08-01 | 2022-06-21 | Systems and methods for electronic notetaking and calling into electronic meetings |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201862713281P | 2018-08-01 | 2018-08-01 | |
US16/524,653 US10742695B1 (en) | 2018-08-01 | 2019-07-29 | Methods and systems of recording information related to an electronic conference system |
US16/855,610 US20200252442A1 (en) | 2018-08-01 | 2020-04-22 | Systems and methods for electronic notetaking |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/524,653 Continuation US10742695B1 (en) | 2018-08-01 | 2019-07-29 | Methods and systems of recording information related to an electronic conference system |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/845,857 Continuation-In-Part US20220321619A1 (en) | 2018-08-01 | 2022-06-21 | Systems and methods for electronic notetaking and calling into electronic meetings |
Publications (1)
Publication Number | Publication Date |
---|---|
US20200252442A1 true US20200252442A1 (en) | 2020-08-06 |
Family
ID=71836838
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/524,653 Active US10742695B1 (en) | 2018-08-01 | 2019-07-29 | Methods and systems of recording information related to an electronic conference system |
US16/855,610 Abandoned US20200252442A1 (en) | 2018-08-01 | 2020-04-22 | Systems and methods for electronic notetaking |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/524,653 Active US10742695B1 (en) | 2018-08-01 | 2019-07-29 | Methods and systems of recording information related to an electronic conference system |
Country Status (1)
Country | Link |
---|---|
US (2) | US10742695B1 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220130393A1 (en) * | 2020-10-23 | 2022-04-28 | Naver Corporation | Method, system, and non-transitory computer readable record medium to record conversations in connection with video communication service |
US11496330B2 (en) * | 2020-11-07 | 2022-11-08 | M/S. Amagi Media Labs Pvt. Ltd | Video playout integrated with video conferencing for a group-watch video system |
JP2023051950A (en) * | 2021-09-30 | 2023-04-11 | エピックベース株式会社 | Information processing system, program, and information processing method |
US11763823B2 (en) | 2020-03-10 | 2023-09-19 | Outreach Corporation | Automatically recognizing and surfacing important moments in multi-party conversations |
US20240012550A1 (en) * | 2022-07-09 | 2024-01-11 | Snap Inc. | Providing bot participants within a virtual conferencing system |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11233831B2 (en) | 2019-07-31 | 2022-01-25 | Centurylink Intellectual Property Llc | In-line, in-call AI virtual assistant for teleconferencing |
EP4143732A1 (en) * | 2020-05-01 | 2023-03-08 | Monday.com Ltd. | Digital processing systems and methods for enhanced collaborative workflow and networking systems, methods, and devices |
US11663824B1 (en) | 2022-07-26 | 2023-05-30 | Seismic Software, Inc. | Document portion identification in a recorded video |
Family Cites Families (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2474083C (en) | 2004-06-25 | 2011-01-25 | Sivakumaran Sanmugasuntharam | Caller id call memo system |
US20070206759A1 (en) | 2006-03-01 | 2007-09-06 | Boyanovsky Robert M | Systems, methods, and apparatus to record conference call activity |
US8064342B2 (en) | 2006-10-27 | 2011-11-22 | Verizon Patent And Licensing Inc. | Load balancing session initiation protocol (SIP) servers |
US7760865B2 (en) | 2006-11-17 | 2010-07-20 | Microsoft Corporation | Escalation from a conversation to a conference |
US8631069B2 (en) | 2007-03-01 | 2014-01-14 | Oracle International Corporation | Web and multi-media conference |
WO2009027323A2 (en) | 2007-08-28 | 2009-03-05 | Roeder Steffen | Method for carrying out a multimedia communication based on a network protocol, particularly tcp/ip and/or udp |
CN101447872B (en) | 2007-11-27 | 2011-09-28 | 阿里巴巴集团控股有限公司 | User identity authentication method, system thereof and identifying code generating maintenance subsystem |
CA2648184C (en) | 2007-12-28 | 2014-07-08 | Bce Inc. | Method and apparatus for conveying a calling party identifier |
US9621561B2 (en) * | 2009-02-27 | 2017-04-11 | Microsoft Technology Licensing, Llc | Enabling trusted conferencing services |
US8972869B1 (en) | 2009-09-30 | 2015-03-03 | Saba Software, Inc. | Method and system for managing a virtual meeting |
US8064582B2 (en) | 2009-10-05 | 2011-11-22 | Vonage Network Llc | Method and apparatus for providing an identifier for a caller ID function in a telecommunication system |
US8391455B2 (en) * | 2010-03-17 | 2013-03-05 | Avaya Inc. | Method and system for live collaborative tagging of audio conferences |
US20110271210A1 (en) | 2010-04-30 | 2011-11-03 | American Teleconferncing Services Ltd. | Conferencing Application Store |
US9392121B2 (en) | 2010-09-20 | 2016-07-12 | International Business Machines Corporation | Seamlessly conferencing a previously-connected telephone call |
US9538133B2 (en) * | 2011-09-23 | 2017-01-03 | Jie Diao | Conveying gaze information in virtual conference |
US9449303B2 (en) * | 2012-01-19 | 2016-09-20 | Microsoft Technology Licensing, Llc | Notebook driven accumulation of meeting documentation and notations |
US10198742B2 (en) | 2012-06-29 | 2019-02-05 | Groupon, Inc. | Inbox management system |
US9064259B2 (en) | 2012-12-19 | 2015-06-23 | Genesys Telecomminucations Laboratories, Inc. | Customer care mobile application |
US20140006611A1 (en) | 2013-07-17 | 2014-01-02 | Paul Andrew Perez | Method and System for Using Timestamps and Algorithms Across Email and Social Networks to Identify Optimal Delivery Times for an Electronic Personal Message |
US9703771B2 (en) * | 2015-03-01 | 2017-07-11 | Microsoft Technology Licensing, Llc | Automatic capture of information from audio data and computer operating context |
GB201505864D0 (en) * | 2015-04-07 | 2015-05-20 | Ipv Ltd | Live markers |
US9338289B1 (en) | 2015-06-26 | 2016-05-10 | Velocify, Inc. | Automatic determination of caller identification data in outgoing calls |
US9699409B1 (en) | 2016-02-17 | 2017-07-04 | Gong I.O Ltd. | Recording web conferences |
US10636317B2 (en) | 2016-05-26 | 2020-04-28 | University Of South Carolina | Automated remote learning device and system for using same |
US20180081855A1 (en) | 2016-09-21 | 2018-03-22 | Scianta Analytics, LLC | Cognitive modeling system including repeat processing elements and on-demand elements |
US10846612B2 (en) * | 2016-11-01 | 2020-11-24 | Google Llc | Actionable suggestions for activities |
SG10201608532PA (en) | 2016-10-12 | 2018-05-30 | Mastercard International Inc | Methods, apparatus and devices for authenticating a call session |
US10193940B2 (en) * | 2017-02-07 | 2019-01-29 | Microsoft Technology Licensing, Llc | Adding recorded content to an interactive timeline of a teleconference session |
US10642889B2 (en) | 2017-02-20 | 2020-05-05 | Gong I.O Ltd. | Unsupervised automated topic detection, segmentation and labeling of conversations |
US20180268318A1 (en) | 2017-03-17 | 2018-09-20 | Adobe Systems Incorporated | Training classification algorithms to predict end-user behavior based on historical conversation data |
US10600420B2 (en) * | 2017-05-15 | 2020-03-24 | Microsoft Technology Licensing, Llc | Associating a speaker with reactions in a conference session |
US20190068526A1 (en) * | 2017-08-25 | 2019-02-28 | Facebook, Inc. | Methods and systems for helper bot platform assistance |
US11700137B2 (en) * | 2017-08-26 | 2023-07-11 | Vmware, Inc. | Collaborative access to virtual desktops |
US20190102846A1 (en) | 2017-10-04 | 2019-04-04 | Boldleads.com, Inc. | Systems and Methods For Increasing Lead Conversion Rates For Prospective Buyers and Sellers Of Real Estate |
EP3499432A1 (en) * | 2017-12-12 | 2019-06-19 | Siemens Aktiengesellschaft | Bot for communications platform |
US11385914B2 (en) * | 2018-01-02 | 2022-07-12 | Microsoft Technology Licensing, Llc | Hybrid intelligence approach to eliciting knowledge for inline notes |
US11276407B2 (en) | 2018-04-17 | 2022-03-15 | Gong.Io Ltd. | Metadata-based diarization of teleconferences |
-
2019
- 2019-07-29 US US16/524,653 patent/US10742695B1/en active Active
-
2020
- 2020-04-22 US US16/855,610 patent/US20200252442A1/en not_active Abandoned
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11763823B2 (en) | 2020-03-10 | 2023-09-19 | Outreach Corporation | Automatically recognizing and surfacing important moments in multi-party conversations |
US20220130393A1 (en) * | 2020-10-23 | 2022-04-28 | Naver Corporation | Method, system, and non-transitory computer readable record medium to record conversations in connection with video communication service |
US11496330B2 (en) * | 2020-11-07 | 2022-11-08 | M/S. Amagi Media Labs Pvt. Ltd | Video playout integrated with video conferencing for a group-watch video system |
JP2023051950A (en) * | 2021-09-30 | 2023-04-11 | エピックベース株式会社 | Information processing system, program, and information processing method |
JP7337415B2 (en) | 2021-09-30 | 2023-09-04 | エピックベース株式会社 | Information processing system, program and information processing method |
US20240012550A1 (en) * | 2022-07-09 | 2024-01-11 | Snap Inc. | Providing bot participants within a virtual conferencing system |
US11880560B1 (en) * | 2022-07-09 | 2024-01-23 | Snap Inc. | Providing bot participants within a virtual conferencing system |
Also Published As
Publication number | Publication date |
---|---|
US10742695B1 (en) | 2020-08-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20200252442A1 (en) | Systems and methods for electronic notetaking | |
Nelson | The next media regime: The pursuit of ‘audience engagement’in journalism | |
US11069367B2 (en) | Speaker association with a visual representation of spoken content | |
US8791977B2 (en) | Method and system for presenting metadata during a videoconference | |
US10003557B2 (en) | Preserving collaboration history with relevant contextual information | |
EP3309731A1 (en) | Managing electronic meetings using artificial intelligence and meeting rules templates | |
US9508058B2 (en) | System providing an interactive conference | |
US9754320B2 (en) | Providing a record of an interactive conference | |
US20150319257A1 (en) | Interest-Based System | |
US8391455B2 (en) | Method and system for live collaborative tagging of audio conferences | |
US20070133437A1 (en) | System and methods for enabling applications of who-is-speaking (WIS) signals | |
US20170004178A1 (en) | Reference validity checker | |
Wasserman | South Africa and China as BRICS partners: Media perspectives on geopolitical shifts | |
Menary et al. | Going virtual: Adapting in-person interactive focus groups to the online environment | |
Wicks et al. | Partisan media selective exposure during the 2012 presidential election | |
Van Hoof et al. | Diverse politics, diverse news coverage? A longitudinal study of diversity in Dutch political news during two decades of election campaigns | |
US20200021453A1 (en) | Increasing audience engagement during presentations by automatic attendee log in, live audience statistics, and presenter evaluation and feedback | |
Matsilele et al. | Reconstruction and adaptation in times of a contagious crisis: A case of African newsrooms’ response to the Covid-19 pandemic | |
CN109272286B (en) | SaaS (software as a service) multi-tenant cloud movie and television project management method and system with script as core | |
Müller-Seitz et al. | Toward a choreography of congregating: A practice-based perspective on organizational absorptive capacity in a semiconductor industry consortium | |
US20220321619A1 (en) | Systems and methods for electronic notetaking and calling into electronic meetings | |
Graves et al. | From public reason to public health: Professional implications of the “Debunking Turn” in the Global Fact-Checking Field | |
Kulczycki et al. | Questionable conferences and presenters from top-ranked universities | |
Lewis et al. | Parent perspectives on young children’s changing digital practices: Insights from Covid-19 | |
Takahashi | Towards inclusive international environmental communication scholarship: The role of Latin America |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SALESLOFT, INC., GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BROWN, AUSTIN MICHAEL;FINNERAN, MATTHEW IRISH;REEL/FRAME:052606/0703 Effective date: 20191016 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
AS | Assignment |
Owner name: PNC BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT, CALIFORNIA Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:SALESLOFT, INC.;REEL/FRAME:058598/0831 Effective date: 20211229 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |