Contacts overview

Anyone the agent captures structured info from. The capture happens via the Collect Leads action — the agent decides when to ask based on conversation context (a hot lead asking a buying question, someone requesting a callback, etc.) and pushes the result into your contacts list.

Contacts isn’t just a CRM mirror. It’s the agent’s own log of who reached out — useful even if you sync the data into Salesforce or HubSpot.

The Leads page lives at /chatbots/[id]/leads in the agent sidebar. A date-range picker at the top with presets (7 / 14 / 30 / 90 days) plus a calendar popover for custom ranges. Below, every lead in the window as a card.

Each card shows:

• Name + email (always)
• Company + phone (when captured)
• Temperature pill — hot / warm / cold, color-coded
• Score — numeric, derived from conversation signals

Three buckets, each tied to conversation signals:

• Hot — explicit buying intent, demo requests, pricing questions with timeline.
• Warm — investigating seriously: deep product questions, comparing alternatives, asking about integration specifics.
• Cold — early interest: curiosity questions, quick info requests, anonymous browsing.

The Configure button on the Leads page opens the form-field editor. You decide which fields the agent should try to collect: name and email by default, plus optional company, phone, and any custom fields you add.

The agent doesn’t robotically ask for every field — it works them into the conversation when natural. You can also mark fields as required (the agent will keep asking until they’re captured) or optional (the agent will move on if the user doesn’t volunteer).