WO2016131108A1 - A system, server and client computing devices for recipient profile electronic feedback aggregation and automated recipient profile feedback sentiment analysis - Google Patents

Abstract

There is provided a server for recipient profile electronic feedback aggregation. The server is configured for serving a feedback submission interface for receiving feedback from a plurality of providers comprising an alphanumeric feedback profile ID input field configured for receiving a unique alphanumeric feedback profile ID, wherein, upon receipt of the unique alphanumeric feedback profile ID via the alphanumeric feedback profile ID input field, the server is configured for identifying at least one recipient profile. The server is then configured for receiving feedback for the at least one recipient profile via the feedback submission interface so as to be able to subsequently generate a recipient profile aggregated feedback data stream interface comprising a sequential display of the plurality of feedback data received in respect of the at least one recipient profile.

Description

A system, server and client computing devices for recipient profile electronic feedback aggregation and automated recipient profile feedback sentiment analysis

Field of the Invention

[1] The present invention relates in particular, but not necessarily entirely, to a system, server and client computing devices for recipient profile electronic feedback aggregation and automated recipient profile feedback sentiment analysis.

Summary of the Disclosure

[2] In the embodiment described herein, there is described a system, server and client computing devices for recipient profile electronic feedback aggregation and automated recipient profile feedback sentiment analysis.

[3] Specifically, there is described the aggregation of feedback in relation to a plurality of recipient profiles utilising unique alphanumeric recipient profile IDs. The recipient profile IDs are disseminated to feedback providers and the server is configured for providing a feedback submission interface so as to allow for the anonymous (that is without utilisation of sensitive recipient information such as email addresses and the like) provision of feedback utilising the recipient profile IDs. The recipient profiles may relate to any entities, such as individuals, companies and organisations, inanimate objects such as consumer products and the like. Furthermore feedback profiles may be hierarchical so as to allow, for example, for the aggregation of feedback from an organisation via the employees of the organisation.

[4] The server is further configured for generating a recipient profile aggregated feedback data stream interface comprising a stream of feedback received in relation to a particular profile.

[5] Furthermore, in embodiment, the server is configured for implementing artificial intelligence automated recipient profile feedback sentiment analysis so as to identify feedback sentiment in relation to feedback received in respect of recipient profiles.

[6] As such, with the foregoing in mind, according to one aspect, there is provided a server for recipient profile electronic feedback aggregation, the server comprising: a database comprising: a recipient profile table adapted to store recipient profile data representing at least one recipient profile the recipient profile data comprising: at least one searchable identifier parameter; and a unique alphanumeric recipient profile ID; and a feedback table adapted to store feedback data, the feedback data stored in relation to the recipient profile data; and a webserver configured for serving: a feedback submission interface for receiving feedback from a plurality of providers comprising: an alphanumeric feedback profile ID input field configured for receiving the unique alphanumeric feedback profile ID, wherein, upon receipt of the unique alphanumeric feedback profile ID via the alphanumeric feedback profile ID input field, the server is configured for identifying the at least one recipient profile; and a recipient profile search control comprising at least one searchable identifier parameter input field for receiving the at least one searchable identifier parameter, wherein upon receipt of at least one search string via the at least one searchable identifier parameter input field, the server is configured for displaying at least one matching recipient profile search results, each of the recipient profile search results being user selectable to select the at least one recipient profile from the at least one matching recipient profile search results; and a feedback input field configured for receiving feedback data in relation to the at least one recipient profile and wherein, in use, the server is configured for receiving, via the feedback input field, a plurality of feedback data and store the plurality of feedback data in relation to the at least one recipient profile; and a recipient profile aggregated feedback data stream interface, and wherein, in use, the server is configured for generating the feedback stream interface in relation to the at least one recipient profile by selecting, from the feedback table, the plurality of feedback data stored in relating to the at least one recipient profile and generating the feedback stream interface such that the feedback stream interface comprises a sequential display of the plurality of feedback data received in respect of the at least one recipient profile.

[7] The feedback input field may be a text input field and wherein the server may be further configured for calculating a feedback sentiment score in accordance with feedback text received via the text input field.

[8] Calculating the feedback sentiment may comprise sentiment phrase matching to identify phrases within the feedback text matching known sentiment phrases.

[9] Each of the known sentiment phrases may be assigned a negative or positive sentiment value.

[10] The known sentiment phrases assigned a negative sentiment value may comprise phrases including "rude", "slow" and "incorrect".

[11] The known sentiment phrases assigned a positive sentiment value may comprise phrases including "nice", "helpful", "fast", "greeted" and "great".

[12] Calculating the feedback sentiment further may comprise sentiment intensifier phrase matching to identify sentiment intensifier phrases within the feedback text matching known sentiment intensifier phrases.

[13] Each sentiment intensifier phrases may be assigned a sentiment multiplicative factor.

[14] The sentiment intensifier phrases may comprise phrases including "very", "always" and

"never".

[15] Calculating the feedback sentiment analysis may comprise multiplying the sentiment value and the sentiment a multiplicative factor. [16] The server may be further configured for calculating an aggregate recipient profile feedback sentiment score in relation to the at least one recipient profile in accordance with a plurality of text received in relation to the plurality of feedback in relation to the at least one recipient profile.

[17] The server may be further configured for calculating the aggregate recipient profile feedback sentiment score for a reporting period.

[18] The recipient profile table may be configured for storing a plurality recipient profile may be hierarchically and wherein, in use, the server may be further configured for calculating an aggregate parent recipient profile feedback sentiment score in accordance with a plurality of children aggregate recipient profile feedback sentiment score.

[19] Should the server detect a negative feedback sentiment score having a magnitude greater than the threshold, the server may be further configured for updating the feedback submission interface with provider instructional data.

[20] In use, the server may be configured for moderating the feedback in accordance with the feedback sentiment score.

[21] The web interface may be adapted to serve the feedback submission interface at a nominated

URL and identify the alphanumeric feedback profile ID from a URL GET parameter.

[22] At least one searchable identifier parameter may comprise at least one of first name and last name.

[23] The recipient profile search results comprise respective profile picture images of the at least one matching recipient profile to aid provider identification of the at least one recipient profile.

[24] The alphanumeric string may be case sensitive.

