Lead details
A lead tells you things in more than one place. The form captures what it asks, such as budget and timeline. Later the same person may give a different budget on a phone call, say they are paying cash on WhatsApp, or move their timeline in an email reply. Lead details keep all of it for each lead, one entry per question:- the current answer, which is the most recent thing they said;
- where they said it: the form, a phone call, a website chat, a text, a WhatsApp message or an email reply, with a reference to that conversation;
- when they said it;
- their exact words;
- the earlier answers it replaced, newest first.
Property landing-page forms
Property forms collect required first name, last name, email, phone (with a country selector), and Buyer / Broker on the first screen. The contact is saved there. The second screen asks for project-specific budget, timeline (0–3, 3–6, 6–12 months, or Just researching), and usage (primary residence, investment, or secondary home). Brokers also see an optional Which firm? question there, shown only for that first-screen answer, and they can leave it unanswered. These answers complete the same lead. Buyer / Broker uses the shared form control, with no answer selected in advance. If a field has invalid options, the form displays a generic configuration error; the omitted question names are available in thedata-erdo-form-error-fields attribute so the configuration can
be corrected. The remaining contact fields still save.
Budget includes Prefer not to say. That choice is recorded explicitly and
never turned into a numeric budget. When creating a development, Erdo takes the
starting price and currency from your supplied documents or the official site
and derives budget bands from them. Every angle uses the same bands. When no
source states a price, the form leaves the budget question out until you supply one.
The phone screen shows an optional unchecked consent checkbox for US/Canada
numbers and a disclosure for other countries, with the supplied privacy-policy
and terms links. Approved business policy URLs are used when configured; otherwise
the hosted form links Erdo AI, LLC’s privacy policy and terms. Leaving the second screen does not erase the saved contact.
What is recorded
From the form: every question your form asks. That is every column in your leads dataset’s declared contract that has no semantic role. Names, email, phone, consent, attribution columns (UTMs, click ids, the page) and the qualification fields are not answers, so they are not recorded as details. Each submission’s answers are recorded when it is captured. From conversations: calls, website chats, text and WhatsApp threads, and email replies linked to a lead. Erdo records only what the lead stated, in words that carry the value on their own:
Their age, health and other sensitive traits are never recorded. Nor is a
request such as “can I book a viewing?”: the timeline already shows it.
Each detail from a conversation passes three checks before it is kept:
- The model reading the conversation is told to transcribe what the lead said, not to conclude anything from it.
- Code confirms the quoted words appear in one of the lead’s own messages, and that every number in the value appears in the quote.
- A second, separate check reads only the quote and the question it answers, and confirms the quote actually states that answer.
Questions and keys
Each question has a key, such asbudget or move_in_timeline, a label and a
one-sentence definition. A form column’s key is its name. When a lead answers a
question your form asks, the conversation’s answer uses the form’s key, so both
answers sit under the same question. A new question gets a new key, and later
conversations reuse it.
Reading details
Details are part of every lead read:- REST:
GET /v1/datasets/{dataset}/leads/{lead}returnslead.details. - MCP:
erdo_get_leadreturns the same. - CLI:
erdo leads get <dataset> <lead>prints a what they told us table first.
source_kind is form, phone_call, widget_conversation, sms, whatsapp
or email_reply. For a form answer, source_ref is the capture it came from.
It is row for an answer read from a lead captured before lead details existed.
Those older leads keep only the answer their row held when details were turned
on. Any answer a later submission had already overwritten cannot be recovered.
Resolving stored lead references
When an app stores lead references outside Erdo, it can resolve many of them after merges in one call.POST /v1/datasets/{dataset}/lead-reference-resolutions accepts
{"lead_refs":[...]} (up to 1,000 UUIDs or 22-character references) and
returns resolved, not_found, and invalid entries. The same operation is
available as erdo_resolve_lead_references and
erdo leads resolve <dataset> <ref...>.
The follow-up engine reads them
A lead playbook decides each lead from its details: the most recent answer to each question, with where and when it was given. The concierge that texts or calls the lead is briefed from the details as they are when the message goes out, so an answer given after the decision was made is the one it uses.Merging leads
When two leads are merged (see Lead identity), the absorbed lead’s details move to the survivor. The most recent answer to each question across both becomes current. The merge response’sdetails_moved says how many
moved.

