Lead Forensics

Visitor identification is a matching service at heart: an IP address is looked up in a business database the company owns, and when supporting sources disagree about which business sits behind an address, in house AI and machine learning weigh the signals before a match is shown. Alerts, the lead manager, contact data and CRM routing run on rules and would work the same without models. A website chatbot answers questions and collects contact details, and the technology behind it is not described.

On the Automate package, priority visitors become Salesforce leads automatically and are assigned to an owner under rules the customer writes from firmographics and site behavior, while known accounts get visit data appended to their records. The chatbot talks to visitors around the clock. Review steps before records are created, limits on how many leads a rule can generate, and controls over what the chatbot may say or promise are not described.

Machine learning sits inside the matching process, weighing sources that disagree about which business owns an IP address, yet the models, the confidence threshold for a match and the share of matches that depend on them go unexplained. The chatbot is described by what it does for visitors, with no word on the technology behind it or on whether visitors learn they are chatting with software. Supplied contact records, by contrast, can each be traced to the source they came from.

Case studies attach figures to named customers. Handtmann traced a deal of about £250,000 to a company that downloaded its pet food brochure but turned out to make horse treats, LightTrans closed a €130,000 software deal, Empire Hire added more than £20,000 in sales in two months, and MPA reports a 720 percent gross ROI. Other stories cite 16,000 opportunities found in six months. How the ROI figures are calculated, and over what period, is not given.

Lead Forensics supplies signals and contacts, and the customer carries the compliance load: lawful basis, privacy notices, cookie consent, opt outs, and the electronic marketing and calling rules that govern any contact data used. The supplied decision makers are not the visitors themselves, which limits what a rep can claim to know. Scrubbing supplied numbers against do not call or telephone preference lists is not offered to customers, although the company checks its own sales calls against the UK TPS and CTPS lists every day.

Customer data is processed under a GDPR data processing agreement covering security, subprocessors, transfers, assistance and deletion or return, and customers can subscribe to notices of agreement and subprocessor changes. Transfers rely on adequacy decisions, standard contractual clauses, the UK transfer agreement or the UK Addendum. The hard question for visitor tracking, the lawful basis for monitoring visitors, is left to each customer along with the notices those visitors see. The subprocessor list sits inside the agreement rather than in public.

Company matches come from a database of business IP addresses built and maintained in house, with supporting sources checked against each other instead of being accepted in a fixed order of preference. Contact data comes from approved third party suppliers that act as independent controllers, and every record can be traced to its original source. The suppliers are not named, and any warranty or indemnity behind the contact data sits in contracts that are not public. Consumer details and sole traders are excluded.

Collection runs through a script the customer places on its own website, with an optional cookie to raise the match rate, so no outside platform is automated. Native connectors reach Salesforce, HubSpot, Microsoft Dynamics, Pipedrive and Zoho. The one open point is LinkedIn: supplied contact records include LinkedIn profiles and the product encourages outreach there, while the suppliers' methods for gathering that data are not described.

Customer data is handled on the customer's instructions, held under ISO 27001 controls, and deleted or returned when the agreement ends. Usage data, logs and telemetry may be used to improve the service, with aggregation or anonymization where appropriate. When an address is not yet in the database the company may research the business behind it, so customer traffic can feed the shared database. Whether visit data or chatbot conversations train the matching models or the chatbot is not addressed.

Two groups meet the product without choosing it. Website visitors are identified at company level, and telling them so is left to the customer's own privacy notice. Visitors who open the chatbot meet a conversational assistant, with nothing saying it introduces itself as software and no position on Article 50 of the EU AI Act. Contacts supplied for outreach are not the visitors, which keeps reps from implying they know who browsed.

The Salesforce connector checks whether a visiting company already exists, creates and assigns new priority leads under customer rules, appends visit insights to existing records, alerts the owner, and adds reports on visits and assignments inside Salesforce. HubSpot, Microsoft Dynamics, Pipedrive and Zoho have native connectors, and more than 60 other tools link in, from Gmail and Google Sheets to Intercom, Jira and email marketing platforms. A public API is not offered, and sync direction and field mapping are not spelled out.

The service runs on cloud infrastructure and processes data wherever the company's systems and approved subprocessors operate, with transfers covered by the usual UK and EU mechanisms. Hosting providers, regions and any customer choice of location are not named. Backups follow standard cycles under access controls, and resilience covers monitoring, alerting, capacity planning and recovery procedures.

Lead Forensics is certified to ISO/IEC 27001, runs an information security management system and holds no SOC 2 report. The certificate and the technical and organizational measures sit in a trust center that customers and prospects can request access to, and penetration test summaries come through the trust center or under NDA. Controls include role based access, encryption in transit, logging, vulnerability management and breach notice without undue delay. Single sign on through a customer's identity provider is arranged with sales.

Two packages are named with their features: Essentials for identification, firmographics, contact data, alerts, the lead manager and CRM integration, and Automate adding workflow automation, CRM lead creation, automated routing and ABM account matching. Price depends on website traffic and the number of new leads found, is set after a one week free trial, and is never shown. Users are unlimited on every plan, so headcount never changes the bill.

Export depends on configuration and the contracted services, with a support or privacy request as the route where it is not self service. At contract end, customer personal data is deleted or returned under the data processing agreement and the customer agreement, unless law requires keeping it. The customer agreement itself, with its term, renewal and notice periods, is not public.

Lead Forensics sends alerts and reports to a team's inbox or CRM rather than outreach to prospects, so its own sending follows the number of alerts configured. Emails written from its contact data go out through the customer's own CRM or campaign tools. Email verification and bounce rates for the supplied contacts are not described.

Sales, marketing, account management, agency and advertising teams at B2B companies are the buyers, with use cases for new leads, pipeline, expansion and lapsed customers. Named customers lean toward manufacturing and industrial firms in the UK, Europe and the US, among them Handtmann, Waupaca Foundry, Coltraco Ultrasonics, YB Fixings, Avail Logistics and LightTrans. The company counts 10,000 businesses as customers and runs sales lines in the US and UK. Match coverage outside those markets is not broken out.