ITUB20152849A1 - SYSTEM AND METHOD FOR THE MANAGEMENT OF ONLINE REVIEWS - Google Patents

Description

"SYSTEM AND METHOD FOR MANAGING ONLINE REVIEWS"

DESCRIPTION

The present invention relates to a system and a method for managing online reviews.

The use of online reviews is known and increasingly widespread, that is, shared reviews that can be inserted and accessed on the Internet through social media and the Web in general.

In particular, online reviews are an increasingly used tool to share opinions about products and, above all, services purchased.

For example, some of the sectors in which the use of online reviews has become an increasingly important and decisive tool in the final decisions of consumers are those of tourism and catering (hotels, restaurants, holiday packages and the like).

However, the use of such online reviews presents problems and obvious limitations at present.

First of all is the well-known problem of false online reviews, that is, reviews made by people who have never actually used the service offered, but who have a mostly personal interest in releasing a positive or negative review.

In fact, to date, it is impossible or extremely complicated to carry out checks on the actual reliability of the reviews entered and there are no tools capable of carrying out such checks in a reliable and automated way.

The main task of the present invention is to devise a system and a method for managing online reviews that allows to eliminate the problem of false online reviews, that is, reviews made by subjects who have never actually used the service offered, but who have a personal interest in giving a positive or negative review.

Another object of the present invention is to devise a system and a method for managing online reviews that allows to overcome the aforementioned drawbacks of the prior art in the context of a simple, rational, easy and effective use and low cost solution. The above purposes are achieved by the present system for managing online reviews having the characteristics described in claim 1.

The above purposes are also achieved by the present method for managing online reviews having the characteristics described in claim 10.

Other characteristics and advantages of the present invention will become more evident from the description of a preferred, but not exclusive, embodiment of a system and method for managing online reviews, illustrated by way of example, but not limited to, in the accompanying table. drawings in which:

Figure 1 is a block diagram illustrating the system according to the invention. With particular reference to these figures, 1 generally indicates a system for managing online reviews R.

Advantageously, the system 1 according to the invention is a "third" system capable of reliably certifying the qualities (or limits) of commercial businesses and professionals, of public and private bodies.

In fact, system 1 makes it possible to take advantage of the possibility of issuing an online review R every time an electronic economic transaction T occurs for a service, thus certifying and making this review reliable.

In particular, system 1 makes it possible to exploit the electronic payment vehicle as a certification of a transaction T of goods between the two parties involved: customer C and service provider F (or, possibly, of products).

Each R review can only be released for a single transaction T.

Therefore, the system 1 according to the invention allows to eliminate the problem of false online reviews, that is, of reviews made by subjects who have never actually used the service offered, but who have a personal interest in issuing a positive or negative review. Therefore, the subjects involved in the use of system 1 are customers C, suppliers F of products or services and managers G of payment services on mobile devices (mobile payment) or by traditional electronic payment.

Specifically, C customers access system 1 for managing reviews R and become the only "producers". It is not possible for anyone other than a customer C of the service managed through system 1 to enter R reviews.

Naturally, each customer C can carry out S searches among the reviews R already entered and present within the system 1.

Preferably, access to system 1 is completely free for C customers. C customers' natural propensity to release R reviews is exploited.

Preferably, the F suppliers of products and services pay an annual fee or a token per review R received.

Only quality F suppliers will be in the top positions; it will not be possible to pay in order to be placed in important positions.

Preferably, the reviews R managed by system 1 relate to transactions T occurred for services (retailers, professionals, branches of communications companies, ...). However, the use of system 1 for the management of reviews R linked to T transactions with product suppliers is not excluded. The G providers of payment services on mobile devices (such as, for example, Google Wallet, Apple Pay or similar) are interested in using system 1 as they get a service that benefits them over "competitors" banks / credit cards or, trivially, as they risk losing a competitive advantage over their direct competitors.

The activity envisaged by the G payment service managers for integration to system 1 requires very little effort and is fully compliant with the provisions of the privacy laws. In fact, G managers are not required to provide information on the amounts of transactions T, nor on the personal details of customers C.

As schematized in Figure 1, system 1 comprising a management and control unit 2 suitable for managing online reviews R entered by customers C.

