Integrations
There are four doors into your stack: a native AgentTech Dialer campaign, a native Solved Enroll client record, an HTTP post, or a signed webhook. Everything below is one of those four, described specifically.
How a system connects
Pick the door that matches what you run. Most buyers end up using two of the four, one for the agents and one for the reporting.
Native into AgentTech Dialer
Leads land in a campaign and start dialing. Nothing to build, no mapping to agree, and dispositions come back automatically against the originating lead id.
Native into Solved Enroll
A client record arrives pre-populated so the fact-find starts from what the prospect already told us. Solved Enroll is in private beta, with a public rollout planned for 2027.
HTTP post
One POST per lead to an HTTPS endpoint you name, sent within seconds of the form submission, carrying either our field names or yours. Any CRM that can accept a request can accept leads.
Signed webhook
The same payload inside an event envelope, followed by lifecycle events: accepted, rejected, credited, and disposition received. For systems that want a stream rather than a handoff.
Everything named on this page describes protocol-level and API-level compatibility. It is not a claim of a partnership, a certification, a reseller agreement, or a marketplace listing with any vendor. AgentTech Dialer and Solved Enroll are sister companies inside Solved Ventures.
Dialers and contact centers
This is the category the delivery path was built for. AgentTech Dialer is a sister company inside Solved Ventures, so leads arrive in a campaign rather than in an inbox, and the seconds an integration hop would cost are seconds you keep.
Everything else in this category connects by HTTP post into whatever list, campaign, or queue object the system exposes. The prospect time zone on the payload is what the calling windows should key on, not the time zone of your office.
AgentTech Dialer
Native. Leads land in a campaign and start dialing, with no endpoint to build and no field mapping to agree. Dispositions flow back against the originating lead id automatically. Both companies sit inside Solved Ventures, which is why this path exists at all.
How it connectsPredictive and power dialers
Any dialer that can accept an inbound HTTP post into a list or campaign. We post one lead per request with the field names the dialer expects, and the prospect time zone on the record is what its calling windows should key on.
How it connectsContact center platforms
Delivered by HTTP post into the queue or campaign object the platform exposes. Where the platform has an inbound API rather than a webhook URL, we call it directly with the credentials you supply at onboarding.
How it connectsClick-to-call and manual desks
Smaller desks without a dialer take delivery into a CRM queue and work it by hand. Delivery windows matter most here, because a lead that arrives after the floor closes will not be dialed until it has already aged.
How it connectsCRM and agency management systems
No connector directory to wait on. If a system can receive an authenticated HTTPS request or expose a record-creation endpoint, it takes leads.
Any CRM with an inbound webhook
The most common setup by a wide margin. You expose an HTTPS URL, we post the lead as JSON, you answer 200. Every field is documented, and the signature lets you verify the request came from us.
How it connectsCRMs with a REST API only
Where there is no inbound webhook, we call the record-creation endpoint directly using credentials you provide, mapping our fields onto the ones the API expects.
How it connectsAgency management systems
Delivered as a new prospect or client record with the contact block and vertical answers populated, so the first conversation starts from what the prospect already told us rather than from data entry.
How it connectsSolved Enroll
Native. The client record arrives pre-populated and the fact-find starts at the recommendation. In private beta today, with a public rollout planned for 2027.
How it connectsSpreadsheet and inbox workflows
Honest about the tradeoff: a scheduled export into a file is supported, and it is the slowest path there is. Use it for reporting, not for the leads your agents are supposed to call today.
How it connectsCustom internal applications
Register an HTTPS endpoint, verify the signature, deduplicate on the lead id, return a success status quickly, and do enrichment out of band.
How it connects
Whichever system receives the lead, store the lead_id on the record. It is the key for credits, consent record requests, disposition feedback, and every support conversation about a specific lead.
Lead management platforms
Systems whose whole job is receiving, routing, and assigning leads. They take the post on their intake URL and route it with the fields already on the payload.
Lead distribution platforms
Platforms that route records to agents or offices accept our post on their inbound intake URL. Point them at one program each so your reporting can still tell the programs apart.
How it connectsLead management systems
Systems built around a fixed lead schema take our fields mapped onto theirs. Ask for the consent fields to be carried through rather than dropped; they are the ones most often lost in a rigid schema.
How it connectsPing-post intake endpoints
We post the full record rather than pinging first, because every lead is already sold once to one buyer and there is no auction to run. Endpoints built for ping-post accept the post step unchanged.
How it connectsRouting and assignment rules
Assignment logic on your side can key on state, county, vertical, plan interest, budget band, or the campaign reference. Everything those rules need is on the payload at delivery time.
How it connectsData and warehousing
Three ways to get the raw records into your own systems, and one reason to bother: the arithmetic that decides whether a program works belongs to you.
Scheduled export
Leads and delivery records written on a recurring schedule to an endpoint you name, as complete files per window. Load on the delivery window rather than the file timestamp and your month-over-month arithmetic stays correct.
How it connectsWebhook streams
Event-by-event delivery to an HTTPS endpoint when you want the warehouse loaded continuously: lead delivered, accepted, rejected, credited, and disposition received.
How it connectsREST pull by cursor
Query leads, deliveries, and reports by date range and program over the REST API. Cursor paginated, so a backfill is a loop rather than a support request.
How it connectsYour own warehouse
The point of all three is that you can compute your own cost per acquisition without asking us for a spreadsheet, and check it against persistency a quarter later.
How it connectsAnalytics and attribution
What is on the payload so your own reporting can answer the questions that matter, starting with the one about speed.
Source and campaign attribution
Every lead carries a channel, a campaign reference, a device, and a landing page reference. Join them against your outcomes and you can see which concept produces conversations on your floor rather than just form fills.
How it connectsSpeed to dial instrumentation
Subtract your first dial timestamp from the delivered_at field on the payload. That single measurement explains more variance in contact rate than anything else you can instrument.
Cohort and CPA reporting
Attribute policies to the cohort the lead belongs to rather than the month the policy issued, or a good cohort with a long sales cycle will read as a bad one.
How it connectsBusiness intelligence tools
Anything that can read a scheduled file or query an authenticated REST endpoint can chart this data. There is no proprietary connector to wait on and nothing to install.
How it connectsField definitions are in the documentation and the full contract is on the delivery API reference.
FAQs
Integration questions
Does naming a category here mean you have a partnership with a vendor in it?
No. Everything on this page describes protocol-level and API-level compatibility: the system can receive an HTTPS request with a JSON body, or it can call our REST API, or it can consume a scheduled export. None of it is a claim of a partnership, a certification, a reseller agreement, or a marketplace listing with any vendor. The two named exceptions are AgentTech Dialer and Solved Enroll, which are sister companies inside Solved Ventures.
Do I need a developer to receive leads?
Not on the native paths. Delivery into an AgentTech Dialer campaign or a Solved Enroll client record needs nothing built. For HTTP post or webhook delivery you need someone who can expose an HTTPS endpoint and read a JSON body, which for most agencies is either an existing feature of the CRM or an afternoon of work.
My CRM only has an inbound webhook with fixed field names. Can that work?
Yes. Give us the field names the system expects and we post to them, including flattening the nested objects into the dotted or underscored names it wants. The mapping is agreed at onboarding and proven with test leads before the first live record moves.
Can I send leads to more than one place?
Yes. A common setup is native delivery into the dialer so agents start working immediately, plus a webhook stream into a warehouse so the reporting team has the raw records. Each destination is configured separately and a failure at one does not stop the other.
What happens if my system is down for maintenance?
Failed deliveries are retried on a backoff schedule, and a lead that still cannot be delivered is held rather than discarded. You are not billed for a lead we could not deliver. If you know about the downtime in advance, pausing the program is better, because leads delivered into a system nobody is watching still age.
Is there a charge for the API, webhooks, or exports?
No. Delivery, webhook events, the buyer-facing REST API, and scheduled exports are part of a program rather than an integration tier. Pricing is per lead, quoted by vertical and program.
Something else? Contact us
Tell us what you run.
Bring the system you already have and we will tell you which of the four doors fits it, then prove it with test leads.