[25] The database further may comprise a provider profile table adapted to store provider profile data and wherein the server may be configured to prevent the receipt of feedback from a provider until the provider has created a provider profile.

[26] The server may be configured to send recipient response communication data to the provider in accordance with the provider profile data.

[27] The recipient profile aggregated feedback data stream interface may be configured to allow searching of the feedback data.

[28] Searching of the feedback data may comprise searching of the feedback data in accordance with the unique recipient profile ID.

[29] Searching of the feedback data may comprise searching of the feedback data in accordance with at least one of unique organisation ID, unique division ID and feedback data criteria.

[30] The feedback data criteria may comprise a feedback score threshold. [31] The feedback submission interface may be configurable in accordance with feedback template data representing a feedback template.

[32] The server may be further adapted to send a notification upon receipt of the feedback data.

[33] The server may be adapted to send social media platform update data to a social media platform upon receipt of the feedback.

[34] Other aspects of the invention are also disclosed.

Brief Description of the Drawings

[35] Notwithstanding any other forms which may fall within the scope of the present invention, preferred embodiments of the disclosure will now be described, by way of example only, with reference to the accompanying drawings in which:

[36] Figure 1 shows a system for recipient profile electronic feedback aggregation in accordance with embodiments of the present disclosure;

[37] Figure 2 shows an exemplary unique alphanumeric recipient profile ID and associated URL for the purposes of submitting electronic feedback for a recipient profile in accordance with embodiments of the present disclosure; and

[38] Figures 3 and 4 show an exemplary feedback submission interface in accordance with an embodiment of the present disclosure;

[39] Figure 5 shows an exemplary recipient profile aggregated feedback data stream interface in accordance with an embodiment of the present disclosure;

[40] Figure 6 shows an exemplary recipient profile review interface in accordance with an embodiment of the present disclosure; and

[41] Figure 7 shows exemplary artificial intelligence sentiment analysis on provided feedback in accordance with an embodiment of the present disclosure.

Description of Embodiments

[42] For the purposes of promoting an understanding of the principles in accordance with the disclosure, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Any alterations and further modifications of the inventive features illustrated herein, and any additional applications of the principles of the disclosure as illustrated herein, which would normally occur to one skilled in the relevant art and having possession of this disclosure, are to be considered within the scope of the disclosure.

[43] Before the structures, systems and associated methods relating to the system, server and client computing devices for recipient profile electronic feedback aggregation and automated recipient profile feedback sentiment analysis are disclosed and described, it is to be understood that this disclosure is not limited to the particular configurations and process steps disclosed herein as such may vary somewhat. It is also to be understood that the terminology employed herein is used for the purpose of describing particular embodiments only and is not intended to be limiting since the scope of the disclosure will be limited only by the claims and equivalents thereof.

[44] In describing and claiming the subject matter of the disclosure, the following terminology will be used in accordance with the definitions set out below.

[45] It must be noted that, as used in this specification and the appended claims, the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise.

[46] As used herein, the terms "comprising," "including," "containing," "characterised by," and grammatical equivalents thereof are inclusive or open-ended terms that do not exclude additional, unrecited elements or method steps.

[47] It should be noted in the following description that like or the same reference numerals in different embodiments denote the same or similar features.

A system for recipient profile electronic feedback aggregation and automated recipient profile feedback sentiment analysis

[48] Turning now to figure 1, there is shown a system 100 for recipient profile electronic feedback aggregation and automated recipient profile feedback sentiment analysis.

[49] As will be described below in further detail, the system 100 is adapted for aggregating electronic feedback from a plurality of feedback providers (referred to herein as "providers" for convenience) for at least one recipient of feedback (similarly referred to herein as a "recipient" for convenience).

[50] A recipient may be anything for which feedback may be received. In this regard, recipients include individuals, companies and organisations. Furthermore, recipients may include consumer products such as vehicles, household appliances and the like for which feedback may be provided by consumers.

[51] Furthermore, in embodiments, the system 100 is adapted for automating the analysis of feedback sentiment so as to, for example, identify whether provided feedback is positive or negative and the degree thereof.

[52] The system 100 may adapted for receiving electronic feedback through a number of mediums, such as the below mentioned web architecture by way of web server interface, email by way of SMTP interface, PSTN interface and the like.

[53] The system 100 is adapted for providing unique recipient profile IDs for the recipient users of the system 100 so as to be able to receive feedback from providers. [54] In this manner, the system 100 is adapted for allowing the provision of provider initiated feedback as opposed to conventional feedback requesting email campaigns, telephone surveys and the like. Furthermore, the system 100 allows for anonymous provision of feedback wherein confidential contact information (such as email addresses and the like) of recipients need not be provided to providers.

[55] Furthermore, the system 100, in embodiments, is configured for automating a sentiment analysis of feedback provided for recipients so as to be able to gauge automatically the sentiment (i.e. positive or negative) of feedback provided for recipient and the degree thereof.

[56] Specifically now, the system 100 comprises a server 105 for aggregating the electronic feedback. As will be described in further detail below, the server 105 is configured with various software modules for profile management, feedback management, credit and micropayment management and the like. Furthermore, the server 105 comprises a feedback profile database for storing user profile data and feedback data.

[57] Yet further, the server 105 exposes various interfaces for receiving electronic feedback data by the above-mentioned web, email and telephone mediums.

[58] In one embodiment, the server 105 provides cloud-based software-as-a-service, allowing organisations, entities and the like to aggregate electronic feedback in relation to their services, products and the like. This embodiment will be described herein with reference to the preferred embodiment.

[59] As such, in this embodiment, the server 105 may be operably coupled to a manager client computing device 175 across a network 155, such as the Internet. The manager client computing device 175 may be utilised by managers for the purposes of configuring organisation and branch accounts, user profiles, reviewing aggregated feedback and the like.

[60] Furthermore, the system 100 may comprise a provider client computing device 165 utilised by providers and providing feedback for recipients. The client computing device 165 may take on various embodiments such as personal client computing devices such as desktop PCs, mobile communication devices and the like.

[61] Yet further, the system 100 may comprise a recipient client computing device 170 similarly operably coupled to the server 105 across the network 155. The recipient client computing device 170 may be utilised by recipients in configuring respective recipient profiles, responding to providers and the like.

[62] It should be noted that the nomenclature of the client computing devices as used herein is for illustrative purposes only and no technical limitation should necessarily be imputed accordingly. Server for electronic feedback aggregation

