REAL ESTATE BUYER THIRD PARTY FEEDBACK APPLICATION

BACKGROUND

The present disclosure relates generally to a real estate buyer feedback system, and more particularly, to a system and method for obtaining feedback from third parties.

During the property buying process, prospective buyers often consult with third parties (e.g., family and friends) to assist in their decision making. Currently, prospective buyers may often share a link to an online property listing for their family and friends to view, but there is presently no effective solution to tracking their response.

SUMMARY

A method for providing third party feedback associated with a real estate property, according to one disclosed non-limiting embodiment of the present disclosure can include receiving buyer feedback regarding a real estate property from a real estate feedback application; receiving third party feedback based on the buyer feedback from a third party feedback application; and communicating the third party feedback to the real estate feedback application.

A further embodiment of the present disclosure may include, wherein the third party feedback application is a module of the real estate feedback application.

A further embodiment of the present disclosure may include, wherein the third party is a trusted advisor.

A further embodiment of the present disclosure may include, wherein the third party becomes the trusted advisor in response to the third party feedback being within a predetermined range of the buyer feedback.

A further embodiment of the present disclosure may include, wherein the receiving buyer feedback includes receiving the buyer feedback specific to particular rooms of the real estate property.

A further embodiment of the present disclosure may include displaying the buyer feedback and the third party feedback as a scale rating on the third party feedback application.

A further embodiment of the present disclosure may include displaying the scale rating as at least one of numeric, emoji based, and color coded.

A further embodiment of the present disclosure may include, wherein the scale rating is specific to each room of the real estate property.

A further embodiment of the present disclosure may include aggregating the third party feedback from a multiple of third parties prior to communicating an aggregated third party feedback to the real estate feedback application.

A further embodiment of the present disclosure may include averaging the third party feedback from a multiple of third parties prior to communicating an averaged third party feedback to the real estate feedback application.

A further embodiment of the present disclosure may include aggregating the third party feedback from a multiple of third parties with the buyer feedback prior to communicating an aggregated feedback to the real estate feedback application.

A further embodiment of the present disclosure may include, wherein the receiving the third party feedback regarding the real estate property from the real estate feedback application includes receiving the third party feedback from a handheld device.

A further embodiment of the present disclosure may include receiving the third party feedback at a listing recommendation server hosting an analytics software application that compiles the feedback from the buyer and third party feedback.

A system for aggregating third party feedback associated with a real estate property, according to one disclosed non-limiting embodiment of the present disclosure can include a buyer server hosting a buyer application program interface; a buyer storage system in communication with the buyer server, the buyer storage system including a database that stores buyer feedback regarding a real estate property; and a listing recommendation server hosting an analytics software application that compiles the buyer feedback and third party feedback based on the buyer feedback.

A further embodiment of the present disclosure may include, wherein the analytics software application compiles the feedback from a multiple of third parties.

A further embodiment of the present disclosure may include, wherein the analytics software application averages the feedback from a multiple of third parties.

A further embodiment of the present disclosure may include, wherein the analytics software application averages the feedback from the multiple of third parties with the feedback from the buyer.

A further embodiment of the present disclosure may include a handheld device running a real estate feedback application, the real estate feedback application in communication with the buyer application program interface.

A further embodiment of the present disclosure may include, wherein the handheld device running the real estate feedback application, displays an aggregate of third party feedback.

A further embodiment of the present disclosure may include a handheld device running a third party feedback application, the third party feedback application in communication with the real estate feedback application.

The foregoing features and elements may be combined in various combinations without exclusivity, unless expressly indicated otherwise. These features and elements as well as the operation thereof will become more apparent in light of the following description and the accompanying drawings. It should be understood, however, the following description and drawings are intended to be exemplary in nature and non-limiting.

BRIEF DESCRIPTION OF THE DRAWINGS

Various features will become apparent to those skilled in the art from the following detailed description of the disclosed non-limiting embodiment. The drawings that accompany the detailed description can be briefly described as follows:

