Product

Leads

The gap where enquiries get lost is almost always between the form and the follow up. That is what this part of the product is built around.

Nobody counts them

Most organisations cannot answer basic questions about their own enquiries

Ask a small business how many enquiries it received last quarter and you will usually get a number that is a feeling. Ask which advertising produced them and you will get the one someone remembers. Ask what proportion converted and there is frequently no answer at all.

This is not carelessness. It is what happens when enquiries arrive through four channels into an inbox, a telephone and a form, and the only place they are all recorded is in the heads of whoever handled them. There is no ledger, so there is nothing to count.

The cost is not that the questions go unanswered. It is that decisions get made anyway, on impressions. Advertising budget goes to the channel that produced the enquiry somebody remembers most vividly, which is usually the most recent or the most expensive. Staff time goes to the enquiries that feel urgent instead of the ones that convert. And no one notices when a source that used to work quietly stops.

The three things worth recording

You do not need a large amount of information to fix this. You need three things recorded consistently, and the discipline to record them when the enquiry arrives rather than later.

Where it came from. Recorded at the point of capture, from a fixed list rather than free text, because a source field where people type whatever they like produces eleven spellings of the same thing and cannot be counted.

Who owns it. One person, named. The most common way an enquiry dies is not that two people chased it, it is that both assumed the other had, and an unowned lead is one nobody is going to ring.

What happened. Converted, or not, with a reason. That last part is the one everybody skips and the one that pays, because it is the only route to knowing whether you lose on price, on speed, or on something you could fix this month.

An inbox against a record

Six questions, and whether you can answer them

These are the questions a business asks when it is deciding where to spend. Most can answer two of them.

The question With an inbox and a spreadsheet With leads recorded properly
How many enquiries did we get last quarter?No one knows. The number people give is an estimate based on how busy it felt.A count, and a breakdown by source, by owner and by outcome.
Which advertising is working?The one that produced the enquiry someone remembers. Frequently the most recent, or the most expensive.Which sources produced customers rather than telephone calls. Those are different numbers and only one is worth spending against.
Why did we lose that one?An impression, usually price, because price is what people say when they are being polite.A recorded reason on each lost enquiry, and a stage history showing where it actually stopped.
Did anybody follow up?Whoever picked up the telephone knows. If they are away, no one does.The lead has an owner, a stage and a timeline. What was promised and when is on the record.
How long does it take us to convert?Everybody has a number and no two people agree.The stage history, averaged. It is almost always longer than the number people give.
Can we contact the ones who did not buy?Not safely. There is no record of what they agreed to.Consent recorded per channel with a date and a source, so the next contact is one they agreed to.

Capture

Source recorded at the moment it arrives

An enquiry is captured with where it came from, who it is from, what they are asking about and who is dealing with it. That takes about twenty seconds by hand and no time at all when it arrives from a form on your own site.

Source matters more than any other field and it is the one most often left until later. Source recorded at capture is a fact. Source filled in at the end of the month is a survey of what people remember, and it consistently over reports whichever channel is most memorable rather than most productive.

Duplicate detection runs at the same moment. Typed in by hand it matches on email address and on close name matches and shows you what it found, beside the enquiry, for you to judge. Submitted through a form it matches on the address alone, links the enquiry to that person and puts a line on their timeline. Either way the person is found at the moment they arrive, so an existing customer asking about something new does not quietly become a second version of themselves.

Qualification

Against your questions, not a scoring model somebody else designed

Qualification means working out whether you want the work, and what that depends on is specific to your business. Budget, timescale and authority are the classic three, and for a great many organisations at least one of them is irrelevant and something else matters much more: whether the site is within an hour, whether the sector is one you can insure, whether the start date is in a month you have capacity in.

So qualification here is your own fields, asked in your own words, rather than a score computed from a model. A number that no one can explain is a number no one argues with, and a qualification score no one argues with is one nobody has checked.

The questions are yours and the states are ours, and it is worth being plain about which is which. An enquiry has four states you can put it in, new, working, qualified and unqualified, and a fifth, converted, which it reaches by being converted and by no other route. You cannot rename them and you cannot add one. Stages you name yourself belong to a pipeline, which is where the work goes after conversion, so if what you want is your own sequence of steps, that is the thing to reach for and this is not it.

