View source for Managing Applicant Requirements and Matching

= Managing Applicant Requirements and Matching =

Requirements are the structured description of what an applicant wants. Standout uses them to identify suitable properties and they should be updated whenever the customer's search changes.

== When to update requirements ==
Update them when:

* a new applicant registers;
* budget changes;
* preferred areas widen/narrow;
* bedroom or property type needs change;
* a buyer's own property changes status;
* the customer decides to buy rather than rent, or vice versa;
* the customer pauses or resumes their search.

== Add or edit a requirement ==
Open the contact and go to the Requirements area.

Record the criteria the customer has actually agreed, including where relevant:

* buying/renting/auction;
* residential/commercial/business;
* area/postcode and radius;
* minimum and maximum price;
* minimum bedrooms;
* property type and style;
* new-build preference;
* important features.

A customer may have more than one search, for example a primary home and a buy-to-let search.

[[File:Contact Match Requirements.png|none|thumb|1200px|Applicant requirements drive property matching.]]

== Review live matches ==
After saving requirements, review the live matches. A match is an invitation to review the property, not a substitute for judgement. Check the listing before recommending it.

If the same unsuitable properties repeatedly appear, correct the underlying requirement rather than simply ignoring the matches.

== Use Customer Portal for self-service ==
Customers with [[Customer Portal]] access can create, edit, pause/reactivate and delete their own requirements. These are the same records staff see in Standout.

When a customer changes requirements through Customer Portal, the branch is notified and matching is refreshed.

== Keep applicant status meaningful ==
Requirements can exist even if the contact is not currently marked '''Looking'''. If automatic property alerts depend on that status in your agency setup, make sure the status reflects the customer's real position.

== After a useful match ==
If the customer wants to see the property, use [[Booking and Managing Viewings]]. If they are not interested, update the search if their reason reveals that the requirement is wrong or incomplete.

== Good practice ==
Review requirements during meaningful applicant conversations. A requirement that has not been discussed for months is often less useful than it appears.