WO2023047365A1

WO2023047365A1 - Virtual keyboard crm device and methods

Info

Publication number: WO2023047365A1
Application number: PCT/IB2022/059050
Authority: WO
Inventors: Shabu Ans Kandamkulathy
Original assignee: Getmymessage Pte Ltd
Current assignee: Getmymessage Pte Ltd
Priority date: 2021-09-23
Filing date: 2022-09-23
Publication date: 2023-03-30
Anticipated expiration: 2024-03-23

Abstract

A virtual keyboard CRM tool includes both a virtual keyboard interface and a CRM interface to enable a user to more efficiently populate a CRM using common mobile phone interactions. In addition, the virtual keyboard CRM tool can operate using the mobile phone's 5 existing apps such as a contact application, a calendar application, and an email application. In some embodiments, the virtual keyboard CRM tool can read and store information about CRM contacts using the mobile phones contact application.

Description

VIRTUAL KEYBOARD CRM DEVICE AND METHODS

CROSS REFERENCE TO RELATED APPLICATION

This application claims the benefit of and priority to US Provisional Patent Application Number 63/247,621 filed on 23 September 2021, which is hereby incorporated by reference in its entirety. This application also incorporates by reference U.S. Patent Application Serial No. 16/561,115 and International Application No. PCT/IB2020/058289 in their entirety.

TECHNICAL FIELD

This application pertains to CRM tools and interfaces for mobile phone users.

BACKGROUND

This section is intended to introduce various aspects of the art, which may be associated with exemplary embodiments of the present disclosure. This discussion is believed to assist in providing a framework to facilitate a better understanding of particular aspects of the present disclosure. Accordingly, it should be understood that this section should be read in this light, and not necessarily as admissions of prior art.

Customer relationship management (CRM) tools are critical in today’s business environment. Large companies can merge these dedicated CRM tools and processes in their IT infrastructure and employees’ workflow. CRM tools are resource intensive, expensive, and require dedicated management resources.

SUMMARY

Discussed herein is an example virtual keyboard CRM tool method. The method includes displaying, by a virtual keyboard application, a virtual keyboard region of a touchscreen of a mobile phone of a user for displaying a virtual keyboard, the virtual keyboard including a plurality of keys for communicating with a text input area of a first application when the virtual keyboard is in a text entry mode and a CRM region for displaying information and receiving user instructions and interacting with CRM functions when the virtual keyboard is in a CRM, wherein the virtual keyboard in the CRM mode is configured to communicate with at least one of a contacts application, a calendar application, and an email application in the mobile phone. The example method also includes presenting on the touchscreen to the user at least one CRM function key in the CRM region for carrying out various CRM functions. The example method also includes receiving from the user a selection of a CRM function of the various CRM functions detected through the touchscreen, by the virtual keyboard application. The example method also includes responsive to receiving a selected CRM function, displaying within the CRM region, additional CRM function keys or information from at least one of the contacts application, the calendar application, and the email application without leaving the virtual keyboard application or the first application.

Also discussed herein is another example virtual keyboard CRM tool method. The method includes invoking, from within a first application that presented a user with a text input area and after a user selects the text input area on a touchscreen the first application is configured to invoke a virtual keyboard and then receive text from the user’s interactions with the virtual keyboard, the execution of a virtual keyboard application on a mobile phone. The example method also includes displaying, by a virtual keyboard application, a virtual keyboard region of the touchscreen of the mobile phone of the user for displaying a virtual keyboard, the virtual keyboard including a plurality of keys for communicating with the text input field of a first application when the virtual keyboard is in a text entry mode and a CRM region for displaying information and receiving user instructions and interacting with CRM functions when the virtual keyboard is in a CRM, wherein the virtual keyboard in the CRM mode is configured to communicate with at least one of a contacts application, a calendar application, and an email application in the mobile phone; presenting the user in the CRM region of the touchscreen a CRM function key corresponding to at least one of the CRM functions; receiving from the user an interaction with the CRM function key detected through the touchscreen, by the virtual keyboard application; and responsive to receiving the interaction with the CRM function key, displaying within the CRM region results of a selected CRM function and additional CRM function keys.

Additionally or alternatively, the above methods can include the presented at least one CRM function key includes at least two of the various CRM functions including viewing a list of CRM contacts from the contacts application, viewing a list of activities from the calendar application, and viewing a list of follow-ups from a task management application. Optionally, after the user selects viewing a list of activities from the calendar application, the method includes presenting the user with the additional CRM function keys to view the list of activities or create a new activity.

Additionally or alternatively, after the user selects viewing a list of activities from the calendar application, the virtual keyboard CRM tool presents to the user with the list of activities and the additional CRM function keys to view the list of activities in a pop-up window or the calendar application.

Additionally or alternatively, the selected CRM function is viewing a list of CRM contacts from the contacts application, and displayed within the CRM region is a list of the CRM contacts and the additional function keys for the listed CRM contacts included at least two of viewing call details with a selected CRM contact, scheduling an activity with the selected CRM contact, or creating a follow up with the selected CRM contact.

Additionally or alternatively, when viewing the list of follow-ups, the list of follow-ups is fdtered and sorted according to their due date. Optionally, the CRM view has a list of followups related to a CRM contact, and the additional CRM function keys let the user to select sending the CRM contact any of the list of follow-ups.

