A quote request. A friendly email. Someone who says, “A friend gave me your number.” Three new hellos, with three rather different beginnings.

Lovely. Your work has an admirer. Now it helps to know what caught their eye, what they need and who is going to reply.

That is where lead sources become useful. You can choose where to look for your next customer and give the person answering a little context.

This guide covers nine common sources of business leads, a simple way to record them and the follow-up that turns a promising first hello into an actual conversation.

Where do leads come from? The short answer.

Sales leads come from channels where potential customers discover or contact a business: organic search, referrals, paid search, paid social, organic social, email, events, partners and direct outreach.

A lead is a potential customer. An enquiry gives you something more concrete to act on: a request for information, a quote, a visit or a conversation.

There is no universally best source. Start where suitable customers already look for your service, then check whether your team can handle the enquiries those channels bring.

A CRM gives those enquiries a shared home. Kibi keeps connected requests with their owner, conversation and next action, so the promising hello has somewhere to go.

See how Kibi captures business enquiriesHubSpot’s explanation of lead sources

Same form. Different first hello.

FOLLOW THE FIRST HELLO Editorial examples · fictional enquiries

Where they found you ≠ how they reached you.

Pick an enquiry’s backstory

The form is the door. Search brought Alex to it.

SOURCE / CHANNELOrganic searchWhat brought them to you
CAPTURE ROUTEWebsite contact formHow their enquiry arrived
ALEX’S ENQUIRY NOTE
“I found you while searching for an office designer.”

Alex tells you how they found the business. Record that answer; a website form alone does not prove a search visit.

What to record

Source: search, reported by the enquirer. Capture route: website form.

Then give it a next step

Keep the request, choose an owner and agree the next contact. Leave an unknown search term unknown.

Same form. A completely different first hello.

SOURCE / CHANNELClient referralWhat brought them to you
CAPTURE ROUTEWebsite contact formHow their enquiry arrived
ALEX’S ENQUIRY NOTE
“Priya recommended you. Could we talk about our office?”

This enquiry also arrived through the website. The recommendation is its source; the form is how the message reached you.

What to record

Source: client referral, reported by the enquirer. Capture route: website form.

Then give it a next step

Keep the introduction in the note. Ask only for details your team needs; a referral is still waiting for a reply.

The ad starts the interest. The form catches the question.

SOURCE / CHANNELPaid campaignWhat brought them to you
CAPTURE ROUTEWebsite contact formHow their enquiry arrived
ALEX’S ENQUIRY NOTE
“Your studio campaign caught my eye. Can we get an estimate?”

Alex mentions the campaign. That is useful context, but it does not establish every earlier visit or prove which ad caused the enquiry.

What to record

Source: paid campaign, reported by the enquirer. Capture route: website form.

Then give it a next step

Add campaign tags only when they are available through your approved capture setup. Keep missing details unknown.

These examples explain the distinction; they are not live Kibi screens or automatic attribution. Record what you can support, and keep unknowns visible.

A lead source explains how someone found your business. A capture route explains how their details reached you. A campaign adds detail about a particular marketing effort.

For example, a customer recommends your studio. Their friend visits your website and completes a quote form. The reported discovery source is the referral; the capture route is the website form.

Choose a trail in the source map. Each example uses the same form, which is rather the point: the front door does not tell you the whole journey.

Useful details about an enquiry. These are editorial examples, not automatic attribution rules.
What are you recording?An example that makes sense
Discovery source“A previous customer recommended you.” Record that as a reported referral.
Capture routeWebsite quote form. This tells the team where the request arrived.
Campaign detailSpring studio consultation. Keep a campaign name when you actually have evidence for it.
Customer request“Could we discuss a refresh for our reception?” Keep the useful words, not just “interested”.

1. Organic search: they are already looking.

Someone searches for a service, finds a useful page and gets in touch. Organic search leads can arrive through service pages, explanatory articles or a local business listing.

Answer the questions a buyer needs settled before contacting you: what you do, where you work, who it suits and what the next step involves.

A local interiors studio might explain its consultation process and show relevant work. The visitor can then decide whether to ask about their own space.

For a local business, keep your Business Profile accurate too. Google says local results depend mainly on relevance, distance and prominence; a complete profile does not guarantee a particular position.

  • Give the relevant page a clear enquiry action.
  • Keep useful page or source information when your setup provides it.
  • Ask how someone found you when the digital trail cannot explain it.
Google’s guidance on local search visibility

2. Referrals: someone has already put in a good word.

A customer, colleague or friend recommends your business. That introduction gives the conversation context, but it does not tell you everything the new person needs.

Make the handover easy: a useful service page, a contact route and a short explanation of who you help. Let the prospective customer share their own details.