The practical shape of that pipeline is usually four or five stages between arrival and won. If you find yourself wanting twelve, you are describing the tasks someone performs rather than the states a piece of work is in, and the pipeline will stop being kept current within a fortnight.

Conversion

One step, and nothing is retyped

Converting an enquiry creates the relationship and, if you want, the piece of work, carrying the notes, the source, the timeline and the consent across in one action.

The reason this matters is not convenience. It is that every retyping is an opportunity to lose something, and what gets lost is always the same thing: the context. The name and the telephone number survive being copied by hand. The two sentences about what they actually want, and the fact that they were recommended by an existing customer, do not.

The lead record stays as history after conversion, so the question of where a customer originally came from is answerable three years later, which is when somebody finally asks it.

How relationships work

Inside an enquiry

From an enquiry to a customer, without retyping it

What a lead record holds, and why each part earns its place.

Source
Recorded when the enquiry is captured rather than guessed at afterwards. Without it, source reporting is a survey of what people remember, which is a different and much less useful thing.
Qualification
Against the questions your business actually asks, in your own words. A lead is qualified when you know whether you want it, and only you know what that depends on.
Conversion
One step turns an enquiry into a relationship and a piece of work, carrying the notes, the source and the timeline across. Nothing is retyped, so nothing is lost in the retyping.
Duplicate detection
Checked when an enquiry is typed in, when a form is submitted and when a file is imported. By hand it matches on email address and on close name matches and shows you what it found. A form matches on the address alone, because nobody is there to be asked, and it links the enquiry to that person and puts a line on their timeline. Nothing is ever merged for you.
Owner
Every lead has somebody responsible for it. An unowned lead is one no one is going to ring, and the most common cause of a lost enquiry is that everybody assumed somebody else had it.
Web forms
From Standard upwards, a form on your own site creates the lead directly with the source already set, which is the only version of source data that is reliable.
Stage history
How long the enquiry sat at each stage before it converted or did not. This is the number that tells you where you actually lose people, as opposed to where everyone believes you do.
Outcome
Converted, or not, with a reason. A lead marked lost is a record you keep rather than a row you delete, because next year it is the warmest list you own.

The number worth watching is not how many enquiries a source produced. It is how many of them became customers, and most systems make you leave the product to work that out.

Which is why the source is recorded at capture and the outcome is recorded at the end, and why neither is optional.

Reporting

What the numbers actually tell you

Enquiries by source is the least useful of the three

It is the number everybody starts with and the one that misleads most often, because the sources that produce the most enquiries are frequently the ones that produce the worst. A cheap listing site can generate a great deal of volume and almost no work, and if you measure volume you will spend more on it.

Conversions by source is the number to spend against

The same report, filtered to the enquiries that became customers. This is the one that changes decisions, and it frequently reverses them. A source producing four enquiries a month of which three convert is worth considerably more than one producing thirty of which two do, and the second one usually costs more.

Stage history tells you where the process is broken

How long enquiries sit at each stage before moving. This is the diagnostic, and it is almost always surprising. Most organisations believe they lose enquiries at price. The stage history frequently says they lose them between first contact and the second conversation, which is a responsiveness problem, costs nothing to fix, and would never have been found by asking people what they thought.

The reason field, read as prose

Reasons on lost enquiries are the least numerical and most valuable output. Read twenty of them in a row and patterns appear that no report would produce: a competitor mentioned repeatedly, a service you do not offer being asked for weekly, a price point that keeps appearing.

This is also why lost enquiries are kept rather than deleted. Beyond the reporting, the people who enquired and did not buy are the warmest list any organisation owns, and because consent was recorded with a date and a source, contacting them next year is something they agreed to instead of something you hope is acceptable. Whether you may write to them at all is settled by the Privacy and Electronic Communications Regulations rather than by a CRM. What the product does is hold the evidence.

Four habits

Getting the discipline to stick

Record everything, including the obvious rejections

