{"id":74,"date":"2026-08-24T21:00:42","date_gmt":"2026-08-25T02:00:42","guid":{"rendered":"https:\/\/realdialer.com\/blog\/?p=74"},"modified":"2026-09-07T15:20:15","modified_gmt":"2026-09-07T20:20:15","slug":"build-seller-prospecting-list","status":"publish","type":"post","link":"https:\/\/realdialer.com\/build-seller-prospecting-list\/","title":{"rendered":"How to Build a Seller Prospecting List"},"content":{"rendered":"<p>To build a seller prospecting list from multiple lead sources, preserve each raw source, map every file into the same working fields, normalize before matching, merge duplicate people and properties without erasing source history, carry every suppression flag forward, and split the clean records back into separate named calling lists. The result should be one trustworthy operating system, not one giant file called &quot;seller leads.&quot;<\/p>\n<p>I keep these sources separate because I cannot make the same opening to an old CRM lead, a fresh expired, a FSBO, and a neighborhood homeowner. The CRM may hold relationship history; the expired record may hold a newer market event. If I blend them before preserving both, I make the upload cleaner and the call worse.<\/p>\n<p>Use this eight-step workflow:<\/p>\n<ol>\n<li>Give each source a defined job in the pipeline.<\/li>\n<li>Save the untouched raw file and its acquisition details.<\/li>\n<li>Map every file to one canonical working table.<\/li>\n<li>Normalize phones, names, addresses, dates, and status fields.<\/li>\n<li>Match people and properties separately, then review uncertain duplicates.<\/li>\n<li>Apply do-not-call, opt-out, active-listing, and other suppression rules across every copy.<\/li>\n<li>Export separate, source-aware calling lists.<\/li>\n<li>Measure conversations and appointments by source while using deduplicated coverage for the total audience.<\/li>\n<\/ol>\n<h2 id=\"start-with-the-job-of-the-list-not-the-vendor\">Start with the job of the list, not the vendor<\/h2>\n<p>Start with the annual goal and the daily conversation target. I plan around exactly 250 working days per year. The operating floor is 20 meaningful conversations per working day for a 20-listing goal and 50 per day for at least 50 listings. That does not prescribe Monday through Friday, Monday through Saturday, or any other weekday pattern.<\/p>\n<p>Use the <a href=\"https:\/\/realdialer.com\/how-many-people-real-estate-agent-prospect-each-day\/\">daily prospecting calculator<\/a> to translate the conversation goal into the unique people your own contact rate says you must attempt. A meaningful conversation is a real two-way exchange. An unanswered call, voicemail, text sent, or immediate hangup is not one.<\/p>\n<p>Keep enough eligible, current people to support the work without recycling a small audience. List capacity comes from conversation math, not an internet benchmark.<\/p>\n<p><code>unique people to attempt = conversation target \/ your observed attempt-to-conversation rate<\/code><\/p>\n<p>If a fictional agent has recently created one meaningful conversation for every five unique people attempted, a 20-conversation day requires about 100 unique people. The 20 percent rate is only an illustration. Use the agent&#039;s own complete sessions, source mix, and calling windows.<\/p>\n<h2 id=\"separate-source-signal-channel-and-attribution\">Separate source, signal, channel, and attribution<\/h2>\n<p>These four fields often get collapsed into one &quot;lead source&quot; column, and that is where reporting starts to lie.<\/p>\n<table>\n<thead>\n<tr>\n<th>Concept<\/th>\n<th>Question it answers<\/th>\n<th>Example<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Source<\/td>\n<td>Where did this record come from?<\/td>\n<td>Prior CRM export, MLS listing-status review, public property record, open-house form<\/td>\n<\/tr>\n<tr>\n<td>Signal or segment<\/td>\n<td>Why was this person selected?<\/td>\n<td>Prior seller conversation, recent expired status, owner-marketed property, neighborhood around a closing<\/td>\n<\/tr>\n<tr>\n<td>Channel<\/td>\n<td>How can the agent lawfully and appropriately reach the person?<\/td>\n<td>Live call, direct mail, email, door conversation<\/td>\n<\/tr>\n<tr>\n<td>Attribution<\/td>\n<td>Which activity receives credit under the rule you defined?<\/td>\n<td>The named call list tied to the conversation, with earlier CRM and mail touches retained as context<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>A raw source row is not automatically a callable prospect. A prospect is not automatically a lead. A lead is someone whose conversation revealed a real property decision, timing, or useful next step.<\/p>\n<p>When one homeowner appears in three sources, the expired record may hold the freshest signal, the CRM the best relationship context, and a public record the best ownership detail. Keep all three instead of letting the last import rewrite the story.<\/p>\n<h2 id=\"choose-three-complementary-seller-source-lanes\">Choose three complementary seller-source lanes<\/h2>\n<p>The <a href=\"https:\/\/realdialer.com\/best-real-estate-prospecting-methods-listing-agents\/\">best real estate prospecting methods<\/a> are not interchangeable. Build a mix in which each source does a different job.<\/p>\n<table>\n<thead>\n<tr>\n<th>Lane<\/th>\n<th>Useful sources<\/th>\n<th>Pipeline job<\/th>\n<th>Main risk<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Relationship<\/td>\n<td>Sphere, past clients, old seller leads, referrals<\/td>\n<td>Start with trust and prior context<\/td>\n<td>Stale notes or relying on memory instead of a dated next step<\/td>\n<\/tr>\n<tr>\n<td>Current seller signal<\/td>\n<td>Recently expired status after a current representation check, FSBO, valuation request, inbound response<\/td>\n<td>Surface a recent observable sale decision<\/td>\n<td>Treating a public status as permission, treating withdrawn or off-market as unrepresented, or assuming the owner wants the same solution<\/td>\n<\/tr>\n<tr>\n<td>Property and market audience<\/td>\n<td>Circle around a real listing event, geographic farm, absentee owners, landlords<\/td>\n<td>Build a repeatable long-term homeowner audience<\/td>\n<td>Calling broad ownership data &quot;motivation&quot; without evidence<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>NAR&#039;s <a href=\"https:\/\/www.nar.realtor\/news\/real-estate-news\/even-in-a-tougher-market-realtors-are-holding-their-ground\">2026 Member Profile coverage<\/a> reports that the typical member earned 28 percent of business from past clients and customers; agents with more than 16 years of experience drew about half from repeat business. Start with records the agent already owns.<\/p>\n<p>For current seller signals, use the live <a href=\"https:\/\/realdialer.com\/expired-listing-prospecting\/\">expired listing<\/a> and <a href=\"https:\/\/realdialer.com\/fsbo-prospecting\/\">FSBO prospecting<\/a> guides to shape the reason for contact. For market audiences, the <a href=\"https:\/\/realdialer.com\/circle-prospecting\/\">circle prospecting guide<\/a> shows how to build around an actual listing, pending sale, or closing instead of an arbitrary radius.<\/p>\n<h2 id=\"preserve-a-source-ledger-before-changing-the-file\">Preserve a source ledger before changing the file<\/h2>\n<p>Never make the cleaned CSV your only copy. Save the raw file exactly as received, then record:<\/p>\n<ul>\n<li>market and geographic boundary;<\/li>\n<li>source name and source date;<\/li>\n<li>provider, system, or team member who produced it;<\/li>\n<li>permitted use, license, and campaign purpose;<\/li>\n<li>date the data should be refreshed;<\/li>\n<li>operator who prepared the working file;<\/li>\n<li>original filename, location, and a file hash when the process supports it.<\/li>\n<\/ul>\n<p>Name files and lists so another person can identify the market, segment, and source date without opening them:<\/p>\n<p><code>Market - Seller segment - Source date<\/code><\/p>\n<p>For example: <code>Franklin County - Expired 0-30 days - 2026-08-24<\/code>.<\/p>\n<h2 id=\"use-one-canonical-working-field-map\">Use one canonical working field map<\/h2>\n<p>Each vendor, MLS export, CRM, and public-record source uses different headers. Map them into one working table before you attempt to match records.<\/p>\n<table>\n<thead>\n<tr>\n<th>Field group<\/th>\n<th>Keep in the working table<\/th>\n<th>Why it matters<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Property identity<\/td>\n<td>County, APN or parcel ID when available, property address, unit<\/td>\n<td>One owner may control several properties; one address can contain several units<\/td>\n<\/tr>\n<tr>\n<td>Contact identity<\/td>\n<td>Full name, mailing address, each phone, email<\/td>\n<td>A property and a person are not the same record<\/td>\n<\/tr>\n<tr>\n<td>Source history<\/td>\n<td>Source tags, first seen, last seen, source as-of date, raw row reference<\/td>\n<td>Prevents the newest file from erasing useful provenance<\/td>\n<\/tr>\n<tr>\n<td>Seller context<\/td>\n<td>Observable signal, listing status, status checked time, prior conversation note<\/td>\n<td>Gives the agent a truthful reason for the conversation<\/td>\n<\/tr>\n<tr>\n<td>Data quality<\/td>\n<td>Phone verification date, email verification date, address review status<\/td>\n<td>Makes stale or uncertain records visible<\/td>\n<\/tr>\n<tr>\n<td>Eligibility and suppression<\/td>\n<td>Federal, state, and entity DNC review; channel opt-outs; consent record; active-listing review<\/td>\n<td>Keeps suppression attached when duplicates are merged<\/td>\n<\/tr>\n<tr>\n<td>Operating record<\/td>\n<td>Assigned agent, last attempt, last conversation, outcome, next action<\/td>\n<td>Turns a static file into a managed prospecting queue<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The final RealDialer import does not need every upstream field. Keep the full working table and source ledger, then export the fields the calling session needs. The <a href=\"https:\/\/realdialer.com\/real-estate-dialer-setup-checklist\/\">dialer setup checklist<\/a> covers file mapping and preflight from the prepared list to the first controlled block.<\/p>\n<h2 id=\"normalize-before-you-deduplicate\">Normalize before you deduplicate<\/h2>\n<p>Matching dirty data first creates false merges and missed duplicates. Clean the comparison fields in a copy while preserving original values.<\/p>\n<ol>\n<li><strong>Phone:<\/strong> remove formatting for comparison and keep the original display value. RealDialer imports one phone per row and uses the normalized phone as its contact key. If one person has several phones, keep the person-level relationship in the working table, repeat the needed context on each exported phone row, and apply any person-level suppression to every number the request or policy covers.<\/li>\n<li><strong>Address:<\/strong> standardize street suffixes, directionals, city, state, ZIP, and unit without deleting apartment or unit information.<\/li>\n<li><strong>Name:<\/strong> separate owner or contact names only when the source supports it; do not guess that similar initials are the same person.<\/li>\n<li><strong>Dates and status:<\/strong> convert them to consistent formats and keep the source&#039;s as-of date.<\/li>\n<li><strong>Blank and invalid values:<\/strong> quarantine them for review instead of filling them with guesses.<\/li>\n<\/ol>\n<p>USPS says an address should be corrected and standardized before comparison in its <a href=\"https:\/\/postalpro.usps.com\/address-quality\">address-quality guidance<\/a>. The same order helps seller-list matching, but never discard the unit: apartment 2 and apartment 7 are different properties.<\/p>\n<p>Use a property key such as county plus APN where the source provides a trustworthy parcel identifier. Otherwise use the complete standardized address, including unit. Use phone, email, name, mailing address, and source evidence to match people. Send uncertain matches to a manual-review queue.<\/p>\n<p>List overlap is context, not proof of motivation. Three vendors can repeat the same stale error. Several valid sources can also describe the same owner for different legitimate reasons. Investor marketers often call the overlap step list stacking. For a listing agent, overlap should trigger reconciliation and context, not an automatic motivation score.<\/p>\n<h2 id=\"carry-suppression-across-every-duplicate\">Carry suppression across every duplicate<\/h2>\n<p>Apply suppression at the correct scope and use OR logic across duplicates within that scope. If any duplicate marks a phone number do not call, that number remains suppressed across every merged copy. If the documented request or policy applies to the person rather than one number, carry it to every known phone it covers. Preserve email, text, and other channel-specific opt-outs separately. Do not clear a direct request merely because another source lacks the flag; remove it only when documented authority under the applicable rules permits it.<\/p>\n<p>Within RealDialer, a saved do-not-call flag suppresses that normalized-phone contact across all of its list memberships. RealDialer does not automatically discover another phone belonging to the same person.<\/p>\n<p>Public data is not automatic permission to solicit. NAR&#039;s <a href=\"https:\/\/www.nar.realtor\/telemarketing-cold-calling\">telemarketing and cold-calling guidance<\/a> specifically warns agents to check applicable Do Not Call restrictions and explains that a FSBO or expired status does not create a listing-solicitation exemption. The <a href=\"https:\/\/www.ftc.gov\/business-guidance\/resources\/complying-telemarketing-sales-rule\">FTC Telemarketing Sales Rule guide<\/a> also requires covered sellers and telemarketers to maintain entity-specific suppression and use current Registry data under the applicable rules.<\/p>\n<p>Before any channel is used, check the current federal, state, local, brokerage, data-license, MLS, and campaign-specific requirements. Before a listing solicitation, verify current listing and representation status under the applicable rules and, for REALTORS, <a href=\"https:\/\/www.nar.realtor\/about-nar\/governing-documents\/code-of-ethics\/2026-code-of-ethics-standards-of-practice\">Article 16 and Standard of Practice 16-4<\/a>. A withdrawn or off-market status does not by itself prove that the owner is unrepresented. Sensitive life events and protected characteristics are not targeting shortcuts.<\/p>\n<p>An imported record or a product label such as &quot;ready&quot; is not independent legal clearance.<\/p>\n<h2 id=\"split-the-clean-table-back-into-named-calling-lists\">Split the clean table back into named calling lists<\/h2>\n<p>The working table can hold the complete relationship, but the calling lists should stay source-aware. One primary audience per block improves the opening, the notes, and the report.<\/p>\n<p>In RealDialer, each CSV import creates one new named list. The import maps one phone per row plus optional name, email, address, source, notes, and do-not-call fields. Invalid phones are excluded and reported. Within one file, the first occurrence of a normalized phone is retained; later duplicate rows are skipped without field merging. An existing normalized phone matches the saved contact and can join another legitimate named list.<\/p>\n<p>That is phone deduplication, not person, household, or property deduplication. <strong>Keep existing data<\/strong> adds a matched contact to the new list without applying incoming field changes, including a new do-not-call flag. <strong>Update from this CSV<\/strong> can set do not call and never clears an existing flag, but it can replace non-empty saved details, including the contact&#039;s single source value. Resolve suppression before import, preserve immutable provenance in the external source ledger, and verify matched contacts after import.<\/p>\n<p>Import and reconcile one list at a time:<\/p>\n<ol>\n<li>Confirm the list name, raw file, row count, and source date.<\/li>\n<li>Map the phone and supporting fields.<\/li>\n<li>Review invalid phones and duplicates before accepting the result.<\/li>\n<li>Confirm do-not-call flags survived the import decision.<\/li>\n<li>Compare source rows, imported memberships, and excluded rows.<\/li>\n<li>Open a small random sample and verify person, property, unit, current status, phone match, and suppression.<\/li>\n<\/ol>\n<p>The <a href=\"https:\/\/realdialer.com\/real-estate-prospecting-schedule\/\">real estate prospecting schedule<\/a> can assign those named sources to rotation blocks while keeping due callbacks and new responses in a separate priority lane.<\/p>\n<h2 id=\"prioritize-by-observable-evidence-not-a-secret-motivation-score\">Prioritize by observable evidence, not a secret motivation score<\/h2>\n<p>Use a short decision table that an agent can explain:<\/p>\n<table>\n<thead>\n<tr>\n<th>Priority factor<\/th>\n<th>Higher priority when<\/th>\n<th>Do not infer<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Promise or response<\/td>\n<td>A callback is due or the homeowner responded<\/td>\n<td>That every response means listing intent<\/td>\n<\/tr>\n<tr>\n<td>Seller signal<\/td>\n<td>A recent, verified property decision exists<\/td>\n<td>That distress or an owner trait guarantees a sale<\/td>\n<\/tr>\n<tr>\n<td>Relationship<\/td>\n<td>A prior conversation or referral provides context<\/td>\n<td>That familiarity removes channel or opt-out rules<\/td>\n<\/tr>\n<tr>\n<td>Recency<\/td>\n<td>Source and status were checked recently<\/td>\n<td>That several old sources become fresh when stacked<\/td>\n<\/tr>\n<tr>\n<td>Data readiness<\/td>\n<td>Person, property, phone, unit, and suppression are resolved<\/td>\n<td>That a complete row is legally callable or likely to convert<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Priority decides which otherwise eligible record enters the next block. It does not decide eligibility.<\/p>\n<h2 id=\"worked-example-three-sources-one-owner-separate-lists\">Worked example: three sources, one owner, separate lists<\/h2>\n<p>Morgan is a fictional agent. Three records describe the same owner and property:<\/p>\n<table>\n<thead>\n<tr>\n<th>Raw source<\/th>\n<th>What it adds<\/th>\n<th>What could go wrong<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Old CRM seller lead<\/td>\n<td>A prior conversation, preferred name, and a note that timing was uncertain<\/td>\n<td>The phone has not been verified recently<\/td>\n<\/tr>\n<tr>\n<td>Absentee-owner export<\/td>\n<td>Current mailing address and parcel ID<\/td>\n<td>The file calls every absentee owner &quot;motivated&quot;<\/td>\n<\/tr>\n<tr>\n<td>Recent expired-status review<\/td>\n<td>Fresh listing status, property address, and status date<\/td>\n<td>The owner may have relisted or requested no calls elsewhere<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Morgan standardizes the property address and parcel ID, normalizes the phones, and confirms the three rows describe one owner-property relationship. The working record keeps all three source tags and dates. It retains the prior conversation note, uses the freshest verified contact fields, rechecks current listing status, and applies suppression if any copy is ineligible.<\/p>\n<p>The recent expired status and prior relationship can raise operational priority. The presence of three sources does not prove motivation.<\/p>\n<p>Morgan then exports the owner into the separate source list or lists that have a legitimate job in the week&#039;s schedule. The raw files and merge decision remain in the source ledger. Source-specific list metrics can be reviewed later, while portfolio coverage is deduplicated before anyone calls the sum &quot;unique people.&quot;<\/p>\n<h2 id=\"measure-source-quality-through-the-full-path\">Measure source quality through the full path<\/h2>\n<p>Use the same outcome definitions for every named list:<\/p>\n<p><code>source rows -&gt; unique matched people -&gt; suppressed or invalid -&gt; eligible queue -&gt; unique people attempted -&gt; meaningful conversations -&gt; leads -&gt; appointments -&gt; signed listings<\/code><\/p>\n<p>Raw rows and dials are not quality metrics. Duplicate rates reveal source overlap; answer rates test phone quality and calling windows; conversations, leads, appointments, and listings show where the pipeline actually breaks.<\/p>\n<p>RealDialer list reporting can compare progress and outcomes for separate named audiences. It reports the named list attached to a call and its saved outcomes. That is observable list and session attribution, not proof that one source caused a later appointment or listing and not a complete multi-touch ROI model. Do not add list totals together and label the result unique people when one contact belongs to several lists; deduplicate that portfolio total in the working table.<\/p>\n<p>RealDialer&#039;s multi-line workflow is built to reduce unanswered time during a focused block. It processes unanswered ringing, voicemail, busy signals, and failed attempts in parallel so more live conversations can fit into a fixed prospecting block. The purpose is not to inflate a dial count or replace careful list construction.<\/p>\n<p>The <a href=\"https:\/\/realdialer.com\/how-real-estate-dialer-works-behind-screen\/\">behind-the-screen dialer guide<\/a> explains how a prepared list becomes attempts, outcomes, and reporting evidence. The <a href=\"https:\/\/realdialer.com\/real-estate-prospecting-complete-system\/\">complete prospecting system<\/a> connects that evidence to weekly decisions.<\/p>\n<h2 id=\"maintain-the-list-on-a-defined-rhythm\">Maintain the list on a defined rhythm<\/h2>\n<ul>\n<li><strong>Before each import:<\/strong> preserve the raw file, update the source ledger, normalize, deduplicate, and apply suppression.<\/li>\n<li><strong>Before each block:<\/strong> recheck volatile signals, current listing status, campaign eligibility, and a small data sample.<\/li>\n<li><strong>After each block:<\/strong> save outcomes, correct bad numbers, record opt-outs, and date every promised next action.<\/li>\n<li><strong>Weekly:<\/strong> compare sources on unique people attempted, conversations, leads, and appointments; review unresolved imports and duplicates.<\/li>\n<li><strong>On the source&#039;s refresh cycle:<\/strong> replace or update stale records without erasing prior conversations or suppression.<\/li>\n<\/ul>\n<p>Expired, FSBO, and listing-status data can change quickly. The refresh rule should follow the source, not a universal cleanup date.<\/p>\n<h2 id=\"common-seller-list-mistakes\">Common seller-list mistakes<\/h2>\n<ul>\n<li>Mixing every source into one generic queue.<\/li>\n<li>Treating list overlap as proof the owner is motivated.<\/li>\n<li>Matching only by address and merging different units or owners.<\/li>\n<li>Matching only by phone and assuming a shared number identifies one person.<\/li>\n<li>Overwriting source dates and prior notes with the newest file.<\/li>\n<li>Letting one clean duplicate erase a do-not-call flag.<\/li>\n<li>Calling before checking current listing status and campaign rules.<\/li>\n<li>Measuring source quality with raw rows, attempts, or summed list totals.<\/li>\n<\/ul>\n<h2 id=\"frequently-asked-questions\">Frequently asked questions<\/h2>\n<h3 id=\"what-is-a-seller-prospecting-list\">What is a seller prospecting list?<\/h3>\n<p>A seller prospecting list is a source-aware group of homeowners with enough identity, context, eligibility, and next-action data to support useful outreach. It is not a file of unverified names and phone numbers.<\/p>\n<h3 id=\"how-many-people-should-be-in-a-seller-prospecting-list\">How many people should be in a seller prospecting list?<\/h3>\n<p>Size the active queue from the daily meaningful-conversation target and the agent&#039;s own unique-person attempt-to-conversation rate. Keep enough eligible inventory for the source&#039;s refresh cycle, then replenish it throughout the 250-workday plan. Do not use a universal row-count benchmark.<\/p>\n<h3 id=\"should-multiple-seller-lead-sources-be-combined-into-one-list\">Should multiple seller lead sources be combined into one list?<\/h3>\n<p>Combine sources in a working table to resolve identity, history, and suppression. Keep calling lists separate by source or operating purpose so conversations and reporting retain context.<\/p>\n<h3 id=\"what-fields-belong-in-a-real-estate-seller-lead-list\">What fields belong in a real estate seller lead list?<\/h3>\n<p>Preserve person and property identity, complete address and unit, each phone, source dates, observable context, status checks, suppression and consent records, last outcome, and next action. Keep raw-file provenance in a source ledger.<\/p>\n<h3 id=\"how-often-should-seller-prospecting-lists-be-updated\">How often should seller prospecting lists be updated?<\/h3>\n<p>Use a source-specific refresh rule. Listing status and owner-marketed records need faster checks than long-term farm records. Recheck volatile facts before the call block.<\/p>\n<h3 id=\"can-an-agent-call-a-homeowner-found-in-public-records-an-expired-listing-or-a-fsbo-ad\">Can an agent call a homeowner found in public records, an expired listing, or a FSBO ad?<\/h3>\n<p>The public availability of a record does not automatically authorize a listing solicitation. Check the current federal, state, local, brokerage, data-license, consent, Do Not Call, active-listing, and campaign-specific rules. Use qualified legal guidance for the actual campaign.<\/p>\n<p>Build the source system first. Then open the <a href=\"https:\/\/realdialer.com\/dialer\/\">RealDialer calling workspace<\/a> with a named, reviewed list and a clear reason for every conversation.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Build a clean seller prospecting list from multiple sources. Normalize records, preserve context, resolve duplicates, carry DNC flags, and prioritize calls.<\/p>\n","protected":false},"author":1,"featured_media":75,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_realdialer_meta_description":"Build a clean seller prospecting list from multiple sources. Normalize records, preserve context, resolve duplicates, carry DNC flags, and prioritize calls.","footnotes":""},"categories":[4],"tags":[],"class_list":["post-74","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-real-estate-prospecting"],"_links":{"self":[{"href":"https:\/\/realdialer.com\/blog\/wp-json\/wp\/v2\/posts\/74","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/realdialer.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/realdialer.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/realdialer.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/realdialer.com\/blog\/wp-json\/wp\/v2\/comments?post=74"}],"version-history":[{"count":2,"href":"https:\/\/realdialer.com\/blog\/wp-json\/wp\/v2\/posts\/74\/revisions"}],"predecessor-version":[{"id":248,"href":"https:\/\/realdialer.com\/blog\/wp-json\/wp\/v2\/posts\/74\/revisions\/248"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/realdialer.com\/blog\/wp-json\/wp\/v2\/media\/75"}],"wp:attachment":[{"href":"https:\/\/realdialer.com\/blog\/wp-json\/wp\/v2\/media?parent=74"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/realdialer.com\/blog\/wp-json\/wp\/v2\/categories?post=74"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/realdialer.com\/blog\/wp-json\/wp\/v2\/tags?post=74"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}