For companies in Toolradar's lead-request pilot, open Leads for the active verified company. Review confirmed requests, record your team's follow-up status, check notification delivery separately and export the relevant records. Email confirmation is not business qualification.
- Tools listed
- 13,000+
- Submissions decided within 24 hours, last 30 days
- 94%
- Listing reads by AI assistants answering a person, last 30 days
- 66,000+
- Listed tools that are free or freemium
- 53%
Toolradar's own database, read 22 November 2026. Listing is free; it does not guarantee visits, rankings or AI answers.
First published and updated 6 November 2026. Dashboard definitions, filters and export behavior were checked against the current implementation on that date.
Toolradar, part of Dupple, sells vendor services and sponsored placements; see our commercial disclosure. This guide concerns its named-vendor demo requests, a separate product from Dupple's post-signup lead generation.
Confirm that your company can use the pilot
Start with the active company in your account. It must be verified, and the current pilot requires company-level permission unless access is opened more broadly. A message that lead requests are not open for your company is an availability state, not a zero-lead campaign result. Ask about participation through contact rather than creating another company to bypass the message.
Availability and receiving requests are also different. The service must be live, the company must be eligible, and its lead settings must accept requests with a configured notification route. Settings management requires an owner or admin. The company-team guide explains those roles; the claim guide covers getting the right company associated with an authorized account.
An eligible company's dashboard can remain accessible while new requests are switched off. Check availability, company selection and acceptance settings before interpreting an empty list.
Read confirmation and follow-up as separate states
The vendor dashboard selects requests whose email-verification state is verified. An unconfirmed submission is not shown as a vendor lead. Passing that confirmation step does not independently verify the person's employment, purchasing authority, budget or product fit. Review the request and apply your own documented qualification criteria.
Toolradar data: the current follow-up selector has 4 states, New, Contacted, Qualified and Not a fit. They describe the team's workflow for a confirmed request. They are separate from email verification and from whether a notification reached an email provider or a webhook endpoint.
Table: Follow-up states in the company Leads dashboard, implementation checked 6 November 2026. These are definitions, not measured customer results.
| Follow-up state | How a vendor should interpret the label | What it does not prove |
|---|---|---|
| New | A request is waiting for the team's first follow-up. | That it already meets the business's qualification criteria. |
| Contacted | The team records that it replied. | That the person answered, attended a meeting or bought anything. |
| Qualified | The team judged the request to be a relevant buyer. | An independent Toolradar assessment of the person's budget or authority. |
| Not a fit | The team records that the request is unsuitable. | That the email was invalid or notification delivery failed. |
Use a status after the corresponding work has happened. If several colleagues share the dashboard, agree who replies and what Qualified means for that business. Keep notes specific to the inquiry. A status change is an operational record, not a substitute for the conversation itself or a new marketing claim.
Understand the count and list scopes
The dashboard's summary cards count confirmed, non-test requests for the company across its stored history. The page shows the load time and the earliest matching record date when one exists. Those dates do not turn the cards into a report for a selected campaign.
Toolradar data: the list loads 25 records per page, newest first. Its status tabs filter the rows, while the summary cards retain their own all-time definitions. Looking at one page of rows is therefore not the same as reviewing the company's complete history. Use pagination and the displayed filters before comparing a visible row count with a card.
Test requests deserve a separate check. The list can show them, and its Hide test leads control changes that display. Summary cards exclude them. A test record is useful for inspecting the delivery workflow; it is not a real prospect and should not be included in acquisition results. Different scopes can explain a mismatch without showing that a request disappeared.
The dashboard definition snapshot records these implementation rules, without contact records, pilot-company names, a statistical sample or conversion results.
Open the dashboard for the contact details
A vendor notification is deliberately a short notice. The inspected template identifies the product, source context, a fixed seniority label and a company-size band, then links to the dashboard. It does not put the person's name, address, company name or free-text message into the notification, and it does not set a reply address to the requester.
Open the record through the authorized company account to inspect the inquiry and reply using the available contact information. Do not assume that replying to the notification itself contacts the prospective buyer. A missing address in the email is not evidence that the dashboard lost it. The privacy page describes how the product handles these request details.
A request can originate from a product page or a comparison. Its recorded source helps explain context; it does not prove that the person selected a winner, finished evaluating alternatives or committed to a purchase. The comparison-page guide explains that separate surface.
Keep notification delivery separate from buyer progress
The Reached you column concerns delivery routes. Email sent and a successful webhook result are different from the team contacting the person. A webhook response does not prove that a downstream CRM created the intended record, and an email-provider success does not prove inbox placement or reading.
Resend's guide to missing email, read 6 November 2026, explains the difference between provider processing and acceptance by a receiving mail server. Its explanation supports that distinction; it is not evidence for a Toolradar delivery rate. If a notification is missing, inspect the dashboard state and the configured route before classifying the inquiry as lost.
Toolradar data: the current delivery logic limits individual vendor notification emails to 20 in a rolling 24-hour period, then uses a summary path. The dashboard can label an email as paused at the daily limit. That label does not remove the request from the dashboard, and a configured webhook is a separate delivery route. This is an implementation cap, not a forecast that a vendor will receive that many requests.
For a failed delivery, the interface exposes a Send again action after the delivery process has failed. Inspect the displayed error and destination first; retrying a notification should not be reported as a newly acquired person. No email or webhook was sent for this guide.
Export a defined set rather than assume a complete archive
The current CSV export selects confirmed requests for the active company, honors the status filter and excludes test requests by default. The dashboard's export link carries the selected status. Its ordinary link does not include test rows just because the on-screen list is currently showing them.
Toolradar data: the export returns at most 5,000 records, ordered newest first. It has no date-range selector in the inspected route. A download is therefore a bounded set of stored requests, not a promise of an unlimited historical backup. If the result reaches the cap, do not silently treat it as every request the company has ever received.
Before reporting from the file, record the export time, selected status and treatment of tests. Keep its personal information within the team and systems authorized to handle it. A CSV download or an email-confirmed record does not establish a meeting, opportunity or revenue figure. Google's key-event documentation, read 6 November, likewise describes recording a defined action; the meaning of that action still matters when comparing reports.
The vendor analytics guide covers product views, outbound clicks and agent requests. Those counters are not this lead list. Likewise, customer-review invitations collect feedback rather than demo requests. Keep the event definitions separate when explaining performance.
A fictional reconciliation example
For the fictional vendor Birch Relay, a colleague sees test rows in the list but fewer requests in the summary cards. The team checks the test control, confirms that the cards exclude tests and inspects the selected status. It then records the CSV's filters before comparing the download with the dashboard.
This example contains no real prospect or customer result. It keeps a notification being sent separate from the team recording Contacted.
What we could not verify
We inspected dashboard, access, export and notification code. We did not access customer accounts or contacts, submit requests, send notifications or audit downstream CRMs. Pilot settings can change. See the editorial policy for corrections; these definitions do not establish lead quality or campaign outcomes.
Frequently asked questions
Can every verified company receive demo requests?
No. Access is currently a pilot, and eligibility, service availability and company acceptance settings are separate checks. Follow the availability message for the active company.
Does email confirmation make a request qualified?
No. Confirmation precedes the vendor's follow-up workflow. Qualified records the team's judgment of business fit, not independent verification of purchasing authority.
Why are test rows visible but absent from the summary cards?
The list can include test records while the cards exclude them. Review the test control and status filter before comparing those totals.
Does Export CSV download every request?
The inspected route returns up to 5,000 newest confirmed records, honors the status filter and excludes tests by default. It does not provide a date-range selector or guarantee an unlimited archive.
Does Email sent mean that the requester was contacted?
No. That label concerns the vendor notification route. Open the inquiry and record Contacted only after your team has actually followed up.
Spotted an outdated price or a wrong fact? Suggest a correction: we check it against the vendor's own page. Work for one of these vendors? Claim your listing to update it yourself.
Inspect your company's demo requests
Sign in and confirm the active company. Lead requests are currently available to participating pilot companies; follow the page's availability message.
Some offers on this page may be paid placements or contain affiliate links.