# Refresh contact details {/* AUTO-SYNCED SOURCE: this page lives in apps/app/src/modules/db-leads/docs/ and is mirrored into the docs app by `bun sync:module-docs`. Edit it in the module, not in apps/docs. */} A grown book has dead phone numbers and stale addresses. Instead of guessing, ask the person: the **data request** sends a personal link they use to check their own details. What comes back lands directly on the record. ## How it works In the contact panel the **Data request** section sits right below the contact details. The button sends an email in your office's name, with your sender and your branding. The link leads to a plain page on your office's own address. It asks for email (required), phone, address, and one non-binding question: "Are you considering a sale in the foreseeable future?" with four answers from "Yes, currently" to "No". The details land on the contact. In the panel you see per request what is open and what has been answered. Somebody who has already confirmed three fields will answer the fourth. If the selling question came first, a share of people would drop out there, and then even the contact details you would have got without any pushback are missing. ## The consent At the end there is an explicit consent to being contacted. Its wording is **stored verbatim** and moves into your workspace's central contact policy as a permission. This is not decoration: a book with documented consents is legally a completely different thing from one without. The notice about the right to withdraw is included, and the path to it genuinely exists, through the unsubscribe link in every promotional message. If a person has objected to being contacted, no request goes out. The gate sits in the sending path, not in the tool, and therefore applies to every message the platform sends. ## Reminder and withdrawal If no answer arrives within seven days, **one** reminder goes out. Nothing after that. You can revoke an open request. The link becomes invalid immediately. Only shown once a minimum number of requests has been sent. A rate out of three requests is not a rate, it is chance. ## Requirements The contact has an email address. Without it the button is missing. You hold the **Edit contacts** permission (`db-leads.update`). The contact has not objected to being approached. ## Further reading Where requests sit on the contact. Whatever you learn about the property, record it there. Trigger data requests automatically.