What is a synced list?
A synced list is a property list that keeps itself up to date. You choose what belongs in it once — for example “our sold listings” or “Lauren’s current sales” — and Voqo AI re-checks the list every time your integrations sync. New matching properties are added, properties that no longer match drop out, and your AI agent always references the current set on calls. You build one from the Knowledge Base using Quick Create.Creating a synced list with Quick Create
- In the Knowledge Base, open Quick Create.
- Pick a starting template — by status (For Sale, For Lease, Sold, Under Offer), by property type (Houses, Apartments & Units), by feature (Family Homes), or by integration source (realestate.com.au, Domain, VaultRE, AgentBox, Eagle MRI, or Manual).
- Optionally narrow it further (see below).
- Name the list and click Create List.
Filter by listing agent
Any property list can be narrowed to a single listing agent. Click Filter by Agent when creating the list and choose the agent — the list will then contain only that agent’s properties, and stay in sync as their listings change. Listing-agent filtering now works for every connected source, including realestate.com.au. Previously, agents on realestate.com.au listings could be missing from the agent picker; they now appear for all integrations, so you can build clean per-agent lists no matter where the listing came from.Combine an integration source with a listing status
When you sync more than one portal or CRM, the same property can appear twice — once from each source — which can clutter a list. To build a clean, single-source list, you can combine an integration source with a listing status in Quick Create. For example:- realestate.com.au + For Sale — only your current sales from realestate.com.au.
- Domain + For Lease — only your rental stock from Domain.
- realestate.com.au + Sold — only your settled sales from realestate.com.au.
Combining a source with a status keeps a list focused on one source, but it does not remove duplicate properties across sources — the same property can still exist twice in your Knowledge Base, once per integration. Building single-source lists is the cleanest way to avoid mixing duplicates today.

