Communication monitoring systems and methods

Abstract

A system comprising: (a) a compliance server adapted to receive an audio feed of a telephone conversation; (b) an identification module adapted to ascertain IP addresses from which said audio feed originates and identify participants in said telephone conversation using said IP addresses; and (c) an analysis module adapted to ascertain a subject of said telephone conversation.

Claims

1. A system comprising: (a) a compliance server adapted to receive an audio feed of a telephone conversation; (b) an identification module adapted to ascertain IP addresses from which said audio feed originates and identify participants in said telephone conversation using said IP addresses; and (c) an analysis module adapted to ascertain a subject of said telephone conversation; (d) a certification engine adapted to generate a certified copy of the telephone conversation in response to a request from an institution that participated in the conversation.

2. A system according to claim 1, wherein said telephone conversation is in progress.

3. A system according to claim 1, wherein said telephone conversation has been concluded.

4. A system according to claim 1, wherein said analysis module analyzes the audio feed directly.

5. A system according to claim 4 wherein said analysis module relies exclusively on microphone out audio feeds.

6. A system according to claim 1, comprising a speech to text converter which converts said audio stream to a text output.

7. A system according to claim 6, wherein said analysis module analyzes said text output to ascertain said subject of said telephone conversation.

8. A system according to claim 1, comprising a co-ordination module which associates a unique identifier (UID) with each audio stream and transmits said UID to at least one institution represented in said telephone conversation.

9. A system according to claim 1, comprising: a co-ordination module which associates a unique identifier (UID) with each audio stream; and a storage module which stores said audio stream/UID pair and grants access to said pair to at least one institution represented in said telephone conversation.

10. A system according to claim 1, comprising: a verification module adapted to require at least one participant in said telephone conversation to identify the other participant(s) in the conversation and the subject of the conversation.

11. A system according to claim 8, comprising: a query engine adapted to provide a response to a query containing a UID.

12. A system according to claim 11, wherein said query engine is adapted to generate a hierarchical listing of all records associated with a specific UID.

13. A system according to claim 1 comprising: a template generation module adapted to retrieve a template from a template database based on said subject of said conversation and present said template to all participants in said conversation during said conversation; and a template filling module configured to receive audio feed from at least one participant in said telephone conversation and populate fields in said template with details from said conversation prior to conclusion of said conversation.

14. A method comprising: (a) receiving an audio feed of a telephone conversation in progress; (b) ascertaining the telephone numbers of participants in said conversation; and (c) causing a user interface to appear on a device owned by at least one of the participants in the conversation (d) generating a certified copy of the telephone conversation in response to a request from an institution that participated in the conversation.

15. A method according to claim 14, wherein said ascertaining comprises using a look-up table of IP addresses associated with telephone numbers.

16. A method according to claim 14, wherein said causing comprises remote launching of an application.

17. A method according to claim 14, wherein said causing comprises transmission of an SMS to a mobile phone.

18. A method according to claim 14, wherein a compliance server performs said receiving.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) In order to understand the invention and to see how it may be carried out in practice, embodiments will now be described, by way of non-limiting example only, with reference to the accompanying figures. In the figures, identical and similar structures, elements or parts thereof that appear in more than one figure are generally labeled with the same or similar references in the figures in which they appear. Dimensions of components and features shown in the figures are chosen primarily for convenience and clarity of presentation and are not necessarily to scale. The attached figures are:

(2) FIG. 1 is a schematic overview depicting an exemplary context in which various exemplary embodiments of the invention operate;

(3) FIG. 2 is a schematic diagram depicting system according to some exemplary embodiments of the invention;

(4) FIG. 3 is a schematic diagram depicting system according to some exemplary embodiments of the invention;

(5) FIG. 4 is a simplified flow diagram of a method according to some exemplary embodiments of the invention;

(6) FIG. 5a is an exemplary verification dialog box for a first party in a transaction according to an exemplary embodiment of the invention;

(7) FIG. 5b is an exemplary verification dialog box for a second party in a transaction according to an exemplary embodiment of the invention;

(8) FIG. 5c is an exemplary verification dialog box with multiple choice format according to an exemplary embodiment of the invention;

(9) FIG. 5d is an exemplary verification dialog box with free text fields according to an exemplary embodiment of the invention;

