Lead intake
Choose the manual, webhook, or email path that matches the source system.
Bring leads in from manual entry, webhooks, and email — and send every valid one into the same routing engine.
Why it matters
Your demand arrives in more than one way. HoneyFalcon captures manual, webhook, and email leads through their own contracts, then routes them all the same, so no source becomes a disconnected workflow or a spreadsheet nobody watches.
See it in HoneyFalcon
Email intake address with webhook and manual entry navigation in context.
One routing engine, three ways in
Match the entry point to the source
A firm admin can enter a lead manually, a webhook can post leads from an external system, and email intake can turn inbound messages into leads.
Each entry point appears where it actually lives in the firm-admin navigation, so you always know which contract a given source uses.
Everything meets the same rules
However a lead enters, it becomes one traceable record and follows the same allocation, tag, and cost rules as every other lead.
That means you configure routing once, and a new source is onboarded by choosing its intake path — not by rebuilding downstream logic.
Send one test lead per source and confirm the resulting record before you point production traffic at it — it is the quickest way to prove the contract end to end.
Your intake is ready when
- Each source uses one documented intake contract.
- A test lead appears with the expected source, fields, and tags, then routes like any other lead.