Skip to main content
Enformion looks up US consumer public records for leads who supplied an email address or a supported North American phone number. An inbound caller can be enriched using caller ID alone; an email address is not required. Connect Enformion with your galaxy_ap_name and galaxy_ap_password credentials using Connecting integrations. Both actions are available to agents and scripts through the connected organization’s integration.

​
Look up a person

Supply email, phone, or both; name is optional and cannot identify a person on its own. Phone-only enrichment uses reverse-phone Caller ID. With an email, the lookup verifies contact records against the supplied identifiers and can fall back to email lookup and then reverse-phone lookup. The result reports found and, for a match, matched_on (email or phone). Available details include name, age, address history, phone numbers, and relatives. An email returned for a phone match comes from the provider’s record; Erdo does not invent one. A phone match is evidence tied to that number, not proof that the person speaking currently owns it.

​
Find currently owned properties

With a phone alone, Erdo requests a contact record and checks that the record contains that phone and a person ID. It searches properties by that ID and returns only parcels listing that person as a current owner. It never falls back to a name search or uses Caller ID to infer property ownership. found=false means no verified person or currently owned property was found. It does not prove that the person owns no property.

​
Input and result handling

  • Phone-only lookups require a ten-digit NANP number, optionally prefixed with country code 1; formatting such as spaces, parentheses, and hyphens is accepted.
  • Invalid supplied email addresses are rejected, even when a phone is also supplied.
  • An unsupported optional phone is omitted when a valid email is present, so it does not break the email lookup. Without a valid email or supported phone, the action returns an input error before contacting Enformion.
  • Provider errors are distinct from found=false; automations should record failures separately from searches that completed without a match.
These records provide context for a lead. They are non-FCRA data and must not be used for eligibility, credit, or tenancy decisions.