TL;DR

A contact is the persistent profile of a person you have talked to, gathering their details and conversation history in one place.

Key Points

✓

A contact represents a known individual, distinct from an anonymous [[website-visitor]] who has not yet been identified or engaged.

✓

In tools like Intercom, a contact has a role - a lead (engaged but not signed up) or a user (an authenticated customer) - while unknown browsers stay visitors until they start a conversation [1][3].

✓

Contact records accumulate identity fields plus interaction history; HubSpot's default contact properties include name, email, phone, lifecycle stage and original source [2].

✓

Live-chat widgets create or enrich a contact on first message, often via [[visitor-identification]] and an optional [[pre-chat-form]] that captures name and email.

✓

Unlike a CRM lead - an isolated, unqualified record - a contact is a structured profile linked to conversations and other records [4].

✓

A contact differs from a [[conversation]]: one contact can own many conversations over time, each made up of individual [[chat-message]] exchanges.

Visitor, contact, lead, or user?

These terms describe the same person at different stages of engagement. An anonymous Website Visitor browsing your site is not yet a contact. In Intercom's model, the visitor becomes a contact with a lead role the moment they start a conversation or reply to an outbound message, and that lead becomes a user once they sign up or log in ^[1]. Salesforce draws a sharper line: a lead is an isolated, unqualified record - "a virtual fishbowl of business cards" - while a contact is a structured person associated with an account and linked to related records like cases and opportunities ^[4]. The practical takeaway for founders is that a contact is a person you can now address by name, track over time, and follow up with.

What a contact record holds

A contact is more than a name and email - it is a profile that compiles data from every touchpoint into one view. HubSpot's default contact properties span basic identity (first name, last name, email, phone), professional details (job title, company, location), activity timestamps, and marketing data such as lifecycle stage and original source ^[2]. A good live-chat tool enriches the contact automatically: when someone first messages, Eloqra captures page URL, device, browser, OS, and IP-based geolocation alongside any UTM Parameters on the visitor record, and a Pre-Chat Form can collect name and email up front. The result is that an operator sees who they are talking to and where they came from before replying.

Why contacts matter for support and growth

Treating people as durable contacts rather than disposable chat sessions is what lets a small team build relationships at scale. Because a contact persists, every Conversation and Chat Message attaches to the same profile, so context survives across visits and an operator never starts from zero. Contacts also feed downstream work: Lead Capture and Lead Qualification depend on having an addressable record, and Personalization becomes possible once you know who someone is. Eloqra keeps this deliberately lightweight - it identifies a visitor, captures their context, and forwards the conversation to the owner on Telegram - without the heavier CRM machinery of segmented lists or scoring. For an indie hacker, that is often exactly enough to turn chats into customers.

Sources & References

How do visitors, leads and users work in Intercom? ↗

HubSpot's default contact properties ↗

Contacts | Intercom and Fin Developer Platform ↗

Salesforce Leads vs. Contacts: Everything You Need to Know ↗

Last updated: June 25, 2026

Related Terms

Website Visitor

A website visitor is any person browsing a site where a live-chat widget is installed, tracked as an anonymous session until they send a message or identify themselves. In Eloqra, the visitor is the end-user on the other side of the chat bubble, distinct from the operator who answers from Telegram.

Visitor Identification

Visitor identification is the process of attaching context to an otherwise anonymous chat visitor by capturing technical and behavioral signals when they first message. In Eloqra it means recording page URL, device, browser, OS, and IP-based location alongside the conversation, plus optional name and email from a pre-chat form.

Pre-Chat Form

A pre-chat form is a short form shown before a live chat starts that asks the visitor for a small amount of identifying information, typically their name and email. In Eloqra it is the optional collectVisitorInfo step that gates the chat input until the visitor submits their details.

Lead Capture

Lead capture is the process of collecting a prospect's contact details (typically name, email, or phone) at the moment they show interest, so a business can follow up and move them through the sales funnel. On a website it happens through forms, pop-ups, chatbots, and live-chat conversations.

Conversation

A conversation is the threaded exchange of messages between a single website visitor and a project's operators, grouped as one unit with a status and unread counters. In Eloqra it is the container that holds every message, the visitor's captured context, and the assigned operator.

UTM Parameters

UTM parameters are tags appended to a URL's query string (utm_source, utm_medium, utm_campaign, utm_term, utm_content) that record which marketing campaign, channel, and source sent a visitor to your site. The acronym comes from Urchin Tracking Module, the analytics software Google acquired in 2005.

Collect testimonials that build trust

Eloqra gives you a lightweight live chat widget that routes every visitor message to your Telegram — free while in early access.

Get Started Free