[63] Considering specifically now the server 100, as can be seen in figure 1, the server 105 comprises a database 110. In the embodiments described herein, the database 110 is described as a relational database such as a SQL server database. However, it should be noted that other databases, file systems and the like may be utilised within the purposive scope of the embodiments described herein of storing profile data and feedback data.

[64] In this embodiment, the database 110 comprises a profile table 135. The profile table 135 is adapted for storing user profiles of various users, such as recipients, providers, managers and the like.

[65] As alluded to above, the profile table 135 may be configured for storing other types of recipients over and above individuals such as companies, organisations, consumer products and the like.

[66] Furthermore, in embodiment, the profile table 135 may store recipient profiles hierarchically such that, for example, employee recipient profiles may be stored in relation to the employer recipient profiles and the like. In this manner, for example, feedback may be received from the company and/or organisation via the employees thereof.

[67] In embodiments, separate tables may be provided for each of the recipients, providers and managers. However, the database 110 comprises at least a recipient profile table adapted to store recipient profile data representing at least one recipient profile.

[68] By way of exemplary embodiment, the recipient will be described hereafter as a bank teller by the name of George.

[69] Furthermore, the database 110 further at least comprises a feedback table 115 adapted to store feedback data. The feedback data is stored in relation to the recipient profile data. As will be described in further detail below, the feedback table 115 is adapted to store feedback data received from providers.

[70] The server 105 further comprises an interface 180 adapted to receive the feedback data. As will be described in further detail below, the interface 180 may be adapted to receive feedback by various mediums, such as by implementing a web interface 140, email interface 150 and/or telephone interface 145. It should be noted that other interfaces may be implemented by the interface 180 within the purposive scope of receiving feedback, such as by way of cellular text message interface and the like.

[71] The server 105 further comprises various software modules adapted for providing various functionality including that which is described herein. For example, the server 105 may comprise a profile module 120 adapted for allowing for the configuration of user profiles, such as the recipient profile, provider profile and the like. [72] Furthermore, the server 105 may comprise a feedback module 130 providing functionality allowing for the receipt of feedback, the storing of the feedback in relation to recipients, providing feedback search functionality and the like.

[73] Furthermore, the server 105 may comprise a payment module 125 adapted to manage credit and micropayments in relation to feedback provided by providers.

[74] Furthermore, the server 105 may comprise a sentiment artificial intelligence (Al) analysis module 185 configured for automating the detection of sentiment in relation to feedback received.

[75] As such, in use, the server 105 is controlled by computer program code to receive the recipient profile data (i.e. the exemplary user profile data relating to George, the bank teller) and store, in the recipient profile table 135 of the database 110 the recipient profile data.

[76] Now, for the purposes of receiving feedback, the server 105 generates a unique alphanumeric recipient profile ID for each recipient profile.

[77] In a preferred embodiment, the unique recipient profile ID is a user-friendly alphanumeric ID adapted for allowing the user friendly provision of feedback by providers to identify the intended recipient of the feedback. For example, the recipient profile ID assigned to George, the bank teller, may be "b7gEnQ". In this manner, George's customers, utilising the interface 180 may provide anonymous feedback from George utilising the provided recipient profile ID.

[78] As can be appreciated, the recipient profile ID may be provided in differing manners, such as, for example, via point of sale receipts, business cards, posters, subscriber websites all without the need for any disclosure of personal details of the provder or recipient of the feedback.

[79] As such, the server 105 is then able to receive, via the interface 180, the feedback data from a provider, the feedback data comprising the unique recipient profile ID and store, in the feedback table 115 of the database 110, the feedback data relation to the recipient profile data in accordance with the unique recipient profile ID.

Feedback submission interface

[80] As alluded to above, the interface 180 may receive the feedback data in different manners. In a first embodiment, the interface 180 provide a web interface by way of web server 140.

[81] In this embodiment, the server 105 implements a web server 140, such as the Apache Web server, the web server 140 adapted to serve HTTP requests at a particular URL resource, the resource adapted to receive the unique recipient profile ID.

[82] For example, the web server 140 may serve a web page at a particular URL, such as www.pay compliment.com. The web page may comprise an input field adapted to receive the unique recipient profile ID. In this manner, customers, clients and the like maybe invited to provide feedback at the particular URL and to use the unique recipient profile ID to associate the provided feedback with the particular recipient.

[83] In other embodiments, the interface 180 may be adapted to receive feedback via email. In this manner, the interface 180 may comprise an email server such as an SMTP server 150. In embodiments, the SMTP server 150 is configured in "catch all" configuration, so as to be able to receive emails wherein the email address represents the unique recipient profile ID. For example, the SMTP server 150 may be adapted to receive an email comprising the unique recipient profile ID such as, for example b7gEnQ@pavcompiiiTient.corr).

[84] In other embodiments, the interface 180 may implement a telephone interface such as a PBX interface 145 such as a PBX interface having a DTM F module so as to receive the unique recipient profile ID from touchtone telephones across the PSTN network 160. In this manner, providers may telephone a particular number and utilise their keypads to provide feedback, such as by using the keypad to input the unique recipient profile ID, and subsequently record a voice message representing their feedback. In embodiments, the server 105 may convert the voice message to text.

Profile data

[85] As alluded to above, the database 110 may comprise a profile table 135 adapted to store profile data relating to any one of the provider, recipient and manager uses of the system 100.

[86] For the recipient user profile, the recipient profile table 135 is adapted to store recipient profile data representing at least one recipient profile. Herein, the recipient profile data may comprise at least one searchable identifier parameter; and a unique alphanumeric recipient profile ID, such as:

• Unique recipient profile ID (system field); and

• At least one searchable identifier parameter comprising, for example:

a. First Name (mandatory)

b. Last Name (mandatory)

c. Position

d. Company

e. Search Tags

• Other information such as:

a. email (mandatory)

b. Mobile number

c. Profile Picture

• Configuration settings such as:

a. Show in Search Results when people search by name? Default unchecked (mandatory) b. Show in Search Results when people search by tags? Default unchecked (mandatory) c. SMS notification of feedback checkbox

d. Email notification of feedback checkbox