The instinct is to record only the enquiries that might go somewhere, which destroys the denominator. Twenty seconds on an enquiry that is obviously not for you, marked lost with a reason, is what tells you six months later that a fifth of your enquiry volume is unsuitable and where it comes from.

Fix the source list before you start

A short list of sources that people choose from, agreed in advance. Not free text. Six or eight options covering how work actually reaches you, with one called Other that somebody reviews occasionally. A source field where people type freely produces Google, google, Web, Website and Search, and none of them can be counted together.

Give every lead an owner immediately

Even if the owner is provisional. An enquiry with no owner is an enquiry no one will ring, and it is the single most common way work is lost in a small organisation. The allocation being wrong is a much smaller problem than the allocation being absent.

Build one view and look at it on a Friday

Enquiries at any stage with no activity for ten days. That is the list. It takes two minutes to build and it is the highest return thing anybody does with this part of the product, because those people have not decided yet and nobody has spoken to them.

When it stops counting

Six ways lead capture stops telling you anything

Most enquiries arrive with no source

The symptom is a report where the largest category is unknown. The cause is a source field that is optional at the moment when the person filling it in is busy.

The fix is fewer sources and a habit, not a required field. A required field with a default produces a report that is confidently wrong, which is worse than one that admits a gap.

Nothing is ever closed as lost

The symptom is four hundred open leads, most of them from last year. The cause is that closing feels like giving up, so everything stays open indefinitely.

The consequence is that conversion rate becomes uncomputable, and conversion rate by source is the entire point. A lead closed with a reason is information. A lead left open for eleven months is not optimism, it is missing data.

Everything is converted immediately

The symptom is a pipeline that looks healthy and a forecast that is never right. The cause is converting on first contact, which moves the qualification decision into the pipeline where it is much more expensive to make.

Two people are working the same enquiry

The symptom is a customer mentioning that somebody already called them. The cause is a shared inbox with no owner on the enquiry.

An owner at the point of capture solves it, and it costs one click. The version of this that damages a business is when the two people give different answers about price.

The source list has grown to thirty

The symptom is a report with a long tail of ones and twos. The cause is adding a source for every campaign rather than for every kind of origin.

Sources should be stable enough to compare across years. Campaigns are a different question and belong with the campaign rather than on the person.

No one reads the report

The symptom is careful recording and no decisions. The cause is that the report was never anybody's job to look at.

Read it once a quarter, in front of whoever decides where money goes. It is a fifteen minute conversation and it is the only reason any of the recording was worth doing.

Not in here

Five things lead capture leaves alone

No lead scoring. Nothing assigns a number to how promising an enquiry is. A score nobody can explain is a score no one acts on, and a score anybody can explain is a saved view with fewer moving parts.

No automatic routing rules. No assignment by territory, by round robin, or by product. At this size an owner is chosen by the person taking the enquiry, who usually knows something a rule does not.

No web tracking. Nothing follows somebody around a website, records which pages they read, or attributes an enquiry to a sequence of visits. That is a different category of product with different consent implications and it sits badly beside recording consent as a fact with a source.

No contact database or address finding. No buying a list, no enrichment, no automated prospecting. This is a position instead of a gap.

No merging. Duplicates are found at capture and shown to you, and nothing is ever joined up for you. If the same person enquires twice you still have two enquiries, both pointing at the same record. That is deliberate: merging is a judgement about your own business and a destructive operation, and the two enquiries are two real events even when they came from one person.

From form to work

One enquiry, followed from the form to the piece of work

Consider a five person surveying practice that takes most of its work from its own website. It does not exist and is not a customer. It is here because the sequence is easier to follow when somebody is in it.

Tuesday morning: the form is submitted

Somebody fills in the enquiry form on the practice's own website. They give a name, an email address and two sentences about a building they are buying. The form has a consent question on it with a sentence of wording the practice wrote.

An enquiry is created at that moment. Its source is the one the form carries rather than one the visitor picked from a list, which is why source from a form is worth more than source recorded by hand. The two sentences are kept as the note. What brought this person in and what they most recently came through are both recorded as that form. The audit entry names the visitor rather than a member of staff, because no member of staff did anything.