FIG. 1 is a general schematic system diagram of a real estate feedback application system.

FIG. 2 is a schematic diagram of a handheld device.

FIG. 3 is a flowchart of a method to provide feedback for real estate, with the system of FIG. 1.

FIG. 4 is a screenshot of the real estate feedback application property listing view.

FIG. 5 is a screenshot of the real estate feedback application feedback view.

FIG. 6 is a schematic diagram of a system to provide feedback for real estate which is a portion of the system of FIG. 1.

FIG. 7 is a flowchart to provide feedback from a buyer's handheld device.

FIG. 8 is a schematic block diagram of feedback provided from a buyer's handheld device to a seller.

FIG. 9 is a flowchart illustrating operation of the third party real estate feedback application.

FIG. 10 is a schematic diagram of a portion of a third party real estate feedback application system.

FIG. 11 is a screenshot of the real estate feedback application feedback view.

DETAILED DESCRIPTION

FIG. 1 schematically illustrates a system 10 to facilitate communication for real estate transactions. A property buyer “B” is typically represented by a showing agent “R” while a property seller “S” is typically represented by a listing agent “L.” The listing agent “L” communicates with the buyer “B” only indirectly, such as by communication with the showing agent “R” who then communicates information with the buyer “B.” Although only particular agents are referred to in the illustrated embodiments, the functions of such personnel may be otherwise assigned or rearranged. For example, the listing agent “L” may be a senior person in an agency who utilize a seller's assistant. The showing agent “R” may similarly utilize a showing assistant. As is discussed below, the prospective buyer “B” may wish to obtain input from third parties “T” such as family, friends, and/or others.

The system 10 generally includes a subsystem 12 that may be controlled by a single owner. The subsystem 12 generally includes a listing recommendation server 14, a buyer server 16, a buyer storage system 18, a log storage system 20, and an electronic key server 22. The listing recommendation server 14 communicates with the buyer storage system 18, the log storage system 20, and a storage system 24. The buyer storage system 18 includes a database 19 that stores, for example, feedback created by the buyer “B” (e.g., buyer feedback, third party feedback, etc.). The log storage system 20 includes a database 21 that collects activity data associated with the property showings.

The storage system 24 may include, but not be limited to, a database for managing key holders 25A, a security database 25B that hosts security protocols, and a listing database 25C that stores extracted property data from external databases 26A, 26B, 26N. The storage system 24 communicates with the external databases 26A-26N such as the Real Estate Transaction Standard (RETS) framework that stores MLS data. Communication between the various servers may include internet protocols or the like. The MLS data may include information such as number of bedrooms, number of bathrooms, price of listing, etc. RETS is a framework that can be adopted by computer systems to receive data from the Multiple Listing Service (MLS) servers, as well as those of other real estate systems provided they also have software installed designed to communicate using the RETS framework. The national association of realtors refers to RETS as a “common language.”

A multiple of handheld devices 28, 30, 32, may communicate with the subsystem 12. For example, the handheld devices 28, 30, 32, may be a smartphone, tablet, or other mobile device of the respective individual. Handheld device 28 is used by the potential buyer “B,” handheld device 30 is used by the showing agent “R,” and handheld device 32 is used by the listing agent “L. Various other handheld devices such as those used by the third parties “T” may also be in communication with the subsystem 12 either directly or through communication with the handheld devices 28, 30, 32, as an intermediary.

Information is accessible by the listing agent “L” through the subsystem 12 so that the listing agent “L” can, for example, generate reports for their seller “S,” send updates about a particular listing to showing agents “R”, or provide feedback from a buyer “B” to their seller “S.” The subsystem 12 may also obtain information from a Real Estate Transaction Standard (RETS) framework that stores MLS data. The subsystem 12 may also obtain information generated by an electronic key box 50 that occurs as a consequence of the showing, such as number of times shown, time spent at the subject property for each showing, return showings, etc. The subsystem 12 may also be used by the listing agents “L” to receive automatic notification (e.g., email notices) when a showing occurs at their listings. The subsystem 12 may also be used by the buyer “B” as a repository for information (e.g., details of each property the buyer has viewed, feedback on the properties, etc.). The seller “S” can also receive feedback from the buyer “B” either directly from the subsystem 12, or through communications with the listing agent “L” who communicates with the subsystem 12.

