'Let' properties showing randomly on the website

[quigger]

Our GTH client reported....

• Our xxxxx lettings department have been receiving phone calls and emails from customers enquiring about different rental properties they have seen on the website but the properties have already been let a while ago so these properties shouldn’t be on the website.
• Some of these properties are from 6 months ago, 1 year ago and 2 years ago.
• We are aware that sometimes there WAS an issue when removing staff from the Reapit system - it reignited properties attached to those staff, i.e. when a staff member left the business.

So our questions are:

• What should offices be doing on Reapit when a property has been let and no longer available?
• We had been using agreement_signed as an additional marker for Let properties and hiding them from the website (after a certain let time). What actions need to take place within the CRM, to set a value for agreement_signed?

See related ticket: https://github.com/reapit/foundations/issues/8738

Current example property: TIL210008

[AshDeeming]

Hi @quigger Could you confirm the filters being used to surface properties? The example provided relates to a property which has had an 'unavailable' status since June 2022?

[quigger]

This is the request we send;

https://platform.reapit.cloud/properties?embed=documents&fromArchive=false&internetAdvertising=true&pageNumber=1&pageSize=100&lettingStatus=toLet&lettingStatus=tenancyCurrentUnavailable&lettingStatus=tenancyCurrent&lettingStatus=arrangingTenancyUnavailable&lettingStatus=arrangingTenancy

We do get TIL210008 property back, as it’s in status tenancyCurrentUnavailable.

On our side, we then filter out properties where agreementSigned is older than X weeks.

We have expected TIL210008 to have agreementSigned set, but it’s null.

[quigger]

Hi @AshDeeming - was that information useful?

[AshDeeming]

Thanks @quigger