Skip to content

Sales & CRM Systems

Lead capture: every inquiry becomes a record, wherever it arrived

Inquiries come in as form notifications, voicemails, forwarded emails and marketplace messages. Capture turns each one into the same kind of record, with its source attached, before anyone has to remember it.
Discuss your systemSee five formats become one record ↓
Form notification09:31D.R. · roof leak · Clark StVoicemail21:14“…the drain at 2200 Lincoln”Referral emailfwd“…neighbor P.S., water heater”Marketplace#48213Faucet replacement · ZIP 60657Intakesaved firstLead record1 of 42 of 43 of 44 of 4contactD.R.M.K.P.S.#48213requestRoof leakDrainWater heaterKitchen faucetlocationClark St2200 Lincoln—60657sourceWeb formPhoneReferralMarketplacechannelFormVoicemailEmailMarketplacereceived09:3121:1408:0510:12missingTimingCallback timeAddressPhone number

Where inquiries actually arrive, and what gets lost on the way

Each channel loses something different. Capture has to handle all of them, not just the website form.

  1. 01

    Web form

    An email notification to a shared inbox

    Lost on the way: Whether anyone replied, and which page it came from.

  2. 02

    Phone

    A voicemail or a note on paper

    Lost on the way: The call itself, if nobody listens back.

  3. 03

    Email

    A thread, sometimes forwarded twice

    Lost on the way: Who it was originally from.

  4. 04

    Referral

    A name passed along by someone else

    Lost on the way: Who referred them, which is the part worth thanking.

  5. 05

    Marketplace

    A message inside another company's dashboard

    Lost on the way: The deadline to respond, and the request after it expires.

From five formats to one record

Every lead gets the same shape, so qualification, routing and reporting never have to guess where a field lives.

  • Form notification09:31

    New submission: Name: D.R. · Phone: (312) 555-0199 · Message: roof leak at the office on Clark St, sometime this week?

  • Voicemail transcript21:14

    Hi, this is M.K., calling about the drain at 2200 Lincoln. Call me back at 555-0123.

  • Referral emailfwd

    Forwarding my neighbor P.S., she needs her water heater looked at. Her number's below.

  • Marketplace message#48213

    Request #48213 · Kitchen faucet replacement · ZIP 60657 · responds within 24 h

Lead record

contact
D.R.
request
Roof leak
location
Clark St
source
Web form
channel
Form notification
received
09:31
missing
Timing not confirmed
Contact
Who, and how to reach them. Matched against existing contacts before a new one is created.
Request
What they asked for, in their words and as a structured service type.
Location
An address or ZIP, because most service businesses route on it.
Source
Where the lead came from: the referrer, the campaign, the marketplace.
Channel
How it arrived: form, call, email, marketplace.
Received
The time it arrived, not the time someone typed it in.
Missing
What the inquiry didn't say.

The missing field matters most. A gap that's recorded gets asked about on the first call. A gap that's filled in with a guess becomes a wrong quote.

Same person, or the same message twice?

Duplicate delivery

Web form · 09:31:04

D.R.(312) 555-0199roof leak

Web form · 09:31:44

D.R.(312) 555-0199roof leak

Match: same submission, same fields, 40 seconds apart

Kept once. The second delivery is logged, not turned into a second lead.

Returning customer

Contact since July

D.R.(312) 555-0199gutter repair

Web form today

D.R.(312) 555-0199roof leak

Match: same phone, different request, three months apart

New lead, linked to the existing contact. Their history comes with it.

Treating every repeat as a duplicate hides returning customers. Treating every repeat as new floods the CRM. Identity rules, written down and agreed, decide which is which, and the edge cases go to a person.

Saved first, synced second

Capture keeps its own copy of every inquiry before it touches the CRM. If the CRM is slow or down, the lead still exists, and the sync is retried until it lands. Intake owns the raw inquiry; the CRM owns the relationship. Keeping those two jobs separate is what makes “we never lose a lead” true.

  1. 09:31:04intake.receivedWeb form, D.R.
  2. 09:31:05lead.createdSaved in intake
  3. 09:31:06crm.sync failedCRM timeout
  4. 09:33:06crm.sync okRetried

What capture hands off

In

Forms & calls
submissions · call outcomes · transcripts
Email & referrals
messages · forwarded referrals
Marketplaces & lists
requests · imports from approved sources
Lead capture
normalize · match · save first

Out

Lead record
source · channel · what's missing
Contact link
the existing contact, when there is one
Event
lead.created → starts qualification

Worth building when inquiries arrive in more than one place

Good fit

  • Inquiries arrive through three or more channels.
  • Someone retypes inquiries into the CRM by hand.
  • You can't say where last month's leads came from.

Not the right fit

  • Every inquiry already lands in one system with its source recorded.
  • The problem is that too few inquiries arrive. Capture handles interest; it doesn't create it.

Where capture does its work

What happens next

Questions about lead capture

Do we need to replace our website forms?

Usually not. Existing forms can send to the intake directly or through their notification email. We change a form only when it's missing something the business actually needs.

Can it capture leads from marketplaces and directories?

When the marketplace offers an export, an API or a notification email, yes. When it doesn't, the request is entered once, in the intake, instead of in several places.

What happens to spam and junk submissions?

They're captured and marked, not silently dropped, so a real inquiry caught by a filter can still be found.

How do phone calls get captured?

From call logs and voicemail transcripts, or completely when calls are answered by an AI receptionist that writes the record during the call.