The listing recommendation server 14 hosts, for example, at least an analytics software application 32 that compiles and runs analytics against buyer ratings and MLS listing data from the storage system 24. The buyer server 16 hosts a buyer application program interface (API) 34, and the electronic key server 22 hosts an electronic key API 36. An application program interface (API) may include a set of routines, protocols, and/or tools for building software applications. The API specifies how software components should interact. APIs are used when programming graphical user interface (GUI) components. A server-side web API is a programmatic interface with one or more publicly exposed endpoints to a defined request-response message system.

The listing recommendation server 14 may communicate with a real estate application 38 on the handheld device 28 through the buyer API 34. An agent application 40 on the handheld device 30 may communicate with the listing recommendation server 14 and the electronic key server 22. The buyer API 34 and the electronic key API 36 may also communicate with other external systems through a firewall “F.”

The real estate application 38 may be a mobile application on the handheld device 28 that may be used by the buyer “B” to rate the properties they have seen and, as will be further described below, receive third party feedback from third parties “T” based on the buyer “B” feedback. The real estate application 38 communicates with the buyer storage system 18 through the buyer API 34 which then stores the feedback, ratings, and notes taken by the property buyer in the database 19 of the buyer storage system 18.

The agent application 40 may be a mobile application on the handheld device 30 that may be used by the showing agent “R” to access the electronic key boxes 50 via a short distance communication standard (e.g., Bluetooth). Alternatively, or in addition, the electronic key boxes 50 may be connected (e.g., cellular) directly to the listing recommendation server 14. The electronic key API 36 of the electronic key server 22 communicates with the agent application 40 to sync activity information from the electronic key boxes 50 to the electronic key API 36 (e.g., accessed key boxes, update the count of proprietary keys generated for that particular property, create a timestamp indicating that lockbox is opened), and showing notifications (e.g., to an associated showing agent “R”).

With reference to FIG. 2, each handheld device 28, 30, 32, generally includes a handheld device antenna 60, a handheld device transceiver 62, a handheld device processor 64, a handheld device memory 66, a GPS module 68, an input device 70, a display 72, and a handheld device power supply 74. The handheld device processor 64 may be any type of microprocessor having desired performance characteristics. The handheld device memory 66 may include any type of computer readable medium that stores the data and executable instructions described herein below. The executable instructions may be stored or organized in any manner and at any level of abstraction, such as in connection with one or more applications, processes, routines, procedures, methods, etc. The handheld device transceiver 62 is a transceiver of a type corresponding to the transceiver 62 and the handheld device antenna 60 is a corresponding antenna.

With reference to FIG. 3, a method 200 for operation of the system 10 is disclosed in terms of functional block diagrams. The functions are programmed software routines capable of execution in various microprocessor based electronics control embodiments and represented herein as block diagrams.

Initially, the owner of the subsystem 12 may have agreements with MLS to selectively extract (202) data such as MLS data from the external data servers 26A-26N (FIG. 1) through the listing recommendation server 14. Next, the agent application 40 syncs (204) with the listing recommendation server 14 and pulls MLS data for desired property listings of interest to the buyer “B” as, for example, selected by the showing agent “R.” This may be performed through an automated sync through the agent application 40. The showing agent “R” may also perform a manual sync to obtain the MLS data.