If the consent question is on the form, the exact words that were shown are recorded along with the answer and the date. Not a tick, the wording. A tick cannot be produced later when someone asks what was agreed to, and the sentence can. The someone who asks is usually a person quoting it back at you, and occasionally the Information Commissioner's Office.

One thing does not happen: the enquiry arrives with no one responsible for it. That is the one gap a form cannot close, and closing it is the first thing somebody at the practice has to do by hand.

Tuesday, later: somebody picks it up

A surveyor moves it to being worked, which records who did that and when. The practice's qualification is two questions: is the property within an hour of the office, and is it a kind of building they can insure. The answers go on the enquiry as a note. That is the whole of their qualification and it is enough, because it is the thing they actually decide on.

Thursday: it converts

Conversion checks the email address against the relationships the practice already has. This one is new, so a relationship is created and given the source the enquiry carried, instead of leaving that fact behind on a record no one will open again.

A piece of work is created at the same moment, in the default pipeline at its first open stage, with a stage history entry written from nothing into that stage. The clock on the first stage therefore starts on the Thursday it actually started, not on the day somebody remembered to add it. A timeline entry appears on the new relationship recording that it came from an enquiry and what kind. Audience membership is worked out again in the same instant, so the customer they have just won is not invisible to every campaign.

All of that is one transaction. If the practice had no pipeline to put the work into, the conversion would refuse rather than create the relationship and quietly leave the work undone.

Six months later: the only part that pays

The source report now shows, for that form and for every other way work reaches them, how many enquiries arrived and how many became customers, next to each other. That comparison is what the practice could not make before, and it is the reason any of the recording above was worth doing.

Six arrivals

The same person enquiring three times, and five other awkward arrivals

Enquiries are messier than any model of them. These are the six the tidy version of the story leaves out.

The enquiry is from someone already on your books

At the moment of conversion the email address is checked against the relationships you already have. If it matches one, the enquiry joins that record instead of creating a second version of the same customer. This is the failure people notice, because their history sits under one record and their new work under the other, and once anything has been filed against both it cannot be undone by hand.

The same person enquires three times in a year

You get three enquiries, and all three lead to the same relationship. What first brought them in stays as it was; what they most recently came through is updated. Both are kept deliberately, because they answer different questions. One says what got them into the room and the other says what made them act this time, and an organisation choosing which of those to spend against needs both numbers instead of an average of them.

The enquiry is a company instead of a person

If a company name was recorded on the enquiry, conversion creates an organisation and names it after the company. If not, it creates a person. That is decided by what somebody recorded rather than by inspecting the name for something that looks like a company, which is a guess that is wrong about sole traders roughly whenever it matters.

Somebody deleted an enquiry and now wants it back

Deleted enquiries go to a recycle bin and wait thirty days before they are removed for good. Anyone who may work an enquiry may bin it and may restore it, because a bin is reversible. Restoring puts the record back into search as well as back into the list.

Whilst an enquiry is in the bin it cannot be qualified and it cannot be converted. It is treated as absent rather than quietly resurrected into a relationship, which is the behaviour you want the first time someone bins a spam enquiry and someone else clicks convert on a stale screen.

Somebody tries to convert the same enquiry twice

It is refused. An enquiry that has already converted points at the relationship it produced, and converting it again would create the second record the email check exists to prevent.

A stranger ticks the consent box using somebody else's address

The address on a public form is typed by whoever is filling it in and nothing verifies it. So a form submission never writes a consent answer against a record that already exists. It only records consent for a record the submission itself created.

The reason is the version of this that does damage: somebody who knew a customer's email address could otherwise submit the form with the box left clear and quietly remove a real customer from every future campaign. The enquiry is still created, and it still shows what was ticked, so a member of staff can see it and act on it. The proper answer is a confirmation message before any consent is recorded at all. That is worth building and it is not what happens today.

What it writes into

Conversion is the single most connected action in the product

Almost everything else in Consonas has a narrow blast radius. This one writes into six other places, which is why it is one step and one transaction.

Converting an enquiry creates or joins a relationship, which is what makes it appear in the relationship list, in search, and in every audience whose question it now answers. Audience membership is recalculated at that instant instead of the next time something else happens to the record, because otherwise nothing would ever happen to the record again and a new customer would belong to no audience for as long as they stayed a customer.