Optionally, when the user selects to send any of the list of follow-ups to the CRM contact, the virtual keyboard application sends a selected follow-up to the CRM contact using a predetermined communication method stored in the follow up in a task management application or associated with the CRM contact in the contact application. A further option is the virtual keyboard application sends the selected follow-up using the predetermined communication method with a predetermined user message. Another option is the user does not have to type on a keyboard or manually open another application for the virtual keyboard application to send the selected follow-up using the predetermined communication method with the predetermined user message.

Additionally or alternatively, the above methods can include presenting to the user a plurality of other CRM function keys; after receiving from the user a selection of the plurality of other CRM function keys, invoking at least one of the contacts application, the calendar application, and the email application and acquiring information from the invoked application, and filtering information from the invoked application and presenting at least some of the filtered information to the user in the CRM region. Optionally, they can include presenting the user with a new CRM function key next to the filtered information; and in response to receiving a selection of the new CRM function key from the user, updating data in the invoked application.

In some embodiments, the first application can be different from the virtual keyboard application, the contacts application, the calendar application, and the email application. In some embodiments, the virtual keyboard in the CRM mode is configured to communicate with the contacts application, the calendar application, and the email application without the user separately needing to open or switch to the contacts application, the calendar application, and the email application.

In some embodiments, in response to a user request to view clients, the CRM region displays CRM contacts and a user option to receive prior call details, a user option to view or modify a schedule, or a user option for following up for any of the CRM contacts.

In some embodiments, the prior call details include date and time of prior calls. Additionally or alternatively, interacting with the CRM function key sends a follow-up to a CRM contact, wherein information is stored in the follow-up or the contact application indicating a pre-determined preference of a CRM contact, and in response to the user pressing the CRM function key, sending the follow-up to the CRM contact based on the pre-determined preference of the CRM contact. Optionally, sending the follow-up includes sending a predetermined message that has been set by the user together with the follow-up.

In some embodiments, the virtual keyboard application stores in the contact application for each CRM contact at least two of lead status, source type, tax ID, product, account owner, and a CRM client flag.

In some embodiments, the method displays a function key for toggling the virtual keyboard between text entry mode and CRM mode.

Also discussed herein is an example mobile phone device with a virtual keyboard having an embedded CRM tool. The device includes a processor; a touchscreen display; memory; storage including a virtual keyboard application, a contacts application, a calendar application, and an email application; wherein the virtual keyboard application is configured to be executed by the processor, the virtual keyboard application including instructions for: invoking the virtual keyboard application to display in a portion of the touchscreen display a virtual keyboard including a CRM region; displaying on the touchscreen in the CRM region at least one CRM function key for the user to select a CRM function; receiving through the touchscreen display an indication of a selected CRM function, and executing the selected CRM function in at least one of the contacts application, the calendar application, or the email application.

Optionally, the contacts application, the calendar application, and the email application are not integral with the virtual keyboard application. Additionally or alternatively, the contacts application, the calendar application and the email application are default contacts application, calendar application and email application of the mobile phone.

In some embodiments, following a mobile phone call, the instructions include asking the user whether to save the contact as a CRM contact. Additionally or alternatively, following a mobile phone call, the instructions have the processor check CRM fields or CRM flags in the contacts application as to whether the contact is a known CRM contact. Additionally or alternatively, following a mobile phone call, the instructions include extracting call information from the phone application and using the extracted call information to update CRM fields or CRM flags in the contacts application. Additionally or alternatively, the CRM fields or CRM flags in the contacts application are at least one of existing fields or flags of contacts in the contact application and newly created fields or flags in the contacts of the contact application. It will be appreciated that variations of the above are possible and that method steps and device instruction steps can be interchanged without deviating from the scope of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive examples are described with reference to the following figures. Drawings are not drawn to scale and are not limited to the exact layouts depicted.

So that the manner in which the present inventions can be better understood, certain illustrations, diagrams, screen layouts, charts and/or flow charts are appended hereto. It is to be noted, however, that the drawings illustrate only select embodiments of the inventions and are therefore not to be considered limiting of scope, for the inventions may admit to other equally effective embodiments and applications. Reference numerals are optionally repeated to emphasize various features, but their absence should not be interpreted to mean the absence of a feature. Additionally, the same reference numeral may be used across embodiments for similar features even if such features are not identical.

Figure 1 is a diagram depicting how an example virtual keyboard CRM tool interacts with other software components of a mobile phone.

Figure 2 is a diagram depicting common hardware components of a mobile phone that can be used with virtual keyboard CRM tool.

Figure 3 is a conceptual screen layout illustrating an example computing device that is using an example virtual keyboard CRM tool in virtual keyboard mode in conjunction with a messaging app.

Figure 4 is a conceptual screen layout illustrating the device and virtual keyboard CRM tool of Figure 3 toggled into CRM mode showing an example set of CRM function keys in the CRM region.

Figure 5 is a conceptual screen layout illustrating the device and virtual keyboard CRM tool of Figure 3 showing CRM contacts and CRM function keys for each contact.

Figure 6 is a conceptual screen layout illustrating the device and virtual keyboard CRM tool of Figure 3 with an example interface showing call details of a CRM contact.

Figure 7 is a conceptual screen layout illustrating the device and virtual keyboard CRM tool of Figure 3 with an example scheduling interface and related CRM function keys.