In particular, this management and control unit 2 is equipped with at least one storage unit 3 of the reviews R and means of presentation 4 of the reviews entered to customers C (and suppliers F).

For example, the means of presentation 4 of the reviews may comprise a suitable web portal.

The system 1 also comprises at least a customer interface unit 5 operatively connected to the management and control unit 2 and provided with means for registering and authenticating customers C and with means for inserting a new online R review relating to said transaction T.

In particular, the customer interface unit 5 can be implemented by means of a suitable software application that can be installed on a personal computer 5a and / or on a mobile device such as a smartphone 5b or a tablet 5c.

For example, an application for smartphone 5b or tablet 5c can be provided for re-entering reviews R, with the possibility of searching for suppliers F located in the vicinity of customer C, or by reading a QR-code printed on the receipt or receipt.

Usefully, Γ the use of a mobile device 5b, 5c with the related application will make authentication and recognition operations faster, as each mobile device is generally uniquely linked to a specific user.

Preferably, the system 1 also comprises at least one supplier interface unit 6, operationally connected to the management and control unit 2 and provided with means of registration and authentication of suppliers F of products or services.

Similarly to the customer interface unit 5, also the supplier interface unit 6 can be implemented by means of a suitable web page, a software application that can be installed on a personal computer and / or on a mobile device such as a smartphone. or a tablet.

Usefully, if a customer C reviews a supplier F who is not registered on system 1, then that review R is made accessible to customers C for thirty days, then it is made invisible, possibly until supplier F decides to take part of the service and to register on system 1, eventually paying the requested contribution.

Advantageously, the system 1 comprises at least a unit 7 for generating a unique transaction code CT, operatively connected to said management and control unit 2 and capable of generating and forwarding the unique transaction code CT to the management and control unit itself. in the event of a transaction T between a supplier F of products and services and a customer C.

In particular, the unique transaction code CT includes:

an IDc customer identification key;

an identification key of the IDp supplier;

an IDT transaction identification key.

In particular, this unit of generation 7 of a unique transaction code can be connected and / or implemented within a payment management system P of an existing operator G and able to manage payment services on mobile devices and / or e-commerce and / or traditional electronic payment.

Advantageously, moreover, the management and control unit 2 comprises means 8 for verifying the correspondence between customer C, supplier F and transaction T associated with a new review R entered by a customer C and the identification key of the customer HDc, the identification of the IDF supplier and the identification key of the IDT transaction present within the unique transaction code CT-Usefully, the service provided through system 1 is multichannel, as it can be developed entirely for web services, but translates in the same way to electronic payments through mobile devices (such as NFC or credit cards).

Therefore, the verification means 8 of the management and control unit 2 of the reviews R can be constituted by WebServices that receive information from payment management systems such as Google Wallet, Apple Pay, Facebook Pay or similar.

According to a preferred embodiment, the customer identification key IDc comprises an N-digit customer identification alongside an identification of the payment management system P with which the payment for transaction T was made. No other relative information to customer C will be shared with the management and control unit 2. When customer C registers on system 1, the management and control unit 2 makes a unique association between user and password to the account and makes a first authentication in order to validate the identity. If the login is successful, you will also receive the IDc customer identification key. The various identification keys of the customer IDc received from the different payment management systems will therefore be linked to the user's account P.

Again according to a preferred embodiment, the identification key of the IDT transaction includes the date and time instant of the transaction.

Preferably, the IDT transaction identification key format is as follows: YYYY-MM-DD H24: mm: ss.mill Timezone.

Furthermore, again according to a preferred embodiment, the supplier identification key Π3⁄4 comprises an N-digit supplier identification alongside an identification of the payment management system P with which the payment for the transaction T was made.

In addition, together with the identification key of the IDF supplier, the name of the business and the complete address of the supplier F may also be communicated (only for registered suppliers who have expressly granted the release of privacy to share certain information).

However, different embodiments of the system 1 with different implementations of the customer identification key IDc, the identification key of the supplier IDp and the identification key of the IDT transaction are not excluded.

In addition, in order to ensure the reliability of the new R review by means of verification 8, the R review includes the following information:

the identification key of the customer IDc;

the identification key of the IDF supplier;

the identification key of the IDT transaction.

a vote relating to the transaction T carried out;