[87] As is evident from the above recipient profile data, the recipient profile data comprises the unique recipient profile ID such that, when receiving feedback via the interface 180, the server 105 is adapted to store the feedback data in relation to the relevant profile using the unique recipient profile ID.

[88] As alluded to above, the recipient profile data may comprise other information, such as first name, last name and the like. In this manner, providers may search for a particular recipient without necessarily having to use the unique recipient profile ID.

[89] As also alluded to above, the recipient profile data may comprise profile picture data allowing for recipients to browse photographs of recipients for visual recognition of particular recipients, especially advantageous where the name or the unique recipient profile ID may not be known to the provider.

[90] Yet further, the recipient may configure whether the recipient profile is to be shown when provide a search by name and/or by tags. For the latter, the recipient profile data may comprise various tags to facilitate searching, such as "branch manager", "technical support" and the like describing the recipient, for example.

[91] Furthermore, the recipient may configure their profile to receive SMS and email notifications upon receipt of feedback from providers.

Unique recipient profile I D

[92] In a preferred embodiment, the unique recipient profile ID is a user-friendly alphanumeric unique recipient profile ID which may be utilised by providers in a user-friendly manner and providing feedback. For example, the unique recipient profile ID may comprise the alphanumeric characters of b7gEnQ.

[93] As can be seen, the unique recipient profile ID is short and may be either memorised by the provider and/or input easily.

[94] In embodiments, the unique recipient profile ID may be case-sensitive.

[95] In another embodiment, other unique recipient profile IDs may be utilised other than alphanumeric strings within the purposive scope of the embodiments described herein.

[96] In embodiments, the system 100 allows for multiple recipient profile IDs under one membership with differing organisational ownership of each of these. This means a person may have several concurrent roles with different organisations, or many roles over time, each with a separate IDs but all of the IDs are associated to the same member's feedback stream (so effectively the system 100 acts as a feedback aggregator for all roles in this regard).

Provider table

[97] In embodiments, and as alluded to above, the database 110 may comprise a profile table 135 for providers. In this manner, when receiving feedback from providers, the server 105 may be adapted to store provider profile data within the provider profile table 135.

[98] As such, in this embodiment, the server 105 may be adapted to verify the provider profile data to prevent against abuse, spam and the like by requiring providers to create an account with the server 105 prior to their feedback being submitted.

[99] For example, the server 105 may require providers to provide an email address, and/or other contact information, such as a telephone number, first and last names and the like. The server 105 may be adapted not to transmit the providers of feedback until such time that the provider has verify their account, such as by verifying their email address.

[100] It should be noted that the system 105 may be adapted to keep the contact information of the provider anonymous to recipients and managers. In this manner, providers may provide feedback without fear of retribution.

Anonymous two-way communication

[101] In embodiments, the server 105 is adapted to allow anonymous two-way communication between the provider and the recipients. For example, upon receipt of feedback from a provider, the server 105 may be adapted to allow the recipient to respond to the provider.

[102] In this regard, the communication may be anonymous in that the confidential contact information (such as email address, mobile number and the like) of the recipient (or that of the provider) need not be disclosed.

[103] For example, for the above-mentioned embodiment where the provider profile table 135 comprises an email address of the provider, upon receipt of feedback data from the provider, the recipient, utilising the recipient client computing device 170 may input a response to the provider, such as a text comment or the like wherein, upon receipt of the response from the recipient, the server 105 is adapted to email the response to the provider such that the provider, utilising the provider client computing device 165 may receive the response.

Feedback searching

[104] In embodiments, the feedback module 130 is adapted to provide for feedback searching capabilities, especially for use by managers of recipients. [105] In this manner, managers may authenticate with the server 105 utilising the manager client computing device 175 so as to be able to retrieve feedback data in various formats.

[106] For example, managers may be adapted to retrieve feedback for a particular recipient, such as by inputting the unique recipient profile ID, or other identifying information. In embodiments, the server 105 may be adapted to summarise the feedback, such as by providing an average feedback score. In this manner, poor performing recipients may be identified by managers.

[107] In other embodiments, feedback may be searched utilising other search queries, such as across an organisation, divisions of organisations, for particular types of providers, particular types of feedback and the like.

Feedback data templates

[108] In embodiments, the feedback data may be provided by way of a template. For example, the server 105 may be configured with feedback template data comprising various feedback fields for population by the provider. For example, the feedback template data may comprise a text input field wherein the provider may input free form text. Other feedback fields may be utilised, such as rating scores, such as a star rating from 1 to 5.

[109] In embodiment, the manager or the recipient may configure the server 105 in accordance with the feedback fields that may be utilised by the provider when providing feedback.

[110] In embodiments, the system allows for users to define templates to structure feedback and to decide if these apply to the entire organisation, a workgroup (team) or set of workgroups, and if the templates are publicly visible or restricted to other members of the workgroup or team.

[Ill] In embodiments, feedback submission interface may comprise a plurality of provider selectable templates allowing the recipient to choose the appropriate input fields for the provision of feedback, such as one word of feedback, free-form text input, structured question format, star rating format and the like, including a combination of these.

Moderation

[112] In embodiments, the feedback model 130 is adapted to implement moderation. For example, in one embodiment, the feedback module 130 may be adapted to allow managers, utilising the manager client computing device 175 to moderate feedback, prior to the provision of the feedback to the recipient, such as to guard against abuse, sensitive feedback issues and the like.

[113] In embodiment, and as will be described in further detail below, the server 105 may be configured for automated sentiment analysis so as to be able to auto moderate wherein, for example, for feedback for which the server 105 has detected has been very negative, the server 105 may require managerial intervention prior to provision to the recipient or alternatively refusal of the receipt of the feedback from the provider or yet further or alternatively instructing the provider to change the language used.

[114] In a further embodiment, the server 180 may implement profanity filtering so as to either remove offending words, or to flag inappropriate feedback text accordingly.

Notifications

[115] In embodiments, the feedback model 130 is adapted to provide notifications upon receipt of feedback.

[116] As alluded to above, the manager or the recipient may configure whether to receive notifications by way of SMS, email and the like.

[117] In embodiments, notifications may be sent upon receipt of each item of feedback data. In other embodiments, notifications may be sent when other criteria is met, such as a feedback rating of a recipient falling beneath a certain threshold or exceeding a certain threshold.

[118] Such modifications may be sent to the relevant recipient and/or the relevant managers.

