Lead Intake

Supported sources

Field mapping

Every lead ends up as a row with this canonical shape, regardless of source:

{
  customer_name: string?,
  phone:         string?,
  email:         string?,
  source:        "website" | "landing_page" | "sms" | "email" |
                 "facebook" | "google_business" | "missed_call" | "manual",
  service_type:  string?,
  message:       string,           // required — verbatim text we received
  property_address: string?,
  zip_code:      string?,
  created_at:    ISO-8601 string
}

If a source sends a field we don't recognize (e.g. a Facebook custom question), it lands in message appended below a --- separator so nothing is silently dropped.

Deduplication

We dedupe on a rolling 24-hour window using phone OR email within the same business_id. A duplicate doesn't create a new lead — it appends to the existing lead's message thread and triggers a follow-up rule ("customer reached out again"). This is intentional: customers who text and then fill the web form are the same person and you don't want two AI replies.

Routing rules

After parse, each lead is checked against your rules in order. The first matching rule wins:

1. Out of service area — zip not in your list → polite decline + suggest a referral partner if you've set one.
2. Blocked service type — e.g. "commercial only" or "residential only" → polite decline.
3. Quiet hours — outside your hours → confirm receipt + schedule follow-up for your next open window.
4. VIP customer — phone matches an existing customer → routed directly to you, AI does not reply.
5. Default — qualify + reply.

Testing a source

Every source has a Send test lead button in Integrations. The test lead is tagged source = manual so it doesn't pollute your analytics. You can also pipe to a sandbox AI configuration (Settings → AI Rules → "Test mode for new sources") to verify the reply before going live.