Through the agent application 40, the showing agent “R” can then authorize (206) the property buyer “B” to access the desired property listings of interest to the buyer “B.” Through the agent application 40, the showing agent “R” may, for example, authorizes the buyer “B” through input of buyer identification information (e.g., buyer name and email address.) The buyer identification information is then communicated to the listing recommendation server 14 so that the listing recommendation server 14 communicates the buyer “B” (e.g., via email to provide a link to an app store) with a code to unlock (208) the real estate application 38. The buyer “B” is then authorized to download the real estate application 38 and the desired property listings of interest to the buyer “B,” to maintain the value of the showing agent “R” in the real estate transaction. Alternatively, the buyer “B” already has the real estate application 38 and the desired property listings of interest to the buyer “B” are readily received.

Through the agent application 40, the showing agent “R” can continue to push (210) property listings to the real estate application 38. Access may be provided for one or more properties by a showing code, or other information that unlocks one or more modules in the real estate application 38. The modules may include features or other aspects that are particular tailored to certain parties in the real estate transaction. The showing agent “R” is able to selectively push the desired property listings of interest to the buyer “B” (one example property listing illustrated by screenshot “P”; FIG. 4) through the subsystem 12 to be viewable within the real estate application 38. The showing agent “R” also uses the agent application 40 to operate the electronic key box 50 to access the property for showing to the buyer “B.”

Next, during the showing, feedback is entered into the real estate feedback application 500 by the buyer “B” for the property (216; FIG. 5 and FIG. 6) as further discussed below. The feedback may include any data associated with the properties that may, for example, facilitate reviewing and comparing properties. The real estate feedback application 500 may be a module of the real estate application 38, and/or other application.

In addition to the features discussed above, the buyer “B” can utilize the real estate feedback application 500 to record feedback for each property visited. In one or more embodiments, the buyer “B” can take pictures, videos, and/or notes during the property showing. In one or more embodiments, the feedback may be provided as a scale rating (FIG. 5). For example, the scale rating may be numeric 300 (e.g., 1-10), emoji based 302 (e.g., happy face, sad face), color coded (e.g., red, yellow, green), or other such ranking. Further, the rating may be specific to particular areas of the property, (e.g., backyard, kitchen, etc.) and/or features, (e.g., appliances, fixtures, etc.). In one or more embodiments, the buyer “B” is prompted for feedback. In one or more embodiments, the buyer is prompted for feedback based on the location of the buyer within the property (e.g., via global positioning of the buyer within the property by way of the GPS module 68 (FIG. 2)) such that when the buyer enters, for example, the kitchen, the real estate feedback application 500 prompts the buyer for feedback on the kitchen, etc. In one or more embodiments, the buyer can add a category 304 to provide feedback thereon (e.g., garage).

The feedback is then saved in memory 66 (FIG. 2) via the real estate feedback application 500 so that the buyer can review at a later time (218). The feedback can also be used to compare properties reviewed by the buyer. As the buyer generates feedback about the property, the real estate feedback application 500 may also upload the feedback to the buyer storage system 18 via the buyer API 34 (220; FIG. 1). Once the showing is complete, the buyer “B” can choose to selectively share the feedback with their showing agent “R” via the real estate feedback application 500 which, in response, authorizes the listing recommendation server 14 to release the feedback from the buyer storage system 18. The agent application 40 then syncs with the listing recommendation server 14 and downloads the feedback (222). The showing agent “R” is then able to review the feedback on the agent application 40.

Through the agent application 40, the showing agent “R” can communicate the feedback to the listing agent “L” (224). In one or more embodiments, the feedback may be forwarded through an email app, text messaging app, social media, or other app on the handheld device 30, and need not be through the subsystem 12. For example, an email app resident on the handheld device 30 is called by the agent application 40, and the feedback is automatically copied into the email by the agent application 40. The showing agent “R” may then edit the email prior to sending the feedback to the listing agent “S.”

With reference to FIG. 7, a method 600 for providing feedback via the real estate feedback application 500 from the perspective of the buyer “B” is disclosed in terms of functional block diagrams. The functions are programmed software routines and executable instructions capable of execution in various microprocessor based electronics control embodiments and represented herein as block diagrams.