Manager feedback

[119] In embodiments, feedback module 130 is adapted to allow for the provision of management feedback, either to the recipient or to the provider.

[120] For the former, and for example, the feedback module 130 may be adapted to allow a manager to provide feedback to a recipient for a particular item of feedback data received from a provider. Such feedback may be kept confidential from the provider viewable to the recipient only. For example, the server 105 may be adapted to allow the manager, using the manager client computing device 175 to review various items of feedback data for a particular recipient. For selected feedback items, the manager may provide feedback, such as by way of helpful comments to address problems and the like.

[121] For the latter, and again for example, the feedback module 130 may be adapted to allow a manager to provide feedback directly to a provider of feedback.

Review Cycles

[122] In embodiments, feedback module 130 is adapted to allow a manager to provide feedback to a recipient over a schedule of recurring review cycles.

[123] For the former, and for example, the feedback module may create a review cycle for a defined schedule such as quarterly, six monthly or annually, and enforce the provision of feedback from a manager to a recipient at the conclusion of a given review cycle. [124] For the latter, the feedback module may allow draft feedback for a recipient to be saved by the manager during the review cycle, and for that feedback to be delivered to the recipient at the end of the review cycle.

[125] The feedback module may accept alternative events to trigger the delivery of scheduled manager feedback to a recipient, such as, but not limited to, the receipt of a file.

Credit/Micropayments

[126] In embodiments, the server 105 comprises a payment module 125 adapted to allocate credit and/or payments in relation to the provision of feedback.

[127] For example, in one embodiment, providers may be incentivised to provide feedback in exchange for credits or payments. For example, providers may be incentivised with a promise of the receipt of one credit for each item of feedback data provided. Such credits may be collected by providers for exchange for goods, services, or payment.

[128] In other embodiments, the provider of the feedback may in conjunction with providing feedback, assign units of credit and/or payments to the recipient. Such credits may be collected by recipients for exchange for goods, services, or payment.

Social media

[129] In embodiment, the server 105 may interface with various social media platforms, so as to push social media update notifications to various social media platforms.

[130] For example, the server 105 may provide star ratings to the Google+ feedback platform or alternatively provide notifications to a Facebook profile, such as a Facebook profile associated with an organisation associated with the server 105.

Artificial intelligence for automated sentiment analysis

[131] As alluded to above, the software modules may comprise a sentiment analysis module 185 for automating the analysis of sentiment of provided feedback. Specifically, the sentiment analysis module 185 may be able to identify whether provided sentiment is positive or negative and the degree thereof.

[132] Specifically, turning now to figure 7, there is shown an exemplary analysis of sentiment of provided feedback for various feedback items. The exemplary feedback provided in figures 7 is for a McDonald's fast food restaurant.

[133] For example, for the first feedback item, the provider has stated "On my regular trip from Virginia to Maryland, I have chosen to stop at the Mcdonald's Restaurant on St. Barnabas Rd. because of Travis's friendly, courteous greeting. He always remembers me and my regular order-and with a smile says, "I got your order." [134] Now, in embodiment, the sentiment analysis module 185 is configured for generating a summary of the feedback. For example, the sentiment analysis module 185, on the basis of the above provided exemplary feedback may summarise the feedback as follows "He always remembers me and my regular order-and with a smile says, "I got your order."". Summary generation may comprise removing known commonplace phrases or phrases comprising unrelated keywords. For example, for the portion of the sentence comprising "On my regular trip from Virginia to Maryland", the sentiment analysis model 185 may identify the words "trip", "Virginia" and "Maryland" and identify that this portion of the feedback does not relate to feedback per se for the McDonald's restaurant.

[135] Furthermore, the sentiment analysis model 185 may identify words that are pertinent for feedback when providing the summary such as identifying words such as "always", "my ... order" and the like so as to provide the above summary of "He always remembers me and my regular order".

[136] The sentiment analysis module 105 may utilise phrase matching analysis for the purposes of identifying phrase sentiment. For example, phrases such as "remembers", "fast", "full of energy" are allocated a positive phrase sentiment. Conversely, phrases such as "very rude" and "incorrect" are allocated a negative phrase sentiment. Furthermore, each phrase may be allocated a sentiment degree wherein, for example, "very rude" is allocated a phrase sentiment degree of -1 whereas the phrase "incorrect" is allocated a phrase sentiment of -0.8.

[137] Furthermore, phrase degree intensifiers may be utilised wherein phrases such as "very", "always" and the like each have a multiplicative factor used to intensify the sentiment. For example, the phrase "always" may intensify the phrase sentiment of -1 for the word "rude" by 1.5 such that the resultant phrase "always rude" results in a sentiment degree of -1.5.

[138] In embodiment, for the purposes of uniformity, the sentiment analysis module 185 may substitute portions of the phrase such as, for example, substituting a phrase such as "ladies room" with the word "bathroom".

[139] By analysing the sentiment degree, the sentiment analysis module 185 may be configured for calculating a recipient sentiment in accordance with the feedback provided for the recipient. For example, for the exemplary recipient Travis in figure 7, the sentiment analysis module 185 has allocated a positive recipient sentiment of 0.69.

[140] In embodiment, having calculated feedback sentiment for recipients, the server 105 may be configured for taking further action, such as notification of managers, such as for example, where a recipient receives very negative feedback.

[141] Furthermore, and as alluded to above, the server 105 may be configured for implemented moderation in accordance with sentiment wherein, for example, when receiving feedback via the feedback submission interface, should the server 105 detect very negative sentiment the server 105 may update the feedback submission interface to instruct the provider to moderate the language such as by utilising alternative language. In other embodiments, for very negative feedback, as opposed to providing the feedback directly to the recipient, the server 105 may be configured for directing the negative feedback to the recipient's manager for review and moderation if necessary prior to provision to the recipient.

[142] Conversely, for very positive calculated sentiment the server 105 may be configured for notifying the recipient's colleagues, managers and the like.

[143] In other embodiment, other artificial intelligence/machine learning techniques may be utilised for identifying aspects other than sentiment.

Profile indexation

[144] In embodiments, the server 180 may be configured for implementing profile indexation wherein various fields stored within the profile table 135 may be exposed by the web server 140 for crawling by search engines, such as Google and the like.

