What DeliChat does
DeliChat identifies who is on your website, scores how interested they are and tells your team when someone is worth a conversation. Every other part of the system reads from it.
The short answer
DeliChat resolves anonymous website traffic into named, company-attached leads where the law and the visitor’s consent allow, keeps a running intent score for each person, and flags hot moments in real time. It is the foundation the outbound and CRM tabs build on.
Anonymous visitor identification
Resolves anonymous traffic into named, company-attached leads with no form fill, within the limits of the law and the visitor’s consent.
Live intent scoring
Page views, scrolls, return visits, email opens and replies roll into one running score for each person.
Auto Connect
The moment someone goes hot, such as a third visit today or a return to the pricing page, the team is flagged in real time.
One record, every channel
Chat, web voice, inbound phone and outbound all work from the same history, so nobody starts cold.
Personalised welcomes
When someone your email reached later lands on the site, DeliChat can recognise them and adapt the greeting, where the law and the visitor’s consent allow.
A plain-English daily brief
Who came in, who warmed up and who is worth calling today, written so you can act on it without opening a dashboard.
DeliChat is one of the Deli Suite tools. The product page, DeliChat, covers features and pricing; this page explains how it behaves and where the boundaries sit.
From visit to record
An anonymous visit becomes a record when DeliChat resolves who is behind it and opens it in DeliHub. Everything that person does next is added to the same record.
Why this matters
Most visits end without a form fill
B2B websites convert roughly 2% to 5% of visitors into a known lead through a form. Identification is about the rest.
2% to 5%
of visitors become a known lead through a form
95% to 98%
leave without identifying themselves
Source: Tomba and Launch Leads B2B website conversion benchmarks, a published range rather than a measurement of your site.
The flow
Five steps from anonymous visit to a team that knows what to do
- 1
Arrive
A visitor lands
From search, an AI answer, an email or a referral.
- 2
Resolve
DeliChat identifies
The company, and the person where the law and consent allow.
- 3
Record
A record opens
One record per person in DeliHub, with every visit on it.
- 4
Score
Attention adds up
Views, return visits, opens and replies feed one running score.
- 5
Act
The team is flagged
The right channel picks up warm, with context.
The same record is used by every channel, which is why visitors can be approached warm instead of cold. The CRM side is covered on the DeliHub documentation page.
How the intent score behaves
The score is a running total of attention, not a one-off event. It steps up when someone engages, and cools when they go quiet.
Score over time
How one person’s intent score moves
The shape matters here, not the numbers. The chart is deliberately drawn without a numeric axis.
One blog visit. Barely moves the score.
Three service pages in one session. A large step up.
A return visit. Another large step.
An email open. Adds to the running total.
A return to the pricing page. Crosses the hot line, so Auto Connect flags the team.
Silence. The score cools on its own.
That behaviour lets the system prioritise without anyone watching a dashboard. The hottest people surface on their own, and people who stop engaging drift down the list without being deleted.
Auto Connect
Auto Connect flags your team the moment someone goes hot, so the follow-up happens while the interest is still fresh.
A hot moment might be a third visit in a day or a return to the pricing page. Auto Connect raises the alert and puts the full history in front of whoever picks it up. If the visitor was previously reached by email, DeliChat can also recognise them and adapt its greeting.
Auto Connect alert
Illustrative exampleHot visitor on the site now
Northbridge Advisory, Operations Director
- Third visit today
- Back on the pricing page
- Opened Tuesday’s email
Suggested next step
Call today, with the history open on the record.
Personalised welcome
Illustrative exampleDeliChat on the site
The greeting adapts because the visitor was recognised from an email we sent. Where consent is required it must be in place first.
What happens next depends on the channel: a note on LinkedIn, a same-day email or a call for the hottest moments. That choice is covered in signal-based outbound.
Read this before you switch it on
Privacy and consent
Whether a visitor can be identified depends on where they are and on what they have agreed to. The rules differ by market, particularly the UK, the EU and California.
- UK
United Kingdom
UK GDPR and the Privacy and Electronic Communications Regulations (PECR) apply. Cookies and similar technologies that are not strictly necessary generally need consent before they are set, and information about a named person is personal data.
Person-level identification is switched on only where the consent and the lawful basis support it.
- EU
European Union
The GDPR and the ePrivacy rules apply, and each member state enforces them through its own regulator. The working assumption is the same consent-first approach to non-essential tracking.
We configure per market, because member states do not all apply the rules in exactly the same way.
- US
California
The CCPA, as amended by the CPRA, centres on notice, the right to opt out of the sale or sharing of personal information, and honouring opt-out preference signals, rather than blanket prior consent.
Notice and opt-out handling are part of the set-up, so a visitor who opts out is not identified.
General information in broad terms, not legal advice. Rules change and vary by sector, so confirm your own position with your counsel.
What this means in practice
- Company-level and person-level are different. Knowing which company visited is a lighter question than naming the individual. DeliChat resolves the person only where the law and the visitor’s consent allow.
- Markets are set up before launch. The markets you sell into decide how identification is configured, not the other way round.
- Some visitors stay anonymous. That is by design, and we report it plainly.
For who owns the data, how outreach stays compliant and what happens if you leave, read data ownership and privacy. The site-wide policies are the privacy policy and the cookie policy.
Tracking and measurement
If it cannot be measured it cannot be improved. Tracking is a set of layers, and each one writes to a place you can inspect.
| Layer | What it does | Where it lands |
|---|---|---|
| Analytics | GA4 with defined conversion events: form submissions, bookings, diagnostic completions and key page visits. | Your GA4 property |
| AI referrals | A named channel group for traffic arriving from ChatGPT, Perplexity, Gemini and Copilot, so it is reported as its own channel. | GA4 reports |
| Search | Google Search Console connected and monitored for impressions, position and clicks. | Search Console |
| Booking | One booking system wired into the CRM. Every booked meeting lands on the right record and triggers the right follow-up. | DeliHub record |
| Identification | DeliChat on every page, writing visits, scores and conversations into DeliHub. | DeliHub record |
| Schema and site health | Structured data, sitemaps, redirects and internal links maintained so the site stays crawlable. | Your site |
| Automation | Webhooks and workflows that move a lead from a form, diagnostic or reply into the right pipeline stage and nurture sequence. | DeliHub pipeline |
Where we do not have access to something, such as your analytics before an engagement starts, we say so plainly instead of estimating. The measurement side of an engagement is laid out in the engagement tab, and the identification layer in action is on the DeliChat page.
Common questions
The questions we hear most about identification and scoring.
Does DeliChat identify every visitor?
No. Identification depends on the data available and on the visitor’s jurisdiction and consent, so some visitors stay anonymous. We do not claim a match rate, and we would rather tell you what was and was not identified than estimate it.
Is identifying website visitors legal?
It depends on where the visitor is and what they have agreed to. Rules differ across the UK, the EU and California, so identification is configured with each client around the markets they sell into, before it goes live. This is general information, not legal advice, so confirm your own position with your counsel.
What does the intent score actually tell me?
It is a running total of attention, used to decide who to pay attention to first. A single blog visit barely moves it, three service pages, a return visit and an email open move it a lot, and silence lets it cool. It is a prioritisation aid, not a prediction that someone will buy.
Next in the reading order is outbound, which uses these signals. Back to the documentation overview.