Everything between a stranger arriving and a named person owning them — with the page that made the lead still attached to it.
By Latha Kumaresan, Director · Reviewed 23 Sep 2026Lead capture collects new enquiries from web forms, landing pages and inboxes into the CRM with their source attached. Lead routing then assigns each one to the right person — by territory, company size, product interest or round-robin — so it is followed up quickly. In Treepie Flow both happen in seconds, duplicates are caught on entry, and the page that produced the lead stays attached through to closed revenue.
A form posts into a queue, the queue is checked twice a day, and by the time somebody replies the prospect has spoken to two competitors. Nobody was negligent.
The second failure is attribution. The source that produced the lead is captured at the form and lost at the first hand-off, so marketing reports impressions and clicks while sales reports revenue, and the two conversations never meet.
Treepie assigns at the moment of capture, schedules first contact as a task, and keeps the source attached all the way to the closed deal. The intake becomes accountable and the reporting becomes arithmetic.
Web forms, CSV and API intake land on the same record shape with validation applied once, then route by the rules you wrote.
Web forms, CSV and API intake landing on one record shape, with validation defined once and shared by every route.
Web formsLanding page captureCSV & API importBy territory, size, source or round robin, with a named fallback so nothing sits unowned.
Lead routingRound robinTerritory rulesThe page and campaign that produced the lead stay attached through qualification into the deal it becomes.
Lead source trackingUTM captureRevenue attributionFirst contact created as a task at capture, so the clock starts before anybody reads the queue.
Speed to leadFirst-contact taskFollow-up remindersA lead matching a known organisation attaches to it rather than creating a duplicate, and the account owner is told.
Lead deduplicationAccount matchingOwner notificationIf first contact misses its SLA it escalates by name, not to a dashboard.
Lead SLAEscalation rulesNamed fallbackRules are ordered and evaluated top-down. The first match wins; anything unmatched goes to a named fallback owner — never to nobody.
The lead, the deal and the invoice are views of one row, so crediting revenue to a page is a lookup rather than a model.
Attribution takes longer to pay off, because it needs a full sales cycle. Once source rides the record into closed revenue, the conversation changes from which page gets traffic to which page pays for itself.
Because it never leaves the record.
Get leads that are already enriched, deduplicated and assigned.
“Which new leads are mine today?”See unclaimed leads, wait times and who is at capacity.
“How long do inbound leads wait for a first reply?”Know which pages and campaigns produce leads that turn into revenue.
“Which landing page sourced the most closed revenue?”Change routing rules without code, with a fallback owner for anything unmatched.
“Where do leads from Ireland go?”