Figure 8 is a conceptual screen layout illustrating the device and virtual keyboard CRM tool of Figure 3 with an example scheduled activities interface.

Figure 9 is a conceptual screen layout illustrating the device and virtual keyboard CRM tool of Figure 3 with an example follow-ups interface. Figure 10 is a conceptual screen layout illustrating the device and virtual keyboard CRM tool of figure 3 with an example mid call or post call phone interface.

Figure 11 is a flow chart depicting an example method of treating contacts and CRM contacts before and after a user call with a contact.

Figure 12 is a flow chart depicting an example method of displaying and handling follow-ups and enabling the user to touch a function key to send follow-ups to clients.

Figure 13 is a flow chart depicting an example method of displaying function keys in CRM mode and responding to a user selection of the function keys by interacting with specific apps.

Figures 14A and 14B are example screenshots of contacts in iOS and Android operating systems.

DETAILED DESCRIPTION

Detailed descriptions of one or more preferred embodiments are provided herein. It is to be understood, however, that the present invention may be embodied in various forms. Therefore, specific details disclosed herein are not to be interpreted as limiting, but rather as a basis for the claims and as a representative basis for teaching one skilled in the art to employ the present invention in any appropriate manner.

Small and Medium Businesses (“SME”), especially those outside of the United States of America, rely heavily on free social messaging apps like WhatsApp® and LINE® for various business interactions like talking with customers and dealing with suppliers. They can connect with many in their market using the popular messaging app of that market. For many SMEs, communications, most of the time occurs through these messaging apps. With these apps expanding their reach with voice calls - these platforms have become the de facto way of doing business.

Existing customers of the SME businesses are often found in the Phone contacts but managing them effectively becomes a challenge as recording these conversations, tracking, and following up of these clients falls outside the app and must be manually managed. Some SMEs do venture out to install dedicated CRMs but the friction of moving out from their favorite messaging app results in underutilization of these dedicated CRM apps in managing the interactions of their entire business.

A benefit of the example embodiments herein is that the users can manage clients without having to leave their favorite messaging app in a simple and convenient manner and at the same time manage tasks/requests of these clients in a single application. Another benefit is improving the functionality of the mobile phone for the user by having the information captured and recorded in the place where the information is being generated. Dedicated CRM tools are difficult to setup, manage and sustain on an ongoing basis, which requires a lot of discipline, investment, and a sustained level of focus. SME Businesses often do not have time to maintain such a parallel setup which leads to most business using simple excel sheets to manage their clients. The virtual keyboard CRM tools described herein considerably reduce this complexity and makes it simple for a small business owner to manage customers. An additional benefit is filtering of the information in a way that the user can easily digest and providing it in a virtual keyboard where the user commonly interacts with the user’s favorite apps. Another benefit is improving the efficiency of the mobile phone as the phone does not require a separate and bulky dedicated CRM app with duplicative information.

Figure 1 is a diagram depicting how an example Virtual Keyboard CRM Tool 100 interacts with other software components of Mobile Phone 1. For the purposes of this specification, “mobile phone” is defined as a portable touch screen device that can communicate through social messaging apps such as a mobile phone, smart phone, cellular phone, tablet, smart watch, and their equivalents. Included in this definition is non-foldable, foldable, keyboarded, non-keyboarded single screen and multiscreen devices. Mobile phones generally have app-based operating systems, but it would be understood by a person of skill in the art that other types of operating systems can utilize the same or similar configurations and achieve the same goals.

The example virtual keyboard CRM tool can work with any application where text is needed (e.g., to be inputted into a text field) and entered on a touchscreen display through an onscreen keyboard. For the purposes of this specification, the generic application needing text input will be described as a Social Messaging App 10 to highlight certain benefits of the virtual keyboard CRM tool embodiments. A “social messaging app” or “messaging app” is an application installed on or interfaced through a mobile phone to provide instant messaging between users including but are not limited to WhatsApp®, LINE, SMS, MMS, iMessage®, Facebook® Messenger, Telegram®. A Caller App 15 can be apps like the default Android or IOS phone apps, Google voice, any voice over IP app, or can be the Messaging App 10 as the messaging apps like WhatsApp add voice and video calls. The data flows of the mobile phone are not limited by the arrowed connectors of Figure 1. Shown are example arrowed connectors to illustrate how the apps interface together. But it will be appreciated by person of skill at the art that a phone’s contact app interacts with the phone’s operating system. Mobile phone 1 works under Mobile Phone Operating System 5. Examples of mobile phone operating systems include iOS, Android, Windows Phone, and Samsung. “Caller” as used herein shall be construed as a contact established or contacted through the calling app regardless of which party placed the call. “App” and “application” can be used interchangeably throughout this disclosure.

