Lead delivery methods: CRM, email, webhook, and what to ask a provider for
Email, CRM and webhook are not three grades of service; they are three answers to one question: who makes the first call, and where are they when the lead lands? Choose the method for that person, then hold the provider to the same standard whichever you pick.
Three lead delivery methods are common in the Australian finance-lead market: an email per lead, a direct push into your CRM, and a webhook to a URL you control. The premium option is whichever one puts the enquiry in front of the person who will dial it, in real time once it clears verification, with every field in its own place.
A solo broker on the road is looking at a phone. A three-person team is looking at a CRM queue. A firm with an operations person is looking at its automation. Match the pipe to the person, then run the checklist below.
Email, one lead per message
The simplest pipe, and the hardest for a provider to get wrong. Lands on your phone as well as your desk. Weak points: shared inboxes nobody owns, filters that quietly reroute, and re-keying into your CRM that happens later or never.
Direct CRM delivery
The enquiry is created as a contact, lead or deal in your CRM on delivery, each submitted field mapped to a CRM field. Best for teams, round-robin and reporting. Needs a mapping agreed before go-live and an alert rule, or the record is created and then ignored.
Webhook
The provider posts a structured payload to an endpoint you control. You decide what happens next: create the record, text the assigned broker, open a task, stamp the time. Most flexible, and you own the plumbing and its failures.
Delivery method is a staffing decision dressed up as a technical one. Work out who dials, then choose.
- Solo broker, mostly on the road. Email to an inbox that pushes to your phone, with a background integration creating the CRM record so nothing is re-keyed. You need the alert more than the database.
- Small team with round-robin. Direct CRM delivery with an assignment rule, so each enquiry lands on one named person with a task and a due time. A lead that belongs to the team belongs to nobody.
- Firm with its own stack. Webhook into your automation layer: dedup, assign, alert by SMS, and stamp the delivery time so time to first call is measured without anyone logging it.
- First time buying leads. Run email and a CRM copy in parallel. Once the mapping has held for a full week, keep the email as a backup or switch it off. Nobody should lose a lead to an unfinished integration.
Whichever you pick, you need an alert channel a human notices and a system of record that survives staff changes. Email is a good alert and a poor database; a CRM is the reverse until notifications are set up. The method does not convert the lead; the first call does, see how to convert finance leads.
These apply whether you chose email, CRM or webhook. A provider who has done this for brokers before will have the answers ready.
- Field-level delivery. Full name, verified mobile, email, finance type, loan amount, purpose, estimated timeframe and the notes from submission, each in its own field, not pasted into a comments box. The full list is in what data fields a finance lead should include.
- Two timestamps. When the enquiry was verified and when it was delivered to you. Without them you cannot measure your time to first call, or tell a slow provider from a slow team.
- A lead reference that matches the invoice. One identifier on the delivered record and on the bill, so reconciliation is a lookup rather than an argument.
- A test lead before go-live. A clearly marked test lead pushed down the real pipe, so you watch the mapping land before any spend.
- Duplicate and failure behaviour. If the same person enquires twice, is a second record created, the first updated, or the enquiry held back? If your CRM rejects the record or the webhook errors, does the provider retry, fall back to email, or drop it?
- Credentials you control. Integration access into your CRM should be issued by you, scoped to creating records, and revocable without a phone call.
When CRM or webhook delivery fails, it is rarely the connection. It is the mapping. The mobile arrives with a leading zero when your CRM expects a country code, so click-to-dial breaks. The loan amount arrives as text, so your pipeline report cannot add it up. The timeframe arrives as free text where your CRM has a picklist, so it lands in the wrong field or none. The notes from submission, often the sentence that explains the enquiry, land in a field nobody has on screen.
Three checks fix most of it. Agree a written mapping, one submitted field to one CRM field, before anything is live. Open the test record the way your team will open it, on a phone, not the admin screen. Give verification status its own field rather than a line in a note, so the mobile you dial is the one that was confirmed. And if your CRM merges new enquiries into existing contacts, make sure this submission's amount, purpose and timeframe are kept, not overwritten.
Every lead is delivered to the broker's inbox or CRM in real time, after the prospect has confirmed their mobile by SMS code and the enquiry has passed automated scoring and a human qualification review, carrying the eight fields listed under field-level delivery above. Pay per lead, no lock-in contracts, no setup fees, and campaigns are typically live within 7 days, which leaves you time to settle your mapping and ask for a test record. The field list on business loan leads is what will land in your CRM; the rest of the provider decision is in how to choose a finance lead provider.