From intent to a dialable lead
Four steps, all of them ours. We generate the demand, qualify it before it moves, deliver it into the tool your agents already have open, and let your own dispositions shape what comes next.
The path a lead takes
Nothing in this chain is outsourced to a vendor we cannot call, which is the reason each step can be described this precisely.
-
1
Generate
We buy the media and write the offers ourselves. Every program starts with a campaign we own: the placement, the creative, the landing page, and the disclosure the prospect reads before they hit submit. Nothing is bought from an aggregator and rebadged, so we can tell you exactly where a record came from and what it was told.
-
2
Qualify
Phone validation, duplicate suppression across programs and time, state and county licensing geography, age and product fit, and the disqualifiers your desk supplies all run before delivery. A record that fails any of them is not sent and not billed. Filtering after the fact is just a dispute process with better branding.
-
3
Deliver
In seconds, by one of four paths: natively into an AgentTech Dialer campaign, natively into a Solved Enroll client record (open to agencies in the Solved Enroll private beta), by HTTP post, or by webhook. Delivery happens on submission because speed to dial is the single biggest lever on contact rate, and every minute a lead sits in a batch is spent.
-
4
Convert and feed back
Your agents work the lead and send the disposition back. Those outcomes tighten the filters on that buyer's traffic: the sources that produce bad numbers get cut, the intent signals that produce sales get weighted, and the program you are buying next month is shaped by what your own floor did last month.
What qualifying actually means
Five checks run in line, before the record is delivered and before it is billed.
- Phone validation. Line type and reachability are checked before the record is sent, so a disconnected number is caught here rather than by an agent.
- Duplicate suppression. Across programs and across time, not just inside one campaign. A prospect who filled out two of our forms is one lead, and a record you already bought is not sold to you again.
- Licensing geography. State and county targeting matched to where your agents can actually write. A lead in a state you are not appointed in is a lead you cannot work.
- Age and product fit. A 52-year-old asking about Medicare is not a Medicare lead. Product interest, age band, and the answers captured at the form all have to line up with the program you bought.
- Your own disqualifiers. The rules your desk learned the hard way: counties that never close, answers that predict a no, list sources you want excluded. Add them and stop paying for them.
Four ways a lead reaches your desk
Pick one or run two side by side. Delivery is on submission in every case.
AgentTech Dialer
Leads land in a campaign and start dialing. The disposition comes back to us automatically, so the feedback loop closes without anyone exporting a spreadsheet.
See the dialerSolved Enroll
The client record is created with what the prospect already told us, so the fact-find starts from the answers instead of repeating them back.
See the platformHTTP post
Field mapping you specify, posted to your endpoint on submission. If your system accepts a form post, it accepts our leads.
Delivery and routingWebhook
A signed payload to your listener with retries when your endpoint is down, and a notification when we could not deliver at all.
See integrationsPacing is part of delivery
Daily and hourly caps, dayparting so leads arrive while agents are on the phone, and the ability to pause without penalty when you are short-staffed. A program that floods a desk on Monday and goes quiet on Thursday is not a volume problem, it is a pacing problem. Details are on the delivery page.
The first week of a new program
Four moments, in this order. None of them involve a contract negotiation.
Day one
Test mode
Sample leads flow through your integration before a dollar is spent. You confirm the fields land where you expect them and that a record opens correctly in front of an agent.
Day two
Integration sign-off
We agree the field map, the caps, the delivery windows, and the disqualifiers in writing. Whoever owns your CRM is on that thread, not hearing about it later.
Week one
A small ramp
Volume starts below what your floor can handle on purpose. The point of the first week is a clean measurement, not a big number.
End of week one
First review
We look at delivery, contact, and whatever outcomes you have back. Anything obviously wrong gets cut, and the ramp moves only if the numbers earned it.
Why the ramp starts small
Because the only number that matters is the one your own floor produces, and you cannot read it through a flood. A small first week gives you a clean cost per acquisition on your agents, your scripts, and your states. Scale after that is arithmetic. Scale before it is a guess you pay for.
What can go wrong, and what happens then
Every lead program has bad days. The difference is whether the rules were written before one of them arrived.
A bad batch gets through
It happens: a source degrades, or a creative attracts the wrong intent. Submit the records inside the stated window and the credit is applied against the written criteria rather than argued. Then we go find the source and cut it, because crediting the same problem twice is not a fix.
Your endpoint goes down
We retry, and we tell you we could not deliver rather than letting the records disappear quietly. If the outage is long, the program pauses instead of pushing leads into a system nobody is watching. You are not billed for what we could not hand you.
A vertical does not fit your desk
Some floors are excellent on final expense and flat on Medicare, and a script or a licensing footprint is usually the reason. When the numbers say a vertical is not working for you, the honest move is to say so and move the budget to the one that is, or stop. We would rather keep one program working than sell three that do not.
Credit criteria are defined before you buy and the submission window is stated up front, so a bad batch is a process rather than a negotiation. The written rules are on the pricing page.
FAQs
About the process
How long does it take between a form fill and a lead arriving?
Delivery happens on submission. The qualification steps run in line, and the record is posted to your endpoint as soon as it clears them. There is no nightly batch and no queue where leads sit overnight losing value.
What happens if a lead fails one of the filters?
It is not delivered and you are not billed for it. Phone validation, duplicate suppression, licensing geography, product fit, and your own disqualifiers all run before the record reaches you, which is the point of running them at all.
How long does integration take?
Native delivery into an AgentTech Dialer campaign or a Solved Enroll client record is a configuration step rather than a project. An HTTP post or webhook into your own CRM usually takes an afternoon once someone on your side can tell us the field names and the endpoint. Test mode comes first either way.
Do I have to send dispositions back?
No, but the programs that perform best are the ones that do. Outcomes are what let us tighten filters on your traffic specifically rather than guessing from delivery data alone. Read more on the delivery page.
What does the first week actually look like?
Test mode into your endpoint, then integration sign-off, then a deliberately small ramp so you can measure your own cost per acquisition, then a first review where we cut what is not working. The ramp is set by what your floor can work, not by what we would like to sell.
Something else? Contact us
Start in test mode, not with a commitment.
Tell us your verticals, your states, and what your floor can work in a day. The first week is designed to prove the math on your own numbers.