> ## Documentation Index > Fetch the complete documentation index at: https://docs.dispoiq.app/llms.txt > Use this file to discover all available pages before exploring further. # Skip tracing and contact enrichment > Prepare lookup inputs and review contact results and pending charges. Last updated: October 8, 2026. Check the person or company, correct the lookup inputs, then review the returned details before saving or using them. Skip tracing searches for contact information associated with a subject. A returned phone number does not prove ownership, decision-making authority, current contactability or permission to send texts. This guide describes the Investor Map lookup and Contacts import workflows where activated for an authorized owner or admin. Availability depends on your workspace and the actual controls offered. It does not promise a particular result or introduce a price, refund rule or data license. ## 1. Prepare the lookup inputs Use the actual person or business associated with the property, rather than a guessed decision-maker. Similar names and shared addresses can produce wrong matches. | Subject | Information to check | | - | - | | Person | First and last name, property street address, city, state and ZIP code where known. The import workflow needs a usable first name, last name, property address, city and state to build an individual lookup. | | Company | Actual company name and the relevant state. Check the property and mailing details instead of assuming a registered agent or mailing recipient is the owner or a decision-maker. Company lookup support depends on how the workflow recognizes and supplies the company identity. | Mapping an **Entity name** column in a CSV does not by itself establish that a company lookup will use it. Check the offered import workflow and supported inputs before requesting enrichment. Do not substitute an invented person's name to force a lookup. If the lookup, import action or input you need is unavailable, contact **[support@dispoiq.app](mailto:support@dispoiq.app)** with the workspace and the existing result or import reference. Support will check your authority, the available workflow, supported person or company inputs and recorded outcome, coordinating authorized technical review when needed. Keep the lookup result separate from its Contact-save or import-processing result; a completed lookup is not confirmation that a Contact was saved. Available results can include owner, address, phone and email associations. They can be wrong, old or nonpublic; review attribution before relying on them. A returned email address is information to review, not an enabled customer email-sending feature. DispoIQ's application-notification emails to users are a separate function. Do not infer a missing decision-maker or overwrite an actual company identity merely to obtain a match. ## 2. Look up a result in Investor Map Open a property or owner result and check its identity and address against the transaction shown. See the [Buyer Search & Data Accuracy guide](/help/buyer-search) for the difference between transaction history and verified ownership or investment intent. The individual result offers two distinct actions where available: * **Skip trace** requests contact details for the selected subject. A lookup result alone does not mean a Contact has been saved. * **Save contact** can request the lookup and then save or reuse the attributable, usable contact details. Wait for the saved confirmation and check the resulting Contact before relying on it. A result may contain several numbers or attributable people. It may also return no usable phone, an ambiguous identity or a suppressed number. Those outcomes can prevent saving a usable Contact. Do not create a duplicate or change the name to route around a block. A saved or technically messageable status is not messaging consent. ## 3. Enrich eligible rows after a Contacts import Open the import's result report and review rows missing a phone. Where offered, **Skip trace** queues eligible rows for background processing. It does not automatically enrich every record in the file. Rows without sufficient lookup information cannot produce a supported request. Review the results as processing progresses. A usable returned number can send the row back through the Contacts import process, including its matching and suppression checks. Rows can remain without a usable phone even when a lookup was performed. Read the outcome rather than assuming that an attempted lookup created a Contact. If the report shows work in progress, paused work or a billing-review state, follow the action actually offered. Do not repeatedly submit a pending lookup to force a result. A **Resume skip tracing** control, where offered, is different from starting a fresh request. Background processing has no completion deadline promised by this guide. Contact [support@dispoiq.app](mailto:support@dispoiq.app) for help with file preparation, mapping and import-result checks. ## 4. Review the accepted charge and the wallet status Check the billable event and customer rate disclosed and accepted for the lookup before starting paid work. A displayed row count or a source's match is not a quoted dollar price. New paid work requires the funding and authorization applicable to that operation. A wallet reservation is a hold, not a final charge. A billable match can exist even when its returned numbers are missing, unusable or suppressed; whether that match is chargeable depends on the accepted schedule. Conversely, a confirmed no-match or confirmed rejection before paid work may release a hold under the applicable route's rules. Do not assume that every unsuccessful, failed or unfinished operation is free, chargeable or refundable. An unknown outcome may remain pending for review. A held amount and a finalized charge are different records; neither a failed save nor an empty Contact list establishes what was spent. Check any available records, confirmations or operation references. Contact support if charge or hold evidence is missing, or if the result and charge do not agree. Valid, already-authorized final charges remain payable at the accepted rate; this guide does not authorize an arbitrary card charge or promise automatic wallet funding. The [Usage Pricing & Messaging Fees](https://docs.dispoiq.app/help/usage-pricing) and [Wallet & Billing History](https://docs.dispoiq.app/help/wallet-billing) explain holds and settlement. Billing-error corrections, mandatory rights and expressly owed refunds remain available under the applicable agreement. The feature-specific offer you expressly accept must identify the lookup's billable event and charges, including how no-match, unsuccessful, repeated and pending outcomes affect them. Before another paid attempt, confirm the existing result, any held or settled amount and the offer for the proposed action. If the displayed estimate or charge is unclear or conflicts with the offer, ask support to review it before authorizing more work; do not infer your price from an at-cost label or another source's fee table. Support records lookup and billing questions, checks workspace authority and compares the accepted event and rate with available request, result, hold and settlement evidence. We will coordinate authorized review, explain the confirmed or unresolved outcome, release a reservation established to be unincurred under the applicable event rules, and correct verified billing errors. A confirmed result with no usable Contact and an uncertain lookup are different outcomes; neither alone establishes a universal free or charged result. This process promises no detailed history screen, automatic recovery, refund-processing time or completion deadline. Valid already-authorized final charges are settled in full at the accepted rate even if they exceed a reservation or remaining wallet funds and leave a negative balance. That does not permit new unfunded paid work. A pending hold alone is not a final debt; a negative available-funds figure can include other outstanding holds. Card top-ups depend on an available route and a separate funding instruction you expressly accept with its triggers, amounts and limits. Saving a card alone supplies no arbitrary-charge or unlimited-retry authorization, and pending payment is not confirmed wallet funding. Funding an existing charge does not create a second usage charge. Billing-error corrections, mandatory rights and all expressly owed refunds remain available under the [Subscription, Cancellation & Refund Policy](https://docs.dispoiq.app/policies/billing-refunds). ## 5. Validate the result before relying on it Treat enrichment as a lead for verification. A name, address or phone association may be incomplete, outdated, shared or incorrectly attributed. A company's principal, agent or associated person is not automatically authorized to sell the property or make investment decisions. A phone label does not establish that the number still belongs to that person. Compare the result with information you are lawfully entitled to use. Keep the original source and the corrections you make. Do not represent a lookup as verification of title, identity, creditworthiness, eligibility or a person's willingness to buy. Results are not guaranteed to be complete, current, unique or accurate, and an empty result does not prove that no contact information exists. For a suspected wrong match, stop relying on the affected details and ask support about the available correction process. Include enough information to identify the workspace and affected result; request a secure route before sending sensitive material. This guide does not promise that a correction to your record changes every upstream source. ## 6. Keep permission and suppression separate from enrichment A sourced phone number, public record, saved Contact, do-not-call indicator or registration approval is not permission to text. Before any customer-initiated SMS/MMS, obtain and retain the recipient's prior express written permission for the identified sender, number and message subject. A recipient-initiated text may permit a directly relevant response in that same conversation only where applicable requirements permit; it does not authorize a recurring campaign or unrelated promotion. Honor opt-outs, wrong-number reports and applicable suppression requirements. Screening depends on the information returned and the controls actually enabled. An absent or negative registry indicator is not a legal clearance, and an unknown indicator is not proof that a number was checked. Do not delete suppression history, reimport the number or create another Contact to bypass a restriction. Messaging is limited to eligible routes and destinations actually offered for the United States and Canada. Follow the [Messaging & Communications Policy](https://docs.dispoiq.app/policies/messaging) and contact [support@dispoiq.app](mailto:support@dispoiq.app) for consent-record and opt-out questions before sending. ## 7. Preserve data-use and export restrictions Your uploaded records and licensed enrichment results can carry different rights, even when combined in one Contact. Paying for or saving a result does not transfer ownership or permit unrestricted export, redistribution, resale or independent reuse. Process the information only within your authority, applicable notices, source restrictions and any agreed processing terms. See the [Buyer Data & Permitted Use Policy](https://docs.dispoiq.app/policies/buyer-data) and [Data Retention, Export & Deletion Policy](https://docs.dispoiq.app/policies/data-retention). The export-request window after paid access ends does not extend normal paid access or expand the license for sourced information. A future change in permitted processing must satisfy the applicable agreement, notices, authorizations and individual rights; this guide supplies no blanket permission for a new use. DispoIQ must maintain the applicable source authority and supply any restrictions or required downstream terms through an appropriate agreed channel before the affected use. Required permissions, notices and rights controls must precede the delivery or reuse they cover. Information protected by an earlier no-sale or incompatible disclosure commitment must remain restricted until the proposed use is consistent with that commitment and the required lawful basis, notices, permissions and rights controls exist. Publishing this guide does not establish that those steps are complete or cancel an earlier protection. Combining source results with uploaded records does not bypass those limits or the customer-provided information, consent and future-use safeguards in the [Privacy Policy](https://docs.dispoiq.app/policies/privacy). For a wrong association, correction, withdrawal or restricted-use question, contact **[support@dispoiq.app](mailto:support@dispoiq.app)** with the affected result or import reference. Support will record the request, check authority and scope, coordinate appropriate authorized technical or source cooperation, and explain the outcome or any justified limits. Keep affected use paused when a required permission or restriction is unresolved. A source or export restriction does not remove a non-excludable individual privacy right, and correcting your record does not promise every source or recipient copy changes. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.