It creates the piece of work in the sales pipeline, at the first open stage of the default pipeline, and writes the opening stage history entry. That entry is the reason the sales page can tell you how long deals sit in the first stage without anyone typing a date. Where the enquiry came from is copied onto the work as well as onto the relationship, so the question of which source produced the money is answerable from the pipeline instead of requiring someone to trace back to an enquiry from two years ago.

It writes a timeline entry on the relationship saying where it came from, so the answer is visible on the record rather than only in a report. It writes an audit entry, as does capture, qualification, binning, restoring and permanent deletion. Those six entries are on every plan including the free one, permanently, because an audit trail with holes in it is not an audit trail. And it emits an event, so an outbound webhook can tell another system that an enquiry has become a customer.

The permission that gets checked

The check made at conversion is the one on the enquiry, not the one on the pipeline. The practical consequence is worth knowing before you set roles up: someone who may convert enquiries can put work into the pipeline through that route. If your reason for withholding the sales permissions from someone is that you do not want them adding to the pipeline, withhold conversion from them too, and let them qualify instead.

What conversion does not touch

It does not move consent, because consent was never on the enquiry. Consent belongs to a person and is recorded against the relationship at the point it was given, which is why a form that asks the consent question creates that record straight away instead of waiting to see whether the enquiry goes anywhere. An enquiry that never converts still leaves behind an accurate record of what its sender agreed to.

Four decisions

Four decisions, and what was rejected each time

An enquiry is its own record, not a flag on a relationship

The obvious design is one table of people with a field saying whether they are a lead or a customer. It was rejected. Most enquiries never become anything, so that design fills the list of people you have relationships with mostly with people you do not, and every count, every export and every audience then has to remember to exclude them.

The cost of the decision is real and you will feel it: there are two places a name can be, and someone looking for a person has to accept that search returns both kinds. We took that over a relationship list that is four fifths strangers.

Conversion is all of it or none of it

The alternative is to create the relationship immediately and let the piece of work be added afterwards, which is simpler and is what happens when the two steps are separate screens. It was rejected because the failure is invisible. A converted enquiry pointing at nothing looks exactly like a converted enquiry, and the way you find out is a customer ringing about work nobody has a record of.

So if any part of the conversion cannot complete, none of it does. The visible cost is that a practice with no pipeline configured gets a refusal at the moment it least wants one, rather than a partial success it would not notice.

Where someone came from is copied, not looked up

The tidy version stores the source once, on the enquiry, and joins back to it from the relationship and the work. It was rejected because nothing downstream ever looks back at the enquiry. By the time anyone asks which source produced a piece of business, they are looking at the business, and if the answer is not there it is not an answer.

Copying data is normally the wrong instinct and here it is the right one, because the fact being copied does not change. Where someone originally came from is fixed the moment it happens.

Two answers about origin are kept, not one

Most products record one attribution field and it quietly answers whichever question the person who wrote it had in mind. There are two questions. What first brought this person into contact with you, and what they came through this time, are different, and the gap between them is frequently a year and two different budgets.

Both are kept on the enquiry, and both survive conversion onto the relationship and onto the work. The uncomfortable half is that you now have two numbers where you expected one, and the first meeting where they disagree is an argument. That argument is the useful part.

Rights over an enquiry

Who may do what to an enquiry

Four permissions, and one consequence of them that surprises people.

See enquiries
Which enquiries somebody sees depends on their role, exactly as it does for relationships. An enquiry marked sensitive is reachable only by roles allowed to reach sensitive records, so an enquiry about something a person would not want discussed in an open office can be handled by two people instead of nine.
Record an enquiry
Separate from seeing them, because the person who answers the telephone is frequently someone you want typing enquiries in and not someone you want reading everyone else's.
Work and qualify
Moving an enquiry between stages, adding the note, and marking it as not for you. The same permission covers the recycle bin in both directions, binning and restoring, on the grounds that an action you can undo needs a lower bar than one you cannot.
Convert
Held separately, because conversion is the step that creates a relationship and a piece of work instead of editing a record that already exists. It is the one worth thinking about when you write a role.
Remove for good
Only possible for something already in the recycle bin, which means permanent deletion always happens in two deliberate steps at least a moment apart. There is no route that takes a live enquiry straight to gone.
On every plan
Capturing, qualifying and converting enquiries, the source report, the recycle bin and the audit entries behind all of it are on every plan including the free one. None of them is a paid upgrade and none of them ever will be.
Needs Standard or above
A form on your own site that creates the enquiry directly is a Standard feature and has nothing to do with the marketing module, which starts a plan higher. Everything a form does can be done by hand on any plan; what you lose is the reliable source, which is the part worth paying for.

