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.
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.
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:
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 33 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
With reference to
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 (
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”;
Next, during the showing, feedback is entered into the real estate feedback application 500 by the buyer “B” for the property (216;
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 (
The feedback is then saved in memory 66 (
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
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;
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” (
With reference to
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 (
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 (
With continued reference to
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.
This application claims the benefit of provisional application Ser. No. 62/527,404, filed Jun. 30, 2017.
Number | Name | Date | Kind |
---|---|---|---|
5361201 | Jost et al. | Nov 1994 | A |
6041311 | Chislenko et al. | Mar 2000 | A |
6472973 | Harold et al. | Oct 2002 | B1 |
6609109 | Bradley et al. | Aug 2003 | B1 |
6624742 | Romano et al. | Sep 2003 | B1 |
6883002 | Faudman | Apr 2005 | B2 |
6973432 | Woodard et al. | Dec 2005 | B1 |
7006977 | Attra et al. | Feb 2006 | B1 |
7904511 | Ryan et al. | Mar 2011 | B2 |
8024349 | Shao et al. | Sep 2011 | B1 |
8103597 | Arnebeck | Jan 2012 | B2 |
8140421 | Humphries et al. | Mar 2012 | B1 |
8140443 | Fawaz | Mar 2012 | B2 |
8145661 | Billman et al. | Mar 2012 | B1 |
8244851 | Postoaca | Aug 2012 | B1 |
8478651 | Crafts et al. | Jul 2013 | B1 |
8688594 | Thomas et al. | Apr 2014 | B2 |
8832136 | Billman et al. | Sep 2014 | B1 |
8983927 | Rao | Mar 2015 | B2 |
9104782 | Visioli et al. | Aug 2015 | B2 |
9128471 | Shahid et al. | Sep 2015 | B1 |
9213461 | Eraker et al. | Dec 2015 | B2 |
9361583 | Holloway et al. | Jun 2016 | B1 |
20020022980 | Mozayeny et al. | Feb 2002 | A1 |
20020049624 | Raveis et al. | Apr 2002 | A1 |
20020072930 | Scites | Jun 2002 | A1 |
20030229649 | Herrero | Dec 2003 | A1 |
20040088172 | Baglioni | May 2004 | A1 |
20050182745 | Dhillon et al. | Aug 2005 | A1 |
20050256866 | Lu et al. | Nov 2005 | A1 |
20060080114 | Bakes et al. | Apr 2006 | A1 |
20060282304 | Bedard et al. | Dec 2006 | A1 |
20070016428 | Loveland | Jan 2007 | A1 |
20070174764 | Roseway et al. | Jul 2007 | A1 |
20070226046 | Share | Sep 2007 | A1 |
20080109433 | Rose | May 2008 | A1 |
20080262902 | Bullis et al. | Oct 2008 | A1 |
20090153291 | Larson et al. | Jun 2009 | A1 |
20090182788 | Chung et al. | Jul 2009 | A1 |
20090192862 | Hoggard | Jul 2009 | A1 |
20100131331 | Ginsburg et al. | May 2010 | A1 |
20110066561 | Lazarre et al. | Mar 2011 | A1 |
20110238586 | Mainville | Sep 2011 | A1 |
20110251876 | Fisher | Oct 2011 | A1 |
20110251974 | Woodard et al. | Oct 2011 | A1 |
20110275441 | Wilson | Nov 2011 | A1 |
20120323587 | Llosa | Dec 2012 | A1 |
20130018957 | Parnaby et al. | Jan 2013 | A1 |
20130254289 | Cutri et al. | Sep 2013 | A1 |
20130325606 | Balduf et al. | Dec 2013 | A1 |
20130325623 | Balduf et al. | Dec 2013 | A1 |
20130346151 | Bleakley et al. | Dec 2013 | A1 |
20140026094 | Zimmerman et al. | Jan 2014 | A1 |
20140136517 | Li | May 2014 | A1 |
20140222620 | Polston | Aug 2014 | A1 |
20140266586 | Fisher et al. | Sep 2014 | A1 |
20140279176 | Taylor et al. | Sep 2014 | A1 |
20140279592 | Ruebush et al. | Sep 2014 | A1 |
20140304178 | Bengson et al. | Oct 2014 | A1 |
20140375422 | Huber et al. | Dec 2014 | A1 |
20150242919 | Wickam | Aug 2015 | A1 |
20150269689 | Ferguson et al. | Sep 2015 | A1 |
20150317581 | Fawaz | Nov 2015 | A1 |
20150324941 | Garg | Nov 2015 | A1 |
20150356801 | Nitu et al. | Dec 2015 | A1 |
20160048874 | Brajer et al. | Feb 2016 | A1 |
20160098806 | Chen et al. | Apr 2016 | A1 |
20160117785 | Lerick et al. | Apr 2016 | A1 |
20160189320 | Oddo | Jun 2016 | A1 |
20160267576 | Crossman Sullivan et al. | Sep 2016 | A1 |
20160314545 | Jessen | Oct 2016 | A1 |
20160364929 | Fisher et al. | Dec 2016 | A1 |
20160379321 | Abraham et al. | Dec 2016 | A1 |
20180253780 | Wang et al. | Sep 2018 | A1 |
20180374170 | Kuenzi et al. | Dec 2018 | A1 |
20190005516 | Spath | Jan 2019 | A1 |
20190005564 | Beatty et al. | Jan 2019 | A1 |
Number | Date | Country |
---|---|---|
2017100177 | Mar 2017 | AU |
2717878 | Apr 2012 | CA |
106446009 | Feb 2017 | CN |
0177793 | Oct 2001 | WO |
2012135932 | Oct 2012 | WO |
2014018065 | Jan 2014 | WO |
2014160806 | Oct 2014 | WO |
Entry |
---|
Redfin Shared Search Makes it Easy for Spouses, Agents and Parents to Work Together on a House Hunt, Glenn Kelman, Apr. 6, 2015, https://www.redfin.com/blog/2015/04/redfin-shared-search-makes-it-easy-for-spouses-agents-and-parents-to-work-together-on-a-house-hunt.html, pp. 1-11. (Year: 2015). |
Redfin Shared Search Makes it Easy for Spouses, Agents and Parents to Work Together on a House Hunt, Glenn Kelman, Apr. 6, 2015, https://www.redfin.com/blog/2015/04/redfin-shared-search-makes-it-easy-for-spouses-agents-and-parents-to-work-together-on-a-house-hunt.html, pp. 1-11. |
Sharing Your Favorite Homes Just Got Easier with Trulia's iMessage Extensions, Mili Dutta, Feb. 23, 2017, https://www.trulia.com/blog/tech/trulia-imessage-extensions/, pp. 1-4. |
Listingbook enables house hunters to ‘search like an agent’, Andrea V. Brambila, Jan. 14, http://www.inman.com/2015/07/10/listingbook-enables-house-hunters-to-search-like-an-agent/, pp. 1-11. |
What is the average amount of showings before a house is sold? https://www.trulia.com/voices/Home_Selling/What_is_the_average_amount_of_showings_before_a_ho-709776, Trulia, Jul. 7, 2014, pp. 1-14. |
What is the average number of showings before an offer is made? https://www.trulia.com/voices/Home_Selling/What_is_the_average_number_of showings_before_an_o-23671, Trulia, Feb. 27, 2008, pp. 1-11. |
Long Time on Market Makes Moody Sellers?, https://www.redfin.com/blog/2007/09/long_time_on_market_makes_moody_sellers.html, Redfin Blogger, Sep. 20, 2007, pp. 1-3. |
U.S. Non-Final Office Action dated May 21, 2020 issued for related U.S. Appl. No. 16/017,358. |
U.S. Final Office Action dated Sep. 11, 2020 issued for related U.S. Appl. No. 16/018,288. |
Welcome to the First-Ever Redfin Housing Demand Index, Capturing U.S. Homebuyer Demand and Forecasting Home-Price and Sales Trends, Written by Nela Richardson on Jul. 23, 2015, https://www.redfin.com/blog/2015/07/july.html, pp. 1-7. |
U.S. Non-Final Office Action dated May 27, 2020 issued for related U.S. Appl. No. 16/018,285. |
Xiwang Yang et al., Circle-based Recommendation in Online Social Networks, eeweb.poly.edu/faculty/yongliu/docs/CircleRec.pdf, Knowledge Discovery and Data Mining, pp. 1-9, 2012. |
U.S. Non-Final Office Action dated Nov. 19, 2020, issued for related U.S. Appl. No. 16/018,288. |
U.S. Notice of Allowance dated Oct. 21, 2020 issued for related U.S. Appl. No. 16/018,285. |
U.S. Final Office Action dated Nov. 27, 2020 issued for related U.S. Appl. No. 16/017,358. |
Number | Date | Country | |
---|---|---|---|
20190005557 A1 | Jan 2019 | US |
Number | Date | Country | |
---|---|---|---|
62527404 | Jun 2017 | US |