Initially, the buyer “B” downloads (602) the real estate feedback application 500 from a source such as an app store. The real estate feedback application 500 communicates (604) with the listing recommendation server 14 via the buyer API 34 to pull the agent selected MLS listings. The showing agent “R” then typically escorts the buyer “B” for a showing of particular properties selected by the buyer (606). Next, during the showing, the buyer “B” enters (608; FIG. 5) the feedback into the real estate feedback application 500. The real estate feedback application 500 then saves the feedback for retrieval at a later time (610). The buyer “B” can then utilize the real estate feedback application 500 to review the feedback and compare notes on the properties.

Once the showing is complete, the buyer can choose to share the ratings with their showing agent “R” (612). If they so choose, the real estate feedback application 500 will send a message to the listing recommendation server 14 though the buyer API 20 to release the ratings to the showing agent “R.” The feedback may be provided to the listing agent “L” through the subsystem 12. In this embodiment, the real estate feedback application 500 uploads the feedback data from the buyer database 18 to the electronic key server 22 via the buyer API 34 which then generates a report for the listing agent “L” (FIG. 8). The feedback report may include, but is not limited to, the buyer's feedback on the subject property, the buyer's feedback on the subject property compared to other properties, the buyer's interest in the subject property compared to other buyers' interest in the subject property by other buyers, other properties which may be comparable to the subject property based on the buyer's feedback, etc.

With reference to FIG. 9, a method 800 for the third party “T” to provide feedback via a third party feedback application 700 is disclosed in terms of functional block diagrams. The functions are programmed software routines and executable instructions capable of execution in various microprocessor based electronics control embodiments and represented herein as block diagrams. The third party feedback application 700 may be an application separate from, or integrated with, the real estate feedback application 500, a module of the real estate application 38, and/or other application, web interface, and/or social media interface. The third parties can, through the third party feedback application 700, provide their feedback on the feedback initially provided by the buyer “B.”

The third party feedback application 700 communicates with the subsystem 12 either directly (e.g., through the Internet) and/or using the real estate feedback application 500 resident on the handheld device 28 of the buyer “B” as the intermediary.

Initially, the buyer “B” may determine feedback (802) as described above (FIG. 7). Next, the buyer “B” may invite (804) desired third parties “T” to provide feedback via the third party feedback application 700 (FIG. 10).

In one or more embodiments, the real estate feedback application 500 may be configured to access a contact list 702 on the handheld device 28 (FIG. 10) of the buyer “B” to permit selection of particular third parties “T” (e.g., X, Y, Z) to whom a third party feedback request from the real estate feedback application 500 is to be sent (806). In one or more embodiments, these third parties “T” may be unknown to the buyer “B” and provide crowd source type feedback. For example, the feedback of the buyer “B” may be posted or otherwise distributed to the third parties “T” such as property improvement show watchers, social media applications, select individuals who access a website, or other group of individuals who are interested in providing their feedback on the subject property but may not actually know the prospective buyer “B.” In one or more embodiments, the real estate feedback application 500 may provide the third party feedback request through social media, text messaging, a pop-up in the third party feedback application 700 or though another notification scheme. In one or more embodiments, the third party “T” can be become a trusted advisors where a history of scores within a narrow range of the buyer's scores on a property will elevate the third party “T” to that status. The buyer “B” may request “trusted advisors” outside of their own personal network of third parties “T” to score a property which may lead to an in-app purchase opportunity.

With continued reference to FIG. 9, and further reference also to FIG. 11, the third parties “T” review (810) the feedback generated by the buyer “B.” In one embodiment, the feedback generated by the buyer “B” for a room of the subject property is initially displayed as a line graph 900 with a slider 902 that initially is located at a position 905 equivalent to the feedback generated by the buyer “B” (e.g., 3 of 10) on the third party feedback application 700. The third party “T” may then move the slider 902 to indicate their third party feedback (e.g., to position 907; 5 of 10). Movement of the slider 902 provides, in this embodiment, a visual indication of a difference between the feedback generated by the buyer “B” (slider original position 905) and the feedback provided by the third party “T” (position 907).

