WO2019244074A2

WO2019244074A2 - System for obtaining resources from a user

Info

Publication number: WO2019244074A2
Application number: PCT/IB2019/055168
Authority: WO
Inventors: Karl Christopher Lennox NIMMO; Damian Giovanni LINCESSO
Original assignee: Integrum Ltd
Current assignee: Integrum Ltd
Priority date: 2018-06-19
Filing date: 2019-06-19
Publication date: 2019-12-26
Anticipated expiration: 2020-12-19
Also published as: WO2019244074A3

Abstract

This invention relates to a messaging system for obtaining resources from a user. The system (1) includes a messaging app (2) running on a mobile device (3) and the functionality to send and receive fulfillable messages through the messaging application (2). Fulfillable messages and requests are sent from a first user to another user wherein the receiving user may comply with requirements as set out by the first user. The receiving user may send a requested document, text message, data file, verification result, or authentication result to the first user through the messaging app (2) to fulfil the message. The system (1) includes a process configuration tool (4) in the form of a graphical user interface (GUI) for a user to construct the nodes, branches, and flows of the process (6) by arranging fulfillable messages diagrammatically in a flowchart structure (5).

Description

SYSTEM FOR OBTAINING RESOURCES FROM A USER

FIELD OF THE INVENTION

This invention relates to a messaging system and more specifically, but not exclusively, a messaging system for obtaining resources from a user. BACKGROUND TO THE INVENTION

Messaging applications are known in the art and are becoming increasingly popular. Modern messaging applications can exchange messages of different media types such as images, audio and locations. Businesses are also increasingly using messaging applications to communicate with clients and to conduct business. A problem with existing messaging applications is that the application does not provide sufficient features for automated interaction with the users of the messaging application.

OBJECT OF THE INVENTION

It is accordingly an object of this invention to provide a messaging system, which, at least partially, alleviates the problem associated with the prior art or which provides a useful alternative thereto. SUMMARY OF THE INVENTION

In accordance with the invention there is provided a messaging system for obtaining resources from a user comprising:

- a messaging application running on a mobile device of a user;

- the system including functionality to send fulfillable messages to the messaging application of the user;

- the fulfillable message requesting a resource from the user which complies with requirements specified in the fulfillable message;

- the application providing means for fulfilling the request as a message;

- the application providing the user with means for fulfilling the request through capturing the resource; and

- a process configuration tool for configuring a sequence of interactions with a user by arranging fulfillable messages in a desired configuration.

The application may provide the resource for fulfilling the request message automatically. The resources may include documents, information, authentication, and/or location of the user.

The fulfillable message may be a location request message and the resource requested from the user may be a location in the form of GPS coordinates. The fulfillable message may be an encapsulation of a previously executed process and the resource may be a representation of the completion of the process.

The process fulfillable message may be a know your customer (KYC) fulfillable message and the resources may be a previously executed process, proof of address, photo of identity document, or a biometric of the user.

The fulfillable message and resources may be stored and reused for future processes or interactions.

The fulfillable message may request biometric authentication or identification as the resource. The biometric authentication or identification may include fingerprint scanning, facial recognition; eye scan recognition and voice recognition. The fulfillable message may require the resource to be text, an image or a voice recording.

The fulfillable message may be a form with fields and options which may be completed and submitted as the resource. The fulfillable message may be directed at a number of users in a group.

The fulfillable message may be sent to the group simultaneously requiring a resource from each user.

The users may send fulfillable messages to other users within the same group. The messaging system providing a configuration tool for configuring a workflow process to be sent to a user or a group of users.

The workflow process may be a flowchart of fulfillable messages created by means of the configuration tool.

The flowchart may include branches with integrated logic and other decision-making nodes.

The configuration tool may be used to create simple or complex workflow processes consisting of fulfillable messages. The tool may include text analysis functioning to analyse messages received.

The tool may include data validation means.

The resources may be evaluated and subjected to logical operators in order to determine the flow through the flowchart and the associated order of fulfillable messages in the process.

BRIEF DESCRIPTION OF THE DRAWINGS

An embodiment of the invention is described below, by way of example only, and with reference to the drawings in which:

Figure 1 is a schematic representation of a messaging system for obtaining resources from a user through a mobile device;

Figure 2 is a schematic representation of a workflow configuration tool for creating a customized process;

Figures 3 to 9 are schematic representations of the system of Figure 1 in use; and

