Matching, filters, and list views

How matching works When your team enables listing matching , Anymelk compares active buyer requests against active listings using shared fields: Transaction type and property kind Budget vs price fields Area ranges Categories and amenities Other configured rules Matches surface as: Match count badges on property and buyer request cards Notifications when new inventory fits an open buyer request (or new demand fits a listing) Dedicated match views on detail pages where implemented Matching is assistive — agents still judge fit (view, building reputation, owner terms) before pitching. Reviewing matches from a buyer request Open the buyer request detail page. Look for a matches section or linked listings list showing compatible listings sorted by relevance. Click through to property detail to verify photos and status. Present a curated shortlist to the client rather than every numeric match. Reviewing matches from a listing Property cards display “N matches” when demand exists. Open the property and inspect which buyer requests align — useful when a new listing lands and you want immediate outreach to hot buyers. Filters on the requests list Use Refine results like the properties area: Search — title or internal labels Tracking number — pinpoint one record Status — draft, active, pending approval Transaction type and property kind Budget and area ranges Customer — all buyer requests for one contact Category and amenity filters — mirror property filters for symmetry Combine filters to answer questions like “active rental buyer requests under 50M/month in District 5 with parking.” Status tabs Active — open demand Pending approval — submissions awaiting review Archive — closed or expired intakes Agents living on pipeline work stay on Active with personal filter bookmarks. Card view vs table view Toggle with the view control top-right — same pattern as properties. Cards — scan client names, budgets, match counts visually. Table — sort by updated date, budget, or status; better for managers auditing stale buyer requests. View choice persists in the link. Acting on matches Recommended flow when notified of a new match: 1. Open the buyer request — confirm still active (client not already under contract) 2. Open the listing — confirm still on market and photo-ready 3. Call client with two sentences of context 4. Log notes on customer or buyer request 5. Schedule reminder for tour feedback Dismiss false positives by refining buyer request amenities or archiving outdated demand — do not ignore bad data. Stale buyer request hygiene Matches degrade when buyer requests go stale: Archive fulfilled deals promptly Bump budget fields when clients expand range Weekly team review: buyer requests with no activity in 30 days Some teams add calendar reminders for reopening calls. Filters + matching together Filters narrow human review; matching automates first pass. Use both: 1. Filter buyer requests needing attention (e.g., high budget active rentals) 2. Sort by match count descending in table view if column available 3. Work top three manually Permissions Reading buyer requests requires request read . Matching notifications respect the same scope — you only hear about team data you can access. Tips Align amenity vocabulary with listings — matching reads structured fields only When client rejects a match, note why in buyer request notes to tune future picks Run requests basics tour for filter and view toggle locations Treat matching as a daily inbox, not a monthly report — speed wins deals when inventory is tight.