[145] In this manner, search engine searches may reveal various profile information such as first name and last name combinations of various recipients stored within the profile table 135 so as to allow Internet users to search by name and thereafter, by clicking on the search engine link so as to browse to a resource served by the web server 140, provide feedback for the recipient.

[146] Other information may be exposed by the web server 140, such as feedback ratings and the like in accordance with data retrieved from the feedback table 115.

Workflows

[147] The server 180 may be configured with feedback workflows allowing the specification of the flow of feedback to various users of the system. For example, a feedback workflow template may be created for George, the bank teller, wherein any feedback received is first sent via the server 182 George's manager for review and wherein, the manager may then elect whether to send the feedback to George or whether to send a communication back to the provider requesting clarification.

[148] For example, a customer of the bank may utilise George's unique alphanumeric recipient profile ID to provide feedback via the feedback submission interface. Thereafter, in accordance with the workflow, the feedback is provided to George's manager. In this regard, the web server 180 sends an email communication comprising a URL comprising a unique identifier or the like operable by the manager to view the feedback.

[149] The interface provided to the manager may allow the manager to decide to send the feedback to George or to request clarification from the customer. For the former, the feedback may appear in the recipient profile aggregated feedback data stream interface for George and/or be sent via email to George, the email comprising a unique URL pointing to the feedback.

[150] For the latter, the server 180 would send an email communication back to the customer comprising a unique URL wherein the customer may input further clarification information which is then sent back to the manager in the manner described above.

Exemplary embodiments

[151] Having described the above exemplary technical architecture and embodiment, there will now be described a specific exemplary embodiment for illustrative purposes with reference to the exemplary graphical user interfaces as substantially provided in figures 2 - 6. It should be noted that these embodiments are exemplary only and that no technical limitation should necessarily be imputed to the embodiments described herein accordingly.

[152] These exemplary embodiments will utilise the above-mentioned exemplary embodiment of the utilisation of the system 100 for receiving provider feedback for George, the bank teller.

[153] As such, in this embodiment, George's employee, such as George's manager would create an account of the server 105 so as to create a profile for the bank organisation including one or more recipient profiles including a recipient profile for George. Alternatively, George may create the user profile himself. The user profile would be created with the above recipient profile data, such as George's first and last name, profile picture and email address.

[154] Upon receipt of the profile data for George, the profile module 120 would create a unique recipient profile ID for George, being b7gEnQ.

[155] The unique recipient profile ID would then be provided by the server 105 for the purposes of notifying prospective providers. For example, referring to figure 2, there is shown a card 200 which may be placed upon George's desk inviting providers to provide feedback. As can be seen, the card 200 comprises the unique recipient profile ID for George and the URL which may be utilised by the provider for the purposes of providing feedback.

[156] As such, a client of the bank, having interacted with George may subsequently decide to leave feedback for George. In this example, the client was particularly happy with George's customer service. As such, the provider, utilising the provider client computing device 165 would browse to the resource as advertised by the card 200. Referring now to figure 3, there is shown the exemplary feedback submission interface 300 to display by the web browser application of the provider client computing device 165.

[157] The interface 300 is adapted to allow the provider to identify George so as to be able to subsequently provide feedback. As can be seen from the interface, the interface 300 comprises a unique recipient profile ID input field, shown as the "Pay Compliment ID" in the embodiment, wherein the provider may input the unique recipient profile ID shown on the card 200.

[158] Alternatively, and for embodiments where the provider is not in possession of the unique recipient profile ID, the interface 300 allows the provider to search for George, such as by searching by first name, last name, city, company, branch and the like. As can be seen, should more than one recipient profile match the search query, various candid results may be displayed including the profile picture so as to allow the provider to visually recognise the appropriate recipient.

[159] Having identified George using the interface 300, the feedback provision interface 400 as substantially shown in figure 4 is displayed by the provider client computing device 165. As can be seen, the interface comprises a summary of the George's profile data, such as George's profile picture.

[160] The interface 400 comprises two feedback input fields, comprising a free form text input text area and a star rating input. As such, utilising the interface, the provider input a comment about how great George's customer service was and rates George with five stars.

[161] In embodiment, the interface 400 may receive feedback in other manners, including other multimedia formats including by way of voice and/or video input.

[162] The provider inputs the text "George is always very rude" into the free form text input field. A substantial real time, the sentiment analysis module 185 detects a negative sentiment of -1.5 and therefore the feedback provision interface 400 updates to instruct the provider to utilise more appropriate language. Alternatively, the feedback provision interface 400 may request further information for clarification to substantiate the very negative feedback.

[163] Having input the feedback, the server 105 may prompt the provider to create an account including in creating a provider user profile comprising an email address for the provider so as to allow for the above-mentioned two-way communication.

[164] Upon receipt of the verification of the profile of the provider, the server 105 may notify both George and George's manager by way of email. The notification may comprise a time restricted one time link allowing George to view the comment without first authenticating with the server 105.

[165] George's able to view the comment and the star rating and respond to the provider with a thank you message. The server 105 is adapted to email George's response to the provider using the provider provided email address from the provider profile data stored within the provider profile table 135. George isn't able to see the email address or other contact information of the provider.

[166] Referring to figure 5, there is shown an exemplary recipient profile aggregated feedback data stream interface 500 comprising a feedback stream comprising various feedback items received from providers. The interface 500 comprises various feedback items received for George. [167] As can be seen from the interface 500, the feedback stream comprises feedback items, George's replies to the feedback items, and provider replies to replies.

[168] Turning now to figure 6, there is shown an exemplary interface 600 for utilisation by George's manager utilising the manager client computing device 175 for the purposes of reviewing George's performance.

[169] As can be seen from the interface 600, the manager is able to view the various feedback items received by George and provide review comments for George accordingly.

[170] Utilising the sentiment analysis module 185, the server 105 is able to calculate the aggregate feedback sentiment for George in accordance with the feedback received in the last 30 days. In this regard, the server 105 calculates that George has received positive sentiment of 0.7 which is an improvement of the previous positive sentiment of 0.5 received for the previous reporting period.

[171] Furthermore, the server 105 is configured for calculating the aggregate feedback sentiment for George's bank in accordance with the calculated feedback sentiment for the individual employees of the bank including George. Herein, the server 105 calculates that George's bank has received a positive sentiment of 0.2 which is down from the previous positive sentiment of 0.4 for the previous reporting period.

