Saved Search Implementation Guide
Provides the full saved-search workflow for creating and managing searches linked to clients, configuring email or SMS match alerts and delivery frequency, supporting two-way replies, inserting application links and message tokens, tracking match state, and customizing templates for new-listing, price-change, sold and related notifications; Related terms include “create a saved search,” “client search alerts,” “email or SMS frequency,” “new listing notification,” “price-change alert,” “sold alert,” “two-way reply,” “message token,” “match state,” and “custom alert template”; Its focus is the complete saved-search notification lifecycle.PopularPreventing Duplicate Saved Saved Searches in the Repliers API
Explains how Repliers normally detects and merges similar saved searches for the same client, which changes update an existing record versus create a distinct search, why accidental duplicates occur, and how support can enable an account-level option that always creates a new saved search when the application requires separate records; Related terms include “duplicate saved searches,” “same client and same criteria,” “existing search updated instead of new one,” “merge similar searches,” “why was no new ID created,” and “always create a separate saved search”; Its focus is saved-search deduplication behavior, not duplicate property listings.Few readersSaved Searches: The Initial Match Limit, Why It Exists, and How to Build Around It
This guide explains how saved search alerts work, why there is a cap on the number of initial matches, what the 406 error means, and the UX patterns we recommend so that your users never run into the limit at all. How saved search alerts actually work There are two distinct phases in the life of a saved search, and most confusion about the system comes from conflating them. Phase 1 — Creation or update. When a saved search is created or updated, the API evaluates the filters against cuFew readers