One of the benefits of the example virtual keyboard CRM tool is the way it interfaces with many core mobile phone applications, which can be better understood with reference to Figure 1. In some embodiments, the virtual keyboard CRM tool connects with several of the phones core apps including a Phone Contact App 20, a Phone E-mail App 25, a Phone Task Management App 35 (which can also be integrated with a virtual keyboard, as shown in the incorporated by reference application PCT/IB2020/058289), and/or a Phone Calendar App (30). The virtual keyboard CRM tool, instead of being required to maintain all its own databases for contacts, emails, task, and calendar, can remain lightweight and rely on the existing tools of the mobile phone. In contrast, dedicated CRM tools maintain information about contacts in the tools themselves. The example virtual keyboard CRM tool can maintain information about CRM contacts in the phone's contact app, as later discussed in the contexts of Figures 14A and 14B. Such information may be found in flags, fields, or customizations of the contacts within the phone contact app. It is presumed that a user uses the mobile phone for both business use and non-business use (e.g., family) and that the user does not want plan on business contacts tracked by a CRM tool. Therefore, it is useful to describe in this specification both CRM contacts and non-CRM contacts. And many times, it may not be known whether a contact is a CRM contact or a non-CRM contact. For example, a new caller that is not found in the user’s current contact list in the phone’s Contact Application 20 may be a CRM contact or a non-CRM contact, and it will need to be determined to which group this contact belongs. One method of identifying this is to ask the user immediately after a call whether to treat this contact as a CRM contact, and then after being appropriately classified as a CRM contact, call details can be stored for the CRM contact.

In another example embodiment, the virtual keyboard CRM tool can have its own tools duplicating or improving the tools of the mobile phone. This may be useful if a user, an operating system, or a manufacturer does not want an application changing some of the core applications of the phone and/or their stored information. The information from the core apps can be downloaded and/or synchronized into the virtual keyboard CRM tool through its own databases such as an optional CRM Tool Database 105. This optional database can be stored on the device or remotely, such as in the cloud.

Figure 2 is a diagram depicting common hardware components of a mobile phone that can be used with virtual keyboard CRM tool. As the virtual keyboard CRM tool is designed to work with common mobile devices, the example mobile phone contains storage 200, Touch Screen Interface 205, Microphone 210, Networking components 215, telephony components 220, speaker 225, Memory 230, touch screen display 235, processor 240, Input/Output (I/O) Components 245, Battery/Power System 250, Camera 255 and System Bus 260 connecting the various components together. However, the hardware is not limited to that shown in Figure 2 as other hardware configurations with more, less, or different components are possible.

Figure 3 is a conceptual screen layout illustrating an example computing device that is using an example virtual keyboard CRM tool in virtual keyboard mode in conjunction with a messaging app. Messages 305 are shown in a Messaging Application User Interface 310. As the user is supposed to type into Text Input Area 315, a virtual keyboard application would be invoked and a plurality of keys. The Text Input Area 315 can be part of the virtual keyboard application and portion of the screen 350 (also referred to as “virtual keyboard area” or “virtual keyboard region”) and/or it can be part of the social messaging app and portion of the screen. It will be understood that the virtual keyboard can be moved or configured differently and may not look the same as shown here. The virtual keyboard CRM tool 100 includes a Plurality of Keys 325 the user uses to type in text, emojis, or other inputs. As shown in the figure, the plurality of keys representing a USA style keyboard. The plurality of keys can be in any language and characters/letters. Above the Plurality of Keys 325 in this example configuration is a Function Key Bar 320 including CRM Toggle Function Key 330 on the far right.

Figure 4 is a conceptual screen layout illustrating the device and virtual keyboard CRM tool of Figure 3 toggled into CRM mode showing an example set of CRM function keys in the CRM region. Upon the user pressing the CRM Toggle Function Key 330, the virtual keyboard CRM tool enters CRM mode and CRM Region 360 appears replacing the plurality of keys 325. It will be appreciated that CRM Region 360 may not have to replace or wholly replace the plurality of keys 325 and that other configurations and relationships of the features are possible. In CRM Region 360, the user can interact with various CRM aspects of the virtual keyboard CRM tool without opening a separate application and having to switch between screens.

Shown in Figure 4 is an example high level menu of CRM function keys including View Clients Function Key 365. Follow Ups Function Key 370, View Schedule Function Key 375, Sync Contacts Function Key 380, and Add New Contact Function Key 385. Touching the Add New Contact Function Key 385 allows the user to add to the database of CRM clients (the phone contacts or a separate contacts database). This can open a contact information form or user interface that resembles the phone contact input or a separate form or interface that is visually tailored to being a CRM contact display (regardless of where or how the CRM contact data is stored).

Touching View Clients Function Key 365 of Figure 4 displays an example listing of all CRM contacts as shown on Figure 5. Figure 5 is a conceptual screen layout showing CRM contacts and CRM function keys for each contact. Long lists of CRM contacts can be shown over several screens accessible through scrollbars, swiping, tabs, or other mechanisms (not shown). On this screen is shown each CRM contact’s name 400, Contact Call Details Function Key 405 (telephone icon), Contact Schedule Task Function Key 410 (calendar icon), Contact Create Follow Up Function Key 415, and Search Function Key 420 Touching the Search Function Key 420 lets a user search for any client or CRM contact instantly. Touching this function key opens a screen (not shown) that allows the user to search for any client to view details of that client.

Touching the Contact Call Details Function Key 405 (telephone icon) for a CRM client takes the user to the Call details screen as shown in Figure 6. Figure 6 depicts an example interface showing call details of a CRM contact. This includes a list of all interactions by the user with this specific client on the caller app including details such as: Date, time of call, and short details of the call. Touching “. . . ” More Info Function Key 435 results in a full screen view (not shown) that pops up for that call. This or the prior screen can also log all the CRM contact touchpoints like emails, messages, etc., giving the user a complete picture of the user’s recent interaction with the user’s CRM contact.