(10) FIG. 6 is an exemplary logic tree for verification according to one exemplary embodiment of the invention;

(11) FIG. 7 is a simplified flow diagram of a method according to some exemplary embodiments of the invention;

(12) FIG. 8a is a simplified schematic representation of a computer system according to some exemplary embodiments of the invention;

(13) FIG. 8b is an exemplary graphical user interface (GUI) according to some embodiments of the invention;

(14) FIG. 9a is a simplified schematic representation of a computer system according to some exemplary embodiments of the invention;

(15) FIG. 9b is an exemplary graphical user interface (GUI) according to some embodiments of the invention; and

(16) FIG. 9c is an exemplary graphical user interface (GUI) according to some embodiments of the invention.

DETAILED DESCRIPTION OF EMBODIMENTS

(17) Embodiments of the invention relate to systems and methods for communications monitoring. Specifically, some embodiments of the invention are used to log details of a verbal transaction and/or to assure institutional compliance with applicable recordkeeping regulations.

(18) The principles and operation of a system and/or methods according to exemplary embodiments of the invention may be better understood with reference to the drawings and accompanying descriptions.

(19) Before explaining at least one embodiment of the invention in detail, it is to be understood that the invention is not limited in its application to the details set forth in the following description or exemplified by the Examples. The invention is capable of other embodiments or of being practiced or carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein is for the purpose of description and should not be regarded as limiting.

(20) Overview

(21) FIG. 1 is a schematic overview depicting an exemplary systemic context in which various exemplary embodiments of the invention operate indicated generally as 100. Systemic context 100 includes a compliance center 110 and a plurality of institutions communicating with one another by telephone (e.g. concerning financial transactions). For simplicity, only two institutions (first institution 120 and second institution 130) are depicted although in actual practice a much larger number of institutions may be served by compliance center 110.

(22) In the normal course of business a specific individual at first institution 120 initiates a telephone call 122 to a specific individual at second institution 130. Call 122 concerns a specific financial transaction being negotiated. First institution 120 provides a duplicate audio stream 124 of call 122 to compliance center 110 as part of a pre-existing service agreement between center 110 and institution 120.

(23) If second institution 130 also has a pre-existing service agreement with center 110, that institution also provides a duplicate audio stream 134 of call 122 to compliance center 110.

(24) Within the framework of the service agreements between compliance center 110 and institutions 120 and/or 130, center 110 maintains a database of client related data 113. According to various exemplary embodiments of the invention client related data 113 includes, but is not limited to, employee names, voice prints for each employee, institutional telephone numbers assigned to each employee, IP addresses of computers assigned to each employee and/or mobile telephone numbers belonging to each employee and/or e-mail addresses of each employee.

(25) Alternatively or additionally, in some embodiments compliance center 110 maintains an archive of stored recordings 114 of audio streams 124 and/or 134.

(26) Alternatively or additionally, compliance center 110 uses human personnel to monitor audio streams 124 and/or 134 (e.g. using listening stations equipped with earphones).

(27) A more detailed explanation of how compliance center uses data 113 to analyze audio streams 124 and/or 134 and provide compliance services to institutions 120 and/or 130 is provided hereinbelow.

(28) In some exemplary embodiments of the invention, audio streams 123 and 124 are provided as microphone out audio feeds.

(29) Exemplary Compliance Center System

(30) FIG. 2 is a schematic diagram depicting a system, identified generally as 200, for monitoring and cataloging telephone calls by participant(s) and/or by subject according to some exemplary embodiments of the invention.

