Delivery and routing
A lead sitting in an inbox is a lead you paid for and did not work. Ours arrive on submission, in the system your agents already have open, with the field names you chose.
Four ways a lead reaches your floor
Two of them are native, because the systems belong to the same group. The other two exist because most desks already run something else, and a lead vendor should adapt to your stack rather than the other way around.
Native into an AgentTech Dialer campaign
The record lands in the campaign and list you name and enters the dial order under that campaign’s rules. There is no endpoint to build and no mapping to agree on, because both sides of the handoff are ours. Agents start dialing on leads that arrived while they were on the previous call, and dispositions flow back to us automatically, which is what makes the filters improve instead of staying frozen at whatever we guessed on day one.
Native into a Solved Enroll client record
A client record is created with the fact-find already populated from what the prospect told us: demographics, geography, plan or coverage interest, the budget or face amount, and the health answers where they gave them. The agent opens a quote instead of re-asking questions the prospect already answered twenty minutes ago, which is the single most irritating thing that happens on a first call.
HTTP post into your own CRM
We post each lead to a URL you give us, using the field names you specify, in the format your system expects. You define what a successful response looks like, and anything else counts as a failed delivery and enters the retry path. Any CRM that can accept a post can accept our leads, and you do not have to move your desk onto our software to buy from us.
Webhook into your own application
For the buyers whose stack is an application rather than a CRM form handler. We push a JSON event to the URL you subscribe, each event carries an id so a retry cannot create the same lead twice, and your side acknowledges with a 2xx. Same timing, same retry behavior, same delivery log.
About the Solved Enroll path. Solved Enroll is in private beta ahead of its 2027 public rollout, so native delivery into it is available to agencies in the beta program. The other three paths are available to any buyer.
What each method requires
The honest setup cost, stated before you commit to anything. Two of these need a login. Two of them need a short conversation between your developer and ours.
Delivery methods
| Method | What it requires | What happens on submission |
|---|---|---|
| AgentTech Dialer campaign | An accountPick the campaign and the list. Nothing to build, nothing to map. | Enters the dial orderDispositions return to us automatically, so the filters keep learning. |
| Solved Enroll client record | Beta accessAvailable to agencies in the private beta ahead of the 2027 rollout. | Client record createdFact-find pre-populated from the form, ready to quote. |
| HTTP post | URL and field mapForm-encoded or JSON, your auth header or key, and your definition of a successful response. | Posted to your endpointRetried on failure, with every attempt and response written to the delivery log. |
| Webhook | A subscribed URLYour side returns a 2xx. Each event carries an id, so a retry cannot double-create a lead. | Event pushedSame timing and the same retry behavior as an HTTP post. |
Every method starts in test mode. Sample records travel the real path with a test flag set, so you can prove the mapping, the authentication, and the agent screen before a dollar moves. Test records do not bill and are excluded from reporting.
There is no nightly CSV and no emailed batch, because a batch is just a delay with a filename. If you want a flat file for reconciliation, pull it from reporting rather than making it the delivery path.
Pricing is per lead and quoted by program, with no platform fee and no monthly minimum to start. See pricing.
Delivered on submission, because speed to dial is the lever
Of all the things a buyer can change about a lead program, the gap between the form and the first dial is the biggest single one, and it is the one most often lost to the vendor rather than to the floor. A record that reaches you an hour later is being worked against a prospect who has moved on with their day.
- Sent when the form is submitted. Not queued for a nightly job, not held for a quality review that happens tomorrow. The filters run first, and they run in line.
- Both timestamps are on the record. When the prospect submitted and when we delivered. You should never have to ask a vendor how old a lead is.
- No aged inventory, ever. We do not hold records back to sell later, which is the other reason an old lead usually shows up in a batch.
- Measure it yourself. We are not going to hand you a contact rate statistic. Run the program small, compute your own numbers, and scale the part that survives.
What happens when something breaks
Endpoints go down. Certificates expire on a Saturday. Somebody renames a field in your CRM and nobody tells the person who owns the integration. The question is not whether it happens, it is whether you find out from us or from a hole in your pipeline.
- Retries on a backoff schedule. A failed post is retried rather than dropped, so a brief outage costs you minutes instead of a morning of leads.
- Delivery confirmation, both ways. Every attempt is logged with your response. A lead we sent and a lead you accepted are two different facts, and both are on the record.
- You get told. Sustained failures raise an alert to your named contact rather than accumulating quietly in a queue.
- A fallback you choose. Hold for redelivery when your endpoint comes back, or fail over to a second path, decided when the program is set up rather than during the outage.
- Undelivered is not billable as delivered. A record we could not hand you is flagged as undelivered and handled under the credit criteria written down before you bought anything.
Pacing you control, and a loop that actually closes
Two things separate a program you can run for a year from a program you cancel in six weeks: volume that matches what the floor can work, and a vendor who wants to know what happened to the leads.
Caps, windows, and pause
- Daily and hourly caps. Hard limits on how much arrives, adjustable without a contract change, so Monday does not flood the floor and Thursday does not starve it.
- Dayparting. Delivery windows set against the prospect’s local time, so leads land while your licensed agents are on the phone and not after the last one goes home.
- Pause without penalty. Short-staffed week, a holiday, a carrier problem. Pause the program, resume it, no renegotiation.
- Ramp rather than launch. Start below what you think you can handle, prove the economics on your own numbers, then raise the cap.
Disposition feedback
- Outcomes come back. Automatically on the AgentTech path, or posted back to us from your own system on the others.
- Filters tighten on your traffic. Not on a global average, on your program specifically, which is the only version of this that means anything.
- Patterns get fixed at the source. Repeated bad records on one source get that source changed rather than credited every month forever.
- Most vendors never close this loop. Their incentive is not to know. Ours is different, because our sister companies work the same traffic.
Delivery, contact, and outcome data is visible by program and by day, and exportable, so you can compute your own cost per acquisition without asking anyone for a spreadsheet.
What gets delivered
Medicare leads
Advantage, Part D, and Supplement, split by enrollment window and targeted by county.
Medicare programsLife insurance leads
Term and permanent as separate programs, with the coverage amount captured at the form.
Life programsFinal expense leads
Burial coverage intent with the monthly premium budget captured up front.
Final expenseThe exclusivity policy
One buyer per lead on every delivery path, and no resale as an aged record.
ExclusivityAlso worth reading: how the program runs end to end, pricing by program, consent and compliance, and what delivery looks like for agents and agencies.
FAQs
Questions about delivery and routing
How quickly does a lead reach my agents?
Delivery happens on submission, not in a nightly batch. We are not going to quote you a contact rate curve, because you can measure your own on your own traffic. What we can promise is that we will not be the reason the lead is late, and that the timestamp on the record tells you exactly when the form was filled out and when we sent it.
What do you need from me to set up an HTTP post?
A URL, the field names you want, whether you want form-encoded or JSON, how you authenticate, and what a successful response looks like from your side. That last one gets skipped by most integrations and it is the one that decides whether a retry fires when something breaks. Setup is usually an afternoon, and it starts in test mode.
What happens if my endpoint is down?
We retry on a backoff schedule rather than dropping the record, every attempt is written to the delivery log with the response we got, and you get told rather than finding out from a gap in your CRM. If a record still cannot be delivered when the retry window closes, it is flagged as undelivered and handled under the credit criteria agreed before you started buying.
Can I test the integration before spending money?
Yes, and you should. Test mode sends sample records through the real path with a test flag set, so you can confirm the field mapping, the auth, and what the agent actually sees on screen. Test records do not bill and do not contaminate your reporting.
What is the difference between the AgentTech path and an HTTP post?
The AgentTech path has nothing to build. You pick the campaign, the lead enters the dial order, and dispositions come back to us without anyone exporting anything. An HTTP post is for the CRM you already run, which means you control the field mapping and you own the endpoint. Both deliver on submission. Only the first one closes the feedback loop by default.
Can I cap volume, set delivery hours, or pause?
Yes to all three, and none of them cost anything. Daily and hourly caps are adjustable without a contract change, delivery windows are set against the prospect's local time, and a program can be paused and resumed without a penalty. A desk that is short three agents this week should stop buying this week.
Something else? Contact us
Wire it up in test mode first.
Send us your endpoint and your field names, and we will run sample records through the real path before anything bills.