Description:FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See Section 10 and Rule 13)

Title of Invention:
A METHOD AND SYSTEM FOR CALL MANAGEMENT

Applicant:
HASHAI TECH(OPC) PRIVATE LIMITED
An Indian entity having address as:
91SpringBoard, 74/II Techno Park, “C” Cross Road, Opp Gate No 2, Seeps, Andheri East, Mumbai, Maharashtra 400093

The following specification particularly describes the invention and the manner in which it is to be performed.

CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY
[0001] The present application does not claim priority from any other application.
TECHNICAL FIELD
[0002] The present subject matter described herein, in general, relates to advancements in communication technology, specifically focusing on call management systems. More specifically, the present subject matter addresses methods and systems for automating the process of initiating and managing phone calls, with an emphasis on integrating user interfaces and digital sources to streamline communication workflows.
BACKGROUND
[0003] This section is intended to introduce the reader to various aspects of art, the relevant technical field or area of knowledge to which the invention pertains, which may be related to various aspects of the present disclosure that are described or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements in this background section are to be read in this light, and not as admissions of prior art. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches, which in and of themselves may also correspond to implementations of the claimed technology.
[0004] In today's fast-paced world, the necessity for rapid and efficient communication methods has become increasingly critical. Traditional communication solutions often require manual dialing of phone numbers, a process that involves reading phone numbers from various sources, such as spreadsheets, word processing documents, or PDF files, and then dial these numbers into a mobile phone keypad. This manual process is not only laborious but also prone to human errors, such as incorrect number entries or misreading of digits. Such inefficiencies are exacerbated in environments where high volumes of calls are made, leading to significant time wastage and increased operational costs.
[0005] Currently, there is no streamlined mechanism to directly transfer phone numbers from digital sources on a computer to the mobile phone for dialing. The inability to copy and paste phone numbers seamlessly from applications like spreadsheets, word processing, or PDF into a mobile phone interface represents a considerable gap in the existing communication technologies. Existing solutions to such problems offer functionalities which are typically limited to specialized environments, such as call centers, where users have access to integrated software systems and desk phones that facilitate direct calling from the software system. These systems are designed for high-volume communication and involve sophisticated setups that are not practical for everyday users.
[0006] For the average user, who may need to make numerous calls on a daily basis, the lack of an efficient dialing solution means that they must manually input phone numbers into their mobile devices, leading to the increased potential for errors and inefficiencies. This process can be particularly cumbersome when dealing with large datasets or when frequent dialing is required. The current state of technology does not provide an easy and effective way for everyday users to dial numbers directly from their digital sources, resulting in a significant operational disadvantage.
[0007] Therefore, there is a long-felt need for a more intuitive and efficient method that bridges the gap between user computing applications and mobile communication. An improved solution would allow users to initiate and manage phone calls directly from user computing based interfaces or applications, eliminating the need for manual dialing. Such a system would integrate seamlessly with existing digital sources, enabling users to dial phone numbers with minimal effort and reducing the likelihood of errors associated with manual entry.
[0008] In view of the above challenges, addressing these technical issues requires the development of an advanced system that provides user computing application based dialing capabilities. This system would enable users to initiate calls directly from their user computing interface or applications by integrating with various digital sources, such as spreadsheets and documents. By simplifying the process of transferring phone numbers and eliminating manual dialing, the invention aims to enhance user efficiency and accuracy in communication. The proposed solution seeks to offer a more streamlined and user-friendly approach, ultimately improving the overall communication experience for everyday users.
[0009] Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through the comparison of described systems with some aspects of the present disclosure, as set forth in the remainder of the present application and with reference to the drawings.
SUMMARY
[0010] This summary is provided to introduce concepts related to a method for initiating and managing calls using a user computing application based dialing service and the concepts are further described below in the detailed description. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining or limiting the scope of the claimed subject matter.
[0011] According to embodiments illustrated herein, there is provided a method that may involve initiating and managing calls using a dialing service. In one implementation of the present disclosure, the method for call management involves several key steps. Initially, a processor may provide a user interface to a user on their device. This user interface may allow the user to input information, which the processor then receives and processes. The method may involve the processor to extracts a profile information of the user, which may include personal details and call handling preferences. Based on the profile information and/or the user inputs, the processor may transmit a call request to the user device. Finally, the processor may enable initiating a call on the user device, utilizing one or more call management services running on the user device, based on the transmitted call request. It is important to note that the one or more call management services are configured to be make it compatible with the user interface, thereby enabling the call management functionality provided by the disclosed method. This method ensures seamless call management by integrating user profile data and user inputs on a non-mobile which may include, but is not limited to, a laptop, a desktop interface, a non-mobile interface, phone user interface, or a combination thereof to facilitate efficient call initiation and handling on the mobile phone user interface.
[0012] In another embodiment, the method may further enhance the call management functionality by incorporating additional features. These features could include logging and archiving capabilities where users can log conversations, archive numbers, and search by name or number. Call-related information of the user’s mobile phone may be synchronized with the user interface of the user computing application , providing comprehensive logs and insights. The method might also support advanced call handling options such as SIM card selection preference and various number formats configuration. Additionally, the user interface could include a dialing interface with a phone number placeholder and action buttons, as well as a notification mechanism to alert users of incoming or outgoing calls. Contact management within the user application may be enhanced with functionalities for importing and synchronizing contact data with user devices. This embodiment ensures a more robust and user-friendly call management system, catering to diverse user needs and preferences.
[0013] In an embodiment, the system for call management may include a memory, and a processor configured to execute programmed instructions stored in the memory. The processor may provide a user interface to the user on their device, receive one or more user inputs on the interface, and extract the user's profile information. Based on this profile information, user inputs, or a combination of both, the system could generate and transmit a call request to the user device. Subsequently, the system might initiate the call on the user device, utilizing one or more call management services running on the user device, based on this call request. It is important to note that the one or more call management services are configured to make it compatible with the user interface, thereby enabling the call management functionality provided by the disclosed system. This comprehensive approach may efficiently manage calls, seamlessly integrating user inputs and profile information to enhance the user experience.
[0014] In another embodiment, a non-transitory computer-readable storage medium is disclosed. The non-transitory computer-readable storage medium having stored thereon, a set of computer-executable instructions causing a computer comprising one or more processors to perform various steps. The steps may involve providing a user interface to a user of a user device. Further, the steps may involve receiving one or more user inputs on the user interface. Further the steps may involve extracting a profile information of the user. Further, the steps may involve transmitting a call request on the user device based on one of the profile information of the user, the one or more user inputs, or a combination thereof. Furthermore, the steps may involve initiating a call on the user device based on the call request.
[0015] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
BRIEF DESCRIPTION OF DRAWINGS
[0016] The accompanying drawings illustrate the various embodiments of systems, methods, and other aspects of the disclosure. Any person with ordinary skills in the art will appreciate that the illustrated element boundaries (e.g., boxes, groups of boxes, or other shapes) in the figures represent one example of the boundaries. In some examples, one element may be designed as multiple elements, or multiple elements may be designed as one element. In some examples, an element shown as an internal component of one element may be implemented as an external component in another, and vice versa. Further, the elements may not be drawn to scale.
[0017] Various embodiments will hereinafter be described in accordance with the appended drawings, which are provided to illustrate and not to limit the scope in any manner, wherein similar designations denote similar elements, and in which:
[0018] The detailed description is described with reference to the accompanying figures. In the Figures, the left-most digit(s) of a reference number identifies the Figure in which the reference number first appears. The same numbers are used throughout the drawings to refer to the like features and components.
[0019] FIG. 1 is a block diagram that illustrates a system environment (100) for call management, in accordance with an embodiment of the present disclosure.
[0020] FIG. 2 is a block diagram (200) that illustrates various components of an application server (104) configured for performing steps for the call management, in accordance with an embodiment of the present disclosure.
[0021] FIG. 3A-3B are flow diagrams (300) that illustrate flow of user registration on a user mobile device applications and non-mobile applications, in accordance with various embodiments of the present disclosure.
[0022] FIG. 4 is a flowchart that illustrates a method (400) for call management, in accordance with an embodiment of the present disclosure, and
[0023] FIG. 5 illustrates a block diagram (500) of an exemplary computer system for implementing embodiments consistent with the present disclosure.
DETAILED DESCRIPTION
[0024] The present disclosure may be best understood with reference to the detailed figures and description set forth herein. Various embodiments are discussed below with reference to the figures. However, those skilled in the art will readily appreciate that the detailed descriptions given herein with respect to the figures are simply for explanatory purposes as the methods and systems may extend beyond the described embodiments. For example, the teachings presented, and the needs of a particular application may yield multiple alternative and suitable approaches to implement the functionality of any detail described herein. Therefore, any approach may extend beyond the particular implementation choices in the following embodiments described and shown.
[0025] The terms “comprise”, “comprising”, “include(s)”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, system or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or system or method. In other words, one or more elements in a system or apparatus preceded by “comprises… a” does not, without more constraints, preclude the existence of other elements or additional elements in the system or apparatus.
[0026] Reference throughout the specification to “various embodiments,” “some embodiments,” “one embodiment,” or “an embodiment” means that a particular feature, structure, or method described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in various embodiments,” “in some embodiments,” “in one embodiment,” or “in an embodiment” in places throughout the specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0027] The present disclosure relates to a method for enhancing communication connections via mobile devices by utilizing a dialing service. The method addresses the need for a more efficient and user-friendly way to initiate and manage calls directly from the user interface and/or external interfaces, thereby improving the overall communication experience for users. This method leverages modern computing technologies to facilitate real-time interactions between individuals, streamlining the process of dialing phone numbers and initiating calls from digital sources.
[0028] The objective of the present disclosure is a method that simplifies the call initiation process by allowing users to start calls directly from a user interface /external interface. This method aims to reduce the inefficiencies and potential errors associated with manual dialing and offer a more integrated solution for managing communication tasks. By synchronizing contacts between the user interface and the user mobile device, the method enhances the accuracy and ease of managing contact information.
[0029] Another objective of the present disclosure is to integrate the user computing based dialing service with existing third-party applications like CRM, HR, support, directory applications. This integration is intended to facilitate seamless contact and call management, improving efficiency in customer interactions and providing advanced call handling options such as SIM card selection and support for various number formats.
[0030] Yet another objective of the present disclosure is to offer features for logging, archiving, and searching call-related data. This functionality is designed to support effective call information management, enabling users to access and organize call records efficiently. The method also includes the capability to initiate calls even when the user mobile device screen is locked, based on user permissions, further enhancing accessibility and convenience.
[0031] Referring to FIG. 1 is a block diagram that illustrates a system (100) environment for call management for a user, in accordance with an embodiment of the present disclosure. The system (100) typically includes a database server (102), an application server (104), a communication network (106), and a user computing device (108). The database server (102), the application server (104), and the user computing device (108) are typically communicatively coupled with each other via the communication network (106). In an embodiment, the application server (104) may communicate with the database server (102), and the user computing device (108) using one or more protocols such as, but not limited to, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), RF mesh, firebase cloud, messaging, Bluetooth Low Energy (BLE), and the like, to communicate with one another.
[0032] In an embodiment, the database server (102) may refer to a computing device configured to store the user's mobile app data. Additionally, the database server (102) may include a special-purpose operating system specifically designed to perform one or more database operations on multimedia content. Examples of database operations may include, but are not limited to, Select, Insert, Update, and Delete. In an embodiment, the database server (102) may include hardware that may be configured to perform one or more predetermined operations. In an embodiment, the database server (102) may be realized through various technologies such as, but not limited to, Microsoft® SQL Server, Oracle®, IBM DB2®, Microsoft Access®, PostgreSQL®, MySQL®, SQLite®, distributed database technology and the like. In an embodiment, the database server (102) may be configured to utilize the application server (104) for the storage and retrieval of data used for managing user profiles, handling call logs, and processing multimedia content related to the call management system (100).
[0033] A person with ordinary skills in art will understand that the scope of the disclosure is not limited to the database server (102) as a separate entity. In an embodiment, the functionalities of the database server (102) can be integrated into the application server (104) or into the user computing device (108).
[0034] In an embodiment, the application server (104) may refer to a computing device or a software framework hosting an application or a software service. In an embodiment, the application server (104) may be implemented to execute procedures such as, but not limited to, programs, routines, or scripts stored in one or more memories for supporting the hosted application or the software service. In an embodiment, the hosted application or the software service may be configured to perform one or more predetermined operations. The application server (104) may be realized through various types of application servers such as, but are not limited to, a Java application server, a .NET framework application server, a Based application server, a PHP framework application server, or any other application server framework.
[0035] In an embodiment, the application server (104) may be configured to utilize the database server (102) and the user computing device (108) in conjunction for providing seamless data synchronization, efficient call management services, and real-time updates to a user interface. In an implementation, the application server (104) corresponds to a user interface platform for managing user interactions, processing user inputs, and delivering real-time call handling and management.
[0036] In an embodiment, the communication network (106) may correspond to a communication medium through which the application server (104), the database server (102), and the user computing device (108) may communicate with each other. Such communication may be performed in accordance with various wired and wireless communication protocols. Examples of such wired and wireless communication protocols include but are not limited to, Transmission Control Protocol and Internet Protocol (TCP/IP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), Wireless Application Protocol (WAP), File Transfer Protocol (FTP), ZigBee, EDGE, infrared IR), IEEE 802.11, 802.16, 2G, 3G, 4G, 5G, 6G, 7G cellular communication protocols, and/or Bluetooth (BT) communication protocols. The communication network (106) may either be a dedicated network or a shared network. Further, the communication network (106) may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like. The communication network (106) may include, but is not limited to, the Internet, intranet, a cloud network, a Wireless Fidelity (Wi-Fi) network, a Wireless Local Area Network (WLAN), a Local Area Network (LAN), a cable network, the wireless network, a telephone network (e.g., Analog, Digital, POTS, PSTN, ISDN, xDSL), a telephone line (POTS), a Metropolitan Area Network (MAN), an electronic positioning network, an X.25 network, an optical network (e.g., PON), a satellite network (e.g., VSAT), a packet-switched network, a circuit-switched network, a public network, a private network, and/or other wired or wireless communications network configured to carry data.
[0037] In an embodiment, the user computing devices (108) may refer to a computing device used by the user for call handling and management. In one embodiment, the user computing device (108) may correspond to a user mobile device which initiates the call requested through an external user interface. In another embodiment, the user computing device (108) may correspond to a device hosting/rendering the external user interface by which the user makes the call request. The user computing devices (108) may comprise of one or more processors and one or more memory. The one or more memories may include computer-readable code that may be executable by one or more processors to perform predetermined operations. In an embodiment, the user computing devices (108) may present an user interface to receive user inputs and communicate the call handling request/response with the application server (104). For example, user interfaces are presented on the user computing devices (108) to display a portal visualizing user profiles and relevant information, to provide users with an intuitive and comprehensive view of their contact details, call history, and call handling preferences. Examples of the user computing devices (108) may include but are not limited to, a user device (108), a personal computer, a laptop, a personal digital assistant (PDA), a mobile device, a tablet, or any other computing device.
[0038] The system (100) can be implemented using hardware, software, or a combination of both, which includes using where suitable, one or more computer programs, mobile applications, or “apps” by deploying either on-premises over the corresponding computing terminals or virtually over cloud infrastructure. The system (100) may include various micro-services or groups of independent computer programs which can act independently in collaboration with other micro-services. The system (100) may also interact with a third-party or external computer system. Internally, the system (100) may be the central processor of all requests for transactions by the various actors or users of the system. A critical attribute of the system (100) is that it can concurrently and instantly complete the call handling and management in collaboration with other systems. In a specific embodiment, the system (100) is implemented to provide call management capabilities, including the storage and retrieval of user profiles, call logs, and multimedia content.
[0039] FIG. 2 illustrates a block diagram (200) showing various components of the application server (104) configured for stepwise call management, in accordance with an embodiment of the present invention. The block diagram (200) includes the following key components: a processor (202), a memory (204), a transceiver (206), a user interface unit (208), a profile extraction unit (210), a call requesting unit (212), a profile creation unit (214), and an insights generation unit (216). The user interface unit (208) allows users to input their preferences and includes a dialing interface for the user. This interface consists of one or more placeholders and one or more action buttons. The profile extraction unit (210) along with the profile creation unit (214) may be responsible for creating and maintaining user profiles based on the input provided by the users, including detailed information about the users. The call requesting unit (212) may initiate calls based on the received call requests. The profile creation unit (214) allows users to create their profiles on the user interface, including user authentication and synchronization of the user’s contact list from their device. The insights generation unit (216) may provide detailed analytics and reports based on the collected call data of the user on the user interface.
[0040] The processor (202) comprises suitable logic, circuitry, interfaces, and/or code that may be configured to execute a set of instructions stored in the memory (204), and may be implemented based on several processor technologies known in the art. The processor (202) works in coordination with the transceiver (206), the user interface unit (208), the profile extraction unit (210), the call requesting unit (212), the profile creation unit (214), and the insights generation unit (216) for providing call management service to the user. Examples of the processors (202) include but are not limited to, a standard microprocessor, microcontroller, central processing unit (CPU), an X86-based processor, a Reduced Instruction Set Computing (RISC) processor, an Application- Specific Integrated Circuit (ASIC) processor, and a Complex Instruction Set Computing (CISC) processor, distributed or cloud processing unit, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions and/or other processing logic that accommodates the requirements of the present invention.
[0041] The memory (204) comprises suitable logic, circuitry, interfaces, and/or code that may be configured to store the set of instructions, which are executed by the processor (202). Preferably, the memory (204) is configured to store one or more programs, routines, or scripts that are executed in coordination with the processor (202). Additionally, the memory (204) may include any computer-readable medium or computer program product known in the art including, for example, volatile memory, such as static random-access memory (SRAM) and dynamic random-access memory (DRAM), and/or non-volatile memory, such as read-only memory (ROM), erasable programmable ROM, a Hard Disk Drive (HDD), flash memories, Secure Digital (SD) card, Solid State Disks (SSD), optical disks, magnetic tapes, memory cards, virtual memory and distributed cloud storage. The memory (204) may be removable, non-removable, or a combination thereof. Further, memory (204) may include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement particular abstract data types. The memory (204) may include programs or coded instructions that supplement the applications and functions of the system (100). In one embodiment, the memory (204), amongst other things, serves as a repository for storing data processed, received, and generated by one or more of the programs or the coded instructions. In yet another embodiment, the memory (204) may be managed under a federated structure that enables the adaptability and responsiveness of the application server (104).
[0042] The transceiver (206) comprises suitable logic, circuitry, interfaces, and/or code that may be configured to receive, process or transmit information, data or signals, which are stored by the memory (204) and executed by the processor (202). The transceiver (206) is preferably configured to receive, process or transmit, one or more programs, routines, or scripts that are executed in coordination with the processor (202). The transceiver (206) is preferably communicatively coupled to the communication network (106) of the system (100) for communicating all the information, data, signals, programs, routines or scripts through the network.
[0043] The transceiver (206) may implement one or more known technologies to support wired or wireless communication with the communication network (106). In an embodiment, the transceiver (206) may include but is not limited to, an antenna, a radio frequency (RF) transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a Universal Serial Bus (USB) device, a coder-decoder (CODEC) chipset, a subscriber identity module (SIM) card, and/or a local buffer. Also, the transceiver (206) may communicate via wireless communication with networks, such as the Internet, an Intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN). Accordingly, the wireless communication may use any of a plurality of communication standards, protocols and technologies, such as: Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for email, instant messaging, and/or Short Message Service (SMS).
[0044] The user interface unit (208) may comprise a dialing interface that may include one or more placeholders and one or more action buttons, or a combination thereof. This dialing interface may include one or more placeholders for entering or displaying a phone number, enabling users to easily input the number they wish to call. The user inputs may comprises dialing the phone number, selecting the phone number from the call history interface, selecting a contact from a contact list, a paste action corresponding to a copy or cut action from an external interface, click event on a call icon, click event on a hyperlink, selecting a number from a user computing interface, right click on the number on the user computing interface, or a combination thereof. Additionally, the dialing interface may incorporate multiple action buttons to enhance functionality and user convenience. These action buttons may include a call start button for initiating calls, an end call button for terminating active calls, a create contact button for adding new contacts to an address book, an edit contact button for modifying existing contact details, an add comment button for annotating call related information, an import button for bringing in contacts from external sources, and a sync button for updating contact information across devices. The combination of these features ensures a comprehensive and user-friendly dialing experience, allowing users to manage their calls and contacts efficiently. In another embodiment, the user interface unit (208) features a comprehensive call history interface designed to present users with detailed information about their call activities. This call history interface may provide a wealth of information, including but not limited to the phone number dialed, the start time and end time of each call, and the duration of each call. Additionally, the disclosed user interface unit (208) includes the capability to record and store call recordings for all the calls made through the user interface. Users can also add comments associated with each call, which can be displayed alongside the call details, providing further context and notes on the interactions. Moreover, the user interface is designed to be highly accessible. Users may interact with it through a standard internet browser, which means that it may be compatible with most user computing interfaces. This accessibility may be further enhanced by the availability of software applications, mobile applications, web browser plugins, or application programming interfaces (APIs) that facilitate seamless interaction with the call history interface. This ensures that users can easily access and manage their call history data without needing specialized software. Additionally, the user interface may be integrated with third-party applications, such as Customer Relationship Management (CRM) systems. This integration means that users can manage their call data and history within the familiar context of their existing CRM system/applications, whether they are using a personal computer, laptop, desktop PC, or any variant of these devices running on any operating system.
[0045] In an exemplary embodiment, the system (100) may integrate with third-party application like CRM applications such as HubSpot, Zoho CRM, and Salesforce and similar as well as other kinds of software including but not limited to HR, Support, B2B, B2C, Banking, directory, and other where user wants to interact with businesses with simple click to connect on his mobile. This integration may allow users to synchronize contact information and call data between the user computing application and their CRM systems. For instance, if a user updates a contact's details in the CRM, those changes could be reflected in the user computing application and vice versa, ensuring consistency across platforms.
[0046] The profile extraction unit (210) may be configured to extract profile information of the user. Further, the profile information of the user may include the username, contact details, user device ID, user device type, call handling preferences, or a combination thereof. In an embodiment, the contact details may include the user’s phone number, the user’s email ID, the user’s address, the user’s contact list from the user device, and the call history from the user device. Further, the call handling preferences may correspond to a Subscriber Identity Module (SIM) selection preference before call initiation, the user’s control preference over the call initiation, configuration preference for supporting phone number formats, and call configuration preference on a lock screen of the user device. The call configuration preference on the lock screen of the user device may corresponds to initiating a call directly when the screen of the user device is locked, based on the call handling preferences. Further the user’s control preference over the call initiation may correspond to populating the phone number on a dialing interface of the user device application and receiving a user confirmation, on the dialing interface of the user device application, for initiating the call.
[0047] In another embodiment, the system (100) may support call handling features, such as the ability to specify which SIM card to use for a call initiation. Users might be able to choose between multiple SIM cards on their device, depending on their preferences or needs. For example, if a user has both a personal and a business SIM card, they could select which one to use for the call initiated from the user interface. The system (100) may also support various number formats, including international prefixes and spaces, to accommodate different dialing requirements.
[0048] In an embodiment, the call requesting unit (212) may be configured for transmitting a call request to the user computing device (108). This request may be based on various factors such as the profile information of the user, specific inputs provided by the user, or a combination of these elements. Once the call request is sent, the call requesting unit (212) may also be responsible for initiating the call on the user computing device (108) after processing the request. This ensures that the call is set up according to the user’s preferences and inputs.
[0049] In an embodiment, transmitting the call request to the user computing device (108) may involve sending the call request to one or more call management services operating on the user computing device (108). These call management services are designed to handle and facilitate the call initiation process and are compatible with the user interface. The call management services may use the profile information of the user, which includes details such as contact information, call handling preferences, and device specifics, to configure and initiate the call. It is important to note that the one or more call management services are configured to make it compatible with the user interface, thereby enabling the call management functionality provided by the disclosed system (100). This process ensures that the call is set up according to the user's predefined settings and preferences, allowing for seamless and efficient call management. Furthermore, the primary function of these call management services is to facilitate the initiation of calls by interfacing with the user device’s hardware and software. They manage tasks such as setting up the call, routing it through the appropriate network channels, and ensuring that the call connects successfully. These call management services are engineered to be fully compatible with the user interface, meaning they can seamlessly integrate with and respond to commands from the user interface. This compatibility ensures that the call management services can efficiently process and act upon the call request, providing a smooth and reliable call initiation experience.
[0050] In an embodiment, the profile creation unit (214) may facilitate the creation of a user profile through the user interface. The unit (214) may manage the creation of the user profile by guiding users through authentication, which is typically based on the user’s phone number to verify identity and secure user account. Once authenticated, the profile creation unit (214) may facilitate the synchronization of the user’s contact list from their device. This synchronization process ensures that the contact information is accurately reflected in the user profile, enabling features such as quick access to contacts and integration with other call management functionalities. The profile creation unit (214) may also handle the integration of additional profile elements, such as user preferences and call handling settings, providing a comprehensive and personalized user experience.
[0051] In an embodiment, the insights generation unit (216) may be integral to the process of analyzing and generating detailed insights from the call data collected through the user interface. In another embodiment, the insights generation unit (216) may utilize advanced data processing algorithms to examine the specifics of each call, including but not limited to phone numbers, call start and end times, call durations, call recordings, and any associated user comments.
[0052] In another embodiment, insights generation unit (216) may aggregate this information to produce various types of analytics and reports. For example, it might identify trends in calling patterns, such as peak calling times or frequent contacts. It may also track metrics like call duration averages or the frequency of calls to specific numbers. In addition, the insights generation unit (216) may be capable of providing comparative analyses, such as how current call activities measure up against historical data. Reports generated by the insights generation unit (216) may be presented in user-friendly formats, such as graphs, charts, or tables, allowing users/stakeholders to easily interpret and utilize the information. These insights can assist users in understanding their call behaviors, optimizing their communication strategies, and making data-driven decisions to improve their call management.
[0053] In an exemplary, but non-limiting embodiment, the system (100) may include a mobile or tablet app designed to provide users with seamless experience for initiating and managing calls. The app could feature a login UI (user interface) that allows users to authenticate their accounts and synchronize their contacts with the user computing application. For example, users might log in and see their contacts automatically updated from the user computing application, enabling them to start calls directly from their mobile devices without manually inputting phone numbers.
[0054] In another embodiment, the user computing application might offer a dialing interface where users can enter phone numbers and initiate calls directly. This interface may include options for users to input numbers and initiate calls with a single click. For instance, if a user finds a phone number on a webpage, they could type or copy/paste it into the dialing interface and click “Dial” to start the call. The user computing app might then send the call request to the mobile app, which could either directly initiate the call or populate the number in the dialer app for user confirmation.
[0055] In yet another embodiment, the system (100) could include a user computing application / browser plugin that enables users to dial numbers directly from web pages. The plugin might be available for popular browsers like but not limited to Chrome, MS Edge, Firefox, and Opera and any other commonly used browser, allowing users to right-click on any listed phone number and select an option to initiate the call. For example, if a user is viewing a contact list or a business directory, they might simply right-click on a phone number and choose “Dial” to start the call through the user device application -based service.
[0056] In an additional embodiment, the system (100) may offer features for logging and archiving call data. Users might be able to log conversations, archive phone numbers, and search through call records by name or number. For example, if a user needs to reference a previous conversation, they could search the call logs by contact name or phone number to find the relevant details.
[0057] In yet another embodiment, the application might support various number formats, including international prefixes and special characters such as "-", "+", and "0". This feature could ensure that users can input phone numbers in different formats and still successfully initiate calls. For example, a user might enter a phone number with an international prefix like "+91" or include spaces and hyphens, and the system would correctly process and dial the number.
[0058] In another embodiment, the system (100) could provide functionality for managing contacts within the application. This may include importing contacts from CSV or any other format files but is not limited to spreadsheet, vCard (VCF), or XML files, or a combination thereof, for updating contact information, adding comments, and archiving old contacts. For instance, a user may import a CSV file containing their entire contact list and then update individual contact details or add notes about specific contacts.
[0059] In a further embodiment, the system (100) may support organizational and team management features, allowing multiple users to be managed under a single account. Organizations might set up accounts for different teams, manage user access, and utilize a common repository of data. For example, a company could have separate teams for sales and support, each with their own access rights and shared contact information, enabling efficient team coordination and data management.
[0060] Further, FIG. 3A and 3B illustrate flow diagrams (300) depicting the process of user registration on a user mobile device applications and non-mobile applications.
[0061] Further, FIG. 3A is a flow diagram (300) that illustrates the process of user registration on the user mobile device application. The diagram details the sequence of actions required for a user to create an account on the user computing device (108) / mobile platform. It includes steps such as entering registration information, completing user verification (such as SMS verification or biometric authentication), and finalizing the account setup. The diagram also shows how the user computing device (108) / mobile application interacts with backend services (Database (102)) to synchronize user data and settings with any user computing systems, ensuring a consistent and seamless registration experience across both platforms.
[0062] Furthermore, FIG. 3B is a flow diagram (300) that illustrates a detailed process for user registration on the non-mobile applications, specifically a user computing device. The diagram outlines the sequence of steps involved, starting from the initial user input of registration details, such as personal information and contact data. It includes verification steps, such as email confirmation or phone number validation, and ends with the creation of a user profile in the system. The diagram also shows interactions between the user interface and backend services (Database (102)) to ensure data integrity and synchronization throughout the registration process.
[0063] FIG. 4 is a flow diagram that illustrates a method (400) for call management from a non-mobile application to the user device (108) /mobile device using a database server (102), in accordance with at least one embodiment of the present disclosure. The method (400) starts at step (402) and proceeds to step (410). This flow diagram details each stage of the call initiation process, highlighting the interactions between the user computing application, database server (102), and user device (108) / mobile device to facilitate seamless communication.
[0064] In operation, the method (400) may involve a variety of steps to initiate a call from the non-mobile application to a user device (108) / mobile device
[0065] At step (402), the method (400) is configured for providing a user interface to a user of the user device (108). This initial step may involve displaying an interactive user interface on the user device (108). The user interface is designed to enable the user to input relevant details for initiating a call, such as phone numbers or contact information. During this step, the system (100) may present various interactive elements, such as user input fields, buttons, and menus, to facilitate user interaction. The user interface may also include features for selecting contacts, entering phone numbers, or specifying call preferences.
[0066] At step (404), the method (400) comprises a step of receiving via the processor (202) one or more user inputs on the user interface. The step (404) encompasses capturing and processing various forms of input provided by the user, such as entering a phone number, selecting a contact from a list, or specifying call preferences. The processor (202) records these inputs, which may include details like the recipient’s number, call type (e.g., voice or video), and any additional user instructions or preferences related to the call. The received inputs are then used to prepare the call request, ensuring that all necessary information is accurately gathered and processed.
[0067] At step (406), method (400) involves a step for the processor (202) to extract the profile information of the user. The step (406) entails retrieving and analyzing the user’s profile data, which may include details such as the user’s name, contact information, device ID, and any specific call handling preferences. The processor (202) accesses this profile information from a database or storage system, ensuring that the call request is tailored to the user's individual settings and requirements. The extracted profile information can include various elements, such as the user’s preferred phone number formats, call preferences (e.g., SIM selection), and historical call data.
[0068] At step (408), method (400) involves a step for transmitting a call request to the user device (108). This process entails the processor (202) sending the call initiation details based on the extracted user profile information and the inputs provided by the user. The transmission includes assembling the necessary data, such as the recipient’s phone number and any call preferences, and then delivering this information to the user device (108). The call request may be routed through various communication channels or call management services to ensure proper handling and execution. This step is critical for transitioning from the preparation phase to the actual initiation of the call, setting up the call request for further processing and connection establishment.
[0069] At step (410), method (400) involves a step for initiating a call on the user device (108) based on the call request. This step encompasses the processor (202) taking the call request, which has been transmitted to the user device (108) and using it to initiate the actual call. The processor (202) may interact with call management services running on the user device (108) to start the call, ensuring that all necessary details from the request, such as the recipient’s phone number and any user preferences, are correctly applied. This process ensures that the call is established and connected as specified by the user’s inputs and profile information, completing the call initiation phase.
[0070] Let us delve into a detailed example of the present disclosure. In this example, the process of initiating a call using a call management system is illustrated to show how the method operates in a practical scenario.
[0071] Consider a user interacting with a call management system (100), which could be integrated into various platforms such as a user computing application, a mobile app, or a desktop application. The user begins by accessing the interface provided by the system (100), which may offer features for dialing, managing contacts, and configuring call preferences.
[0072] The user enters a phone number into the provided interface and selects an option to initiate a call. The system (100) captures this input and sends it to its backend processing unit. The processor (202) in the backend system extracts the user's profile information, which might include details like preferred call formats, SIM card choices, and specific call handling settings.
[0073] Based on this profile information, the system (100) prepares a call request that includes the phone number entered by the user and incorporates any relevant preferences or configurations. This call request is then transmitted to the user's device or the appropriate call management service.
[0074] Upon receipt of the call request, the user device (108) or call management service processes the request according to the specified details. This involves initiating the call by dialing the number and applying any user-specific settings, such as selecting the correct SIM card or configuring call preferences.
[0075] Once the call is initiated, the user can proceed with the communication as intended. This example demonstrates how the method supports flexible call management by adapting to different interfaces and user preferences, ensuring a seamless and customized calling experience.
[0076] Working Example:
[0077] To illustrate the practical application of the call management method (400), consider a scenario involving a user interacting with a call management system (100) across different platforms. This working example highlights the key steps and functionality involved in initiating and managing a call.
[0078] The user accesses the call management system (100), which could be integrated into various platforms such as a user computing application, mobile app, or desktop application. The system is designed to provide a user interface for managing calls, including options for dialing numbers, managing contacts, and configuring call settings.
[0079] The user opens the user interface and inputs, selects or searches a phone number they wish to call. They may also select additional options such as choosing a specific SIM card, applying call preferences, or selecting contact details from their contact list.
[0080] The system (100) captures the user's input and sends this information to the backend processing unit. Here, the processor (202) extracts the user's profile information, which may include preferred phone number formats, SIM selection preferences, and other call handling configurations.
[0081] Based on the extracted profile information and the user's inputs, the system generates a call request. This request includes details such as the phone number to be dialed and any applicable preferences. The call request is transmitted to the user device (108) or a call management service.
[0082] Upon receiving the call request, the user device (108) or call management service processes the request. This involves dialing the specified number and applying the user's preferences. For instance, if the user prefers a specific SIM card for calls or has set preferences for handling calls on a locked screen, these settings are applied.
[0083] The call is then established, allowing the user to communicate with the intended recipient. The system (100) ensures that the call initiation adheres to the user's preferences and configurations, providing a seamless and customized calling experience.
[0084] This working example demonstrates how the call management method (400) can be effectively applied across various platforms, allowing users to initiate and manage calls with flexibility and efficiency. The integration of user profile information and preferences ensures that the calling process is tailored to individual needs and settings.
[0085] A person skilled in the art will understand that the scope of the disclosure is not limited to scenarios based on the aforementioned factors and using the aforementioned techniques and that the examples provided do not limit the scope of the disclosure.
[0086] FIG. 5 illustrates a block diagram (500) of an exemplary computer system (501) for implementing embodiments consistent with the present disclosure.
[0087] Variations of computer systems (501) may be used for automating the process of initiating and managing phone calls, with an emphasis on integrating user interfaces and digital sources to streamline communication workflows. The computer system (501) may comprise a central processing unit (“CPU” or “processor”) (502). The processor (502) may comprise at least one data processor for executing program components for executing user- or system-generated requests. A user may include a person, a person using a device such as those included in this disclosure, or such a device itself. Additionally, the processor (502) may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, or the like. In various implementations the processor (502) may include a microprocessor, such as AMD Athlon, Duron or Opteron, ARM’s application, embedded or secure processors, IBM PowerPC, Intel’s Core, Itanium, Xeon, Celeron or other line of processors, for example. Accordingly, the processor (502) may be implemented using mainframe, distributed processor, multi-core, parallel, grid, or other architectures. Some embodiments may utilize embedded technologies like application-specific integrated circuits (ASICs), digital signal processors (DSPs), or Field Programmable Gate Arrays (FPGAs), for example.
[0088] Processor (502) may be disposed of in communication with one or more input/output (I/O) devices via I/O interface (503). Accordingly, the I/O interface (503) may employ communication protocols/methods such as, without limitation, audio, analog, digital, monoaural, RCA, stereo, IEEE-1394, serial bus, universal serial bus (USB), infrared, PS/2, BNC, coaxial, component, composite, digital visual interface (DVI), high-definition multimedia interface (HDMI), RF antennas, S-Video, VGA, IEEE 802.n /b/g/n/x, Bluetooth, cellular (e.g., code-division multiple access (CDMA), high-speed packet access (HSPA+), global system for mobile communications (GSM), long-term evolution (LTE), WiMAX, or the like, for example.
[0089] Using the I/O interface (503), the computer system (501) may communicate with one or more I/O devices. For example, the input device (504) may be an antenna, keyboard, mouse, joystick, (infrared) remote control, camera, card reader, fax machine, dongle, biometric reader, microphone, touch screen, touchpad, trackball, sensor (e.g., accelerometer, light sensor, GPS, gyroscope, proximity sensor, or the like), stylus, scanner, storage device, transceiver, video device/source, or visors, for example. Likewise, an output device (505) may be a user’s smartphone, tablet, cell phone, laptop, printer, fax machine, video display (e.g., cathode ray tube (CRT), liquid crystal display (LCD), light- emitting diode (LED), plasma, or the like), or audio speaker, for example. In some embodiments, a transceiver (506) may be disposed in connection with the processor (502). The transceiver (506) may facilitate various types of wireless transmission or reception. For example, the transceiver (506) may include an antenna operatively connected to a transceiver chip (example devices include the Texas Instruments® WiLink WL1283, Broadcom® BCM4750IUB8, Infineon Technologies® X-Gold 618-PMB9800, or the like), providing IEEE 802.11a/b/g/n, Bluetooth, FM, global positioning system (GPS), and/or 2G/3G/5G/6G HSDPA/HSUPA communications, for example.
[0090] In some embodiments, the processor (502) may be disposed of in communication with a communication network (508) via a network interface (507). The network interface (507) is adapted to communicate with the communication network (508). The network interface (507) may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), transmission control protocol/internet protocol (TCP/IP), token ring, or IEEE 802.11a/b/g/n/x, for example. The communication network (508) may include, without limitation, a direct interconnection, local area network (LAN), wide area network (WAN), wireless network (e.g., using Wireless Application Protocol), or the Internet, for example. Using the network interface (507) and the communication network (508), the computer system (501) may communicate with devices such as shown as a laptop (509) or a mobile/cellular phone (510). Other exemplary devices may include, without limitation, personal computer(s), server(s), fax machines, printers, scanners, various mobile devices such as cellular telephones, smartphones (e.g., Apple iPhone, Blackberry, Android-based phones, etc.), tablet computers, eBook readers (Amazon Kindle, Nook, etc.), laptop computers, notebooks, gaming consoles (Microsoft Xbox, Nintendo DS, Sony PlayStation, etc.), or the like. In some embodiments, the computer system (501) may itself embody one or more of these devices.
[0091] In some embodiments, the processor (502) may be disposed of in communication with one or more memory devices (e.g., RAM 513, ROM 514, etc.) via a storage interface (512). The storage interface (512) may connect to memory devices including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as serial advanced technology attachment (SATA), integrated drive electronics (IDE), IEEE-1394, universal serial bus (USB), fiber channel, small computer systems interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, redundant array of independent discs (RAID), solid-state memory devices, or solid-state drives, for example.
[0092] The memory devices may store a collection of program or database components, including, without limitation, an operating system (516), user interface application (517), web browser (518), mail client/server (519), user/application data (520) (e.g., any data variables or data records discussed in this disclosure) for example. The operating system (516) may facilitate resource management and operation of the computer system (501). Examples of operating systems include, without limitation, Apple Macintosh OS X, UNIX, Unix-like system distributions (e.g., Berkeley Software Distribution (BSD), FreeBSD, NetBSD, OpenBSD, etc.), Linux distributions (e.g., Red Hat, Ubuntu, Kubuntu, etc.), IBM OS/2, Microsoft Windows (XP, Vista/7/8, etc.), Apple iOS, Google Android, Blackberry OS, or the like.
[0093] The user interface (517) if for facilitating the display, execution, interaction, manipulation, or operation of program components through textual or graphical facilities. For example, user interfaces may provide computer interaction interface elements on a display system operatively connected to the computer system (501), such as cursors, icons, check boxes, menus, scrollers, windows, or widgets, for example. Graphical user interfaces (GUIs) may be employed, including, without limitation, Apple Macintosh operating systems’ Aqua, IBM OS/2, Microsoft Windows (e.g., Aero, Metro, etc.), Unix X-Windows, or web interface libraries (e.g., ActiveX, Java, JavaScript, AJAX, HTML, Adobe Flash, etc.), for example.
[0094] In some embodiments, the computer system (501) may implement a web browser (518) stored program component. The web browser (518) may be a hypertext viewing application, such as Microsoft Internet Explorer, Google Chrome, Mozilla Firefox, Apple Safari, or Microsoft Edge, for example. Secure web browsing may be provided using HTTPS (secure hypertext transport protocol), secure sockets layer (SSL), Transport Layer Security (TLS), or the like. Web browsers may utilize facilities such as AJAX, DHTML, Adobe Flash, JavaScript, Java, or application programming interfaces (APIs), for example. In some embodiments the computer system (501) may implement a mail client/server (519) stored program component. The mail server (519) may be an Internet mail server such as Microsoft Exchange, or the like. The mail server may utilize facilities such as ASP, ActiveX, ANSI C++/C#, Microsoft .NET, CGI scripts, Java, JavaScript, PERL, PHP, Python, or WebObjects, for example. The mail server (519) may utilize communication protocols such as internet message access protocol (IMAP), messaging application programming interface (MAPI), Microsoft Exchange, post office protocol (POP), simple mail transfer protocol (SMTP), or the like. In some embodiments, the computer system (501) may implement a mail client (520) stored program component. The mail client (520) may be a mail viewing application, such as Apple Mail, Microsoft Entourage, Microsoft Outlook, or Mozilla Thunderbird.
[0095] In some embodiments, the computer system (501) may store user/application data (521), such as the data, variables, records, or the like as described in this disclosure. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle or Sybase, for example. Alternatively, such databases may be implemented using standardized data structures, such as an array, hash, linked list, struct, structured text file (e.g., XML), table, or as object-oriented databases (e.g., using ObjectStore, Poet, Zope, etc.). Such databases may be consolidated or distributed, sometimes among the various computer systems discussed above in this disclosure. It is to be understood that the structure and operation of the any computer or database component may be combined, consolidated, or distributed in any working combination.
[0096] Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present invention. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term “computer- readable medium” should be understood to include tangible items and exclude carrier waves and transient signals, i.e., non-transitory. Examples include Random Access Memory (RAM), Read- Only Memory (ROM), volatile memory, nonvolatile memory, hard drives, Compact Disc (CD) ROMs, Digital Video Disc (DVDs), flash drives, disks, and any other known physical storage media.
[0097] Various embodiments of the disclosure encompass numerous advantages including a method for providing call management service. The disclosed method and system have several technical advantages, but not limited to the following:
[0098] The system centralizes call management tasks, enabling users to initiate, monitor, and control calls from a unified interface. This consolidation streamlines call operations and reduces the need for multiple disparate tools.
[0099] By incorporating user profile information, the system allows for dynamic adjustment of call settings based on individual preferences. This includes customization options such as SIM card selection, phone number formats, and call handling during locked screen scenarios.
[00100] The method supports integration with various platforms, including user computing applications, mobile devices, and desktop systems. This versatility ensures that users can manage their calls across different devices seamlessly.
[00101] The user interface is designed to be intuitive and user-friendly, offering features such as dialing interfaces, contact synchronization, and call history tracking. This improves the ease of use and overall user satisfaction.
[00102] The system efficiently handles call initiation in real-time, ensuring that user requests are processed promptly and accurately. This includes the ability to initiate calls based on specific user inputs and profile information.
[00103] The method supports detailed management of call-related data, including logging, archiving, and searching call information. This capability facilitates better organization and retrieval of call records for analysis and review.
[00104] The system generates actionable insights based on call data, providing users with detailed analytics and reports. These insights can help users make informed decisions and optimize their call management practices.
[00105] The system includes robust authentication mechanisms to ensure secure access and management of user profiles. This includes verifying user credentials and protecting sensitive contact information.
[00106] In summary, these technical advantages solve the technical problem of inefficiencies and errors associated with manually dialing phone numbers from various sources. By enabling direct dialing from digital sources and integrating with existing communication systems, the disclosed method eliminates the need for manual input, thereby reducing the potential for mistakes and streamlining the dialing process.
[00107] Additionally, these advantages contribute to improved user productivity and satisfaction. Users benefit from a more efficient and error-free method of initiating calls, as they can directly transfer phone numbers from documents and applications to their dialing system. This integration enhances overall communication efficiency and provides a more seamless user experience, addressing the needs of both everyday users and specialized environments.
[00108] Furthermore, the invention involves a non-trivial combination of technologies and methodologies that provide a technical solution for a technical problem. While individual components like processors, databases, encryption, authorization and authentication are well-known in the field of computer science, their integration into a comprehensive system for providing efficient call management and seamless communication introduces significant improvements and advancements. This integration enhances the ability to directly transfer phone numbers from digital sources into dialing systems, thereby streamlining the communication process and reducing manual input errors. The present disclosure approach brings about technical advancements in the field of communication technology by addressing the inefficiencies associated with manual dialing and improving the overall user experience. The novel combination of these technologies ensures a more effective and user-friendly system for managing and initiating calls, demonstrating a meaningful progression in how communication tasks are automated and handled.
[00109] The present disclosure may be realized in hardware, or a combination of hardware and software. The present disclosure may be realized in a centralized fashion, in at least one computer system, or in a distributed fashion, where different elements may be spread across several interconnected computer systems. A computer system or other apparatus adapted for carrying out the methods described herein may be suited. A combination of hardware and software may be a general-purpose computer system with a computer program that, when loaded and executed, may control the computer system such that it carries out the methods described herein. The present disclosure may be realized in hardware that comprises a portion of an integrated circuit that also performs other functions.
[00110] A person with ordinary skills in the art will appreciate that the systems, modules, and sub-modules have been illustrated and explained to serve as examples and should not be considered limiting in any manner. It will be further appreciated that the variants of the above-disclosed system elements, modules, and other features and functions, or alternatives thereof, may be combined to create other different systems or applications.
[00111] Those skilled in the art will appreciate that any of the aforementioned steps and/or system modules may be suitably replaced, reordered, or removed, and additional steps and/or system modules may be inserted, depending on the needs of a particular application. In addition, the systems of the aforementioned embodiments may be implemented using a wide variety of suitable processes and system modules, and are not limited to any particular computer hardware, software, middleware, firmware, microcode, and the like. The claims can encompass embodiments for hardware and software, or a combination thereof.
[00112] While the present disclosure has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made, and equivalents may be substituted without departing from the scope of the present disclosure. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present disclosure without departing from its scope. Therefore, it is intended that the present disclosure is not limited to the particular embodiment disclosed, but that the present disclosure will include all embodiments falling within the scope of the appended claims.
, C , Claims:WE CLAIM:
1. A method (400) for call management, wherein the method (400) comprising:
(402) providing, by a processor (202), a user interface of a user device (108) to a user of the user device (108);
(404) receiving, by the processor (202), one or more user inputs on the user interface;
(406) extracting, by the processor (202), a profile information of the user;
(408) transmitting, by the processor (202), a call request to the user device (108) based on one of the profile information of the user, the one or more user inputs, or a combination thereof; and
(410) initiating, by the processor (202), a call on the user device (108) based on the call request.
2. The method (400) as claimed in claim 1, wherein the user interface comprises a dialing interface, wherein the dialing interface comprises one or more placeholders, one or more action buttons or a combination thereof, wherein the one or more placeholders are used to input a phone number, wherein one or more action buttons comprises a call start button, an end call button, a create contact button, an edit contact button, add comment button, import button, sync button or a combination thereof; wherein import button corresponds to importing contact information from one of CSV, spreadsheet, vCard (VCF), XML, any other format, or a combination thereof.
3. The method (400) as claimed in claim 1, wherein the user interface comprises a call history interface, wherein the call history interface comprises details of calls performed by the user through the user interface, wherein the detail of calls comprises the phone number, call start time, call end time, call duration, call recording, comments or a combination thereof.
4. The method (400) as claimed in claim 1, wherein the user interface is provided through at least one of a web browser, software application, mobile application, user computing application, web browser plugin, application programming interface (API) or a combination thereof, wherein the user interface is integrated with a third-party application, wherein the third-party application comprises a CRM, HR, Support, directory or any other application.
5. The method (400) as claimed in claim 1, wherein the user device (108) comprises a mobile phone, a tablet, any handheld device or a combination thereof.
6. The method (400) as claimed in claim 3, wherein the one or more user inputs comprises dialing the phone number, selecting the phone number from the call history interface, selecting a contact from a contact list, a paste action corresponding to a copy or cut action from an external interface, click event on a call icon, click event on a hyperlink, selecting a number from the user interface, right click on the number on the user interface, or a combination thereof.
7. The method (400) as claimed in claim 1, comprises creating a user profile, by the user on the user interface, wherein the user profile comprises the profile information of the user, wherein the profile information of the user comprises username, contact detail, user device ID, user device type, call handling preferences or a combination thereof, wherein creating the user profile comprises a user authentication process based on user’s phone number, wherein creating the user profile comprises synchronizing user’s contact list from the user device through import button, wherein the contact details comprise the user’s phone number, user’s email ID, user’s address, the user’s contact list from the user device, call history from the user device, wherein the call handling preferences correspond to a Subscriber Identity Module (SIM) selection preference before the call initiation, user’s control preference over the call initiation, configuration preference for supporting phone number formats, call configuration preference on a lock screen of the user device (108).
8. The method (400) as claimed in claim 7, wherein the call configuration preference on the lock screen of the user device (108), corresponds to initiating a call directly when the screen of the user device (108) is locked, based on the call handling preferences, wherein the SIM selection preference before the call initiation corresponds to choosing a SIM from a plurality of SIMs for initiating the call, wherein the user’s control preference over the call initiation corresponds to populating the phone number on a dialing interface of the user device (108) and receiving a user confirmation, on the dialing interface of the user device (108), for initiating the call.
9. The method (400) as claimed in claim 3, comprises generating one or more call insights based on the details of calls performed by the user through the user interface.
10. The method (400) as claimed in claim 1, wherein transmitting the call request to the user device (108) corresponds to sending the call request to one or more call management services running on the user device (108), wherein the one or more call management services are compatible with the user interface, wherein the one or more call management services facilitate the call initiation on the user device (108) based on the profile information of the user.
11. A system (100) for call management, wherein the system (100) comprises:
a memory (204);
a processor (202), wherein the processor (2020) is configured to execute programmed instructions stored in the memory (204), by:
providing a user interface of a user device (108) to a user of the user device (108);
receiving one or more user inputs on the user interface;
extracting a profile information of the user;
transmitting a call request on the user device (108) based on one of the profile information of the user, the one or more user inputs, or a combination thereof; and
initiating a call on the user device (108) based on the call request.
12. A non-transitory computer-readable storage medium having stored thereon, a set of computer-executable instructions causing a computer comprising one or more processors to perform steps comprising:
providing a user interface of a user device (108) to a user of the user device (108);
receiving one or more user inputs on the user interface;
extracting a profile information of the user;
transmitting a call request on the user device (108) based on one of the profile information of the user, the one or more user inputs, or a combination thereof; and
initiating a call on the user device (108) based on the call request.
Dated this 16th Day of August 2024

Priyank Gupta
Agent for the Applicant
IN/PA-1454