Loading
Lead 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.
Most intake failures are boring. 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; there was simply no owner and no clock, and a queue without either is a waiting room.
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. Whatever model is bolted on later is an argument about maths rather than a fact about the record.
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 all land on the same record shape with validation applied once, then route by the rules you wrote.
A fallback owner exists precisely so that nothing can sit unassigned while everyone assumes somebody else has it.
Time to first contact is the first to move, usually sharply, because assignment and a due task remove the two reasons it was ever slow. Teams that measured this in hours tend to end up measuring it in minutes, and the effect on conversion is visible before the month is out.
The second number is unowned leads, which should be zero and rarely is. A fallback owner plus escalation by name makes the gap visible immediately; most companies find a handful of routes — an old form, a switchboard, a partner email — that were quietly dropping enquiries.
Attribution takes longer to pay off, because it needs a full sales cycle to become interesting. But once source rides the record into closed revenue, the marketing conversation changes from which page gets traffic to which page pays for itself — and effort moves accordingly.
It does not score leads with a proprietary model — ranking uses criteria you can read.
It will not clean a bought list; validation rejects rubbish rather than repairing it.
It is not a marketing automation suite; nurture sequences belong to your email tool.
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.
| Shared inbox | Form tool plus CRM | Treepie Flow | |
|---|---|---|---|
| Time to an owner | When someone checks the inbox | After the sync runs | Seconds, by rule |
| Duplicates | Created every time | Often created | Caught on entry |
| Source tracking | Lost | Partly kept | Page, campaign and referrer to revenue |
| Routing rules | None | Basic | Territory, size, interest, round-robin, fallback |
| Unclaimed leads | Invisible | In a list | Queue with wait time and escalation |
Yes, via the API or a posted payload. The field map is defined once and shared by every intake route, so behaviour is identical wherever the lead came from.
It attaches to that organisation rather than creating a duplicate, and the account owner is notified so the conversation is not had twice.
On the lead, then on the deal it becomes. Attribution is therefore a property of the record rather than a last-click model applied at the end.
A required fallback owner and an SLA on first contact, with escalation by name when the clock runs out.
Yes — matching runs across leads and organisations, and proposed merges are reviewed rather than applied silently.
Yes. Because source rides the record, the lead’s outcome — including closed value — is visible without exporting anything.
Yes, through the API or a posted payload, sharing one field map with Flow’s own forms.
Within seconds of arrival, after the duplicate check and enrichment have run.
Territory, company size, product interest, source and round-robin within a team, in an order you set, with a fallback owner.
It waits in a queue with its wait time visible, and escalates to a manager after the threshold you set.
A matching enquiry attaches to the existing record as activity instead of creating a second lead.
UTMs, referrer, landing page and campaign are captured on arrival and carried through to the deal and closed revenue.
Yes. Round-robin can skip people who are away or at their limit of open leads.
Yes. Forms record which purposes the person agreed to, with the wording shown, onto the contact.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.