Leads
A lead here is one row whether it is a person or a company, and the part that matters operationally is the second half of it: who holds this record, and what happens when nobody does.
Contacts
Manage your contact database and relationships
| ↓ | ||||||||
|---|---|---|---|---|---|---|---|---|
| James | Brown | Analyst | Harbour Data | Qualified | 94 | A. Kwan | 0d | |
| James | Johnson | Specialist | Ardent Logistics | Meeting Scheduled | 91 | M. Ortiz | 1d | |
| Jessica | Harris | Supervisor | Kestrel Health | Proposal Sent | 88 | S. Bhatt | 3d | |
| Sarah | Thomas | Coordinator | Halden Retail | Qualified | 85 | S. Bhatt | 2d | |
| Christopher | Williams | Executive | Meridian Freight | Interested | 82 | Saurav Kumar | 0d | |
| Michael | Williams | Coordinator | Northbridge | Meeting Scheduled | 76 | J. Reyes | 1d | |
| Matthew | Lopez | Developer | Selby Compliance | Interested | 71 | A. Kwan | 4d | |
| Jane | Davis | Manager | Larkfield Group | Contacted | 64 | M. Ortiz | 2d | |
| David | Johnson | Manager | Bramble Foods | Contacted | 57 | S. Bhatt | 6d | |
| Ashley | Martinez | Manager | Vantage Numbers | Contacted | 49 | J. Reyes | 9d | |
| Jane | Rodriguez | Manager | Halden Retail | Not Qualified | 21 | Saurav Kumar | 14d | |
| Daniel | White | Lead | Meridian Freight | Lost | 12 | M. Ortiz | 28d |
Product figures from the platform’s own defaults - not customer averages
How it works.
One table, two kinds of lead
A record is marked individual or business and both live in the same table. A business one fills fourteen company columns on that row, so there is no second object to keep in step and a filter reaches both kinds at once.
Held by a person, a role or a team
Assignment names one of three things. Pointed at a role or a team, the record is waiting rather than owned, and it shows in that queue for everyone who sits in it.
Taking one is a transfer
Claiming writes you onto the record and clears the role and team it was waiting in. You must hold that role or belong to that team, and a record already held by somebody else answers with a refusal rather than changing hands.
The awkward flags live on the record
Federal and internal do-not-call, known litigator, per-channel opt-outs and the date consent was given are columns on the lead itself, so the dialer reads them from the same place a rep does.
Two moments in every record.
Every record passes through the same seven. Leads is the lit ones, and everything either side of it is a different page in this category.
- 01Capture
how it arrives, and from where
- 02Shape
the fields and stages it carries
- 03Find
getting back to the right ones
- 04Work
what happens against it day to day
- 05Advance
moving it towards a decision
- 06Protect
who may see it, and staying clean
- 07Report
what the floor is judged on
The specifics.
8 facts- Kinds
- Individual or business, in one table, defaulting to individual
- Fields
- Seventy-nine across eight sections, from lead identity through to tags and other
- Company data
- Fourteen of those sit on the lead row. There is no separate company object
- Assignment
- A user, a CRM role or a team. Only a user assignment counts as held
- Claiming
- Refused when somebody already holds it. Two clicks in the same instant are not fenced off from each other, so it is first past the post rather than a queue
- Opening a queued one
- Opening one from a role or team queue puts your name on it, and only if you hold that role or sit in that team
- Score
- A whole number on the record, filtered and sorted on like any other column
- Paging
- A hundred rows at a time by default, two hundred as the ceiling
What else writes to this record.
A record is worked by more than one part of the system at once. These are the ones that put something on it, or read it back.
More in Leads & Sales CRM
11 capabilitiesThe system of record the phone writes to directly - no sync job.
Unlimited pipelines, each with its own stages, win probability, colour and temperature. Seven seeded, and every stage change writes itself onto the deal.
Eleven field types, all of them on the picker, with options, defaults and a section of their own, on leads, deals, products and vendors. No cap on how many.
Sort the fields you add into named sections with their own colour, order and table visibility, then grant or withhold a whole section per permission profile.
Eighteen type-aware operators, a trigram search across seven columns, and a straight account of where a custom-field filter is resolved and what it costs.
Tick rows and reassign, export, delete or enrol them at once, filtered per record by permission, so a mixed selection returns a verdict per row.
Upload, map, review. Headers auto-map against the full field catalogue, imports stream so memory stays bounded, and a failed row never stops the run.
Matched on normalised email then phone, at the moment a record is written, so the duplicate is caught on the way in rather than found in a report later.
Calls, voicemails, emails and texts merged into one chronological history per lead, attached by the number they reached, with duration and the wrap-up code.
Tasks with assignees, reminders, comments and templates, raised by hand or by a sequence, and the only CRM object that leaves the app to find someone.
A role tree, sixteen org-level flags, per-entity CRUD and sharing rules across branches - so a BPO runs several clients on one tenant, safely.
Ten measures over six windows, with attainment read from won deals and logged work the moment you open the target rather than filed by hand or overnight.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Leads & Sales CRM
See leads on your own floor.
Thirty minutes, your numbers and your data. We will set leads up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included