Patent Application
20230247142
The present invention relates generally to the field of computer networking and computerized communications sessions, and more particularly to a method and system for intelligent management of multi-party communications.
Communications networks for enabling multi-party communications, e.g., by telephone, e-mail and/or SMS/text, are well-known in the art. Often, a first party wishes to communicate with a second party, identifies contact information for the second party, and then prepares and/or initiates a communication to/with the second party using the second party's contact information, e.g., by placing a telephone call to a specific person have a respective telephone number, using a telephone.
In accordance with the present state of the art, a first party seeking to communicate with a second party generally needs to know, look up, and/or request assistance in finding a suitable person or consultant to deliver a specific service needed. After the individual believes that a suitable second party has been identified, e.g., as a viable resource for a particular service/information need, then the first party needs to identify contact information for that resource/second party, and then attempt to contact the resource/second party (sometimes needing to make repeated attempts to contact the second party, or to contact other parties if the particular second party is unavailable). In the end, the second party may or may not respond, provide value, or have capacity to deliver the information and/or service needed, resulting in wasted time and effort on the part of the first party.
In certain contexts, a first party wishes to communicate with a second party to fulfill a particular need, yet the identity of the second party is initially unknown and/or undetermined. For example, in a healthcare context, a first party may wish to communicate with a suitable person/consulting entity to obtain a specific service, information or consultation, yet is initially unsure of who that suitable person is. For example, a primary care physician may be providing medical care to a particular patient, and may wish to consult with a specialist to obtain an opinion/medical guidance and/or other information (with respect to medical treatment for the patient) from the specialist's point of view. However, the primary care physician may be initially unsure as to who is a suitable person to contact for such guidance. For example, the primary care physician may be unsure as to whether the primary care physician needs the advice of a nephrologist or other specialist, or may be certain that a nephrologist is needed, but be unsure of who is a nephrologist, or may be aware of a number of persons that are nephrologists, but may be unsure as to which nephrologist has the appropriate expertise, or may be aware of a number of nephrologists with appropriate expertise, but may be unaware of which nephrologist is presently “in-network” with respect to the patient's insurance, or readily available to have a discussion with the primary care physician for obtaining such an opinion/medical guidance or other information.
Current assistive communication systems depend on a tightly coupled, known network of individuals to allow for connections to be made or a rudimentary call list that places all the decision making on the person attempting to find a suitable second party/service provider. The first party user must know the need as well as the service and/or second party/service provider that will meet that need in order to attempt to establish a communication channel directly with that suitable second party/service provider. Often, the user has no shared understanding of the current capacity of the second party/service provider until a call to the second party/service provider is made.
What is needed is a system that can lessen the burden on the first party, and/or reduce or eliminate the need to identify which second party/resource has capacity and will be the most relevant to the first party's need, affording the first party the opportunity to avoid inefficiencies in obtaining access to an available, suitable second party, and to instead continue to be productive at other tasks.
The present invention provides a method and system for management of multi-party communications that is capable of intelligently assessing a first party/requestor's need and matching the first party need to a suitable second party resource that is most probable to meet that need in an efficient manner. The system effectively serves as a chatbot-based switchboard operator that allows requestors to state a need for a service or consultation, and then automatedly have that need researched and/or matched to the most appropriate resource/service provider based on real-time automated inquiry and/or known data from past research. Further, the system is capable of contacting one or more resources/service providers, confirming that a particular resource/provider can meet the current need, and also coordinating/facilitating a communication session between the first party/requestor and the second party/resource without the need for human intervention.
Accordingly, after the system has identified the requestor's need/requested resource, the requestor can continue with other tasks and wait for the system to asynchronously facilitate a communication session with a service provider. Further, after a resource need has been identified, the system manages/routes the resource request to a relevant resource providers that has the best chance of meeting that need based on trained models (coupled with known request volume), and attempt to contact a resource provider via phone, text, or software application. The system then starts an interactive session with the resource service provider to validate the contact's identity, confirm the service needed, and confirm the contact has the capacity to meet the need/provide the requested resource. If any of the above is not met, the system will record why the match was not made and attempt a session with the next most-likely resource provider. The system uses success and failure to inform its future triage functionality.
After the validation process is complete, the system notifies the original requestor that a resource has been found and is available to provide the requested resource. A communication session is then started for the two parties (requestor and resource provider) to facilitate communication between them. The system learns based on success/failure/other datapoints recorded for each interaction, including if the need was successfully met between the user and the second party. Information is logged to inform selection of resource providers for meeting future resource requests. This serves to prioritize the resource providers the system attempts to contact based on time of day, volume of requests, and success or failure rates.
At any point during this process, if a connection fails to be made, or repeated attempts have been unsuccessful, the system will escalate the need to a human operator or follow up with the initial requestor regarding the status of fulfilling the request.
An understanding of the following description will be facilitated by reference to the attached drawings, in which:
The present invention provides a method and system for management of multi-party communications that is capable of intelligently assessing a first party/requestor's need and matching the first party need to a suitable second party resource that is most probable to meet that need in an efficient manner. The system effectively serves as a chatbot-based switchboard operator that allows requestors to state a need for a service or consultation, and then automatedly have that need researched and/or matched to the most appropriate resource/service provider based on real-time automated inquiry and/or known data from past research. Further, the system is capable of contacting one or more resources/service providers, confirming that a particular resource/provider can meet the current need, and also coordinating/facilitating a communication session between the first party/requestor and the second party/resource without the need for human intervention.
Accordingly, the system of the present invention is capable of acting as an intelligent, AI-based chatbot communication operator, to understand a requestor's need, intelligently route communication requests, interface with and connect relevant parties, and track communication interactions between parties. Accordingly, the present invention may be helpful, for example, to companies that benefit from efficient communication to meet business needs within the company, to companies that benefit from efficiently aligning needs to resources available outside the company, to companies that would benefit from asynchronous communication channel coordination, and to individuals that need a service or consultant for a specific need that don't have the time to vet manually by contact potential service provider options.
More particularly, the present invention provides a system that intelligently triages a requestor's need for a resource, and effectively directs/escalates the requestor's inquiry to the resource that is most probable to meet that need in the most efficient manner. In certain embodiments, the system acts as a chatbot operator allowing users to state the need for a service (e.g., a medical consultation), have that need matched to the most appropriate resource (e.g., service provider) based on known data, reach out to that resource (e.g., service provider), confirm that the resource (e.g., service provider) is available and able to meet the need, and coordinate a communication session between both parties without the need for human intervention.
Currently an individual needs to know, look up, or request assistance in finding a person or consultant or other resource available and able to deliver a specific service needed. Once the individual believes a viable resource is identified, the individual needs to attempt to contact (sometimes making repeated attempts to multiple parties) the resource. In the end, the contact may or may not respond, provide value, or have capacity to deliver the service needed resulting in wasted time and effort. The present invention provides a system that eliminates the need to identify what resource has capacity and will be the most relevant to the user's need, allowing the user to continue being productive at other tasks.
The system's functionality is implemented by a computerized device and/or computing system comprising conventional hardware and software as well as special-purpose software in accordance with the present invention.
According to illustrative embodiment(s) of the present invention, various views are illustrated in
The following detailed description of the invention contains many specifics for the purpose of illustration. Any one of ordinary skill in the art will appreciate that many variations and alterations to the following details are within scope of the invention. Accordingly, the following implementations of the invention are set forth without any loss of generality to, and without imposing limitations upon, the claimed invention.
An exemplary embodiment of the present invention is discussed below for illustrative purposes.
In accordance with a certain aspect of the present invention, one or more of the Requestor Computing Device 84 and/or the Resource Provider Computing Devices 94a, 94b may store and execute an “app” or other purpose-specific application software in accordance with the present invention, although this is not required in all embodiments.
In accordance with the present invention, the network computing environment 100 further includes Intelligent Communication Management System (ICMS) 200. In this exemplary embodiment, the ICMS 200 is operatively connected to the Requestor Computing Device 84 and the Resource Computing Devices 94a, 94b for data communication via the communications network 50. Additionally, the ICMS 200 is operatively connected for data communication with the Requestor Telephone 80 and the Resource Telephones 90a, 90b for data (e.g., voice) communication via the communications network 50. Hardware and software for enabling communication of data by such devices via such communications networks are well known in the art and beyond the scope of the present invention, and thus are not discussed in detail herein.
Accordingly, the exemplary ICMS 200 of
The ICMS 200 may communicate with other computers or networks of computers, for example via a communications channel, network card or modem 220. The ICMS 200 may be associated with such other computers in a local area network (LAN) or a wide area network (WAN), and may operate as a server in a client/server arrangement with another computer, etc. Such configurations, as well as the appropriate communications hardware and software, are known in the art.
The ICMS 200 is specially-configured in accordance with the present invention. Accordingly, as shown in
Further, as will be noted from
As shown in
In accordance with the present invention, the exemplary embodiment of the ICMS 200 shown in
In accordance with the present invention, the exemplary embodiment of the ICMS 200 shown in
In accordance with the present invention, the exemplary embodiment of the ICMS 200 shown in
In the exemplary embodiment shown in
In accordance with the present invention, the exemplary embodiment of the ICMS 200 shown in
Exemplary operation of the system of
Next, the method involves identifying one or more resources (e.g., service provider) options matching the request (i.e., well-suited to provide the requested resource). This may be performed by the Resource Matching Module 250, and may involve the RMM 250 referencing (e.g., querying) Request Data 224a and/or Resource Data 224b indicating which resource providers are known to the ICMS 200 as shown at 310. In certain embodiments, a set of resource providers may be identified by the RMM 250 that matches the request criteria.
Next, the method involves selecting a suitable resource provider, as shown at 312 in
After at least one preferred resource has been identified by the SM 260, the ICMS then starts an automated query process involving automated communication with (e.g., placement of a telephone call to) a resource provider, e.g., as part of a Call Resource Workflow, as shown at 400, and as discussed in greater detail with reference to
Referring still to
If, however, the desired resource is successfully contacted as part of the Call Resource Workflow, as shown at 316, then the system will log/record the successful contact (e.g., as part of the Contact Data 224d), as shown at 320, and the method will proceed to perform the Connect Parties Workflow (e.g., under control of the Connection Module 290), as shown at 700, and the exemplary method ends, as shown at 323.
Next, it is determined if the identified resource has been contacted successfully (i.e., if the telephone call is answered), as shown at 404. If the identified resource has not been contacted successfully (e.g., if the telephone call was not answered), then the QM 270 (in this example) leaves an audio message indicating that the resource should call back to the system, as shown at 406. For example, a general-purpose resource call back script could be stored in the system, and be retrieved and processed and verbalized by the chatbot such that the called party hears spoken words/synthetic speech of the script (e.g., “Hello, we are trying to reach [resource provider name]? Please ask [resource provider name] to return this call by calling [telephone number]”). For example, this may involve transmission of data via the communications network 50. The method may then proceed to start the Request Call Back Escalation Process 500, as shown in
If it is determined at 404 that the call has been answered, or at 408 that the resource has been successfully connected, then the QM 270 confirms the resource's identity, as shown 410. For example, this may involve information exchange to confirm current availability and suitability of the resource. For example, a general-purpose resource provider identity confirmation script could be stored in the system, and be retrieved and processed and verbalized by the chatbot such that the called party hears spoken words/synthetic speech of the script (e.g., “Hello, is your name [resource provider name]? Can you confirm your ID?”).
The QM 270 may then receive a response, e.g., via speech provided by the called resource and associated data transmitted to via the communications network 50. It is then determined if the response indicates that the correct resource identity has been confirmed, as shown at 412.
If so, after the resource provider identity has been confirmed, then it can be determined whether the resource provider can meet the criteria for the need (e.g., for the relevant service, provided within the relevant timeframe, and/or according to other criteria), as shown at 414. This may be performed, for example, using verbalization of a similarly stored script (e.g., “Are you available for a consultation for the next 15 minutes? Are you able to consult on a patient presenting X and Y diagnosis?”). Criteria questions could be scripted based on the identified need and supplemented by specific needs by the requestor (such as a timeframe identified by the requestor).
It is then determined if the resource is available as needed, as shown at 416.
If the QM 270 is unsuccessful in contacting the resource provider (e.g., no answering of the telephone call and/or no call back) as shown at 408, or if the resource is not available at 416, then the QM 270 logs the unsuccessful attempt, as shown at 418, and returns (e.g., displays or stores) an unsuccessful connection status, as shown at 420, and the method ends, as shown at 421. This may involve storing associated data reflecting the failed connection as Connection Data 224e and/or Selection Data 224c for use in making a future selection of a suitable resource to contact, and the Escalation Module 280 may then determine whether to re-attempt contact and/or to identify an alternative (e.g., next best) resource provider to contact, e.g., as determined by the Selection Module 260 and/or Escalation Module 280. This is discussed in greater detail below with reference to
If, however, the QM 270 is successful in contacting the resource provider and the resource is determined to be available as needed at 416, then the QM 270 may log the successful identification of an available resource, as shown at 422. This may involve storing data reflecting this successful contact in the Selection Data 224c and/or in the Connection Data 224e. The QM 270 may then place the resource on hold for next steps, and return a successful connection status, as shown at 424, and this method ends as 41. For example, the Connection Module 290 may subsequently initiate a connection (e.g., acting like a switchboard operator) to connect or facilitate a telephone call (or other communication session) between the requestor and the available resource provider thus identified (e.g., as part of a Connect Parties Workflow, discussed in greater detail below with reference to
If, however, it is determined at 510 that the escalation timer has expired then the method flow continues to 514, where the EM 280 logs that the escalation timer has expired, as shown at 514. The method flow then returns to the previous workflow, as shown at 516, and the method ends, as shown at 517.
If, however, it is determined at 506 that the calling timer has expired then the EM 280 calls (in this embodiment) the resource and logs another attempt to contact the resource, as shown at 518. It is then determined whether the resource (e.g., service provider) has answered the telephone call (in this example) as shown at 520. If it is determined at 520 that the resource has not answered the phone call, then the system 200, e.g. EM 280, leaves a voicemail message for the resource (e.g. using a script and or a pre-recording and/or synthesized text to speech, in a manner similar to that described above), as shown at 522 and method flow returns to 508 where the EM 280 again checks whether the escalation timer has expired, and the method flow continues as described above.
If, however, it is determined at 520 that the resource did answer the telephone call (in this example) then the EM 280 logs that the reserves answered, e.g., as Connection Data 224e, as shown at 524. The method flow then returns to the previous workflow, as shown at 516, and the method ends, as shown at 517.
If it is determined at 606 that the telephone numbers match, then the EM 280 provides a message, e.g., using text to speech functionality, to greet the caller, asked the caller to confirm the caller's identity, in a manner similar to that described above, as shown at 608. It is then determined whether the incoming telephone number matches the identity of the requested resource, as shown at 610. If not, then EM 280 starts a transfer to live operator workflow 900, as shown at 612.
If, however, it is determined at 610 that the incoming telephone number and identity of the resource do match. Then the EM 280 places the caller on hold, as shown at 614, and starts the Connect Parties Workflow 700, as shown at 616, and the method ends, as shown at 617.
If, however, it is determined that 606 that the incoming telephone number does not match a telephone number of an active call request, then the EM 280 provides a message, e.g., using text to speech functionality, to greet the caller, ask the caller to confirm the caller's identity, and asks the caller to identify a reason for the call, as shown at 618, in a manner similar to that described above. It is then determined whether there is an active request open with respect to the caller and/or an associated resource, as shown at 620. If so then the caller is placed on hold, as shown at 614, and the method continues as described above. If not, then EM 280 starts a transfer to live operator workflow 900, as shown at 612.
It is then determined whether the requester has responded to the initiated contact, e.g., by answering a telephone call, as shown at 704. If the Requestor does answer the telephone call, then the CM 290 may act somewhat like an automated switchboard operator to open a telephone connection (or in certain embodiments, enables a different communication channel or facilitates communication via a different communication channel) between the identified resource provider and the original Requestor, as shown at 706. This allows the parties to communicate directly (e.g., by telephone), exchange information, and allows the requestor to receive the requested resource (e.g., consultation) from the resource provider (e.g., nephrologist). The CM 290 may then log the connection between the caller (resource/service provider) and the original requestor, as shown at 708. The CM 290 may store data reflecting the successful connection and proper match of resource provider to request as Selection Data 224c for future reference and/or as Connection Data 224e. This exemplary method then ends, as shown at 709.
If, however, it is determined at 704 that the requester has not responded, e.g., by answering the telephone call, then the EM 280 may start a Party Connection Escalation Workflow 800, discussed below with reference to
If is then determined whether a communication connection was successfully established with the requestor, as shown at 710. If so, then the method flow continues to 706 where the CM 290 opens a telephone or other connection between the identified resource provider and the original requestor, as described above, and the method flow continues as described above.
If it is determined at 710 that a connection was not successfully established with the requestor, then the CM 290 logs the failed connection attempt, as shown at 712. This may involve recording data as Selection Data 224c for future reference and/or as Connection Data 224e. The method flow then continues to the Transfer to Live Operator Workflow 900, as described below with reference to
If, however, it is determined at 816 that the connection escalation timer has expired then the method flow continues to 820, where the EM 280 logs that the escalation timer has expired, as shown at 820. The method flow then returns to the previous workflow, as shown at 812, and the method ends, as shown at 813.
If, however, it is determined at 806 that the connection attempt timer has expired then the EM 280 calls (in this embodiment) the requestor and logs the attempt to contact the requestor, as shown at 808. It is then determined whether the requestor has answered the telephone call (in this example) as shown at 810. If it is determined at 810 that the requestor has not answered the phone call, then the system 200, e.g., EM 280, checks the connection escalation time, as shown at 814 and the method flow continues as described above.
If, however, it is determined at 810 that the resource did answer the telephone call (in this example) then the method flow then returns to the previous workflow, as shown at 812, and the method ends, as shown at 813.
It is next determined whether a live operator has answered the call, as shown at 904. If it is determined in 904 that the live operator did not answer the call, then caller may be kept on hold, and a timer may be used to time a next attempt, as shown at 906. Method flow then continues to 902 and proceeds as described above.
If, however, it is determined at 904 that the live operator answered the call, then the CM 290 logs the answering of the call, as shown at 908, which may involve storing Selection Data 224c and/or Connection Data 224e, as described above. Next the live operator may conduct a telephone discussion with the requestor that requested the resource, identify/validate the caller's need and triage in a manual fashion during the connected communication session, as shown at 910. The live operator will then manually match the call with a suitable service provider, as shown at 912, and record associated data as Selection Data 224c and/or Connection Data 224e, so that the system may subsequently learn from this manual matching (following failed automated matching by the system), to make a better, more accurate match in a future iteration of the process. This exemplary method then ends.
Accordingly, it will be appreciated that the present invention provides a system and method that can lessen the burden on a resource requestor, and/or reduce or eliminate the need to identify which resource provider has sufficient capacity for providing and is most relevant to the requested resource, thereby affording the requestor an opportunity to continue be productive at other tasks, rather than having to research resource providers, select preferred resource provides, contact resource providers, waste time waiting “on hold,” re-attempting call inquiries, and/or speaking with resource providers lacking present capacity for providing the requested resource.
Further, the system and method of the present invention provide a method and system for management of multi-party communications that is capable of intelligently assessing a first party/requestor's need and matching the first party need to a suitable second party resource that is most probable to meet that need in an efficient manner. The system effectively serves as a chatbot-based switchboard operator that allows requestors to state a need for a service or consultation, and then automatedly have that need researched and/or matched to the most appropriate resource/service provider based on real-time automated inquiry and/or known data from past research. Further, the system is capable of contacting one or more resources/service providers, confirming that a particular resource/provider can meet the current need, and also coordinating/facilitating a communication session between the first party/requestor and the second party/resource without the need for human intervention.
This system and method of the present invention principally relies upon several elements. One of those elements is a computerized communication management engine that can interface with a resource requestor/user to understand the service/consultant/resource provider/resource that is needed. This is done via a computerized, automated “bot” interface (via a voice-based or text-based platform). After the need has been identified, the requestor can continue with other tasks and wait for the system to asynchronously facilitate a communication session with a suitable service provider.
When a need has been identified, the computerized communication management engine routes the need to a relevant resource provider that has the best chance of meeting the request for the resource based on trained models coupled with known request volume, and attempts to contact the resource provider via phone, text, or application. The computerized communication management engine starts an interactive session to validate the resource provider's identity, confirm the resource/service needed, and confirm that resource provider has the current capacity to meet the requestor's need. If any of the above conditions is not met, the computerized communication management engine will record why the match was not made and attempt a session with the next most-likely service provider. The computerized communication management engine uses success and failure to inform its future triage functionality in selecting a suitable resource provider.
After the validation process is complete, the computerized communication management engine will notify the original requestor that a suitable resource provider has been found and is available to provide the requested resource/service. The computerized communication management engine then enables or facilitates a communication session for the parties, so that the requested resource may be obtained.
Lastly, the computerized communication management engine learns based on datapoints recorded for each interaction, including if the need for a requested resource was met successfully. Information is logged to inform future requests. This is used to prioritize the resource providers that the computerized communication management engine will attempt to contact based on time of day, volume of requests, and success or failure rates, etc.
At any point during this process, if a connection fails to be made, or repeated attempts have been unsuccessful, the system will escalate the need to a human operator or follow up with the initial requestor with the status.
Accordingly, a system in accordance with the present invention may be used, for example, by companies that benefit from efficient communication to meet the business needs within the organization, by companies that benefit from efficiently aligning needs to resources outside of the organization, by companies that would benefit from asynchronous communication channel coordination, and by individuals that need a service or consultant for a specific need but who do not have the time to manually vet and contact potential service/consultant options.
While there have been described herein the principles of the invention, it is to be understood by those skilled in the art that this description is made only by way of example and not as a limitation to the scope of the invention. Accordingly, it is intended by the appended claims, to cover all modifications of the invention which fall within the true spirit and scope of the invention.
This application claims the benefit of priority under 35 U.S.C. § 119(e) of U.S. Provisional Patent Application No. 63/304,961, filed Jan. 31, 2022, the entire disclosure of which is hereby incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| 63304961 | Jan 2022 | US |