The third party “T” may also add a comment 910 (e.g., “Did not like the kitchen countertops.”). The comment 910 may be uploaded to the listing recommendation server 14 to be later appended to the feedback report accessible on the real estate feedback application 500. Various other feedback options such as those presented to the buyer “B” may alternatively or additionally be provided by the third party feedback application 700.

In one or more embodiments, the third party feedback application 700 may present a feedback page for each room (e.g., kitchen, bedroom 1, bedroom 2, bathroom 1, etc.) of the subject property reviewed by the buyer “B.” The third party “T” may then select one or more feedback pages (812). In addition, the rooms or areas not reviewed by the buyer “B” may also be accessible (e.g., add a review 912) to the third party “T”.

The third party feedback from the multiple of third parties “T” may then be aggregated (814) by the listing recommendation server 14 to generate aggregated third party feedback. The aggregated third party feedback may then be displayed compared to the feedback generated by the buyer “B” to provide a comparison that is received on the real estate feedback application 500. In one or more embodiments, the third party feedback from the multiple of third parties “T” may be aggregated (e.g., averaged) with the feedback generated by the buyer “B” to provide an overall rating for comparison with other real estate properties reviewed by the buyer “B” and the third parties “T.” Other aggregation methods may also be utilized which may weight one or more aspects of the property either automatically or based on a user input (e.g, 3 car garage a priority).

The term “server” conveys its customary meaning that provides service and/or data connection, e.g., to the handheld device and/or an electronic locking device. The term “handheld device” refers to a portable electronic device that is at least configured to send messages to, and/or receive messages from the listing recommendation server 14 over a long-range wireless communication network, such as a SMS, wireless, or cellular network. Examples of handheld devices include, but are not limited to: a cell phone; a personal digital assistant (“PDA”); a portable computer configured to store and playback digital pictures, songs, and/or videos; and the like. In addition, the handheld device is typically also configured for short-range wireless communications.

The elements described and depicted herein, including in flow charts and block diagrams throughout the figures imply logical boundaries between the elements. However, according to software or hardware engineering practices, the depicted elements and the functions thereof may be implemented on machines through computer executable media having a processor capable of executing program instructions stored thereon as a monolithic software structure, as standalone software modules, or as modules that employ external routines, code, services, and so forth, or any combination of these, and all such implementations may be within the scope of the present disclosure.

The use of the terms “a,” “an,” “the,” and similar references in the context of description (especially in the context of the following claims) are to be construed to cover both the singular and the plural, unless otherwise indicated herein or specifically contradicted by context. The modifier “about” used in connection with a quantity is inclusive of the stated value and has the meaning dictated by the context (e.g., it includes the degree of error associated with measurement of the particular quantity). All ranges disclosed herein are inclusive of the endpoints, and the endpoints are independently combinable with each other.

Although the different non-limiting embodiments have specific illustrated components, the embodiments of this invention are not limited to those particular combinations. It is possible to use some of the components or features from any of the non-limiting embodiments in combination with features or components from any of the other non-limiting embodiments.

It should be appreciated that like reference numerals identify corresponding or similar elements throughout the several drawings. It should also be appreciated that although a particular component arrangement is disclosed in the illustrated embodiment, other arrangements will benefit herefrom.

Although particular sequences are shown, described, and claimed, it should be understood that steps may be performed in any order, separated or combined unless otherwise indicated and will still benefit from the present disclosure.

The foregoing description is exemplary rather than defined by the limitations within. Various non-limiting embodiments are disclosed herein, however, one of ordinary skill in the art would recognize that various modifications and variations in light of the above teachings will fall within the scope of the appended claims. It is therefore to be understood that within the scope of the appended claims, the disclosure may be practiced other than as specifically described. For that reason the appended claims should be studied to determine true scope and content.

REAL ESTATE BUYER THIRD PARTY FEEDBACK APPLICATION

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS-REFERENCE TO RELATED APPLICATIONS

Provisional Applications (1)