Dashboard · Audience
Contacts
Known visitors who shared their contact information, plus the people you imported or synced from your CRM. A contact is a person, not a browser: it links to every visitor record that turned out to be them, and it is what the funnels, the ROI page and the CRM sync count.
Where contacts come from
Every contact carries a Source, the surface that captured them, and a First touch, the campaign that brought their first visit. The two often differ: someone who arrived from a paid ad, browsed for days and then left their email in the chat has source Meeton Chat and first touch Paid ads, which is a conversion the ad platform never saw.
| Source | Meaning |
|---|---|
| Meeton Chat | Converted in the Meeton widget: left their details in the chat. |
| Meeton Calendar | Converted in the widget: booked a meeting from the calendar. |
| Meeton Library | Converted in the widget: left their details in the Library. |
| Website form | Captured from a form on your own site. Not a Meeton widget conversion, though it may be Meeton-assisted. |
| Self-signup | Signed themselves up directly. |
| CSV import | Imported from a file. |
A first touch with no campaign parameters cannot tell organic search, a referral, a bookmark or an AI assistant apart; that needs the first session's referrer, which lives on the visitor. Traffic Insights breaks those out and lists the contacts behind each one.
The table
@domain. Stage, source, company, owner (Assigned to me), intent level, created date, and meetings: All meetings, Booked via Meeton or Has a meeting. Meeton assists and High intent are one-tap chips.Status, owner and deals
A contact's status moves from Active through Contact, Meeting booked, Deal open and Customer, or ends at Lost or Disqualified. Disqualify with a reason: Competitor, Already a customer (before first contact), Spam / Reverse sales, Test, or your own. A disqualified contact leaves every funnel; the export records who disqualified it and when, and whether it was your team, the CRM sync or automatic.
The Owner is a teammate: Assign to me, pick someone, or unassign. Owners are a dashboard field for filtering and notifications; the CRM has its own.
Deals
A contact's record has a Deals card. Deals synced from your CRM appear automatically and are read-only here: the CRM is the source of truth, so edit them there. You can also Add deal by hand, with a status (Open, Won, Lost), an optional amount and a won or lost date. A won deal makes the contact a Customer, counted as a lead and a win in ROI. Self-reported deals are never sent to a CRM.
Someone who was already a customer before Meeton met them is not a deal. Disqualify them as Already a customer instead, or they inflate your win counts.
The contact record
Export summary
Export summary writes a one-page PDF for whoever takes the meeting: who they are, where they came from, what they read, what they asked. The timeline itself stays in the dashboard; nothing is pushed to your CRM.
Import and export
Import CSV takes a file with last name, first name, email, job title, company and the other profile fields. The preflight says how many new contacts will be created and how many existing ones will have their fields and CSV data overwritten; the result reports imported, overwritten, skipped and failed rows. Imported contacts have source CSV import and can be nurtured by Meeton Email like any other.
Export CSV writes the current filter with every column the dashboard knows: identity and company fields, source and first-touch campaign, created and updated dates, disqualification details, original and latest conversion source, Salesforce and HubSpot sync status, form submission and meeting counts, deal status, amount, currency, closed date and source, latest meeting date, engagement totals, intent, persona and the number of linked visitors. Other CRMs explains importing it elsewhere.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| A contact shows no chats or page views | They were imported or synced from the CRM and have never visited with a recognisable browser | Normal. The record fills in the moment a linked visitor identifies with the same email. |
| Source says Website form but you expected Meeton Chat | The chat happened, but the details were left on your own form afterwards | Check the Meeton Assists column: the chat is credited as an assist. Source is the capturing surface, not the first touch. |
| A deal cannot be edited | It came from the CRM | Edit it in HubSpot or Salesforce; the change syncs back within a few minutes. |
| Pipeline value is missing in Sales Insights | No default deal currency, or deals in several currencies | Set the default currency from the link under the KPI; keep CRM deals in one currency where you can. |
| Import skipped rows | Rows whose email already existed were skipped, or a required field was empty | The result lists each count. Re-import with the fixed rows only; existing contacts are overwritten, not duplicated. |
Frequently asked questions
Does Meeton create deals in my CRM?
No. CRM sync writes contacts and activities only. Deals flow one way, from the CRM into the contact's Deals card, so that won deals count in ROI.
What makes a contact Meeton-assisted?
At least one Meeton conversion event: a chat, a form submission in the widget, an ad click, a calendar booking, a download or a call. The Meeton assists only toggle on the Insights pages uses the same test.
Can two contacts be merged?
Contacts are keyed by email, so two emails are two contacts. If the same person used two addresses, keep the one your CRM uses and disqualify the other as Test or with your own reason.
Where is the email sequence a contact is in?
On the record's Emails tab, and in the Emails column of the table. The queue itself, across all contacts, is the Emails tab in the sidebar.