Figure 10 is a schematic representation of a back-end user accessing the system of Figures 3 to 9. DETAILED DESCRIPTION OF THE DRAWINGS

With reference to the drawings in which like features are indicated by like numerals, a messaging system for obtaining resources from a user through a mobile device is generally indicated by reference numeral 1.

The system 1 includes a messaging app 2 running on a mobile device 3. The system may include components, such as a server computer running software for enabling the apps 2 to connect to the server and to other apps, which are not shown or may be implemented in a distributed fashion on many mobile devices 3. The messaging app is software which is installed on a mobile device such as a smart phone. The software enables messages to be sent and received through the Internet and offers an alternative to operator-based text messaging via SMS. The system 1 includes the functionality to send and receive fulfillable messages through the messaging application 2 of the user. Fulfillable messages and requests are sent from a first user to another user wherein the receiving user may comply with requirements as set out by the first user. The receiving user may send a requested document, text message, data file, verification result, or authentication result to the first user through the messaging app 2 to comply with the message and upon receipt, the request message will be fulfilled.

The system 1 includes a process configuration tool 4 for configuring a sequence of interactions with a user by arranging fulfillable messages in a desired configuration. An embodiment of the configuration tool 4 which runs on the user's smartphone as part of the application 2 is shown in figure 2 and an embodiment wherein the configuration tool 4 is provided as a part of a back-end interface is shown in figure 10. A user can manage a message process and configure the process using the workflow configuration tool 4. This process may include interpretation of the user's messages for comparing or validating the information in the message, logic for making decisions and taking different actions according to the process, and storage and calculation of the interpreted messages.

The tool 4 is in the form of a graphical user interface (GUI) and allows the user to construct the nodes, branches, and flows of the process 6 by arranging fulfillable messages diagrammatically in a flowchart structure 5. The flowchart structure 5 may include configuration for how to process the resources (such as storing or transmitting the resources) or logic for determining the flow through the workflow. The tool 4 can also configure interactions between two or more users of the app 2. In the example shown in Figure 2 a first user, such as a creator, may create a customized workflow 6 using the configuration tool 4. Users 7 can be connected to a group as shown in Figure 3 and the process 6 is associated with the group 8. The process 6 consists of a series of fulfillable messages sent by the creator to the group 8. The group 8, or the users in the group, may follow the process 6 set out and comply with each fulfillable message through the messaging app 2. The fulfillable message may be directed at an individual user 7 or a group 8 of users and may be sent to the group simultaneously requiring a resource from each user 7. The users 7 may also send fulfillable messages to other users 7 within the same group 8. The creator may store the provided resources or responses in a database for future use. In a first example shown in figures 4 to 5, a group 8 with multiple employees, is created and subjected to the process 6. The process 6 is simple and has only two fulfillable messages. The first 9 requires employees in the group 8 to indicate whether they will attend a function. This fulfillable message is sent as one wherein an employee may press a button to send one of two specified responses ("YES" or "NO"). If the employee responds "NO" 10, they are removed from the group 8 and informed by a message 1 1. The logic used to interpret the users message 11 is configured using the tool 4 with a simple comparison of the message text to an anticipated response and the system 1 will perform an action which is specified in the tool 4, in this case being to remove the user from the group 8. If the employee responds "YES" in a message 12, then a follow up fulfillable message 13 is sent wherein the employee is requested to indicate the number of guests attending. The tool 4 is configured such that the number in text or as a numeral may be interpreted and stored such that the total number can be calculated when all employees have responded. The responses 14 from the employees are collated and stored. The users may interact with each other in the group as normal, and the group will disband and send the collated data to the employer once the process 6 is completed for all users.

Another example of the system includes a series of different resource requests from one user to another. In the example shown in Figures 6 to 8, a know your customer (KYC) workflow for a banking client is illustrated. KYC processes are common in the financial and credit industries for anti-money laundering purposes and can create an administrative burden on these industries. Simplification and automation of KYC is very desirable, and the following banking example exemplifies how a KYC workflow may be completed by a series of fulfillable messages and responses in the form of resources.

