Help Resources for the Support Team
      Back to home
      1. Internal RG Wiki
      2. Internal Documents
      3. Help Resources for the Support Team

      Listing Statuses

      Overview

      As far as our sites are concerned, there are exactly 3 statuses: ACTIVE, PENDING, and SOLD

      1. ACTIVE  
        • This status is the only one that will show up in property searches
        • Can also be found if the property is specifically searched for (ex: address search, MLS number search) 
        • "Active Properties" in Market Reports 
      2. PENDING
        • Can be found if the property is specifically searched for (ex: address search**, MLS number search) 
        • "Properties Under Contract" in Market Reports 
      3. SOLD
        • Sold Searches 
        • Can be found if the property is specifically searched for (ex: address search**, MLS number search) 
        • "Sold Properties" in Market Reports

      **This refers to the Address Search in the Advanced Search options. The Address Search in the sidebars is only Active properties by default (this can be changed in MCP under Advanced Site Settings > Address Search Status Query Parameter)

      Finding Statuses

      To find the status of a specific listing, debug the listing (Effective Debugging ) and search for the status: 

      To find the statuses of a board Mongo the board's statuses (Effective Mongo): 

      db.properties.distinct('status', {board:126, enabled:true})

      Statuses coming from the board (Example Board: 126): 

      'ACTIVE',
      'APPLICATION RECEIVED',
      'BACK ON MARKET',
      'EXTENDED',
      'SOLD CO OP BY MEMBER',
      'SOLD CO OP NON MEMBER',
      'SOLD-IN HOUSE',
      'SOLD-OFFICE EXCLUSIVE',
      'SOLD-OTHER',
      'UNDER CONTRACT',
      'UNDERCONTRACT-CONT TOSHOW'

      Search Status Map (SSM)

      All statuses from the MLS need to be mapped to one of the 3 statuses available (ACTIVE, PENDING, and SOLD) so that the site knows how to treat them. This is done via the Search Status Map in MCP.

      MCP > Board Settings > Search Status Map

      The format of this field will be "<Board_status>": "<RG_Status>"  (the only RG_Status options are ACTIVE, PENDING, or SOLD)
      Interpretation of the status field on property provided by the MLS for search purposes. Statuses not included here are hidden across the website. Property data is stored with the original status. Site interpretation is not stored anywhere except here.

      Each board has a default Search Status Map set: 

      To copy the default options right click on MCP > Inspect: 

      Format as follows (example 5081):

      {     "ACTIVE": "ACTIVE",     "CLOSED": "SOLD",     "ACTIVE - SHOWING": "ACTIVE",     "COMING SOON / HOLD: "ACTIVE",     "UNDER CONTRACT - SHOWING": "PENDING",     "UNDER CONTRACT - NOT SHOWING": "PENDING"}

      Then make adjustments as needed. In the example below the client wanted the status "UNDER CONTRACT - SHOWING" to still show in property searches on the site, so that was changed to "ACTIVE"

      {     "ACTIVE": "ACTIVE",     "CLOSED": "SOLD",     "ACTIVE - SHOWING": "ACTIVE",     "COMING SOON / HOLD: "ACTIVE",    "UNDER CONTRACT - SHOWING": "ACTIVE",     "UNDER CONTRACT - NOT SHOWING": "PENDING"}

      Alert Status Map (ASM)

      MCP > Board Settings > Alert Status Map

      The format of this field will be "<Board_status>": "<RG_Status>"  (the only RG_Status options are ACTIVE, PENDING, or SOLD)

      Any statuses assigned to the RG Status "PENDING" should not be added to ASM.

      Property Update Emails/MoveTo Push Notifications will only be sent when a property enters or exits one of the groups listed in this field. If a property exits all groups here but remains in some group in SEARCH_STATUS_MAP it will be considered to be "UNDER CONTRACT" for sending alerts, otherwise it will be treated as if it disappeared from the database (or appeared in the database for the converse case).

      For the example from above, if the same information was placed in the ASM field (minus the PENDING): 

      {
           "ACTIVE": "ACTIVE",
           "CLOSED": "SOLD",
           "ACTIVE - SHOWING": "ACTIVE",
           "COMING SOON / HOLD: "ACTIVE",
          "UNDER CONTRACT - SHOWING": "ACTIVE",
      }
      • If a property within a lead's search updated in the board status from "ACTIVE - SHOWING" to "CLOSED" the lead will receive an "Alert" for this change in the form of a property update email (the following send period) or a MoveTo App instant notification (if enabled).
        • It would move on the Market Reports from the "Active Properties" section to the "Sold Properties" section. 
      • If a property updated in the IDX feed status from "COMING SOON / HOLD" to "ACTIVE" the lead would not receive an "Alert" because even though the board status changed the RG Status did not. 
      • If a property's board status changed from "UNDER CONTRACT - SHOWING" to "UNDER CONTRACT - NOT SHOWING" (not in the ASM) a lead would receive an "Alert" because the property would have moved from the RG Status "Active" to the RG Status "Under Contract"
        • It would move on the Market Reports from the "Active Properties" section to the "Properties Under Contract" section. 

      For this same example if we were only to put the following in the ASM field (but left the same in the SSM field):

      {
         "ACTIVE": "ACTIVE",
           "ACTIVE - SHOWING": "ACTIVE",
         "COMING SOON / HOLD: "ACTIVE",
      }
      • If a property moves from board status "ACTIVE - SHOWING" to "CLOSED" an "Alert" will be sent to the lead that it has moved to "Under Contract" even though the status "CLOSED" is mapped to "SOLD" in SSM because "CLOSED" is not mapped in the ASM field.
      • This will also treat all listings still in the IDX feed that are not in the 3 statuses mapped in ASM as "Under Contract" which could cause some confusion if there are only 6 listings in their MLS "Under Contract" for a neighborhood but 92 listings "Under Contract" in a Market Report. 

       

      Use Cases: Coming Soon 

      If a client is wanting to display "Coming Soon" listings on their site, the first step is to verify if we are receiving this status on the feed via one of the options for "Finding Statuses" above. 

      If we are receiving a status for "Coming Soon" (examples: COMING SOON-NO SHOW & COMING SOON / HOLD): 

      • 1. Verify that this status is listed in the site's SSM. 
          • a. If it is move to step 2
          • b. If it is not and they have a custom SSM, add the status and map it to "ACTIVE"
          • c. If it is not and they are on the standard SSM, update it to custom with the "Coming Soon" status mapped to "ACTIVE" and reach out to #board_support slack so they can update the standard SSM
      • 2.  If you are not trained for YAMLs submit the ticket to the YAML queue. 
          • If you are trained for YAML and the custom field is not created reach out to #board_support slack for it to be created before moving forward. 

      Because of the layer of 'translation' for statuses, we can't make Coming Soon it's 'own' status, because our site doesn't have a behavior for that status, only ACTIVE, PENDING, or SOLD. So the only way we can single out Coming Soon listings is with a custom true/false field like this.