How the group integrates
Two directions. Inward, what crosses the boundary between one operating company and the next. Outward, what an outside party can actually connect to. Everything below is protocol and API level, which is the only kind of claim this page makes.
Two directions
A holding company integration page is usually a logo wall. This one is a description of where data crosses a boundary, which is the only version that can be checked.
Inward: between the companies
Six flows carry almost everything that moves inside the group, from a lead entering a campaign to persistency returning to the program that produced it. Each handoff passes a reference plus a scoped grant rather than a copy of the record, which is what stops six versions of the same household from existing.
Outward: for an outside party
Six ways in from outside: each company REST API, signed webhook streams, scheduled exports, lead delivery in both directions, carrier submission and data exchange, and an MCP server for AI agents. Credentials come from the individual company in every case.
Everything named on this page describes protocol and API-level compatibility. It is not a claim of a partnership, a certification, a marketplace listing, or a carrier relationship, and no carrier is named.
What flows between the companies
Owned handoffs, in the order a piece of business moves through them. Each card links to the step on the documentation index that describes what the payload actually carries.
Leads into the dialer
On submission rather than in a nightly batch. What crosses is the lead identifier, the program and vertical, the intent captured, the consent reference, and the filter results, landing in a named campaign.
How the payload worksCalls on owned rails
The dialer does not buy wholesale minutes from a layer above it. Media, recording, transcription, and messaging run on interconnects the group holds, which is why routing and quality changes do not require a vendor ticket.
How the payload worksDialer outcomes into enrollment
A disposition that indicates real interest promotes the contact to a client record, and the call context travels with it so the producer is not restarting the conversation. References cross, not copies of media.
How the payload worksLicensing and appointment checks
Appointment state, hierarchy, and license geography are read from the contracting company at submission time rather than copied into the quoting platform, so a lapsed appointment does not stay quietly true in a second system.
How the payload worksEnrollment into carrier submission
The application is assembled, submitted where the carrier accepts an electronic submission, and handed off as a packet where it does not. The response, including a decline reason, lands back on the application record.
How the payload worksRecords into the warehouse
Complete files per window into a shared analytical store, with health detail minimized on the way in. It is the only place data from all six companies sits together, and it is read-only and governed as such.
How the payload worksThe hop a rented chain does not have
Five of the six internal flows exist in a fragmented chain too, in some form and with more friction. The sixth is the one that only exists when both ends are owned.
- Persistency returns to acquisition. Placement rates, decline reasons, and what stayed on the books are fed back at the program and filter level.
- Lead quality becomes measurable. Not by answer rate, which is what a vendor reports, but by business that was still in force a year later.
- The loop is short. Across a vendor boundary the same signal arrives a quarter late, aggregated, and with no way to act on the filter that caused it.
- Incentives point the same way. Our own distribution sells on our own leads, so lead quality is an internal problem rather than a credit request.
What is live behind these flows
- 2
- Platforms in production with paying customers inside and outside the group: AgentTech Dialer and Solved Telephony.
- 2027
- Planned public rollout for Solved Enroll, which is in private beta with cohort agencies today.
- Pending
- Solved Insurance products are in development, pending state approval. Nothing is placed on them yet.
What an outside party can integrate with
Six doors. Pick the one that matches what you are building; most integrations end up using two of them.
Each company REST API
Telephony for numbers, calls, recordings, messaging, routing, and CDRs. The dialer for contacts, calls, queues, and dispositions. Enrollment for clients, profiles, quotes, recommendations, and applications. Bearer tokens over HTTPS, JSON bodies, cursor pagination, idempotent writes.
APIs across the groupWebhook streams
Subscribe an HTTPS endpoint to call progress, call completion, recording and transcript availability, message delivery receipts, disposition changes, and lead delivery. Deliveries are signed, retried with backoff, at least once, and not ordered.
Shared conventionsScheduled data exports
Records pushed on a schedule to object storage or an endpoint you name, written as complete files per window so a late-arriving record appears in the window its event closed in. The right choice when a warehouse needs yesterday loaded before the morning reports run.
How the flow worksLead delivery, in and out
An HTTP post or a signed webhook on submission, carrying the consent reference rather than a consent flag, plus disposition postback so outcomes return to the program that produced the lead. Delivery reports show caps and dayparting as they applied.
The delivery surfaceCarrier submission and data exchange
Application submission where a carrier accepts it electronically, and a data exchange covering what was submitted, what was decided, and what stayed on the books. The shape is agreed per carrier, because the carrier decides what it accepts.
For carriersMCP server for AI agents
The Solved Enroll capabilities exposed as tools for an agent that speaks the Model Context Protocol, so an AI agent can quote and rank without a bespoke tool layer. Licensable as a REST API or as an MCP server.
The technology
Starting an integration
Four steps, and the first one is not a contract.
-
Name the surfaces
Decide which companies you actually need. Most integrations need one or two, and taking more than you need adds credential management rather than capability.
-
Get credentials from each company
Sandbox alongside production, scoped to the resources you need. There is no group-wide key, so this is one conversation per company; we can start them in parallel.
-
Build against the shared conventions
Bearer tokens over HTTPS, JSON bodies, cursor pagination, idempotency keys on writes, and signature verification on webhooks. Learn them once and they hold on the next surface.
-
Agree the reporting
Decide early whether you want webhook streams, scheduled exports, or both, and which window your own arithmetic will be computed on. Retrofitting this is the most common integration rework.
FAQs
Integration questions
Does naming a protocol here mean you have a partnership with someone?
No. Everything on this page describes protocol-level and API-level compatibility: a system can call a REST endpoint, receive a signed webhook, read an export, or speak the Model Context Protocol. None of it is a claim of a partnership, a certification, a reseller agreement, or a marketplace listing with anyone, and no carrier is named anywhere on this site as a partner.
Do I integrate with Solved Ventures or with an operating company?
With an operating company, always. The holding company runs no product surface and issues no credentials. What the group level is useful for is making sure you are talking to the right companies at the same time when your integration spans two of them.
Why describe the internal flows publicly at all?
Because the internal flows are the argument. The claim that owning the chain is worth the cost is only checkable if you can see what actually crosses each boundary, and which handoffs a rented chain would lose. A partner evaluating us should be able to tell the difference between a diagram and a system.
Can I use one company without the others?
Yes, and most external customers do. AgentTech Dialer and Solved Telephony both sell to customers with no other relationship to the group, which is deliberate: a layer that could only survive on internal revenue would be a subsidy rather than an advantage. Nothing requires you to take the stack.
Is there a charge for the API, webhooks, or exports?
Integration surfaces are part of an account at each company rather than a separate integration tier. You pay that company published rates for the usage the integration generates. The specifics belong to the company you are contracting with, so ask them rather than us.
How does an integration handle consent?
By carrying the consent reference rather than a boolean. The record holds the exact disclosure language shown, the timestamp, the address, and the page, so a question years later is answerable with what the person actually saw. Suppression and opt-out are evaluated before any contact attempt, in every company that can place one.
Which parts of this are available today?
The telephony and dialer surfaces are in production. Lead delivery is operating. The enrollment surface and the MCP server are in private beta ahead of a 2027 rollout, so access there is granted with a cohort rather than issued on request. Solved Insurance is in development pending state approval and has no integration surface yet.
Something else? Contact us
Describe the integration, not the vendor list.
Tell us what you want to happen and we will name the surfaces and get the right teams onto one call.