When they enquire, ask “How did you hear about us?” as a useful, optional question. “Priya recommended you” tells the team more than an unexplained Direct label.

Thank the person for the introduction where appropriate, then focus on the new customer’s request. A warm introduction still deserves a proper reply. Charm needs a little follow-through.

Mailchimp’s guide to referral sources

5. Organic social and useful content: let people get to know you.

A helpful post, a project explanation or an answer to a common question can introduce your work before someone is ready to enquire.

Show something specific: what a consultation covers, how to prepare a brief or which details make a quote possible. Give interested readers a relevant next step.

When they contact you later, the visible digital source may not reveal the post they first remembered. Their own answer can add context that a report misses.

Use categories consistently. An article found through search belongs to the search journey; the same article shared in a social post has a different route. Content is not a separate explanation for every visit.

  • Keep the post or page relevant to the service being discussed.
  • Use a useful contact link rather than making people hunt for it.
  • Record a reported post or recommendation as reported, not proven first-touch attribution.

6. Email: a familiar name starts another conversation.

A newsletter, a relevant update or a previous customer’s reply can lead to a new request. Be clear about the offer and who should respond when someone is interested.

A specific invitation is easier to answer than a grand announcement. “Need help planning the next office move?” gives the reader something concrete to think about.

Keep the campaign detail when available and the customer’s actual request beside it. A reply to an email may arrive differently from a click through to a website form.

In Kibi, a forwarding inbox can receive matching enquiry emails. Configure the filter deliberately and check a fresh test message, rather than sending the team every receipt and lunch reservation.

Forward enquiry emails from Gmail into KibiUse an Outlook forwarding rule

7. Events and local conversations: remember the useful bit.

An open day, workshop or trade event can start a real conversation. The useful lead is the person with a relevant need, not simply every name collected at the door.

Agree how to continue and record enough context to do it well. “Talked about a September office move; asked for a call on Tuesday” is a much better reunion than “Event lead”.

A QR link can take people to a form. Give that event a recognisable route or campaign label, then test what the resulting record actually preserves.

If the conversation happens away from the form, add the enquiry through your supported manual or import process. A business card cannot schedule its own callback, however beautifully embossed.

Bring a reviewed lead list into Kibi

8. Partners and directories: make the introduction legible.

A complementary business, a relevant association or a directory listing can send people your way. Make sure the description and contact route explain the service you actually provide.

A relocation adviser might introduce an interiors studio. The studio still needs the customer’s brief, preferred contact and any relevant deadline, rather than assuming the partner has explained everything.

Keep the referring organisation or listing name when you have it. Check how each enquiry arrives before assuming a directory automatically connects to your CRM.

Where a supported connection is unavailable, review an appropriate enquiry-email, webhook, CSV or manual route. Keep the setup specific; “integrates with everything” is a charming phrase with an expensive aftermath.

9. Direct outreach: a relevant invitation, not a numbers game.

A business can also start the conversation through relevant outreach. Begin with a clear reason the service may help, and an easy way for the recipient to say whether they are interested.

A contact on a list is not automatically an inbound enquiry. Keep prospecting records distinct from people who have asked your team for something.

When a person responds with a genuine request, preserve that context and the agreed next step. Follow the contact preferences and rules that apply to your outreach.

Kibi’s enquiry workflow helps organise the response once it is recorded through a supported route. It is not a prospect database, an automatic source of buyers or a promise of replies.

Choose the next source around a real customer.

You do not need nine campaigns by Friday. Start with one customer type, one useful offer and a source where that person has a reason to notice it.

For an office-refresh studio, that could be a relevant local search page and a referral route. For a workshop business, a partner event and a clear booking enquiry may make more sense.

Write down the expected conversation before buying attention: who is this for, what will they ask, and can your team help? A busy inbox is not the same thing as a suitable customer.

Then check the whole route with fictional details. The right person should be able to find the offer, send the request and reach a teammate who understands what was promised.

  • Customer: who needs this service?
  • Offer: what useful next conversation are you inviting?
  • Source: where will that person discover the offer?
  • Capture: how will the request reach your team?
  • Follow-up: who replies, and what happens when they are away?

Give the enquiry a useful little backstory.

Keep source information close to the request. A small, consistent set of details is more useful than a beautiful taxonomy nobody remembers to fill in.

Record what you actually know. Distinguish an observed campaign tag from “Alex says Priya recommended us”. Both can help, but they are different kinds of evidence.

Google Analytics uses Direct when it has no clear referral source. That does not establish that someone typed your address from memory; missing tracking information can leave the same label.

UTM tags can describe a tagged link, but they do not explain every earlier conversation, forwarded message or device change. Keep the available detail and let unknown remain unknown.