Touching the Contact Schedule Task Function Key 410 (calendar icon), for a CRM client takes the user to a Scheduling screen. Figure 7 depicts an example scheduling interface and related CRM function keys. In this example embodiment, two options are shown: View Activities Function Key 450 and Create New Activity Function Key 455. Touching “View Activities” allows the user to view all the upcoming and outstanding Scheduled Activities 510 including tasks/requests for this CRM contact, as shown in Figure 8. Figure 8 depicts an example scheduled activities interface shown. On this screen a user can use the Open Outside App Function Key 500 (in this case the calendar app).

Touching “Create new” on Figure 7 allows the user to create a new activity for this client.

Touching the 370 Follow Ups Function Key for a CRM contact takes the user to view all follow ups that the user or the user’s business needs to make with this CRM contact whether it is a prospect or existing client. Figure 9 depicts an example follow-ups interface. Every Eisting View Function Key 560 provides the option on various screens including Calls, Schedules, Follow ups to open the listing in a pop-up window view instead of on the virtual keyboard CRM tool.

This view also has fdters (not shown) to view Overdue, Due and Upcoming Follow ups for the CRM contact. A function key (not shown) can take the user directly to the follow ups that the business needs to make with this prospect or client today or which has already become overdue.

Touching the ” Send Follow Up Function Key 555 on this example interface of Figure 9 lets the user use send an automated follow up. In some embodiments, each follow up will be flagged with the communication channel that the CRM contact used recently to communicate with the user or the channel the CRM contact prefers. In some embodiments, the automated follow up can be preset to contain a pre-determined message. In the above ways, the user can send follow ups to the CRM contact in the manner preferred by the CRM contact without needing to type into a keyboard and without needing to open a different app to communicate with the CRM contact. This improves the outcome for the user while decreasing the processing and resources on the mobile phone.

Touching the View Schedule Function Key 375 on Figure 4 lets the user directly view all the upcoming and outstanding activities including tasks/requests for this client

Touching the Sync Contacts Function Key 380 on Figure 4 lets the user manually synchronize contacts from the contacts app. This allows the user manually to synchronize the contacts of the phone to embodiment with the separate optional CRM database. This prevents manual entry when the user starts using the application for the first time.

In various embodiments, the user receives prompts during or after a call, as shown in Figures 10, 11 and 13.

Figure 10 depicts an example mid call or post call phone interface 600 that can be in the CRM region or in a popup window. Touching the Update Call Details Function Key 610 lets the user have the virtual keyboard CRM tool update call details if the call pertained to an existing CRM contact or a person that is desired to be a CRM contact. Touching the Schedule Function Key 615 lets the user schedule a task with the caller. Create Follow Up Function Key 620 is used to create a follow up.

Figure 11 is a flow chart depicting an example method of treating contacts and CRM contacts before and after a user call with a contact. A complex flow chart that can be broken into sub processes, when a user starts to use the CRM tool, some of the user’s contacts may be deemed to be CRM contacts and some may be non-CRM contacts as discussed above. Step 1010 includes determining categories of contact lists that are not CRM contacts so that way the CRM contacts can be identified and classified as such. In Step 1020, the user receives a call from a contact. From here, the virtual keyboard CRM tool determines how to process the contact. In Step 1030, a determination is made of whether it is a new contact, and existing contact or an excluded contact. When it is determined in Step 1095 that the contact is a known contact but a non-CRM contact, nothing is further done in this flow chart. Alternatively, when it is determined that the contact is a known CRM contact, Step 1080 involves inquiring with the user if they want to update the call details of the CRM contact. Upon the user's affirmation, in the virtual keyboard CRM tool will update the CRM contact in Step 1090 and will update existing CRM contract with the call details in Step 1060. Then the user can create follow-ups in Step 1070, or the system can automatically create follow-ups if programmed to do so. Going back to Step 1030, if the caller is determined to be a new contact, the user will be asked by this system in Step 1040 if they want to add the contact. Upon the user’s affirmation, in Step 1050 the virtual keyboard CRM tool will create a new CRM contact. Then, in Step 1060 the virtual keyboard CRM tool update details of the call for the new client in the CRM contact. And lastly, in Step 1070, follow-ups can be created similar to those created for existing CRM contacts.

Figure 12 is a flow chart depicting an example method of displaying and handling follow-ups and enabling the user to touch a function key to send follow-ups to clients. As discussed above, automated follow-ups can be customized to each individual user based on stored flags or information associated with each follow-up or the CRM contact. These can indicate the CRM contact’s desired communication method (e.g., WhatsApp, SMS, or Email) or at least the last known method used by the CRM contact. In this way, in Step 1105 when the user opens the follow-ups list in the virtual keyboard CRM tool, the virtual keyboard CRM tool automatically knows which communication method to use and opens the appropriate app in Step 1110. If the user touches to send the follow-ups in Step 1115, the virtual keyboard CRM tool can send the follow-ups to the clients in Step 1120. A person of skill in the art would realize that Steps 1105 and 1110 can happen in a reverse order.

