Begin with the saved record
Before requesting more information, read the details already saved to the workspace and the latest Activity. You may already have the answer in a note, or the business situation may have changed enough that another lookup is unnecessary.
Opening a saved snapshot is free. A new reveal or re-reveal is a separate action. Keeping that distinction clear lets you review a neighborhood without treating every return to a home as a reason to purchase data again.
Understand what Stale means
PixelKnock marks contacts Stale when at least 30 days have passed since the workspace’s last reveal or refresh. The label offers a reason to review age; it does not prove that the current number is wrong or that another request will find new information.
When Re-reveal Contacts is available, consider the task before using it. A date stamp describes when the workspace retrieved a result. It does not guarantee the original source was updated on that day or that each returned association is current.
Use a decision table before spending
| Situation | First step | Is another reveal necessarily useful? |
|---|---|---|
| Need the last conversation note | Read Activity | No |
| Unsure whether the business serves the home | Confirm service coverage | Not until that question is resolved |
| Saved channel was reported wrong | Read the status and current context | Possibly, but no replacement is guaranteed |
| Old details affect a current task | Identify the exact missing answer | Consider the quote and remaining uncertainty |
A fictional example: a rep revisits a home after a month to prepare a requested discussion. The note already contains the promised topic, but the saved contact channel has a documented problem. That is a clearer reason to evaluate a new request than refreshing every old record simply because a date changed.
Use the quote instead of an assumption
Review the credit information shown for the action. Do not assume that a repeat is free just because the home exists in your workspace, another teammate viewed it or a provider has seen it before. Reuse rules depend on the applicable period and supplier charge; the current quote is the useful decision point.
A paid request can still leave some fields unavailable. After a completed reveal, read the returned result and record the remaining question if it matters. If the action is uncertain or still resolving, follow the app’s recovery state instead of creating repeated requests to force a result. A useful refresh improves the basis for your next decision; it does not promise a reachable contact.