A fulfillable message 15, requesting the client's identification (ID) number (or other form of identification such as a social security number or internal account number), is shown in Figure 6. The client complies with the request by sending their ID number in a message 16. The tool 4 is used to configure interpretation of the ID number by checking whether it is in a correct format and whether the ID number is present in a database of the bank. The system 1 automatically interacts according to the client's response with another fulfillable message 17, sent to the client, based on the client's previous response 16. The message 17 contains personal and contact information of the client which the bank has on record, such as names, addresses, and date of birth. The client is requested to verify whether the information the bank has on its system is correct. The client sends a text message 18 to the messaging app replying that the information is correct and thus fulfilling another request. The next fulfillable message 19, shown in Figure 7, requests the client to provide a photo of their ID and send it in a message 20 through to fulfil the request 19. Fulfillable message 21 requests the client to take a photograph of themselves in order to conduct facial recognition, or another biometric processes, and for storing the photograph on record with the bank. After the photograph 22 is sent, the messaging app 2 requests the client's utility bill 23, shown in Figure 8, to be uploaded to the messaging app 2. The system 1 sends a message 24 informing the client that the KYC workflow is completed, and the client may store the completed process with collated data in the messaging app 2 for future use. The completed and stored KYC workflow process may be accessed in future by the client and may be sent to other institutions requiring the same process.

Similar to the example described above flowcharts which represent real world processes may be constructed by combining many different fulfillable messages such as those described in further detail below. For example, the fulfillable message may be an authentication request message. The authentication request message may be fulfilled by the user by authenticating a proposed action or transaction proposed by the system. The authentication may be as simple as a password or one time pin, or involve matching biometric information of the user. The biometric matching may include fingerprint scanning, facial recognition, eye scan recognition or voice recognition. The fulfillable message may be a form with fields and options 25 which may be completed and submitted as the resource. The form may include text fields, checkboxes, or other fields which, once completed is sent as a message in an appropriate format. In the example shown in figure 9, the user 7 may be requested to connect 26 to a second user, provide proof of identity 27, provide other necessary documents 28, complete a request form 29, upload the request form 30, verify the authenticity of the information 31, and send the workflow 32 to the second user as a secure atomic log 33. The atomic log is an electronic representation, which is understandable by the system, of the completed workflow.

A client may also be requested to send the encapsulation (atomic log) 33 of a previously executed and completed workflow which was automatically saved by the system 1. The fulfillable message and resources may again be stored and reused for future interactions. An example includes a scenario where a company needs a bundle of documents or information in order to register a client. Instead of the client filling in and uploading all relevant documents again, the system 1 may provide a previously executed workflow interaction which already contains all the relevant information and documentation needed by the company. The system 1 allows the messaging app to automatically provide the encapsulation as a resource to the requesting company. If the resource is not available, the system 1 will provide the user with the means for capturing the resource through the messaging app.

A completed and stored workflow process may also be accessed by a back end user. In the example shown in Figure 10, the completed and stored KYC workflow process is accessed through a graphical user interface. The back-end user may send 34 the completed workflow to another user; view 35 the details of the workflow; or delete 36 the workflow. The data and information 37 exchanged during the original completion of the workflow is displayed. The workflow may again be accessed by the back-end user in future.

Those skilled in the art will appreciate that the invention provides means of configuring workflow processes which may serve many purposes, and which can be completed by a user in a familiar messaging format. Another example is set out below wherein the workflow is configured from the perspective of a city or municipality accounts department. The office uses the configuration tool to read all incoming messages and determine if the phone number associated with the incoming message corresponds to one of the accounts under their management. If the number is so associated, the office may present the user with options for retrieving, for example, their utility bill. The user receives the utility bill along with information on the amount due and the date on which the amount became due. If the number is not known to the office, a fulfillable process is initiated wherein the user is requested to provide identifying and authenticating information to have an account associated with the user. Once this is done, the user will receive the relevant utility bill.

In this example, the office may send the utility bill to the user as a fulfillable message in the form of a payment request. The payment request includes the amount due, due date, an image of the bill or statement, and requests the user to provide payment information. The payment information may be, for example, the reference number of a bank transfer, account number for direct debit, or the user's credit card details. Where credit card information is requested, the user may provide the credit card information as the resource in a message and the office can process the credit card transaction for the indicated amount and mark the bill as settled. The transaction may be processed in an automated fashion wherein no human interaction of the office is required.

