Email intake
Create leads from labeled emails sent to the company intake address.
Turn inbound emails from your lead sources into routed leads, without anyone re-typing them.
Why it matters
Some sources still deliver by email. Email intake receives those messages, records each one idempotently, and parses it into a structured lead, so an email source becomes just another entry point into the same routing engine — no manual copy-paste, no missed message.
See it in HoneyFalcon
Step 1 of 3: email intake address and English format labels.
Step 2 of 3: configured extra Email field and exact email label.
Step 3 of 3: resulting email lead fields and source.
Convert inbound email into routed leads
Receive and record every message once
An inbound message is captured as an ingestion event tied to your organization and stored before processing, so nothing is lost between arrival and parsing.
Because capture is idempotent, the same message delivered twice does not create duplicate leads.
Parse into a structured lead
The recorded message is parsed into the lead fields your routing needs, then follows the same allocation, tag, and cost rules as any other source.
An email source is onboarded by pointing it at the intake, not by building a separate downstream workflow.
Send a representative message from the real source and confirm the parsed lead before production traffic — parsing depends on the source's actual format.
Your email intake is ready when
- An inbound message becomes one structured, routed lead.
- A duplicate delivery does not create a duplicate lead.