Avoid putting names, emails or other personal details into campaign URLs. Google prohibits sending personally identifiable information to Analytics. Use ordinary campaign labels instead.

A compact enquiry note your team can adapt. Store details only in fields or notes your setup supports.
Keep thisA useful example
Customer and contact routeAlex Morgan; preferred reply by email.
Actual requestOffice reception refresh; wants to discuss timing.
Capture routeWebsite quote form.
Known discovery sourceReferral — Alex named Priya. Mark customer-reported.
Campaign detail, if knownNo campaign information available. Leave unknown.
Owner and next actionMaya; call at the time Alex agrees to discuss the brief.
Understand Direct traffic in Google AnalyticsGoogle Analytics policy on personal informationUse our free lead-tracking spreadsheet as a starting point

The source brought a hello. Give it some follow-through.

kibi.Illustrative Kibi workflow · fictional enquiry

A callback with a name on it.

“Priya recommended you. Could we talk through an estimate?”Alex’s example enquiry
  1. 01
    Save the actual question

    Keep Alex’s request and the source information you know with the enquiry.

    The useful details, all together.
  2. 02
    Maya owns the reply

    Give the conversation a named owner, so the whole team knows who is replying.

    “Someone” has left the chat.
  3. 03
    Put the callback in Today

    Maya sees the planned follow-up, makes the call and records what happens next.

    A reminder. A human reply.

Kibi keeps the enquiry, owner and planned follow-up together. Today helps Maya find the callback; it does not make the call or send a message for her.

Connect a compatible website form, set up a forwarding inbox or bring in a reviewed CSV. Test the actual route and check which source details and fields reach the workspace.

Then give the enquiry to the person who can help. Routing rules on Team and Growth can support that assignment; your team still handles the conversation.

We make Kibi. If your enquiries are spread across tabs and private inboxes, try it with one real source and the people who answer it.

Kibi CRM has a 14-day trial, then a paid plan. The goal is a team that knows who is replying and what happens next, with a little less “I thought you had it”.

Try Kibi CRM with your next enquiryExplore Today and planned follow-upsSee routing and shared ownershipCheck plans for your team

Keep the source question separate from the sales result.

A source tells you where an enquiry came from. A recorded conversation, won job or payment tells you something else about what happened afterwards.

Before judging a source, check whether the team actually responded. An unanswered enquiry is weak evidence about the customer’s fit or the campaign’s quality.

Our separate outcome guide explains how to review those measures without mixing them together. For now, leave with a source record someone can understand and a next action someone owns.

Follow the enquiry from ad click to recorded outcome

A few questions before the next hello.

Where do business leads come from?

Common lead sources include organic search, referrals, paid search, paid social, organic social, email, events, partners and direct outreach. Start with the channels your buyers use and a clear way to make an enquiry.

What is the difference between a lead source and a website form?

The source describes how someone found your business. The form is the capture route. Someone referred by a customer and someone arriving through search can complete the same form while having different discovery sources.

Which lead source is best for a small business?

There is no universal winner. Choose around your customer, service, budget and ability to respond. Review suitable enquiries and recorded outcomes rather than declaring a channel best because it produced the largest list.

How do I track where my leads came from?

Record the capture route, available campaign or referral information and any customer-reported source. Use consistent labels, check the setup with a test enquiry and leave missing details unknown. Analytics and CRM records can answer different questions.

Does Direct traffic mean someone typed my website address?

Not necessarily. Google Analytics uses Direct when it has no clear referral source. A typed address is one possibility, but missing source information can also result in Direct traffic.

Can Kibi CRM generate leads for me?

Kibi helps capture, organise and follow up enquiries from supported routes. It does not supply a prospect database or guarantee new customers. Your marketing, referrals and other activity bring the interest; Kibi helps your team handle it.

Can I start tracking lead sources in a spreadsheet?

Yes. Start with the request, known source, contact details, owner and next follow-up. Our lead-tracking template gives you a practical starting point. Consider a shared CRM when the team needs a clearer home for connected enquiries and conversations.

Choose one source. Make the next hello count.

Pick one place your next suitable customer might find you. Make the offer understandable, check the enquiry route and agree who picks up the conversation.

Keep a little context with the request. “Priya sent me” deserves more than a lonely row called Lead 47.

External references were checked on 18 October 2026 and are linked beside the relevant advice. Kibi setup follows the current product guides. The worked examples are fictional.

Try Kibi CRM for shared enquiries and follow-upExplore the Kibi CRM demoFind the right setup for your first sourceRead a source-based explanation of lead origin

Try one thing on the next enquiry.
Pick a change your team can use tomorrow.