System and method for live call verification through enterprise mobile application and websites
The system provides live call verification through enterprise mobile apps and websites by using a REST API to authenticate callers against enterprise databases, effectively preventing scams and enhancing user safety and brand reputation.
Patent Information
- Application Number
- PCT/IB2024/054803
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-19
- Filing Date
- 2024-05-17
- Publication Date
- 2024-11-28
AI Technical Summary
Users lack reliable methods to verify the legitimacy of callers during incoming calls from unknown numbers, leading to potential scams and significant financial losses, as current solutions do not provide a way to confirm the identity of the person on the other end.
A system and method for live call verification through enterprise mobile apps and websites, which uses a REST API to check if the caller is an authorized personnel by integrating with the enterprise's database and CRM system, providing real-time verification and warning messages for scams.
Enables users to reliably verify the legitimacy of callers, preventing scam interactions, protecting customers from financial loss, and enhancing brand reputation by ensuring only authorized personnel are recognized as legitimate.
Smart Images

Figure IB2024054803_28112024_PF_FP_ABST
Abstract
Description
SYSTEM AND METHOD FOR LIVE CALL VERIFICATION THROUGH ENTERPRISE MOBILE APPLICATION AND WEBSITESTECHNICAL FIELD
[0001] The present disclosure relates, in general, to enterprise verification, and more specifically, relates to a system and method for live call verification through enterprise mobile apps and websites.BACKGROUND
[0002] Receiving calls from unknown numbers and potential scammers is a common problem faced by users today. This leads to a significant amount of financial loss each year. The current situation for users receiving calls from unknown numbers is risky, as there is no way to verify the legitimacy of the person on the other end. Scammers can easily pretend to be authorities from banks or government agencies and trick users into giving out sensitive information, resulting in an estimated $4 trillion lost to scams each year. Currently, users only have two options when receiving these calls: trust the person and provide information or disconnect the call. However, there is no way for users to verify if the person on the other end is legitimate. There is a lack of reliable methods for users to verify the legitimacy of the person on the other end of the call.
[0003] Therefore, it is desired to overcome the drawbacks, shortcomings, and limitations associated with existing solutions, and develop a reliable method 300 for live call verification through the mobile apps and websites of enterprises.OBJECTS OF THE PRESENT DISCLOSURE
[0004] An object of the present disclosure relates, in general, to enterprise verification, and more specifically, relates to a system 100 and method 300 for live call verification through enterprise mobile apps and websites.
[0005] Another object of the present disclosure is to provide a reliable method for live call verification through the mobile apps and websites of enterprises.
[0006] Another object of the present disclosure is to provide a system that enables users to verify the legitimacy of the person on the other end of the call and avoid falling victim to scams.
[0007] Another object of the present disclosure is to provide a method that is compatible with all devices and can be used for past calls as well.
[0008] Another object of the present disclosure is to provide a system that protects customers from scams.
[0009] Another object of the present disclosure is to provide a system that gets more call connects on outbound calls.
[0010] Yet another object of the present disclosure is to provide a system that increases brand reputation.SUMMARY
[0011] The present disclosure relates, in general, to enterprise verification, and more specifically, relates to a system and method for live call verification through enterprise mobile apps and websites. The main objective of the present disclosure is to overcome the drawback, limitations, and shortcomings of the existing system and solution, by providing a reliable method for live call verification through the mobile apps and websites of enterprises. This enables users to verify the legitimacy of the person on the other end of the call and avoid falling victim to scams. The method is compatible with all devices and can be used for past calls as well.
[0012] The present disclosure provides a system and method for live call verification through the mobile apps and websites of enterprises. This enables users to verify if the call with an enterprise is legitimate, and avoid falling victim to scams. The live call verification is triggered when the user logs into the mobile app of the enterprise, or by a button on the website. As the user is on an active call, the mobile application calls the representational state transfer (REST) application programming interface (API) exposed by the mobile app server of the enterprise to check if the customer is on a call with one of its authorized personnel. If the call is legitimate, the mobile app shows a message confirming the same. If the call is with a scammer, the mobile app shows a warning message.
[0013] Various objects, features, aspects, and advantages of the inventive subject matter will become more apparent from the following detailed description of preferred embodiments, along with the accompanying drawing figures in which like numerals represent like components.BRIEF DESCRIPTION OF THE DRAWINGS
[0014] The following drawings form part of the present specification and are included to further illustrate aspects of the present disclosure. The disclosure may be better understoodby reference to the drawings in combination with the detailed description of the specific embodiments presented herein.
[0015] FIG. 1A, FIG.1C, FIG. IE illustrates an exemplary schematic view of the system, in accordance with an embodiment of the present disclosure.
[0016] FIG. IB, FIG. ID, FIG. IF illustrates an exemplary schematic view of the system for live call verification through the mobile application and websites of enterprises, in accordance with an embodiment of the present disclosure.
[0017] FIG. 2 illustrates exemplary functional components of the proposed system, in accordance with an embodiment of the present disclosure.
[0018] FIG. 3 illustrates an exemplary method of operation of the system, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION
[0019] The following is a detailed description of embodiments of the disclosure depicted in the accompanying drawings. The embodiments are in such detail as to clearly communicate the disclosure. If the specification states a component or feature “may”, “can”, “could”, or “might” be included or have a characteristic, that particular component or feature is not required to be included or have the characteristic.
[0020] As used in the description herein and throughout the claims that follow, the meaning of “a,” “an,” and “the” includes plural reference unless the context clearly dictates otherwise. Also, as used in the description herein, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise.
[0021] The present disclosure relates, in general, to enterprise verification, and more specifically, relates to a system and method for live call verification through enterprise mobile apps and websites. The present disclosure provides a method for live call verification through the mobile apps and websites of enterprises. This enables users to verify if the call with an enterprise is legitimate, and avoid falling victim to scams. The live call verification is triggered when the user logs into the mobile app of the enterprise, or by a button on the website. As the user is on an active call, the mobile application calls the REST API exposed by the mobile app server of the enterprise to check if the customer is on a call with one of its authorized personnel. If the call is legitimate, the mobile app shows a message confirming the same. If the call is with a scammer, the mobile app shows a warning message. The present disclosure can be described in enabling detail in the following examples, which may represent more than one embodiment of the present disclosure.
[0022] The advantages achieved by the system of the present disclosure can be clear from the embodiments provided herein. The reliable method for live call verification is through the mobile apps and websites of enterprises. This enables users to verify the legitimacy of the person on the other end of the call and avoid falling victim to scams. The method is compatible with all devices and can be used for past calls as well. The description of terms and features related to the present disclosure shall be clear from the embodiments that are illustrated and described; however, the disclosure is not limited to these embodiments only. Numerous modifications, changes, variations, substitutions, and equivalents of the embodiments are possible within the scope of the present disclosure. Additionally, the disclosure can include other embodiments that are within the scope of the claims but are not described in detail with respect to the following description.
[0023] FIG. 1A, FIG.1C, FIG. IE illustrates an exemplary schematic view of the system, in accordance with an embodiment of the present disclosure.
[0024] Referring to FIG. 1A, the present disclosure provides a system 100 and a method 300 for live call verification through the mobile application and websites of enterprises. This method 300 enables users to verify the legitimacy of the person on the other end of the call and avoid falling victim to scams. Although the present subject matter is explained considering that system 100 is implemented as an application on a server 106, it may be understood that the system 100 may also be implemented in a variety of computing systems, such as a laptop computer, a desktop computer, a notebook, a workstation, a server, a network server, a cloud-based environment, and the like. The system 100 can be operatively coupled to multiple enterprise devices 102. It would be appreciated that the system 100 may be accessed by multiple users through computing devices 104 i.e., user terminals or applications residing on the computing devices 104. Examples of the user terminals 104 and the enterprise devices 102 may include, but are not limited to, a portable computer, a personal digital assistant, a handheld device, and a workstation. Further, the user terminal 104 can be communicatively coupled with the enterprise devices 102 through a network. In one implementation, the network can be a wireless network, a wired network or a combination thereof.
[0025] As depicted in FIG. 1A, the system 100 includes an assertion defender 108, which is a component in the voice path of the enterprise that screens all outgoing calls and incoming calls. The mobile application server 106 can be integrated with the assertion defender component 108 to receive incoming call and outgoing call events in real time and send push notifications to the user terminal 104.
[0026] In some embodiments, the assertion defender component 108 is responsible for screening all outgoing and incoming calls within the enterprise's communication infrastructure for verification purposes. The assertion defender 108 intercepts call events in real-time as they occur within the enterprise's telecommunication system 100. It listens for signals or events triggered by the telephony hardware or software indicating the initiation or termination of outgoing and incoming calls.
[0027] In an implementation, every enterprise has its mobile application and website. When a user is in conversation with the enterprise as shown in FIG.1A and gets suspicious about the conversation, they can use the live call verification feature depicted in FIG. IB. The user opens the mobile application of the enterprise and logs in. This triggers the live call verification process automatically in the backend. As the user is on an active call, the mobile application calls the REST API exposed by the mobile app server of the enterprise to check if the customer is on a call with one of its authorized personnel. The REST API call is made in the background, without disturbing the user's call.
[0028] As shown in Fig. 1C, if the user does not log into the mobile application, but executes a direct call to the same number, there will be no message from the bank regarding the call verification or status as it is treated as a normal voice call.
[0029] As shown in FIG. IE, the live call verification may work if the user makes or receives the call on a desk phone / landline as well, as long as it is the registered number of the user. The user will receive a push notification stating that the call is verified. Live call verification can be initiated for a non-active (past) call as well. This may help users validate a call that they may have answered in the past.
[0030] FIG. IB, FIG. ID, FIG. IF illustrates an exemplary schematic view of the system 100 for live call verification through the mobile application and websites of enterprises, in accordance with an embodiment of the present disclosure.
[0031] If the call is with a legitimate person, the mobile application shows a message like “You are on call with <person>. Thanks for calling us today”. If the call is with a scammer as shown in FIG. 1C, the mobile application shows a message like "You are not on call with us, and you may be talking to a fraudster / scammer” as shown in FIG. ID.
[0032] In FIG. C, there is no message from the bank if the user makes a direct call. However, as shown in FIG. ID, during the same direct call, if the user logs into the mobile application and performs a ‘Verify Line call’ function, the application will check the status of the line call through the mobile app server 106. If the call is with a scammer as shown in FIG.1C, the mobile application shows a message like “You are not on call with us, and you may be talking to a fraudster / scammer”
[0033] In an embodiment, the mobile application integrates with an existing database of the enterprise or a CRM (Customer Relationship Management) system. The integration allows the mobile application to access records of authorized personnel within the enterprise. The records might include employee names, roles, contact information, and possibly unique identifiers associated with each employee of the enterprise.
[0034] When the system 100 receives a request for call verification, the REST API is called in the backend. During this process, the mobile application extracts relevant information about the ongoing call, such as the caller's phone number, timestamp, and any other available identifiers. It then then queries the enterprise's database or CRM system 100 using the extracted information. It searches for records of authorized personnel that match the provided details, such as employee names, roles, or unique identifiers. The application can use a matching algorithm to compare the extracted information with the records in the database.
[0035] In an embodiment, the matching algorithm may use various techniques, such as: exact match involving checking for exact matches between the caller's information and the records in the database. For example, matching the caller's phone number with the contact information of authorized personnel. Another technique is of fuzzy matching involving allowing for slight variations or errors in the provided information, which could involve comparing similar strings or using techniques like Levenshtein distance to measure the similarity between strings.
[0036] Further, there may be weighted matching for assigning different weights to various attributes or fields in the database and calculating a weighted score for each potential match. It helps prioritize more critical identifiers in the matching process. The mobile application may use probabilistic models to assess the likelihood of a match based on the available information, which might involve statistical techniques like Bayesian inference or machine learning algorithms trained on historical data.
[0037] The REST API can set a threshold for the matching algorithm to determine when a match is considered valid. The threshold can be based on factors such as the level of confidence in the match or predefined criteria established by the enterprise. Based on the results of the matching algorithm and the set threshold, the system 100 determines whether the caller is a legitimate representative of the enterprise or a potential scammer. If there is asufficiently strong match, the call is verified as legitimate; otherwise, it may be flagged for further investigation or identified as suspicious.
[0038] For live call verification, the backend server exposes a set of RESTfiil endpoints, each representing a specific resource or functionality within the system 100. These endpoints are defined using HTTP methods (e.g., GET, POST, PUT, DELETE) and Uniform Resource Identifiers (URIs) to address different operations or data entities. When the enterprise's mobile application, needs to interact with the backend server, it sends HTTP requests to the appropriate REST API endpoint. The requests include relevant data and parameters required to perform the desired operation, such as verifying a live call. Before processing incoming requests, the backend server authenticates and authorizes the client application to ensure that only authorized users or systems can access the protected resources, which may involve using authentication tokens, API keys, or other authentication mechanisms to validate the client's identity and permissions.
[0039] Upon receiving a valid request, the backend server executes the corresponding business logic or processing logic associated with the requested operation. In the case of live call verification, it may involve querying the database to retrieve information about authorized personnel and performing matching algorithms to verify the legitimacy of the caller. The backend server interacts with the database and other external systems as needed to manipulate data, retrieve information, or integrate with third-party services. For example, it may retrieve caller identification information from the database, perform matching algorithms to compare it with authorized personnel records, and generate a verification outcome based on the results.
[0040] In another embodiment, the live call verification can also be triggered by a button and does not have to be automatic on login into the mobile app. The live call verification feature can also be integrated into the website of the enterprise and be triggered automatically on login or by a button. The method 300 can be used to verify both incoming calls to the user from a legitimate source / scammer, as well as outgoing calls made by the user to a legitimate business / fake call center.
[0041] During typical business hours, the enterprise may experience moderate to high call volumes as customers and clients contact the organization for inquiries, support, or transactions. The module should be able to handle these regular call volumes efficiently to ensure smooth operation of the live call verification system 100. Certain times of the day or specific periods throughout the week may see a significant surge in call traffic, such as duringpromotional events, product launches, or seasonal peaks. The module must scale dynamically to accommodate these peak loads without compromising performance or responsiveness.
[0042] As shown in FIG. IE and FIG. IF, the live call verification may work if the user makes or receives the call on a desk phone / landline as well, as long as it is the registered number of the user. Live call verification can be initiated for a non-active (past) call as well. This may help users validate a call that they may have answered in the past.
[0043] As shown in Fig. IF, the user can create a reporting form through the mobile application wherein the user can provide details about the suspected scam, including: caller's identification information (if available), description of the suspicious behavior or conversation, any additional relevant details or evidence (e.g., screenshots, recordings). The form may also include optional fields for users to provide their contact information if they wish to be contacted for follow-up.
[0044] Thus, the present disclosure overcomes the drawbacks, shortcomings, and limitations associated with existing solutions, and provides a reliable method 300 for live call verification through the mobile application and websites of enterprises. This enables users to verify the legitimacy of the person on the other end of the call and avoid falling victim to scams. The method 300 is compatible with all devices and can be used for past calls as well.
[0045] FIG. 2 illustrates exemplary functional components of the proposed system 100 in accordance with an embodiment of the present disclosure.
[0046] In an aspect, the system 100 may comprise one or more processor(s) 202. The one or more processor(s) 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that manipulate data based on operational instructions. Among other capabilities, the one or more processor(s) 202 are configured to fetch and execute computer-readable instructions stored in a memory 204 of the system 100. The memory 204 may store one or more computer-readable instructions or routines, which may be fetched and executed to create or share the data units over a network service. The memory 204 may comprise any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as EPROM, flash memory, and the like.
[0047] The system 100 may also comprise an interface(s) 206. The interface(s) 206 may comprise a variety of interfaces, for example, interfaces for data input and output devices, referred to as I / O devices, storage devices, and the like. The interface(s) 206 may facilitate communication of system 100 100. The interface(s) 206 may also provide acommunication pathway for one or more components of the system 100. Examples of such components include, but are not limited to, processing engine(s) 208 and database 210.
[0048] The processing engine(s) 208 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) 208. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) 208 may be processor executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) 208 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine -readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) 208. In such examples, the system lOOmay comprise the machine -readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to system 100 and the processing resource. In other examples, the processing engine(s) 208 may be implemented by electronic circuitry. The database 218 may comprise data that is either stored or generated as a result of functionalities implemented by any of the components of the processing engine(s) 208 or the system 100.
[0049] The call event detection module 210 continuously monitors the enterprise's telecommunication network to detect incoming calls or outgoing call events. The detection mechanism may involve interfacing with telephony hardware or software components within the enterprise's communication infrastructure. Upon detecting an incoming call or outgoing call event, the module parses the relevant call metadata to extract essential information. The metadata typically includes caller identification information such as phone numbers, timestamps, and any additional data pertinent to the call. The call event detection module 210 may perform data transformation tasks to standardize the format and structure of the extracted call metadata. This ensures consistency and compatibility with the subsequent stages of the verification process.
[0050] Once the call metadata is parsed and transformed, the call event detection module 210 routes it to the appropriate components within the live call verification system 100 for further processing, which may involve transmitting the data to the metadata extraction module 212, database query module 214, or other relevant modules 216 responsible for verification tasks. The call event detection module 210 incorporates error handling mechanisms to manage any unexpected issues encountered during the call eventreception process, including but not limited to error detection, logging, and reporting functionalities to ensure system 100 reliability and stability.
[0051] The call event detection module 210 interfaces with the enterprise's telephony systems, which may include Private Branch Exchange (PBX) systems, Voice over Internet Protocol (VoIP) platforms, or other communication technologies. The module operates in real-time to capture and process incoming calls or call events promptly. This ensures timely verification and response to user interactions with the enterprise's communication channels. The call event detection module 210 is scalable to accommodate varying call volumes and communication patterns within the enterprise, for optimal performance and responsiveness under different usage scenarios. Measures can be implemented to safeguard the integrity and confidentiality of call-related data transmitted through the module, including encryption, access controls, and other security measures to mitigate risks associated with unauthorized access or data breaches.
[0052] In an embodiment, the metadata extraction module 212 continuously monitors incoming calls or outgoing call events from enterprise devices to detect when a call is initiated or received. It listens for signals or events triggered by the telecommunication system 100 indicating the start or end of a call. Upon detecting a call event, the metadata extraction module 212 parses the associated metadata to extract essential information such as: caller's phone number or identifier, timestamp of the call, duration of the call, and any additional metadata provided by the telecommunication system 100.
[0053] The metadata extraction module 212 may also perform data standardization tasks to ensure consistency and compatibility with the subsequent stages of the verification process. It may involve converting timestamps to a standardized format, normalizing phone numbers, or handling special characters in caller identification information. The metadata extraction module 212 incorporates error handling mechanisms to manage any unexpected issues encountered during metadata extraction. It detects and handles errors such as missing or malformed metadata, ensuring that the verification process can proceed smoothly.
[0054] In an embodiment, the database query module 214 serves as an interface between the live call verification system 100 and the database containing records of authorized personnel within the enterprise. It facilitates efficient querying of the database to retrieve relevant information based on the extracted call metadata. The database query module 214 establishes and manages connections to the enterprise's database, allowing the verification system 100 to interact with stored data. It may utilize database drivers or connection pooling mechanisms to optimize performance and resource utilization.
[0055] Upon receiving call metadata from the metadata extraction module 212, the database query module 214 constructs and executes queries to retrieve records of authorized personnel matching the caller identification information. The queries may involve filtering records based on criteria such as employee names, roles, contact information, or unique identifiers associated with each employee. The database query module 214 retrieves relevant data from the database in response to query requests. It may fetch complete records of authorized personnel or specific attributes required for verification purposes, depending on the information extracted from the call metadata.
[0056] Once data is retrieved from the database, the database query module 214 processes the query results to extract actionable information. The database query module 214 may perform operations such as filtering, sorting, or aggregation to refine the dataset and identify potential matches with the caller identification information. The database query module 214 can also incorporate error handling mechanisms to manage exceptions or issues encountered during the query execution process. It detects and handles errors such as database connection failures, query syntax errors, or data inconsistencies, ensuring robustness and reliability of the verification system 100.
[0057] FIG. 3 illustrates an exemplary method of operation of the system, in accordance with an embodiment of the present disclosure
[0058] The method 300 involves, as indicated in FIG. 3, verifying the legitimacy of incoming and outgoing calls through an enterprise's mobile application and website. It includes, as shown in step 302, receiving call events, wherein the method 300 starts by receiving incoming calls or outgoing call events from enterprise devices. At step 304, the method 300 involves extracting call metadata, including caller identification information, which is extracted from the incoming call or outgoing call event. At step 306, the method 300 involves querying database containing records of authorized personnel within the enterprise is queried using the extracted call metadata. The database includes employee names, roles, contact information, and unique identifiers. Further, at step 308, a matching algorithm can be executed to compare the extracted call metadata with the records in the database. Techniques such as exact matching, fuzzy matching, weighted matching, or probabilistic matching are employed. Finally, at step 310, based on the results of the matching algorithm and a predefined threshold, a verification outcome is determined. The outcome indicates whether the caller is a legitimate representative of the enterprise.
[0059] It will be apparent to those skilled in the art that the system 100 of the disclosure may be provided using some or all of the mentioned features and components without departing from the scope of the present disclosure. While various embodiments of the present disclosure have been illustrated and described herein, it will be clear that the disclosure is not limited to these embodiments only. Numerous modifications, changes, variations, substitutions, and equivalents will be apparent to those skilled in the art, without departing from the spirit and scope of the disclosure, as described in the claims.ADVANTAGES OF THE PRESENT DISCLOSURE
[0060] The present disclosure provides a reliable method for live call verification through the mobile apps and websites of enterprises.
[0061] The present disclosure provides a system that enables users to verify the legitimacy of the person on the other end of the call and avoid falling victim to scams.
[0062] The present disclosure provides a method that is compatible with all devices and can be used for past calls as well.
[0063] The present disclosure provides a system that protects customers from scams.
[0064] The present disclosure provides a system that gets more call connects on outbound calls.
[0065] The present disclosure provides a system that increases brand reputation.
Claims
We Claim:
1. A system (100) for live call verification through a mobile application and a website of an enterprise, the system (100) comprising: a processor (202) configured to execute instructions stored in memory (204), wherein the memory (204) stores instructions executable by the processor (202); a database (210) containing records of authorized personnel within an enterprise, said records comprising employee names, roles, contact information, and unique identifiers associated with each employee; a means for receiving an incoming call or an outgoing call event from an enterprise device; a means for extracting a call metadata, including a caller identification information, from said incoming call or said outgoing call event; a means for querying said database (210) using the extracted call metadata to search for the records of authorized personnel matching the caller identification information; a matching algorithm executed by the processor (202) to compare the extracted call metadata with the records in the database, said matching algorithm employing techniques comprising exact matching, fuzzy matching, weighted matching, or probabilistic matching; a means for determining a verification outcome based on the results of the matching algorithm and a predefined threshold, wherein the verification outcome indicates whether the caller is a legitimate representative of the enterprise.
2. The system (100) as claimed in claim 1, wherein the system (100) is further configured to: generate a notification indicating the verification outcome; and transmit said notification to a user terminal associated with the incoming call or outgoing call event, wherein said notification is displayed to a user interacting with the mobile application or website of the enterprise.
3. The system (100) as claimed in claim 1, wherein the means for receiving an incoming call or outgoing call event includes an assertion defender component (108) integrated into a voice path of the enterprise, said assertion defender component (108) screening all outgoing calls and incoming calls for verification purposes.
4. The system (100) as claimed in claim 1, wherein the matching algorithm utilizes a weighted matching technique, assigning different weights to attributes or fields in the database (210) to prioritize critical identifiers in the matching process.
5. The system (100) as claimed in claim 1, wherein the verification outcome is displayed to the user as a message indicating whether the call is with a legitimate person or a potential scammer.
6. The system (100) as claimed in claim 1, wherein the database (210) of authorized personnel is maintained and updated by the enterprise, said database (210) periodically updated to reflect changes in employee information.
7. The system (100) as claimed in claim 1, wherein the means for transmitting the notification to the user terminal comprises a REST API call from a mobile application server (108) of the enterprise to a mobile application residing on the user terminal.
8. The system (100) as claimed in claim 1, wherein the means for extracting call metadata includes extracting caller identification information comprising phone numbers, timestamps, and voice patterns associated with the incoming call or outgoing call event.
9. A method (300) for live call verification through a mobile application and a website of an enterprise, the method (300) comprising: receiving an incoming call or an outgoing call event from an enterprise device; extracting a call metadata, including caller identification information, from said incoming call or said outgoing call event; querying a database (210) containing records of authorized personnel within the enterprise, said records comprising employee names, roles, contact information, and unique identifiers associated with each employee, using the extracted call metadata to search for the records of authorized personnel matching the caller identification information; executing a matching algorithm to compare the extracted call metadata with the records in the database, said matching algorithm employing techniques comprising exact matching, fuzzy matching, weighted matching, or probabilistic matching; and determining a verification outcome based on results of the matching algorithm and a predefined threshold, wherein the verification outcome indicates whether the caller is a legitimate representative of the enterprise.
10. The method (300) as claimed in claim 9, wherein the method (300) further comprising displaying a notification indicating the verification outcome to a user interacting with the mobile application or website of the enterprise.
Citation Information
Patent Citations
Validating provided information in a conversation
US10810212B2
Call authentication at the call center using a mobile device
WO2021041657A1
Cited By
Systems and methods for call center agent validation
US20260163975A1
