Answers to contacts & warm leads
The best lead data is what people tell you themselves. A poll vote, a quiz score or a form answer can be saved straight onto the contact who gave it. You can then segment on it, branch a journey on it, or see it on their profile. Engagement adds up into a score, and the Warm leads tab ranks everyone by it.
Save an answer to a contact field
In the studio, select a poll, rating, quiz, RSVP or form block. On the Content tab, the Data section has a Save answer to contact field setting. On a form, each question has its own. Pick one of the list's existing fields or type a new name, such as plan_interest.
When a recipient from your contact list answers, their answer is written to that field on their contact:
| Block | What's saved |
|---|---|
| Poll | The option they voted for. |
| Rating | The number they picked. |
| Quiz | The number of correct answers in the field you named, and yes or no in the same name plus _passed (for example quiz_score_passed). |
| RSVP | yes or no. |
| Form question | The answer. Choices must be one of the options you wrote, a group of checkboxes is saved as a comma-separated list, and a single checkbox saves yes when it's ticked. |
A few rules keep this safe:
- Only known contacts. Answers are saved only when the email went to a contact list linked as the project's audience (in the studio's Data panel), and only for that recipient's own contact. Anonymous answers, from a forwarded email or a published landing page, are never saved.
- Blank never overwrites. An empty answer leaves the field as it was. A later answer to the same field, from a later send or another block, replaces the earlier one.
- Never the email column. A field can't be named
email, and values are capped at 500 characters. - A full list. If the list already has the maximum number of fields, a new field can't be added. The answer is skipped, and the project's Responses tab shows a warning listing the field. Remove a field you don't use, or save to an existing one.
Answers are saved before journeys react to the same answer, so a journey triggered by a poll vote can already branch on the saved field.
Engagement score
Every contact has an engagement score built from what they do with your emails: opens, clicks, answers, RSVPs and purchases, with bigger actions weighted more. It fades with a 30-day half-life, so it reflects recent interest. The segments page has the exact weights.
The score drives hot-lead alerts, the warm-leads ranking, and the engagement score sent to HubSpot and Pipedrive.
The Intelligence card
Each contact's profile (click a contact in any list) opens with an Intelligence card:
- the engagement score now, its change this week, and a 90-day trend line;
- the best send hour, in your time zone, based on when they open (it needs a handful of opens first);
- their last interaction;
- revenue from emails, and their store orders shown separately if you've connected Shopify or WooCommerce;
- Captured from answers: every field saved from an answer, with the email it came from and the date. A field you've since edited by hand no longer shows its old source.
Warm leads
Contacts → Warm leads ranks your most engaged contacts across every list, highest score first. Each row shows the score, the change this week, the last interaction and the list. Filter to one list with List, and click a contact to open their profile. Load more fetches the next page.
AI connectors can ask for the same ranking: find_contacts with sortBy: "engagementScore" returns a list's contacts by score. See the tool reference.
Privacy
Saved answers are ordinary contact fields, and the record of which email each came from is stored with the contact. Both are included in your account data export and deleted with the contact.