All messages on the messaging system may be encrypted to ensure a user's personal, private, and sensitive information is secure. In the payment request example described above, the credit card information of the user may be encrypted such that only a payment gateway may access the information in an automated fashion and the original credit card details will not be visible to anyone at the office. The payment information may also be provided in a tokenised form, wherein the transaction is completed by the user outside of the system with a trusted payment gateway, and a token of payment is provided to the office which may be sent to the provider for processing or confirmation of the payment. It is envisaged that the invention will provide an interactive messaging system for obtaining resources from a user and allowing users to interact and share data between each other as well as with different institutions. The invention will streamline the process of sharing and obtaining documentation, data, files, images and processes by use of a single message application-based system. The invention is not limited to the precise details as described herein. For example, instead of plain text, documentation or biometric authentication, any response may be sent to fulfil the request as long as it meets the requirements set out in the request. Similarly, users are not limited to employers/employees or companies/clients as the relationship between the users will differ depending on how the process is configured. Payments need not be limited to credit cards and may be processed using reward scheme points or cryptocurrencies.

Claims

1. A messaging system for obtaining resources from a user comprising: a message application running on a mobile device of a user; the system including functionality to send fulfillable messages to the messaging application of the user; the fulfillable message requesting a resource from the user which complies with requirements specified in the fulfillable message; the application providing means for fulfilling the request as a message; the application providing the user with means for fulfilling the request through capturing the resource; and a process configuration tool for configuring a sequence of interactions with a user by arranging fulfillable messages in a desired configuration.

2. The messaging system of claim 1 wherein the application provides the resource for fulfilling the request message automatically.

3. The messaging system of claim 1 wherein the resource is a document of the user.

4. The messaging system of claim 1 wherein the resource is information of the user.

5. The messaging system of claim 1 wherein the resource is authentication of the user.

6. The messaging system of claim 1 wherein the resource is the location of the user.

7. The messaging system of claim 1 wherein the fulfillable message is a location request message and the resource requested from the user is a location in the form of GPS coordinates.

8. The messaging system of claim 1 wherein the fulfillable message is an encapsulation of a previously executed process and the resource is a representation of the completion of the process.

9. The messaging system of claim 8 wherein the encapsulation is a KYC message and the resource is a previously executed process, proof of address, photo of identity document and a biometric of the user.

10. The messaging system of claim 1 wherein the fulfillable message and resource are stored and reused for future processes.

1 1. The messaging system of claim 1 wherein the fulfillable message requests biometric authentication as the resource.

12. The messaging system of claim 1 1 wherein the biometric authentication is fingerprint scanning.

13. The messaging system of claim 1 1 wherein the biometric authentication is facial recognition.

14. The messaging system of claim 1 1 wherein the biometric authentication is eye scan recognition.

1 5. The messaging system of claim 1 1 wherein the biometric authentication is voice recognition.

16. The messaging system of claim 1 wherein the fulfillable message requires the resource as text.

17. The messaging system of claim 1 wherein the fulfillable message requires the resource as an image.

18. The messaging system of claim 1 wherein the fulfillable message requires the resource as a voice recording.

19. The messaging system of claim 1 wherein the fulfillable message is a form with fields and options which are completed and submitted as the resource.

20. The messaging system of claim 1 wherein the fulfillable message is directed at a number of users in a group.

21. The messaging system of claim 20 wherein the fulfillable message is sent to the group simultaneously requiring a resource from each user.

22. The messaging system of claim 20 wherein the users send fulfillable messages to other users within the same group.

23. The messaging system of claim 1 wherein the configuration tool configures the sequence of interactions as a workflow process which is sent to a user.

24. The messaging system of claim 20 wherein the configuration tool configures the sequence of interactions as a workflow process which is sent to the group of users.

25. The messaging system of claims 23 or 24 wherein the workflow process is a flowchart of fulfillable messages created by means of the configuration tool.

26. The messaging system of claim 25 wherein the flowchart includes branches with integrated logic.

27. The messaging system of claim 26 wherein the resources may be evaluated and subjected to logical operators in order to determine the flow through the flowchart and the associated order of fulfillable messages in the process.

28. The messaging system of claim 1 wherein the fulfillable message is a payment request message and the resource is the payment information of the user.

29. The messaging system of claim 28 wherein the payment information is credit card details of the user.

30. The messaging system of claim 28 wherein the payment information is a bank transfer reference number.

31. The messaging system of claim 28 wherein the payment request message includes an amount due.

32. The messaging system of claim 28 wherein the payment request message includes a bill which is provided to the user.