The consequence that surprises people

The source report obeys the same visibility rules as the enquiry list. It is not a separate reporting layer with its own view of the data, it is the same question asked with the same restrictions applied. So a surveyor who can see their own enquiries gets a source report about their own enquiries, and the owner of the practice gets one about all of them.

Both numbers are correct and they are different, which is a genuine problem the first time two people quote them at each other in a meeting. If you want one shared number that everybody argues from, that is not a reporting setting, it is a decision about who may see enquiries. Make it deliberately rather than discovering it in the meeting.

Before the first enquiry

Asked about leads

What is the difference between a lead and a relationship?

A lead is an enquiry: somebody asking about something, who may or may not become a customer. A relationship is a person or organisation you have a real connection with. Conversion is the moment one becomes the other, and it carries everything across so nothing is retyped. Keeping them separate matters because the questions you ask about enquiries, such as how many and from where, are not the questions you ask about customers.

Do lost leads count against my relationship limit?

Leads and relationships are counted separately, and a lead that never converts does not become a relationship. That is deliberate: an allowance that punished you for recording enquiries would push you toward deleting the most useful data you have.

Can two people work the same enquiry?

They can see it and act on it, and one person owns it. Ownership is not exclusivity, it is accountability. The most common way an enquiry is lost is not that two people chased it, it is that both assumed the other had.

What happens to the enquiry when it converts?

It becomes a relationship and, if you want, a piece of work at the same time. The notes, the source, the timeline and the consent all move across. The lead record remains as history, so the question of where a customer originally came from is answerable in three years.

How does duplicate detection work?

It runs in three places and it is not identical in all three. Typing an enquiry or a relationship in by hand matches on email address and on close name matches, and shows you what it found rather than merging it, because two records that look identical are occasionally two people and a product that guesses will eventually guess about somebody who matters. An import does the same, and also compares the rows in the file with each other. A web form matches on the exact address and nothing else, because nobody is there to be asked and two people of one name is an ordinary thing; when it finds one it links the enquiry to that person and writes a line on their timeline saying an enquiry came through the form. In none of the three is anything merged.

Can I capture a lead from my website?

From Standard upwards, yes. A form on your own site creates the lead directly with its source already set. That is worth more than it sounds, because source recorded automatically at capture is reliable and source filled in afterwards is a survey of what people remember.

What if an enquiry is from an existing customer?

Converting it attaches it to the record you already have where the email address matches, so the enquiry appears on their timeline rather than creating a second version of them, and anything the enquiry carried that the record lacked, a telephone number usually, is written onto it. An existing customer asking about something new is one of the most valuable enquiries you get, and it is the one most often lost to a duplicate.

Should I record enquiries that are obviously not for us?

Briefly, and then mark them not for us with a reason, which is the words the screen uses. It costs twenty seconds and it is the only way to know how much of your enquiry volume is unsuitable, which is a real number in most businesses and occasionally an argument for changing where you advertise.

Whose enquiries these are

Four trades where the source report changes the spending

Local service businesses take work through four channels at once and can rarely say which one paid for itself. Tour operators and travel agents take enquiries that run for months before anyone books. Training providers and course operators take them in waves against a calendar, and contractors take them as invitations to tender, where the number worth having is which professional team keeps inviting you.

What an enquiry becomes is described on relationships and sales. The form on your own site that creates one belongs to marketing, and the source report is read on reporting.

Record one month of enquiries

A single month with sources recorded properly will tell you something about your own business that you did not know.

Three people, a thousand relationships, no card and no time limit.