Email to profile resolution

Reverse Contact finds a LinkedIn profile that matches an email address. A Beam agent reads records that carry an email but little else, sends the lookup where your rule permits, and reads the profile the service returns. It writes the found profile link and details back to the record and dates the enrichment. Lookups that return no match, several possible matches, or a profile that conflicts with existing data are set aside for a person to confirm. Routine, confident matches are saved on their own, so teams work from fuller records without researching each contact by hand.

Contact field enrichment

Reverse Contact returns profile details tied to a resolved email. A Beam agent reads the returned data, applies your rule for which fields to trust and fill, and updates the contact with role, company, and other details the service provides. Fields that already hold a different value, or data that looks stale, are not overwritten silently but flagged instead. Records where the new details contradict what sales or support already knew are routed to a person to reconcile. Routine gaps are filled on their own, so contact records stay useful without anyone chasing missing information for each lead.

Match confidence checks

Reverse Contact reports how sure it is that an email and profile belong together. A Beam agent reads that confidence signal, applies your rule for the threshold a match must clear, and only saves details that meet it. Matches above the line are written to the record and tagged with their source, while weaker ones are held rather than trusted. Borderline results, or matches on senior or sensitive contacts, are routed to a person to check before use. This keeps enriched data dependable, so teams are not acting on a guessed profile that quietly turned out to be the wrong person.