I nterpretation

Wireless:

[173] The invention may be embodied using devices conforming to other network standards and for other applications, including, for example other WLAN standards and other wireless standards. Applications that can be accommodated include IEEE 802.11 wireless LANs and links, and wireless Ethernet.

[174] In the context of this document, the term "wireless" and its derivatives may be used to describe circuits, devices, systems, methods, techniques, communications channels, etc., that may communicate data through the use of modulated electromagnetic radiation through a non-solid medium. The term does not imply that the associated devices do not contain any wires, although in some embodiments they might not. In the context of this document, the term "wired" and its derivatives may be used to describe circuits, devices, systems, methods, techniques, communications channels, etc., that may communicate data through the use of modulated electromagnetic radiation through a solid medium. The term does not imply that the associated devices are coupled by electrically conductive wires.

Processes:

[175] Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions utilizing terms such as "processing", "computing", "calculating", "determining", "analysing" or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities into other data similarly represented as physical quantities.

Processor:

[176] In a similar manner, the term "processor" may refer to any device or portion of a device that processes electronic data, e.g., from registers and/or memory to transform that electronic data into other electronic data that, e.g., may be stored in registers and/or memory. A "computer" or a "computing device" or a "computing machine" or a "computing platform" may include one or more processors.

[177] The methodologies described herein are, in one embodiment, performable by one or more processors that accept computer-readable (also called machine-readable) code containing a set of instructions that when executed by one or more of the processors carry out at least one of the methods described herein. Any processor capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken are included. Thus, one example is a typical processing system that includes one or more processors. The processing system further may include a memory subsystem including main RAM and/or a static RAM, and/or ROM.

Computer-Readable Medium :

[178] Furthermore, a computer-readable carrier medium may form, or be included in a computer program product. A computer program product can be stored on a computer usable carrier medium, the computer program product comprising a computer readable program means for causing a processor to perform a method as described herein.

Networked or Multiple Processors:

[179] In alternative embodiments, the one or more processors operate as a standalone device or may be connected, e.g., networked to other processor(s), in a networked deployment, the one or more processors may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer or distributed network environment. The one or more processors may form a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.

[180] Note that while some diagram(s) only show(s) a single processor and a single memory that carries the computer-readable code, those in the art will understand that many of the components described above are included, but not explicitly shown or described in order not to obscure the inventive aspect. For example, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

Additional Embodiments:

[181] Thus, one embodiment of each of the methods described herein is in the form of a computer- readable carrier medium carrying a set of instructions, e.g., a computer program that are for execution on one or more processors. Thus, as will be appreciated by those skilled in the art, embodiments of the present invention may be embodied as a method, an apparatus such as a special purpose apparatus, an apparatus such as a data processing system, or a computer-readable carrier medium. The computer-readable carrier medium carries computer readable code including a set of instructions that when executed on one or more processors cause a processor or processors to implement a method. Accordingly, aspects of the present invention may take the form of a method, an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of carrier medium (e.g., a computer program product on a computer-readable storage medium) carrying computer-readable program code embodied in the medium.

Carrier Medium :

[182] The software may further be transmitted or received over a network via a network interface device. While the carrier medium is shown in an example embodiment to be a single medium, the term "carrier medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term "carrier medium" shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by one or more of the processors and that cause the one or more processors to perform any one or more of the methodologies of the present invention. A carrier medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media.

Implementation :

[183] It will be understood that the steps of methods discussed are performed in one embodiment by an appropriate processor (or processors) of a processing (i.e., computer) system executing instructions (computer-readable code) stored in storage. It will also be understood that the invention is not limited to any particular implementation or programming technique and that the invention may be implemented using any appropriate techniques for implementing the functionality described herein. The invention is not limited to any particular programming language or operating system.

Means For Carrying out a Method or Function

[184] Furthermore, some of the embodiments are described herein as a method or combination of elements of a method that can be implemented by a processor of a processor device, computer system, or by other means of carrying out the function. Thus, a processor with the necessary instructions for carrying out such a method or element of a method forms a means for carrying out the method or element of a method. Furthermore, an element described herein of an apparatus embodiment is an example of a means for carrying out the function performed by the element for the purpose of carrying out the invention.

Connected

[185] Similarly, it is to be noticed that the term connected, when used in the claims, should not be interpreted as being limitative to direct connections only. Thus, the scope of the expression a device A connected to a device B should not be limited to devices or systems wherein an output of device A is directly connected to an input of device B. It means that there exists a path between an output of A and an input of B which may be a path including other devices or means. "Connected" may mean that two or more elements are either in direct physical or electrical contact, or that two or more elements are not in direct contact with each other but yet still co-operate or interact with each other.

Embodiments:

[186] Reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner, as would be apparent to one of ordinary skill in the art from this disclosure, in one or more embodiments.

[187] Similarly it should be appreciated that in the above description of example embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description of Specific Embodiments are hereby expressly incorporated into this Detailed Description of Specific Embodiments, with each claim standing on its own as a separate embodiment of this invention.

[188] Furthermore, while some embodiments described herein include some but not other features included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention, and form different embodiments, as would be understood by those in the art. For example, in the following claims, any of the claimed embodiments can be used in any combination.

Different Instances of Objects

[189] As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third", etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

Specific Details

[190] In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Terminology

[191] In describing the preferred embodiment of the invention illustrated in the drawings, specific terminology will be resorted to for the sake of clarity. However, the invention is not intended to be limited to the specific terms so selected, and it is to be understood that each specific term includes all technical equivalents which operate in a similar manner to accomplish a similar technical purpose. Terms such as "forward", "rearward", "radially", "peripherally", "upwardly", "downwardly", and the like are used as words of convenience to provide reference points and are not to be construed as limiting terms.

Comprising and Including

[192] In the claims which follow and in the preceding description of the invention, except where the context requires otherwise due to express language or necessary implication, the word "comprise" or variations such as "comprises" or "comprising" are used in an inclusive sense, i.e. to specify the presence of the stated features but not to preclude the presence or addition of further features in various embodiments of the invention.

[193] Any one of the terms: including or which includes or that includes as used herein is also an open term that also means including at least the elements/features that follow the term, but not excluding others. Thus, including is synonymous with and means comprising.

Scope of Invention

