How lead clusters work
A lead cluster is the card you work in Leads. When the same customer enquires more than once, Dealer Studio can put those enquiries on one cluster so the salesperson sees one timeline, one assignee, and one pipeline status instead of a new card every time.
What has to match before clustering happens
Section titled “What has to match before clustering happens”Automatic clustering only runs when Automatic Lead Clustering is on for the dealership (it usually is). A new enquiry joins an existing cluster when all of the following are true:
- It belongs to the same contact (matched on email or phone).
- It falls inside the dealership’s Lead Clustering Time window (default is 90 days).
- The existing cluster is still open enough to reuse (not converted, delivered, lost, or invalid).
- By default, it is the same location and the same category group as that cluster.
If any of those fail, a new lead cluster is created for that enquiry.
Locations stay separate by default
Section titled “Locations stay separate by default”By default, Dealer Studio does not cluster across locations.
| Situation | What happens |
|---|---|
| Same customer, same location, within the time window | Joins the existing cluster (when category also matches) |
| Same customer, different location | Creates a new cluster at that location |
| Dealership has Cluster Leads Across Locations turned on | Same customer can join one cluster even if the enquiry lands at another location |
That default matters for multi-site groups: a Northbridge new-car enquiry and a Fremantle service enquiry stay on different cards so each site owns its own follow-up.
If you still need visibility when the same person is active elsewhere on the dealership, ask an administrator about Show active leads at other locations. That does not merge the clusters. It only flags in the sidebar that another location already has an active lead for them.
Category types stay separate by default
Section titled “Category types stay separate by default”By default, Dealer Studio does not cluster across category types. Categories sit in groups, and a new enquiry only joins a cluster whose category is in the same group.
| Group | Examples of categories that share a cluster |
|---|---|
| Sales | New Vehicle Enquiry, Used Vehicle Enquiry, Test Drive Booking, Finance Enquiry, Special Offer Enquiry, Online Purchase, and similar sales intents |
| Trade | Trade-in Enquiry, Sell My Car Enquiry |
| Service | Service Booking, Service Enquiry, Parts Enquiry, Service Retention, Loan Car Booking |
| Service communication | Service Communication (kept on its own so general service messaging does not mix into booking pipelines) |
| General | General Enquiry, Survey, Competition Enquiry, Event Enquiry, SMS Campaign |
So a New Vehicle Enquiry and a later Used Vehicle Enquiry from the same person can share one sales cluster. A Service Booking from that same person becomes a separate service cluster, because a different team usually owns it.
Phone calls are the exception
Section titled “Phone calls are the exception”A lead categorised as a Phone Call can join a cluster in any of those groups. The call often arrives before anyone knows whether it was sales or service, so the product allows it to attach to the matching open cluster for that contact (still subject to location and time rules).
How far back clustering looks
Section titled “How far back clustering looks”Lead Clustering Time sets how old an existing cluster can be and still accept a new enquiry. Options are 3, 7, 30, 90, 180, or 365 days. The usual default is 90 days (about three months).
By default the window is measured from when the cluster was created. If Also cluster from last event date is enabled, a new enquiry can also join when the cluster’s most recent activity or most recent lead falls inside that same window. That helps when someone has been followed up for longer than the creation window alone would allow.
When an existing cluster will not be reused
Section titled “When an existing cluster will not be reused”Even with a matching contact, location, and category group, clustering skips clusters that are already finished for pipeline purposes: converted, delivered, lost, or invalid. A fresh enquiry then starts a new cluster instead of reopening the finished one.
Settings administrators can change
Section titled “Settings administrators can change”These live on the dealership settings form (usually managed by a Dealer Studio administrator or someone with dealership edit access):
| Setting | Default | Effect |
|---|---|---|
| Automatic Lead Clustering | On for most dealerships | Off means every enquiry gets its own cluster |
| Lead Clustering Time | 90 days | How far back a cluster can accept another enquiry |
| Cluster Leads Across Locations | Off | On allows one cluster across locations for the same contact |
| Also cluster from last event date | Off | On also uses recent activity or recent leads for the time window |
| Show active leads at other locations | Off | Sidebar hint only; does not change clustering |
Category groups are fixed by the product. There is no dealership toggle to merge sales into service (or trade into sales) on one cluster.
Quick examples
Section titled “Quick examples”| Customer actions | Result with defaults |
|---|---|
| Website new-car enquiry Monday, test drive booking Wednesday, same location | One sales lead cluster |
| New-car enquiry at Location A, then used-car enquiry at Location B | Two clusters (one per location) |
| New-car enquiry, then a service booking a week later | Two clusters (sales and service) |
| Trade-in enquiry, then sell-my-car enquiry | One trade cluster |
| Enquiry that was marked lost months ago, then a new enquiry after the time window | New cluster |