Figure 13 is a flow chart depicting an example method of displaying function keys in CRM mode and responding to a user selection of the function keys by interacting with specific apps. Figure 13 is an alternate embodiment from Figure 10. In this embodiment, a user Places or receives a phone call using the caller app. this can be a video or a voice call. The virtual keyboard CRM tool in Step 1220 prompts the user whether they want to update call details, schedule, or create a follow up. In Step 1230, the virtual keyboard CRM tool receives input from the user and determines from the input which of the function keys was selected by the user. In response to receiving a selection of the function key, the virtual keyboard CRM tool in Step 1240 opens the appropriate app if it is not already open. Then, in Step 1250, the virtual CRM keyboard tool access his information from the appropriate app related to the selected function key. Next in Step 1260, the virtual keyboard CRM tool presents filtered information from the information it received in the open app. Then, in Step 1270, the virtual keyboard CRM tool receives user input, and in step 1280, makes a modification based on the user input in the appropriate app. Figures 14A and 14B are example screenshots of contacts in iOS and Android operating systems. Figure 14A includes iOS examples of contact modification by the virtual keyboard CRM tool to make the contacts into CRM contacts. In addition to storing the contact information of the user, the lead status, source type, tax ID, associated product, account owner and notes reflect information to help manage the customer relationship. In addition there is a flag of a yes or no indicating that the client is a CRM client. Figure 14B similarly includes Android examples of contact modification by the virtual keyboard CRM tool.

“Apps” are commonly available through application distribution platforms and are typically operated by the owner of the mobile operating system and/or are downloaded from the platform to a target device.

The CRM function key button can be in a function key bar adjacent to the plurality of keys, or it can be nearby Somewhere else in the virtual keyboard region. In addition, there can be more than one CRM function key on the main virtual keyboard region. The CRM function key can be used to toggle the virtual keyboard region to replace the plurality of keys with a CRM region in which the user can interact with the CRM functions of the virtual keyboard CRM tool.

The CRM interacts with a Contact database. The CRM can use the mobile phones existing contact application and/or it can use its own CRM contact database. In one example embodiment, the Virtual keyboard CRM tool does not have its own CRM contact database. The virtual keyboard CRM tool uses existing fields and flags in the mobile phone contacts database, or it can create custom fields and flags in the mobile phone contact database. In another example, embodiment, the virtual keyboard CRM tool has its own CRM contact database. That can be used to duplicate and or synchronize the mobile phone’s existing contacts with the CRM contact database.

In some cases the Messaging app can be the same as the caller app. For example, In WhatsApp it can be used for voice or video calls or messaging. In this situation, WhatsApp can be considered both the messaging app and the caller app.

The virtual keyboard CRM tool may be able to have additional ability to capture information of the mobile phone depending on permissions allowed with other apps. For example, during a video call, the CRM contacts image can be captured and stored in the user’s CRM contact database.

Additionally, other functionality is possible as well using the phone's hardware. For example, when two mobile phones come into close contact for an extended period (and authorized through the virtual keyboard CRM tool or other app), various known sensors can detect this and a data point of an in-person meeting can be captured automatically and stored in the user’s CRM contact and displayed by the user’s virtual keyboard CRM tool.

Additionally, other functionality is possible through interfacing with off device systems. For example, the virtual keyboard CRM tool can interface and sync with the data from virtual keyboard CRM tools on other devices or other CRM systems of a user’s company and interactions between the user’s colleagues and CRM contacts can also be stored and made available to the user through the user’s virtual keyboard CRM tool.

In some embodiments, the virtual keyboard CRM tools send emails directly through the email app. It need not come through typing in the keyboard. For example, pre-configured communication to clients can be setup directly in the virtual keyboard CRM tool and do not require typing out emails each time on the keyboard. Similarly, the virtual keyboard CRM tool can receive email queries and log directly into the CRM without any keyboard intervention.

Instead of the icons and words shown on the function keys described herein, it will be appreciated that other icons, words, phrase, images, pictures, symbols, etc. can be used or associated with the function keys on the user interface and have a similar result.

There has thus been outlined, rather broadly, some of the features of the device and methods in order that the detailed description thereof may be better understood, and in order that the present contribution to the art may be better appreciated.

Although methods and devices similar to or equivalent to those described herein can be used in the practice or testing of the device and methods, suitable methods and materials are described above. The device and methods may be embodied in other specific forms without departing from the spirit or essential attributes thereof, and it is therefore desired that the present embodiment be considered in all respects as illustrative and not restrictive. Other objects and advantages of the various embodiments of the present invention will become obvious to the reader and it is intended that these objects and advantages are within the scope of the present invention. To the accomplishment of the above and related objects, this invention may be embodied in the form illustrated in the accompanying drawings, attention being called to the fact, however, that the drawings are illustrative only, and that changes may be made in the specific construction illustrated and described within the scope of this application.

It will be apparent to those skilled in the art that various modifications and variation can be made to the disclosed methods, software, hardware, materials, components, and methods herein. Other embodiments will be apparent to those skilled in the art from consideration of the specification and practice of the disclosed inventions. Numerous modifications, changes, variations, substitutions, and equivalents will occur to those skilled in the art without departing from the spirit and scope of claimed invention. It is intended that the specification and examples be considered as exemplary only, with a true scope being indicated by the claims and their equivalents. The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential features or elements of any or all the claims. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the claimed invention.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the claims features belong. Moreover, Applicant’s inconsistent use of a term should not be construed as different terms unless defined by Applicant or the context. Likewise, it is to be understood that the phraseology and terminology employed herein are for the purpose of the description and should not be regarded as limiting.