[194] Thus, while there has been described what are believed to be the preferred embodiments of the invention, those skilled in the art will recognize that other and further modifications may be made thereto without departing from the spirit of the invention, and it is intended to claim all such changes and modifications as fall within the scope of the invention. For example, any formulas given above are merely representative of procedures that may be used. Functionality may be added or deleted from the block diagrams and operations may be interchanged among functional blocks. Steps may be added or deleted to methods described within the scope of the present invention.

[195] Although the invention has been described with reference to specific examples, it will be appreciated by those skilled in the art that the invention may be embodied in many other forms.

Claims

Claims

1. A server for recipient profile electronic feedback aggregation, the server comprising:

a database comprising:

a recipient profile table adapted to store recipient profile data representing at least one recipient profile the recipient profile data comprising:

at least one searchable identifier parameter; and

a unique alphanumeric recipient profile ID; and

a feedback table adapted to store feedback data, the feedback data stored in relation to the recipient profile data; and

a webserver configured for serving:

a feedback submission interface for receiving feedback from a plurality of providers comprising:

an alphanumeric feedback profile ID input field configured for receiving the unique alphanumeric feedback profile ID, wherein, upon receipt of the unique alphanumeric feedback profile ID via the alphanumeric feedback profile ID input field, the server is configured for identifying the at least one recipient profile; and

a recipient profile search control comprising at least one searchable identifier parameter input field for receiving the at least one searchable identifier parameter, wherein upon receipt of at least one search string via the at least one searchable identifier parameter input field, the server is configured for displaying at least one matching recipient profile search results, each of the recipient profile search results being user selectable to select the at least one recipient profile from the at least one matching recipient profile search results; and

a feedback input field configured for receiving feedback data in relation to the at least one recipient profile and wherein, in use, the server is configured for receiving, via the feedback input field, a plurality of feedback data and store the plurality of feedback data in relation to the at least one recipient profile; and

a recipient profile aggregated feedback data stream interface, and wherein, in use, the server is configured for generating the feedback stream interface in relation to the at least one recipient profile by selecting, from the feedback table, the plurality of feedback data stored in relating to the at least one recipient profile and generating the feedback stream interface such that the feedback stream interface comprises a sequential display of the plurality of feedback data received in respect of the at least one recipient profile.

2. A server as claimed in claim 1, wherein the feedback input field is a text input field and wherein the server is further configured for calculating a feedback sentiment score in accordance with feedback text received via the text input field.

3. A server as claimed in claim 2, wherein calculating the feedback sentiment comprises sentiment phrase matching to identify phrases within the feedback text matching known sentiment phrases.

4. A server as claimed in claim 3, wherein each of the known sentiment phrases is assigned a negative or positive sentiment value.

5. A server as claimed in claim 4, wherein the known sentiment phrases assigned a negative sentiment value comprises phrases including "rude", "slow" and "incorrect".

6. A server as claimed in claim 4, wherein the known sentiment phrases assigned a positive sentiment value comprises phrases including "nice", "helpful", "fast", "greeted" and "great".

7. A server as claimed in claim 4, wherein calculating the feedback sentiment further comprises sentiment intensifier phrase matching to identify sentiment intensifier phrases within the feedback text matching known sentiment intensifier phrases.

8. A server as claimed in claim 7, wherein each sentiment intensifier phrases is assigned a sentiment multiplicative factor.

9. A server as claimed in claim 8, wherein the sentiment intensifier phrases comprises phrases including "very", "always" and "never".

10. A server as claimed in claim 8, wherein calculating the feedback sentiment analysis comprises multiplying the sentiment value and the sentiment a multiplicative factor.

11. A server as claimed in claim 8, wherein the server is further configured for calculating an aggregate recipient profile feedback sentiment score in relation to the at least one recipient profile in accordance with a plurality of text received in relation to the plurality of feedback in relation to the at least one recipient profile.

12. A server as claimed in claim 11, wherein the server is further configured for calculating the aggregate recipient profile feedback sentiment score for a reporting period.

13. A server as claimed in claim 8, wherein the recipient profile table is configured for storing a plurality recipient profile is hierarchically and wherein, in use, the server is further configured for calculating an aggregate parent recipient profile feedback sentiment score in accordance with a plurality of children aggregate recipient profile feedback sentiment score.

14. A server as claimed in claim 8, wherein, should the server detect a negative feedback sentiment score having a magnitude greater than the threshold, the server is further configured for updating the feedback submission interface with provider instructional data.

15. A server as claimed in claim 8, wherein, in use, the server is configured for moderating the feedback in accordance with the feedback sentiment score.

16. A server as claimed in claim 1, wherein the web interface is adapted to serve the feedback submission interface at a nominated URL and identify the alphanumeric feedback profile ID from a URL GET parameter.

17. A server as claimed in claim 1, wherein at least one searchable identifier parameter comprises at least one of first name and last name.

18. A server as claimed in claim 1, wherein the recipient profile search results comprise respective profile picture images of the at least one matching recipient profile to aid provider identification of the at least one recipient profile.

19. A server as claimed in claim 1, wherein the alphanumeric string is case sensitive.

20. A server as claimed in claim 1, wherein the database further comprises a provider profile table adapted to store provider profile data and wherein the server is configured to prevent the receipt of feedback from a provider until the provider has created a provider profile.

21. A server as claimed in claim 20, wherein the server is configured to send recipient response communication data to the provider in accordance with the provider profile data.

22. A server as claimed in claim 1, wherein the recipient profile aggregated feedback data stream interface is configured to allow searching of the feedback data.

23. A server as claimed in claim 22, wherein searching of the feedback data comprises searching of the feedback data in accordance with the unique recipient profile ID.

24. A server as claimed in claim 22, wherein searching of the feedback data comprises searching of the feedback data in accordance with at least one of unique organisation ID, unique division ID and feedback data criteria.

25. A server as claimed in claim 24, wherein the feedback data criteria comprises a feedback score threshold.

26. A server as claimed in claim 1, wherein the feedback submission interface is configurable in accordance with feedback template data representing a feedback template.

27. A server as claimed in claim 1, wherein the server is further adapted to send a notification upon receipt of the feedback data.

28. A server as claimed in claim 1, wherein the server is adapted to send social media platform update data to a social media platform upon receipt of the feedback.