Review the contact context before your next move.

Keep the property and the person connected.

A contact field is more useful when you know which home led you to it. PixelKnock displays available details in the property record, so you can review the home and returned people together.

Start with an area your business can serve and a reason to research that home. A returned contact record does not establish a homeowner need or interest.

Distinguish a person from a usable channel.

A returned person may have an email, a phone number, both or incomplete information. Phone eligibility and known suppression or format gates can affect what the app makes available. Do not treat a missing phone field as proof that no phone exists.

Contact enrichment can return email-only people. Review the current credit information: returned property and person units can use credits even when no usable phone number is available.

Use a simple research decision.

Before another request, ask whether the missing information would change your next action. If the home is outside your service area, more contact fields may not make the task useful.

• Check the intended property.
• Read the returned person and channel information.
• Note any question that requires confirmation.
• Choose whether to continue, pause or stop.

Keep outreach and recordkeeping clear.

Use your own phone or dialer and the rules that apply to your organization and contact method. PixelKnock does not call, text or email homeowners for you. Data availability and app phone indicators do not establish permission to contact.

After an actual attempt, record what happened in Activity. Save enough context to make the next decision understandable.