Regarding additional interpretation and construction of terms and steps herein, method steps are not in any specified order unless dictated by the context or specific wording. In addition, the use of a word in the singular form should be interpreted where the context allows or does not restrict so as to enable plurality or an “at least one” construction. Positional and directional terms described in this specification may be understood to be different than shown or described, and should not limit the variations of embodiments possible from the claimed features that a person of ordinary skill in the art would understand from the specification, figures, and claims. The term “and/or” in a list means all list items present, some list items present, or one of the list items present, unless such construction is limited by the context. “Including” shall be construed as “including but not limited to.”

[040] The singular forms "a," "an," and "the" include plural reference unless the context clearly dictates otherwise. The use of the word "a" or "an" when used in conjunction with the term "comprising" in the claims and/or the specification may mean "one," but it is also consistent with the meaning of "one or more," "at least one," and "one or more than one."

Wherever any of the phrases "for example," "such as," "including" and the like are used herein, the phrase "and without limitation" is understood to follow unless explicitly stated otherwise. Similarly "an example," "exemplary" and the like are understood to be non-limiting.

The terms "comprising" and "including" and "having" and "involving" (and similarly "comprises," "includes," "has," and "involves") and the like are used interchangeably and have the same meaning. Specifically, each of the terms is defined consistent with the common United States patent law definition of "comprising" and is therefore interpreted to be an open term meaning "at least the following," and is also interpreted not to exclude additional features, limitations, aspects, etc. Thus, for example, "a process involving steps a, b, and c" means that the process includes at least steps a, b, and c.

INDUSTRIAL APPLICABILITY

In addition to the goals stated above, the devices and methods herein can be used to manage, store, respond to, and comment on interactions with third parties using mobile phones.

Reference Numerals

1 Mobile Phone

5 Mobile Phone Operating System

10 Messaging Application

15 Caller Application

20 Contacts Application

25 Email Application

30 Calendar Application

100 Virtual Keyboard application or Virtual Keyboard CRM tool

105 Task Management App in Phone or within Virtual Keyboard CRM tool

200 Storage

205 Touch Screen Interface

210 Microphone

215 Networking

220 Telephony

225 Speaker

230 Memory

235 Display

240 Processor

245 I/O Components

250 Battery/Power System

255 Camera

260 System Bus

305 Messages

310 Messaging Application User Interface

315 Text Input Area

320 Function Key Bar 325 Plurality of Keys

330 CRM Toggle Function Key

350 Virtual Keyboard

360 CRM Region

365 View Clients Function Key

370 Follow Ups Function Key

375 View Schedule Function Key

380 Sync Contacts Function Key

385 Add New Contact Function Key

400 Contact Name

405 Contact Call Details Function Key

410 Contact Schedule Task Function Key

415 Contact Create Follow Up Function Key

420 Search Function Key

430 Call Details

435 More Info Call Function Key

450 View Activities Function Key

455 Create New Activity Function Key

500 Open Outside App Function Key

510 Scheduled Activities

550 Scheduled Follow Up

555 Send Follow Up Function Key

560 Every Eisting View Function key

600 Mid or Post Call Interface Prompt

610 Update Call Details Function Key

615 Schedule Function Key

620 Create Follow Up Function Key

Claims

1. A method comprising: displaying, by a virtual keyboard application, a virtual keyboard region of a touchscreen of a mobile phone of a user for displaying a virtual keyboard, the virtual keyboard including a plurality of keys for communicating with a text input area of a first application when the virtual keyboard is in a text entry mode and a CRM region for displaying information and receiving user instructions and interacting with CRM functions when the virtual keyboard is in a CRM, wherein the virtual keyboard in the CRM mode is configured to communicate with at least one of a contacts application, a calendar application, and an email application in the mobile phone; presenting on the touchscreen to the user at least one CRM function key in the CRM region for carrying out various CRM functions; receiving from the user a selection of a CRM function of the various CRM functions detected through the touchscreen, by the virtual keyboard application; and responsive to receiving a selected CRM function, displaying within the CRM region, additional CRM function keys or information from at least one of the contacts application, the calendar application, and the email application without leaving the virtual keyboard application or the first application.

2. A method comprising: invoking, from within a first application that presented a user with a text input area and after a user selects the text input area on a touchscreen the first application is configured to invoke a virtual keyboard and then receive text from the user’s interactions with the virtual keyboard, the execution of a virtual keyboard application on a mobile phone, displaying, by a virtual keyboard application, a virtual keyboard region of the touchscreen of the mobile phone of the user for displaying a virtual keyboard, the virtual keyboard including a plurality of keys for communicating with the text input field of a first application when the virtual keyboard is in a text entry mode and a CRM region for displaying information and receiving user instructions and interacting with CRM functions when the virtual keyboard is in a CRM, wherein the virtual keyboard in the CRM mode is configured to communicate with at least one of a contacts application, a calendar application, and an email application in the mobile phone; presenting the user in the CRM region of the touchscreen a CRM function key corresponding to at least one of the CRM functions; receiving from the user an interaction with the CRM function key detected through the touchscreen, by the virtual keyboard application; and responsive to receiving the interaction with the CRM function key, displaying within the CRM region results of a selected CRM function and additional CRM function keys.