a text field to contain the description of the review itself. Preferably, the name of customer C is not indicated in the review R, as it is not known, but is randomly selected from a set of predefined standard names for each country.

This will make it possible not to make public the IDc identification key of each customer C and, at the same time, to see the name of people who carry out R reviews, instead of simple codes, in order to make the R review more "familiar" and less aseptic .

The method for managing online reviews using system 1 is described below.

In particular, in the event of a transaction T between a supplier F of products or services and a customer C, the method involves a phase of generation and forwarding of a unique transaction code CT to the management and control unit 2.

Subsequently, the method involves:

a phase of registration and authentication of the customer C at the management and control unit 2, by means of the customer interface unit 5, and a phase of insertion on the storage unit 3 of the management and control unit 2, to be part of customer C and through the customer interface unit 5, of a new online review R relating to the specific transaction T.

Usefully, after the phase of generating the unique transaction code CT, the method can include a phase of sending the customer a link to a Web portal of the management and control unit 2.

Usefully, the aforementioned link can be printed on receipts and receipts via QR-code or similar and can be read by the smartphone or tablet application to speed up the operations of entering the review.

The customer, by clicking on the link, is taken to the web portal page to release the review R.

Advantageously, the method according to the invention further comprises a step for verifying, by means of the verification means 8, the correspondence between:

customer identification key IDc, vendor identification key IDF, and transaction identification key IDT associated with the new review R, and

identification key of the customer IDc, identification key of the IDF supplier and identification key of the IDT transaction present within the unique transaction code CT received.

In the event that this verification is successful, then, system 1 certifies the reliability of the new review 3 and inserts it in the storage unit 3.

Usefully, the method also provides at least one registration and authentication phase of at least one supplier F of products or services at the management and control unit 2 of R reviews, through the supplier interface unit. If necessary, to carry out this registration, the supplier F pays an annual registration fee.

Therefore, the typical flow of information within system 1 is as follows.

Customer C carries out transaction T with supplier F.

The manager G who takes care of the payment sends an e-mail to customer C with the relative link necessary to carry out the review R.

Alternatively, customer C has the ability to log into system 1 and request the list of transactions T performed by him in the last 2-3 months. In this query, all transactions occurred for customer C are retrieved with the list of suppliers F (with additional information keys, where available).

In this case, customer C chooses the appropriate transaction T and can carry out the review R for it.

A transaction T already reviewed can no longer be used again (in the limit, the judgment within the same review R can be changed).

The supplier accesses the service in the same way as customers C. Obviously, he will be able to manage his account and the related service costs, he will be able to see the reviews related to him, without having the possibility to know the references of the customer C who wrote them.

The service charge of the supplier could be linked to a time frame (annual or five years) or to the number of reviews received (in batches of refills of 10 - 50 - 100 reviews).

Below is an example of possible use of system 1.

A customer C wants to submit an R review for a T transaction made the previous week with the GoogleWallet service.

Customer C logs on to the Web portal 4 of the management and control unit 2. Customer C selects the button relating to the insertion of a new review R.

Customer C chooses the operator G with which he made the payment and presses a specific search button.

System 1 sends a call to the WebService of the chosen payment management system P, sending the user code linked to the customer. This code is the key with which the payment system recognizes each user.

The payment management system P returns the list of transactions T to that specific code. In addition to the three keys IDc, IDF and basic IDT, basic information about the supplier F will also be provided (for example, company name and address, where available).

Customer C selects transaction T for which he wants to review R and enters it.

In practice it has been found that the described invention achieves the intended aim and objects.

In particular, it is emphasized that the system and the method according to the invention allow each single new online review to be reliably authenticated.

In practice, therefore, the system and the method according to the invention allow to eliminate the problem of false online reviews, that is, of reviews made by subjects who have never actually used the service offered, but who have a personal interest in issuing a positive review. or negative.

Claims (10)

