CyberFreezeDev
Loading
Every lead keeps its source, and duplicate records merge without losing deals or notes.
A lead is a person filed under a company account, with an owner, an optional hotness from 1 to 5 and a required source.
A lead is a person. Give it a company and Desk files them under that company's account, reusing the account if it already exists. Leave the company out and the person stands alone.
Each lead has an owner (the person who created it, unless you assign someone), an optional hotness from 1 to 5, and a required source. Typical sources are Meta ads, Google ads, website form, BNI referral, client referral, walk-in and manual entry. When the company account already exists it keeps its original source, so a second contact at a client does not rewrite how you won them.
Organisations can add their own required fields, both on accounts and on leads, so the data your team needs is captured at the start.
Email, phone, company and name are matched before creation, with +91 numbers normalised.
Before a lead or contact is created Desk looks for a match on email, phone, company or name. Indian numbers are compared with +91 and a leading zero normalised, so 098xxxxxxx and +91 98xxxxxxx are the same person. Candidates come back with a confidence flag.
Contacts, deals, tasks, comments and tags move onto the record you keep.
Pick the record to keep. The other one's contacts, deals, tasks, comments and tags move onto it, empty fields are filled from it, and the duplicate is removed.
A full copy of the removed record goes to the audit trail first.
A full copy of the removed record is written to the audit trail before the merge, so nothing is lost if the wrong one was picked.
Contacts can carry a referral date and move through stages set per organisation.
For teams that grow through referral networks such as BNI, a contact can carry a referral date and move through referral stages, for example Contacted and Got The Business. The stage list is set per organisation.
Required sources let the source report rank channels by volume and win rate.
Because the source is required, the source report can rank channels by volume and win rate with real denominators.
Contacts can be created in bulk from a spreadsheet, and integrations can push leads in from ad forms or WhatsApp.
Contacts can be created in bulk, which is how most teams move over from a spreadsheet. Leads from ad forms or WhatsApp can be pushed into Desk by an integration; we build those with n8n and as part of our WhatsApp CRM automation service service. Once a lead is in, it moves through the CRM pipeline.
Without it, nobody can say which channel brings customers. A required source is what makes the source report and the monthly leads by source figures meaningful.
Not with one click. A full snapshot of the removed record is kept in the audit trail, and restoring from it is a manual job, so check which record you are keeping.
Yes. +91 prefixes and leading zeros are normalised before numbers are compared.
Last updated