3. The methods of either of claim 1 or 2, wherein the presented at least one CRM function key includes at least two of the various CRM functions including viewing a list of CRM contacts from the contacts application, viewing a list of activities from the calendar application, and viewing a list of follow-ups from a task management application.

4 The methods of claims 3, wherein after the user selects viewing a list of activities from the calendar application, presenting the user with the additional CRM function keys to view the list of activities or create a new activity.

5. The methods of claim 3 wherein after the user selects viewing a list of activities from the calendar application, presenting the user with the list of activities and the additional CRM function keys to view the list of activities in a pop-up window or the calendar application.

6. The methods of either claims 1 or 2, wherein the selected CRM function is viewing a list of CRM contacts from the contacts application, and displayed within the CRM region is a list of the CRM contacts and the additional function keys for the listed CRM contacts included at least two of viewing call details with a selected CRM contact, scheduling an activity with the selected CRM contact, or creating a follow up with the selected CRM contact.

7. The methods of claim 3, wherein, when viewing the list of follow-ups, the list of followups is filtered and sorted according to their due date.

8. The methods of claims 1 or 2, wherein the CRM view has a list of follow-ups related to a CRM contact, and the additional CRM function keys let the user to select sending the CRM contact any of the list of follow-ups.

9. The methods of claim 8, wherein, when the user selects to send any of the list of followups to the CRM contact, the virtual keyboard application sends a selected follow-up to the CRM contact using a predetermined communication method stored in the follow up in a task management application or associated with the CRM contact in the contact application.

10. The methods of claim 9, wherein the virtual keyboard application sends the selected follow-up using the predetermined communication method with a predetermined user message.

11. The methods of claim 10, wherein the user does not have to type on a keyboard or manually open another application for the virtual keyboard application to send the selected follow-up using the predetermined communication method with the predetermined user message.

12 The methods of any of claims 1-11, further comprising presenting to the user a plurality of other CRM function keys; after receiving from the user a selection of the plurality of other CRM function keys, invoking at least one of the contacts application, the calendar application, and the email application and acquiring information from the invoked application, and filtering information from the invoked application and presenting at least some of the filtered information to the user in the CRM region.

13. The methods of claim 12, further comprising presenting the user with a new CRM function key next to the filtered information; and in response to receiving a selection of the new CRM function key from the user, updating data in the invoked application.

14. The methods of either of claims 1 or 2, wherein the first application is different from the virtual keyboard application, the contacts application, the calendar application, and the email application.

15. The methods of either of claims 1 or 2, wherein the virtual keyboard in the CRM mode is configured to communicate with the contacts application, the calendar application, and the email application without the user separately needing to open or switch to the contacts application, the calendar application, and the email application.

16. The methods of either of claims 1 or 2, wherein in response to a user request to view clients, the CRM region displays CRM contacts and a user option to receive prior call details, a user option to view or modify a schedule, or a user option for following up for any of the CRM contacts.

17. The methods of claim 16, wherein the prior call details include date and time of prior calls.

18. The methods of either of claims 1 or 2, wherein interacting with the CRM function key sends a follow-up to a CRM contact, wherein information is stored in the follow-up or the contact application indicating a pre-determined preference of a CRM contact, and in response to the user pressing the CRM function key, sending the follow-up to the CRM contact based on the pre-determined preference of the CRM contact.

19. The methods of claim 17, wherein sending the follow-up includes sending a predetermined message that has been set by the user together with the follow-up.

20. The methods of any of Claims 1-19, wherein the virtual keyboard application stores in the contact application for each CRM contact at least two of lead status, source type, tax ID, product, account owner, and a CRM client flag.

21. The methods of any of Claims 1-20, including displaying a function key for toggling the virtual keyboard between text entry mode and CRM mode. 21

22. A mobile phone device with a virtual keyboard having an embedded CRM tool, the device comprising: a processor; a touchscreen display; memory; storage including a virtual keyboard application, a contacts application, a calendar application, and an email application; wherein the virtual keyboard application is configured to be executed by the processor, the virtual keyboard application including instructions for: invoking the virtual keyboard application to display in a portion of the touchscreen display a virtual keyboard including a CRM region; displaying on the touchscreen in the CRM region at least one CRM function key for the user to select a CRM function; receiving through the touchscreen display an indication of a selected CRM function, and executing the selected CRM function in at least one of the contacts application, the calendar application, or the email application.

23. The device of claim 22, wherein the contacts application, the calendar application, and the email application are not integral with the virtual keyboard application.

24. The device of claim 22, wherein the contacts application, the calendar application and the email application are default contacts application, calendar application and email application of the mobile phone.

25. The devices of any of claims 22-24, wherein following a mobile phone call, the instructions include asking the user whether to save the contact as a CRM contact.

26. The devices of any of claims 22-24, wherein following a mobile phone call, the instructions have the processor check CRM fields or CRM flags in the contacts application as to whether the contact is a known CRM contact.

27. The devices of any of claims 22-24, wherein following a mobile phone call, the instructions include extracting call information from the phone application and using the extracted call information to update CRM fields or CRM flags in the contacts application.

28. The devices of claims 27, wherein the CRM fields or CRM flags in the contacts application are at least one of existing fields or flags of contacts in the contact application and newly created fields or flags in the contacts of the contact application.