CLAIMS 1) System (1) for managing online reviews, comprising: at least one management and control unit (2) of reviews (R) online, equipped with at least one storage unit (3) of said reviews (R) and means of presentation (4) of said reviews (R); at least one customer interface unit (5) operationally connected to said management and control unit (2) and equipped with customer registration and authentication means (C); characterized in that it includes: at least one generating unit (7) of a unique transaction code (CT), operatively connected to said management and control unit (2) and capable of generating and forwarding said unique transaction code (CT) to said management unit and control (2) in the event of a transaction (T) between a supplier (F) of products and services and a customer (C); wherein said unique transaction code (CT) comprises: an identification key (IDc) of said customer (C), an identification key (IDF) of said supplier (F), an identification key (IDT) of said transaction (T); wherein said customer interface unit (5) is provided with means for inserting on said storage unit (3) a new online review (R) relating to said transaction (T); and in which said management and control unit (2) comprises verification means (8) of the correspondence between customer (C), supplier (F) and transaction (T) associated with said new review (R) and said identification key ( IDc) of the customer (C), said identification key (IDp) of the supplier (F) and said identification key (IDT) of said transaction (T). 2) System (1) according to claim 1, characterized in that it comprises at least a supplier interface unit (6), operatively connected to said management and control unit (2) and provided with supplier registration and authentication means ( F) of products or services. 3) System (1) according to one or more of the preceding claims, characterized in that said unit for generating a unique transaction code (CT) can be connected and / or implemented within a payment management system ( P) on mobile devices and / or e-commerce services. 4) System (1) according to one or more of the preceding claims, characterized in that said presentation means (4) of the reviews (R) comprise at least one web portal or the like. 5) System (1) according to one or more of the preceding claims, characterized in that said identification key (IDc) of the customer (C) comprises an N-digit customer identification alongside an identification of the payment management system (P) with which payment was made for the transaction (T). 6) System (1) according to one or more of the preceding claims, characterized by the fact that said transaction identification key (IDT) includes the date and time instant of said transaction (T). 7) System (1) according to one or more of the preceding claims, characterized in that said supplier identification key (IDF) comprises an N-digit supplier identification alongside an identification of the payment management system (P) with which it is payment has been made for the transaction (T). 8) System (1) according to one or more of the preceding claims, characterized in that said review (R) comprises said customer identification key (IDc), said supplier identification key (IDF), said transaction identification key (IDT), a vote and a text field to contain the description of the review (R) itself. 9) System (1) according to one or more of the preceding claims, characterized in that at least one of said customer interface unit (5) and said supplier interface unit (6) comprises at least a software application that can be installed on a personal computer and / or on a mobile device. 10) Method for managing reviews (R) online, characterized by the fact that it includes: in the event of a transaction (T) between a supplier (F) of products or services and a customer (C), at least one phase of generation and forwarding of a unique transaction code (CT) to a management and control unit (2 ) online reviews (R) provided with at least one storage unit (3) of said reviews (R); wherein said unique transaction code (CT) comprises: an identification key of said customer (IDc), an identification key of said supplier (IDp), an identification key of said transaction (IDT); at least one registration and authentication phase of said customer (C) at said management and control unit (2), through a customer interface unit (5); at least one step of insertion on said storage unit (3), by said customer (C) and through said customer interface unit (5), of a new review (R) Online relating to said transaction (T); at least one phase of verification of the correspondence between customer (C), supplier (F) and transaction (T) associated with said new review (R) and said customer identification key (IDc), called supplier identification key (IDF) and said transaction identification key (IDT). 11) Method according to claim 10, characterized in that it comprises at least a registration and authentication step of at least one supplier (F) of products or services at said management and control unit (2) of reviews (R), by means of a supplier interface unit (6). 12) Method according to one or more of claims 10 and 11, characterized in that said customer identification key (IDc) comprises an N-digit customer identification alongside an identification of the payment management system (P) with which it has been paid for the transaction (T). 13) Method according to one or more of claims 10 to 12, characterized in that said transaction identification key (IDT) includes the date and time instant of said transaction (T). 14) Method according to one or more of claims 10 to 13, characterized in that said supplier identification key (IDF) includes an N-digit supplier identification alongside an identification of the payment management system (P) with which the payment for the transaction (T) was made. 15) Method according to one or more of claims 10 to 14, characterized in that said review (R) comprises said customer identification key (IDc), said supplier identification key (IDF), said transaction identification key (IDT), a vote and a text field to contain the description of the review (R) itself. 16) Method according to one or more of claims 10 to 15, characterized in that it comprises at least a step of sending to said customer (C) a link to a web portal of said review management and control unit (2) ( R).