Denha NexusFeature · Lead quality

Lead quality: who fills in the forms and how real they are

Leads from platform lead forms and from client sites land in one feed the moment they are submitted. Each gets a bot score built from a set of signals, is read against the client industry profile, and is checked for whether it actually reached the CRM. The score does not replace a manager - it says what to look at first.

14 days on any plan, no card needed to start. After the click: a three-field form and the workspace.

Where the leads come from

Platform lead forms
Facebook, Instagram and LinkedIn - at the moment the form is submitted
Site forms
A public intake endpoint, up to 5 leads a minute from one address
What arrives
Form fields, campaign and ad, click identifiers, UTM tags
Bot score
A sum of signals: flagged from 40 points, blocked from 70
Industry profile
Qualifying questions and disqualifying answers for the client niche
Delivery
A check that the lead reached the client CRM, when it is passed on

Intake and forwarding work the same way for every client of the agency: there are no per-client scripts anywhere in the system.

01What it looks like

Lead quality in ADS Beast: signals, profile, delivery

Screen recording: the lead feed with bot scores and the signals behind them, industry qualifying fields, CRM delivery status, and conversions going back to the platforms.

A screen recording of the product in the ADS Beast demo workspace. The clients and campaigns on screen exist for the demonstration; no real advertiser stands behind them.
02What it does

What the section does with leads

01

A bot score built from many signals, not one giveaway sign

A disposable mailbox, the speed the form was filled in, repeated text, a phone number that does not exist, a suspicious source - each signal adds points. A lead from 40 points is flagged for review, and from 70 it is blocked. What happens to a flagged lead is a manager decision.

  • The score and the list of signals that fired, on every lead
  • A list of disposable mail domains
  • A flag for review instead of a quiet deletion
02

An industry profile instead of generic questions

A client niche has its own qualifying questions: budget, buying horizon, role in the decision, what the person is interested in. And its own disqualifying answers. The profile decides which fields to ask for and which answers mean the lead is not a fit.

  • Qualifying fields matched to the client niche
  • Disqualifying answers with the reason
  • The lead matched to a client property or service
03

A check that the lead arrived

A lead that stayed in the system and never reached the client CRM does not exist as far as the client is concerned. The system checks delivery and raises an alert when forwarding stops working, rather than when the client asks why nobody is calling.

  • A delivery status on every lead
  • An alert when forwarding to the CRM fails
  • A resend once the connection is back
04

The feedback goes back into the campaigns

When a manager marks a lead as qualified or as a sale, the event goes back to the platforms as a server conversion every 30 minutes. Delivery then learns from real deals instead of everyone who pressed a button.

  • Conversions from CRM stages into Meta, Google and the Advertising in ChatGPT channel
  • Cost per qualified lead, rather than cost per lead
  • A list of the campaigns and ads that bring in rubbish
03How it works

The path of a single lead

From the button press on a form to a conversion back in the ad account there are four steps, and a person takes part in one.

  1. 01

    The form is submitted

    The lead arrives with its form fields, campaign and click identifier.

  2. 02

    Checks

    Bot score, industry profile, disqualifying answers.

  3. 03

    Delivery and work

    The lead goes to the client CRM and a manager sets its status.

  4. 04

    Back to the account

    A qualified lead and a sale go back as server conversions every 30 minutes.

04How it fits together

Where the data comes from and what you get out of it.

Ad accounts hand over their statistics through your own OAuth apps. The system puts them into one picture, agents look for what to change, and only what you approve gets changed.

Platforms
  • Google AdsOAuth
  • MetaOAuth
  • TikTokOAuth
  • LinkedInOAuth
  • Microsoft AdvertisingOAuth
  • Windsor.aiAPI key
ADS Beast
Combines and checks
  • sync every 15 minutes
  • conversion to USD at the day rate
  • reconciliation with the native account
  • 90 days of history
What you get
  1. One spend summaryEvery account in one currency and one date window.
  2. Tasks from agentsWhat to change, where and why, linked to the row in the account.
  3. A person decidesBudgets, bids and statuses change only after approval.

Early access

See your own ad accounts the way the diagram shows them.

We are opening access to agencies in turn. Leave a work email and we will write when your turn comes, then help you connect the first account.

We use the email only to reply about access. Privacy policy

05Figures from the code
70
points and the lead is blocked
40
points and the lead is flagged
30 min
between conversion uploads to the accounts
5
leads a minute from one address on a site form
06What it does not do

What the section does not do

  • It does not delete leads quietly: a flagged lead stays visible, and a manager decides about it.
  • It does not treat a bot score as a verdict - it is a sum of signals, not a fact.
  • It does not work for one client alone: intake and forwarding are the same across the agency.
  • It does not invent qualifying fields that the industry profile does not have.
07Questions and answers

Questions and answers

How is the bot score worked out?

As a sum of signals: a disposable mailbox, the fill-in speed, repeated text, a phone number that does not exist, an odd source. From 40 points the lead is flagged for review, from 70 it is blocked. The signals that fired are listed on every lead.

What happens to a flagged lead?

It stays in the feed with its flag and its list of signals. A manager decides whether to work it. The system does not delete leads quietly.

How does the system know a lead never reached the CRM?

Forwarding to the client CRM is confirmed by the response from the receiving side. If there is no response, or it carries an error, the lead is marked undelivered and an alert goes out naming the client and the channel.

Why send conversions back to the platforms?

So that delivery optimises towards people who buy rather than people who merely submit forms. The event comes from the deal stage in the CRM, not from the fact that a form was sent.

Connect your first form and see how many leads are real at all

The first 14 days are free on any plan and you do not need a card to start. The bot score and the delivery check work from the first lead.

14 days on any plan, no card needed to start. After the click: a three-field form and the workspace.