Integrations
Three of these are not integrations at all, they are sister companies. Everything else connects the ordinary way: an authenticated request, a signed webhook, or a scheduled file. This page says which is which, specifically.
How a system connects
Four doors. Most agencies end up using two of them and never think about it again.
Native
AgentTech Dialer, Solved Enroll, and Solved Marketing lead delivery. Provisioned with the contract, no connector, no second subscription.
REST API
Bearer-token requests over HTTPS for production, readiness, hierarchy, and statements, scoped to your own structure.
Webhooks
Signed JSON deliveries for producer, application, and statement events, so your own system reacts instead of polling.
Scheduled exports
Complete files per window, written daily or weekly to a destination you name. Often the right answer for a smaller desk.
Everything 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, and no carrier is named here.
The Solved stack
The part that is not an integration. These are sister companies inside Solved Ventures, which is why access comes with a contract instead of a separate invoice.
AgentTech Dialer
Native. Seats are provisioned with your contract, not bought separately. Inbound queues, outbound dialing, the built-in client record, call recording, and AI compliance scoring, with contacts, calls, and dispositions reachable over the AgentTech API for agencies that run their own systems.
How it connectsSolved Enroll
Native, and currently in private beta. Multi-product quoting and enrollment from one client record across Medicare, life, and ancillary lines, with clients, quotes, and applications available over its API and a Model Context Protocol server for tooling that speaks it.
How it connectsSolved Marketing lead delivery
Native in two of its four paths: straight into an AgentTech campaign or straight into a Solved Enroll client record, with no endpoint for you to build. The other two are an HTTP post to a URL you name and a signed webhook. Delivery happens on submission rather than in a nightly batch.
How it connectsWhy native is different
These are sister companies under Solved Ventures, so the connection is not a connector. There is no second subscription to keep alive, no vendor in the middle of a support conversation, and no export step between a call and the client record it belongs to.
How it connectsAgency management systems and CRMs
No connector directory to wait on. If a system can send an authenticated HTTPS request or receive a JSON POST, it integrates.
Agency management systems
Pull production, persistency, readiness, and hierarchy over the agency API and write them against your own producer and policy records. Scheduled exports cover teams that would rather load a file than call an endpoint.
How it connectsCRM platforms
Read contacts, calls, and dispositions from the dialer API so the CRM record reflects what actually happened on the phone. Any CRM that can make an authenticated HTTPS request can consume it; no purpose-built connector is required.
How it connectsRecruiting and onboarding tools
Subscribe to producer events and reflect onboarding progress in whatever you use to track recruits. The producer.appointed and producer.ready_to_sell events are the two that matter for a recruiting pipeline.
How it connectsCustom internal applications
Register an HTTPS endpoint, subscribe it to the events you care about, verify the signature against the raw body, and return a 2xx quickly. Deliveries are at least once and not ordered, so key on the event id.
How it connectsWorkflow and automation tools
Anything that can send an authenticated request and receive a JSON POST can drive and observe this data. That covers most low-code automation platforms without anyone building an integration.
How it connectsSpreadsheets and reporting tools
A scheduled export to a location you control, read by whatever your team already opens. Unfashionable, and frequently the right answer for an agency of a dozen producers.
How it connectsCarrier submission and status
The honest section. There is no universal carrier API, so most of this is a prepared submission, a tracked state, and a person who chases.
What is integrable is the state, not the submission. Every carrier runs its own contracting process and its own portals, and we work them rather than pretending a connector exists. What we then hold is a single, consistent record of where every producer stands with every carrier in every state, and that record is available to your systems as data.
Carrier packet submission
Packets are assembled here from the producer profile collected once, then submitted through each carrier process. There is no universal carrier API to integrate with, so the honest description is a prepared submission plus a person who watches it.
How it worksAppointment status tracking
State is tracked per carrier and per state with real values rather than a vague status: submitted, in review, returned, approved. That state is what the agency API and the readiness export read from.
How it worksReady-to-sell verification
Readiness is verified against what carriers report, per carrier, state, and product line, rather than inferred from an approved appointment. It is exposed as data so your dashboard can show it without anyone checking a portal by hand.
How it worksApplication status and escalation
Submitted business is tracked to issue, and a stalled application is chased with the carrier rather than left to age. Applications submitted through Solved Enroll carry their own submission record, which is what makes the chase fast.
How it worksCommission and accounting systems
Statement data as an export, so the numbers in your ledger come from the same records the reconciliation ran against.
Accounting and general ledger systems
Reconciled statement periods and their lines as a scheduled export or an API read, so commission revenue lands in your ledger from the same records the reconciliation used.
How it connectsCommission tracking tools
The unmatched view is the useful one: submitted business with no statement line, and statement lines with no submission record. That is the list a commission tool should be working, not the total.
How it connectsPayroll and producer payout
Hierarchy structure and structure changes as data, so an agency paying producers from its own system can attribute the same way the statements do, including across a mid-period change.
How it connectsChargeback handling
Chargebacks applied in a period, by producer and policy, with the carrier reason where one was given. Exported alongside statements so a payout run can net correctly rather than after the fact.
How it connectsA worked reconciliation, including what to do with each kind of mismatch, is at reconciling a statement.
Data warehousing
If you run an agency of any size you will eventually want this data next to everything else you measure. It goes where your analytics already live.
Scheduled exports
Production, persistency, readiness, certifications, licenses, hierarchy, and statements, written daily or weekly to a destination you name as complete files per window.
How it connectsObject storage you own
An S3-compatible bucket or any storage endpoint that accepts an authenticated write. Load on the export window rather than the file timestamp and the arithmetic stays correct.
How it connectsHTTPS endpoint delivery
For teams that would rather receive a push than schedule a pull. Same datasets, delivered to an endpoint you control and signed the same way events are.
How it connectsEvent streams
Producer, application, and statement events delivered as they happen, for a warehouse that is loaded continuously rather than on a schedule.
How it connectsField-level detail and the event catalog are in the integrations and data access reference. Credentials are issued during onboarding.
FAQs
Integration questions
Does naming a category here mean you have a partnership with a vendor?
No, and nothing on this page should be read that way. Everything below describes protocol-level and API-level compatibility: the system can send an authenticated HTTPS request, receive a signed webhook, or read a scheduled file export. None of it is a claim of a partnership, a certification, a reseller agreement, or a marketplace listing with any vendor, and we do not name carriers on this page at all.
Which parts are native rather than integrated?
AgentTech Dialer, Solved Enroll, and Solved Marketing lead delivery are native, because those are sister companies inside Solved Ventures rather than vendors we resell. Access is provisioned with your contract, data moves between them without a connector, and support does not travel through a second company.
Do I need a developer?
Not to use the stack. Dialer seats, quoting access, and native lead delivery are configured during onboarding with someone alongside you. You need a developer when you want production, readiness, hierarchy, or statement data to appear inside a system you run yourself, which is what the API, the webhooks, and the scheduled exports are for.
Is there a charge for the API, webhooks, or exports?
No. API access, webhook delivery, and scheduled exports are part of an agency contract rather than an integration tier. Lead programs are priced separately, but that is a purchase of leads, not a charge for the delivery mechanism.
Can you integrate directly with a carrier system?
Carrier submission runs through the carrier processes and portals each carrier operates, and those are theirs. What we do is prepare and submit packets and applications, track state across carriers in one place, and escalate when something sits. We will not describe a carrier connection as an integration when what it actually is is a person working a portal and a phone.
What if my system is not in one of these categories?
Then it probably still connects. The practical test is whether it can send an authenticated HTTPS request, receive a JSON POST, or read a file from a location you control. If it can do any one of those, tell us what you want it to know and we will tell you which surface holds that data.
Something else? Contact us
Tell us what you run.
Bring the systems your agency already depends on and we will tell you which of the four doors fits each one.