A lead that expired in someone's inbox
The vendor's partner portal sent a notification: a new lead for a mid-sized company in your region, interested in the product you specialise in. Accept within a set time or it goes to another partner. The notification went to your channel lead, who was at a vendor event for two days. By the time she saw it, the lead had been reassigned.
Another lead was accepted but never followed up, because it was never entered into the CRM. The vendor noticed, and asked why your lead conversion was so low.
Why vendor leads fall through
Vendors pass leads to partners they trust, and they watch what happens: acceptance speed, follow-up, outcome updates. Each vendor runs this differently, through its own portal and notifications, with its own deadlines. Leads arrive irregularly, which makes them easy to overlook, and they sit outside your normal lead flow from your own website and marketing.
Outcome reporting is often required, and it is the step most often skipped because it happens after the deal is won or lost, in a portal nobody visits.
| Stage | Typical requirement | Common failure |
|---|---|---|
| Accept or decline | Within a vendor-set window | Notification not seen in time |
| First contact | Within a set period | Lead not in the CRM |
| Progress updates | At intervals | Portal never updated |
| Outcome | Won, lost or reason | Never reported |
What unanswered leads cost
Each vendor-passed lead is a warm prospect you did not pay to find. Losing it to a slow response is a direct loss. Vendors also allocate future leads based on how partners handle them, so poor handling reduces the flow. And prospects who wait days to hear from anyone form an opinion of you before the first call.
Leads that are accepted and then left also leave you exposed in partner reviews. Vendor channel managers can see accepted leads with no update, and it is a difficult conversation to explain that the lead was never in your CRM in the first place.
The lead intake we build
- Capture: lead notifications from vendor portals are routed to a shared inbox, read, and each lead's details, deadline and vendor reference are extracted; vendor lead APIs are used where they exist.
- CRM creation: every lead is created in your CRM with its source vendor, deadline and reference, and checked against existing customers and open deals to avoid duplicates.
- Assignment: leads are assigned by your rules, such as region, product or customer size, with a named backup when the owner is away.
- Deadline tracking: acceptance and first-contact deadlines are tracked, with alerts to the owner and a manager as they approach.
- Portal actions: the person gets a direct link to accept or update the lead in the vendor portal, and the task is not closed until the action is confirmed.
- Outcome reporting: when the opportunity is won or lost, a reminder prompts the owner to report the outcome to the vendor, with the details prepared.
Leads handled on a normal week
Vendor-passed leads appear in the CRM like any other, clearly labelled, with their deadlines. Nobody depends on one person's inbox. Vendor channel managers see prompt acceptance and outcome updates, which is the behaviour that earns more leads.
Sales managers get something they rarely have: a view of vendor-passed leads by vendor, with how quickly each was accepted, contacted and closed. That makes it easier to see which vendors send leads worth having, and to show a channel manager real numbers at the next partner review.
Are vendor leads slipping in your business?
- Vendor leads arrive in one person's inbox.
- Leads have been reassigned because you did not accept in time.
- Vendor-passed leads are not always entered into your CRM.
- Outcomes are rarely reported back to vendors.
- A vendor has questioned your lead handling.