(31) Depicted exemplary system 200 includes a compliance server 210 (e.g. at center 110 in FIG. 1) adapted to receive an audio feed 124 and/or 134 of a telephone conversation (e.g. 122 in FIG. 1). In some exemplary embodiments of the invention, audio streams 123 and 124 are provided exclusively as microphone out audio feeds. In some embodiments use of microphone out audio feeds contributes to an increase in signal clarity and/or contributes to an improvement in performance of module 220 and/or contributes to an improvement in performance of module 230. For purposes of this specification and the accompanying claims the term “audio feed” (e.g. Microphone out audio feed” include digital files corresponding to analog audio streams.

(32) In the depicted exemplary embodiment, audio feed 124 and/or 134 is processed by an identification module 220 adapted to compare the audio feed to a database 223 of voice prints and identify participants 222 in telephone conversation 122 (FIG. 1). In order to conserve system resources non-voice client related data 113 is often used to “guess” which voice prints to check first. For example, audio stream 124 is tagged in some cases with the phone number that originated the call and/or the phone number dialed. In some embodiments, client related data includes the names of employees associated with these phone numbers. The employees associated with these phone numbers and/or their administrative assistants will be the system's first “guess” for voice print comparison.

(33) Depicted exemplary system 200 also includes an analysis module 230 adapted to ascertain a subject 232 of telephone conversation 122.

(34) According to various exemplary embodiments of the invention identification module 220 and/or analysis module 230 are operated on a telephone conversation in progress or on a telephone conversation which has been concluded (e.g. an archived recording).

(35) In some embodiments, analysis module 230 analyzes audio feed (124 and/or 234) directly. Alternatively or additionally, in some embodiments system 200 includes a speech to text converter 234 which converts the audio stream to a text output 236. In some embodiments, analysis module analyzes text output 236 to ascertain subject 232 of the telephone conversation.

(36) In some embodiments, system 200 includes a co-ordination module 240 which associates a unique identifier (UID) 242 with each audio stream and transmits the UID to at least one institution (e.g. 120 and/or 130) represented in the telephone conversation. If both participating institutions have service agreements with center 110, both will receive the UID.

(37) In some embodiments, system 200 includes a co-ordination module 240 which associates a unique identifier (UID) 242 with each audio stream and a storage module 250 which stores each audio stream/UID pair and grants access 252 to the pair to at least one institution (e.g. 120; 130 in FIG. 1) represented in the telephone conversation. If both participating institutions have service agreements with center 110, both will be granted access 252.

(38) In some embodiments, system 200 includes a certification engine 255 adapted to generate a certified copy 256 of the telephone conversation in response to a request from an institution (e.g. 120 and/or 130) that participated in the conversation. According to various exemplary embodiments of the invention the certified copy includes a digital recording and/or a text transcript. Alternatively or additionally, certification is to the identity of the participants in the conversation and/or the subject of the conversation. Alternatively or additionally, in some embodiments certification engine 255 adapted to generate a certified copy 256 of the telephone conversation in response to a request from a regulatory agency.

(39) Although the above explanation describes a scenario with two institutions participating in a telephone call, the same principles are applicable to calls among three, four or more participating institutions.

(40) In many exemplary embodiments of the invention, system 200 includes a verification module 260 adapted to require at least one participant (e.g. from institution 120 or 130) in the telephone conversation to identify the other participant(s) in the conversation and the subject of the conversation. Again, if both participating institutions have service agreements with center 110, participants from both institutions will be asked to verify participants 222 and subject 232.

(41) In some embodiments, system 200 includes a query engine 270 adapted to provide a response 274 to a query 272 containing a UID 242. In the depicted exemplary embodiment, query 272 originates from one of institutions 120/130. In other exemplary embodiments of the invention, query 272 originates from a regulatory agency (not depicted). According to those embodiments, response 274 goes to the (un-depicted) regulatory agency. According to various exemplary embodiments of the invention queries 272 relate to the nature of the transaction and/or other UIDs related to the same transaction (e.g. “Was this transaction culminated?” or “Were there any UIDs in this transaction prior to this one.”)

(42) In some embodiments, query engine 270 is adapted to generate a hierarchical listing (e.g. sorted by date/time) of all records associated with a specific UID.

(43) Alternatively or additionally, in some embodiments system 200 includes a template generation module 820 (depicted in Fig and described in the accompanying text for that figure) adapted to retrieve a template (821; FIG. 8) from a template database (822; FIG. 8) based on the subject of the conversation and present template 821 to all participants in conversation during the conversation and a template filling module 830 (depicted in FIG. 8 and described in the accompanying text for that figure) configured to receive audio feed from at least one participant in the telephone conversation and populate fields in template 821 with details from the conversation prior to conclusion of the conversation.

(44) Exemplary Alternative Communications Flow

(45) Referring again to FIG. 1, in some embodiments of the invention call 122 itself passes through compliance center 110 on its way from institution 120 to institution 130. According to these embodiments call 122 replaces audio feeds 124 and/or 134 at compliance server 201 (FIG. 2).

(46) Exemplary Financial Institution System

(47) FIG. 3 is a schematic diagram depicting a system, identified generally as 300, for monitoring and cataloging telephone calls by participant(s) and/or by subject according to some exemplary embodiments of the invention.

(48) Depicted exemplary system 300 includes a router 310 adapted to route audio feeds (e.g. 124) of telephone conversations (e.g. 122) to a compliance server 210. It is stressed that server 210 is not part of system 300, although it does interact with system 300. The telephone call itself (122) proceeds to its intended destination (130) through normal channels. In the depicted exemplary embodiment, router 210 also sends audio stream 124 to recorder 312. Recorder 312 makes a recording 332 of stream 124.

(49) In the depicted exemplary embodiment, system 300 includes a cataloging module 320 adapted to associate a UID 242 provided by compliance server 210 with each of the telephone conversations. The UID is associated with participants in a conversation and a subject of the conversation.

(50) In some embodiments, system 300 includes an archive 330 containing recordings 332 of the audio feeds (e.g. 124) of the telephone conversations (e.g. 122). According to various exemplary embodiments of the invention archive 300 is instead of or in addition to storage module 250 in system 200.

(51) In the depicted exemplary embodiment, system 300 includes a verification interface 340 adapted to require at least one participant 341 in a telephone conversation associated with a UID 242 to identify the other participant(s) in the conversation and the subject of the conversation.

(52) Exemplary Verification Method

(53) FIG. 4 is a simplified flow diagram of a verification method, indicated generally as 400, according to some exemplary embodiments of the invention.

(54) Depicted exemplary method 400 includes receiving 410 (e.g. at a compliance server 210; FIG. 2) an audio feed of a telephone conversation in progress, ascertaining 420 the telephone numbers of participants in the conversation and causing 430 a user interface to appear on a device owned by at least one of the participants in the conversation.

(55) In some embodiments, of method 400 ascertaining 420 includes using 422 a look-up table of IP addresses associated with telephone numbers. According to various exemplary embodiments of the invention the IP address is of a computer which also functions as a telephone or of a computer assigned to the same person as the telephone belonging to the telephone number (i.e. the computer and the phone are at the same desk).

(56) Alternatively or additionally, in some embodiments of method 400 causing 430 includes remote launching 432 of an application.

(57) Alternatively or additionally, in some embodiments of method 400 causing 430 includes transmission 434 of an SMS to a mobile phone. In some embodiments, this involves using a look-up table of mobile phone numbers associated with telephone numbers.

(58) According to these embodiments, the SMS serves as interface by accepting a yes/no answer.

(59) Alternatively or additionally, in some embodiments of method 400 causing 430 includes 436 transmission of an e-mail message to an e-mail account. In some embodiments, this involves using a look-up table of e-mail addresses associated with telephone numbers.

(60) Exemplary User Interfaces for Verification

(61) FIG. 4 refers to “causing a user interface to appear on a device”. FIGS. 5a-5d present exemplary user interfaces for use in that context.

(62) FIG. 5a is an exemplary verification dialog box, indicated as 500, for a first party in a transaction according to an exemplary embodiment of the invention. Dialog box 500 presents data on the second party and the specific trade being discussed as determined by the system (e.g. 200 of FIG. 2) and asks for verification using Yes/No radio buttons.

(63) FIG. 5b is an exemplary verification dialog box for a second party, indicated as 502, in a transaction according to an exemplary embodiment of the invention. Dialog box 502 presents data on the first party and the specific trade being discussed as determined by the system (e.g. 200 of FIG. 2) and asks for verification using Yes/No radio buttons. Dialog boxes 500 and 502 together provide “mutual verification” if both elicit a “yes” answer.

(64) If either dialog box 500 or 502 elicits a “no” answer, a dialog box with more response options is provided.

(65) FIG. 5c is an exemplary verification dialog box, indicated as 504, with multiple choice format according to an exemplary embodiment of the invention. Dialog box 504 separates identification of the trade from identification of the participant. Participants are presented as a multiple choice list including a “none of the above” choice. If dialog box 504 elicits a “no” or “none of the above answer, a dialog box with more response options is provided.

(66) FIG. 5d is an exemplary verification dialog box, indicated as 506, with free text fields according to an exemplary embodiment of the invention. Free text field 508 is for entry of the name of the trade being negotiated and free text field 510 of for the name of the person on the other side of the telephone conversation.

(67) Exemplary Verification Logic

(68) FIG. 6 is an exemplary logic tree for verification, indicated generally as 600, according to one exemplary embodiment of the invention. According to various exemplary embodiments of the invention one, or both, participants in a conversation are queried according to the same logic.

(69) At 610 a participant in a conversation is presented with participant(s) and a transaction and asked whether the information is correct (see FIG. 5a and/or 5b).

(70) A “Yes” answer results in verification 650. A “No” answer brings up a new dialog box which presents 620 the transaction identifier in a Yes/No format and a multiple choice list of names including a “None of the above” option. If the user makes no negative choices, the information is considered verified 650.

(71) If the user makes at least one negative choice, a new dialog box which asks 630 for entry of a transaction and participant name in free text fields is presented. If data is entered, the information is considered verified 650.

(72) If the user enters no data, or enters data which conflicts with other information in the system (e.g. data entered by the other party to the conversation) a manual review 660 of the conversation is undertaken. In some embodiments, manual review 660 is by personnel at listening stations equipped with earphones (e.g. at compliance center 110 and/or institution 120 and/or institution 130). According to various exemplary embodiments of the invention such personnel listen to audio streams 124 and/or 134 during the telephone conversation and/or to recordings stored at 250 and/or 330. Alternatively or additionally, manual 660 is conducted on text output 236 from converter 234.

(73) Although logic tree 600 is discussed in the context of dialog boxes, similar logic can be implemented using SMS (small message service), IM (instant messaging) or e-mail messages.

(74) FIG. 7 is a simplified flow diagram of a method for producing a unified record of a conversation according to some exemplary embodiments of the invention indicated generally as 700.

(75) Depicted exemplary method 700 includes separately recording 710 a microphone out audio feed from each participant in a telephone conversation and transmitting 712 the recordings to a server. Use of microphone out audio feeds contributes to an increase in clarity of the recording. In some embodiments, recording 710 includes analog to digital conversion (ADC), using appropriate hardware, Optionally, ADC facilitates transmitting 712.

(76) Depicted exemplary method 700 also includes integrating 720 the microphone out audio feed from each participant in the telephone conversation to produce a unified record 721 of the telephone conversation. The microphone out audio feeds correspond to 123 and 124 in FIG. 1. According to various exemplary embodiments of the invention unified record 721 includes an audio recording 722 and/or a text transcript. In some exemplary embodiments of the invention, unified record 721 includes an audio recording 722.

(77) In some exemplary embodiments of the invention, method 700 includes separately recording 730 a speaker in audio feed from each participant in the telephone conversation and transmitting 732 the recordings to the server. In some embodiments recording 730 includes ADC using appropriate hardware. Optionally, ADC facilitates transmitting 732.

(78) In some embodiments integrating 720 incudes matching 724 a speaker in audio feed from one participant in the telephone conversation with a microphone out audio feed of another participant at the server. In some embodiments speaker out and mic in are recorded on both sides as well as an integrated version on each side for a total of six recordings which are transmitted to the server. Optionally, this redundancy contributes to a reduction in errors in unified record 721 and/or an increase in clarity of unified record 721.

(79) In some embodiments method 700 includes adding 740 a common time indicator to the microphone out audio feeds from each participant in the telephone conversation. According to these embodiments integrating 720 incudes assembling 742 microphone out audio feeds of all participants in the conversation using sequential assembly of the common time indicator.

(80) Alternatively or additionally, in some embodiments method 700 includes performing 750 a speech to text transformation on the recordings so that unified record (721) includes a text transcript 752. For example, according to various exemplary embodiments of the invention speech to text transformation 750 is performed during integration 720 or prior to transmission 710.

(81) FIG. 8a is a simplified schematic representation of a computer system which generates a graphic representation (i.e. on a display screen) of content of a conversation according to some exemplary embodiments of the invention indicated generally as 800.

(82) Depicted exemplary system 800 includes an assignment module 810 configured to receive a microphone out audio feed 801 from at least one participant in a telephone conversation and assign a conversation type 811 to the conversation. Configuration of module 810 includes providing speech recognition capability and/or speech to text capability and/or analysis (e.g. natural language recognition; NLR) of speech and/or text. Assignment of conversation type 811 is based upon this analysis.

(83) Depicted exemplary system 800 also includes a template generation module 820 adapted to retrieve a template 821 from a template database 822 based on conversation type 811 and present said template to all participants in said conversation during said conversation. Presentation is typically made on display screens. In some embodiments use of templates 821 contributes to an ability of participants in a conversation to visually apprehend the contents of the conversation. For example, conversations related to financial transactions can be divided into a small number of categories, each with a relatively small number of associated data items. Display of template 821 allows users to see the nature of the transaction. As the template is filled (see below) the details of the transaction are visually confirmed to the participants in the conversation.

(84) Depicted exemplary system 800 also includes a template filling module 830 configured to receive the microphone out audio feed 801 from at least one participant in the telephone conversation and populate fields in the template with details from the conversation prior to conclusion of said conversation. Configuration of module 830 includes providing speech recognition capability and/or speech to text capability and/or analysis (e.g. natural language recognition; NLR) of speech and/or text. Population of fields in template 821 is based upon this analysis.

(85) In some embodiments assignment module 810 is configured to receive microphone out audio feeds 801 from two or more participants in the telephone conversation and compare them before assigning conversation type 811. In cases where different audio feeds suggest different conversation types a clarification request is provided to one or more participants in the conversation on their display screen. In the event that no clarification requests are answered (or conflicting answers are provided), system 800 shows each participant template 821 for the apparent conversation type based upon their microphone out audio feed 801. If the issue is not resolved during the conversation, the system logs the discrepancy and reports it to supervisory personnel (e.g. using a GUI on a supervisor's screen).

(86) In some embodiments system 800 includes a confirmation engine 840 adapted to whisper 841 at least one of the details from the conversation to at least one of the participants prior to conclusion of the conversation and request confirmation. According to various exemplary embodiments of the invention confirmation is made by pressing a key on the telephone (or keyboard or onscreen virtual keypad) or clicking on an onscreen message or a pop-up message on a display screen. Adaptation of confirmation engine 840 may include, for example, provision of text to speech capabilities. According to these embodiments of the invention, confirmation engine 840 “reads” details from fields in template 821 to one or more participants in the conversation as whispers 841 to elicit confirmation.

(87) Alternatively or additionally, in some embodiments confirmation engine 840 requires input from two or more participants in the conversation. According to various exemplary embodiments of the invention this confirmation is via whispers 841 and/or using onscreen prompts as depicted in FIGS. 5a to 5d and described hereinabove.

(88) FIG. 8b is an exemplary graphical user interface (GUI) produced by system 800 according to some embodiments of the system indicated generally as 802.

(89) GUI 822 is depicted in a filled state at the end of the conversation. In the depicted embodiment template 821 appears on the left and text transcript 752 appear on the right.

(90) System 800 creates the GUI as follows:

(91) Text transcript (752) “six month euro for 77” is perceived by assignment module 810 as indicative of a “Forex Spot” trade (conversation type 811).

(92) Template generation module 820 retrieves the relevant template from DB 822 and displays it to participant(s) in the conversation. When initially displayed only the “deal type” fields (Forex and Spot) are populated.

(93) Template filling module 830 analyzes “six month euro for 77” and populates the amount field with “77”; duration field with “6 month”; and CURR2 field with “euro”.

(94) Template filling module 830 then analyzes six eighty six seven sixty six and populates the bid and ask fields with “686” and “766” respectively.

(95) At this point all the fields in template 821 are populated.

(96) “I'll sell and buy there” closes the deal.

(97) FIG. 9a is a simplified schematic representation of a computer system which incorporates deal confirmation (or non-confirmation) into conclusion of va telephone call according to some exemplary embodiments of the invention indicated generally as 900.

(98) Depicted Exemplary System 900 includes a videoconferencing server 910 in concurrent communication with all participants (two participants 911a and 911b are depicted for clarity although a larger number can be accommodated) in a telephone conversation pertaining to a transaction. In some embodiments each participant 911 uses a “soft” telephone on a computer equipped with a display, microphone and speakers (e.g. a “Madonna headset”).

(99) Depicted Exemplary System 900 also includes a confirmation module 920 which provides a graphical user interface (GUI) 921 that includes (i) one disconnect icon indicating transaction completed (922 FIG. 9b) and (ii) another disconnect icon indicating transaction not completed (923 FIG. 9b) to at least one of participants 911 in the conversation.

(100) In some embodiments GUI 921 is presented to all of participants 911.

(101) In some embodiments if one participant disconnects icons 922 and 923 change on the screen(s) of remaining participant(s) to indicate “deal complete” and “NO DEAL” respectively (not depicted).

(102) In the event that conflicting information is provided via GUI 921 (i.e. at least one participant disconnects using icon 922 and at least one participant disconnects using icon 923) system 900 logs the discrepancy and reports it to supervisory personnel (e.g. using a GUI on a supervisor's screen).

(103) In the depicted embodiment system 900 includes a deal tracking module 930 designed and configured to offer an opportunity to complete a transaction by providing a graphical user interface (GUI) 931 including: (i) one call icon indicating pending transaction (depicted as menu 932 in FIG. 9c) to a user initiating a call to a contact with whom the user has an incomplete transaction pending and (ii) another call icon indicating new transaction (depicted as “new trade” 935 in FIG. 9c).

(104) FIG. 9b is an exemplary graphical user interface (GUI) 921 according to some embodiments of the invention. Depicted (GUI) 921 that includes one disconnect icon 922 indicating transaction completed and another disconnect icon 923 indicating transaction not completed.

(105) FIG. 9c is an exemplary graphical user interface (GUI) 931 according to some embodiments of the invention. Depicted exemplary GUI 931 includes icons 932, 933, 934 and 935.

(106) Icon 932 is a menu indicating pending transactions (Trades 1-5 in this example). A user selects a pending transaction (trade) and then clicks call icon 934 to resume communication with the relevant party.

(107) Icon 935 is a new trade icon. In some embodiments pressing icon 935 highlights contact list 933. Selection of a person from list 933 initiates a call to the selected person concerning a new matter.

(108) Exemplary UID Formats

(109) Unique identifiers (UIDs) 242 can have different formats in different embodiments of the invention. For purposes of illustration only, some possible formats are presented here.

(110) These formats employ components such as, but not limited to transaction names (e.g. industry accepted uniform transaction identifiers), Institutional identifiers (e.g. NASDAQ 3 letter or 4 letter codes), date stamp (e.g. mm/dd/yyyy), time stamp (e.g. hr/min in the eastern time zone) and serial number of conversation related to a specific transaction. According to various exemplary embodiments of the invention these components are presented in different orders and/or in different combinations. As used in this specification and the accompanying claims the term “industry accepted uniform transaction identifiers” indicates nomenclature either imposed upon the financial industry (or a sector thereof) by a regulatory agency or agreed upon by participating financial institutions. In cases where no standardized nomenclature is in place, the system provides a same transaction name to both parties in the transaction for use as part of the UID for all communications associated with that transaction.

(111) One exemplary format is:

(112) [transaction name] [date stamp] [time stamp]

(113) This format has the advantage of being short and of automatically presenting all conversations related to a specific transaction in chronological order (either ascending or descending).

(114) Another exemplary format is [institutional identifier of initiator of call] [transaction name] [institutional identifier of recipient of call] [date stamp] [time stamp]

(115) This format is longer but adds information about which party pursued the other party at various stages of the negotiation. Like the previous format it allows automatically presenting all conversations related to a specific transaction in chronological order (either ascending or descending) if appropriate sort instructions are given.

(116) A third exemplary format is:

(117) [transaction name] [serial number of conversation related to the transaction]

(118) This format is short and makes it easy to detect if relevant conversations are deleted from a list.

(119) Exemplary Use Scenarios

(120) Various exemplary embodiments of the invention described throughout this application are expected to find utility, for example, in the context of swap transactions, mortgage negotiations, futures trading, complex trades, trade union agreement negotiations and talent negotiations (e.g. actors or sports professionals) or any other transaction type.

(121) Exemplary Advantages

(122) According to various exemplary embodiments of the invention information pertaining to details of a financial transaction “closed” (or not “closed”) in a telephone conversation are collected and maintained for future reference. Advantages of such a practice include, but are not limited to, resolution of future disputes between parties to the transaction concerning the transaction details and/or assisting parties to the transaction in complying with applicable regulations.

(123) In some exemplary embodiments of the invention, presentation of dialog boxes (FIGS. 5a-5d and accompanying descriptive text) to participants in a conversation during, or just after, the conversation contributes to collection of accurate information in a timely manner.

(124) Alternatively or additionally, in some embodiments transaction details are logged automatically (e.g. template 821 in FIG. 8). This type of embodiment generates a record of transaction details without active user input. Alternatively or additionally, presentation of a visual record of the transaction in progress contributes to an ability of participants to evaluate the transaction.

(125) Alternatively or additionally, in some embodiments final transaction status is confirmed by one or more participants in a conversation as part of a standard “disconnect call” action (see FIG. 9b and accompanying explanation). This type of embodiment provides manually confirmation without being perceived as extra effort by participant(s) in the conversation.

(126) Alternatively or additionally, in some embodiments the system (e.g. 900 in FIG. 9a) provides a menu of pending transactions (e.g. 932) to users. This type of embodiment contributes to an ability of users to monitor their progress towards completion of transactions.

(127) Alternatively or additionally, in some embodiments provision of a “new trade” icon (935 in FIG. 9c) contributes to an ability of the system to assign a new transaction number when relevant.

(128) Alternatively or additionally, in some embodiments confirmation of information pertaining to a conversation by all participants in the conversation serves to verify that the information recorded by each participant is consistent and/or complete.

(129) Alternatively or additionally, in some embodiments operation of compliance center 110 contributes to a reduction in discrepancies between reports prepared by different institutions working on the same transaction(s).

(130) Technical Character

(131) Various exemplary embodiments improve the performance of existing telephone systems (e.g. VOIP calls made using a computer or other device equipped with a screen, microphone and speaker(s)). According to various exemplary embodiments of the invention this improved performance manifests itself as automated logging of transaction details and/or increased conformation between records kept by different institutions and/or presentation of transaction details in a visual format to participants in a conversation during the conversation.

(132) Alternatively or additionally, various exemplary embodiments of the invention apply different analysis methods in a dynamic environment to achieve results which are not standard in the relevant technology field. The result is a breakthrough which was not previously envisioned.

(133) Alternatively or additionally, various described modules, impart added system functionalities which improve the performance of users participating in phone conversations and/or contribute to an ability of financial institutions to comply with applicable regulations.

(134) It is expected that during the life of this patent many communication protocols will be developed and the scope of the invention is intended to include all such new technologies a priori.

(135) Although the invention has been described in conjunction with specific embodiments thereof, it is evident that many alternatives, modifications and variations will be apparent to those skilled in the art. Accordingly, it is intended to embrace all such alternatives, modifications and variations that fall within the spirit and broad scope of the appended claims.

(136) Specifically, components and/or actions ascribed to exemplary embodiments of the invention and depicted as a single unit may be divided into subunits (For example, various modules, engines or databases depicted may reside in a cloud). Conversely, components and/or actions ascribed to exemplary embodiments of the invention and depicted as sub-units/individual actions may be combined into a single unit/action with the described/depicted function.

(137) Alternatively, or additionally, features used to describe a method can be used to characterize an apparatus or system and features used to describe an apparatus or system can be used to characterize a method.

(138) It should be further understood that the individual features described hereinabove can be combined in all possible combinations and sub-combinations to produce additional embodiments of the invention. The examples given above are purely illustrative and are not intended to limit the scope of the invention which is defined solely claims granted as a patent.

(139) Each recitation of an embodiment of the invention that includes a specific feature, part, component, module or process is an explicit statement that additional embodiments of the invention not including the recited feature, part, component, module or process exist.

(140) Specifically, the invention has been described in the context of financial transactions between institutions but might also be used in the context of transactions including non-institutional participants.

(141) All publications, references, patents and patent applications mentioned in this specification are herein incorporated in their entirety by reference into the specification, to the same extent as if each individual publication, patent or patent application was specifically and individually indicated to be incorporated herein by reference. In addition, citation or identification of any reference in this application shall not be construed as an admission that such reference is available as prior art to the present invention.

(142) The terms “include”, and “have” and their conjugates as used herein mean “including but not necessarily limited to”.