System status
Component state for every part of the Solved Enroll platform, from the client record through carrier submission, the API, and the MCP server.
Component status
Each component is a piece of the platform an agent would notice if it stopped.
-
Operational
Client records
The single client record shared across Medicare, life, and ancillary cases.
-
Operational
Intake and term resolution
Medication and condition lookup, abbreviation handling, and typo correction.
-
Operational
Medicare quoting
MAPD, PDP, Medicare Supplement, and Special Needs Plan quoting.
-
Operational
Formulary and drug pricing
Tier placement, coverage phases, and pharmacy pricing for the client drug list.
-
Operational
Provider directory lookup
Doctor and pharmacy network matching against the plans on screen.
-
Operational
CMS eligibility lookup
Entitlement, current enrollment, and election period checks.
-
Operational
Life underwriting rules
Encoded, versioned carrier rules for term, final expense, whole life, and preneed.
-
Operational
Ancillary quoting
Dental, vision, hearing, hospital indemnity, accident, and critical illness.
-
Operational
AI Plan Recommender
Ranking, scoring, and the explanation attached to each ranked plan.
-
Operational
Enrollment and e-signature
Application prefill and signature by text, tablet, or email.
-
Operational
Carrier submission
Electronic submission and carrier acknowledgement tracking.
-
Operational
API
REST endpoints, webhook delivery, and export jobs.
-
Operational
MCP server
Tool discovery and tool calls for agent runtimes using the recommender.
-
Operational
Portal
Agent and agency sign-in, dashboards, and case lists.
How to read this page
What this page is, what it is not, and how you would actually hear about a problem.
Solved Enroll is in private beta. Agencies are onboarded in cohorts ahead of a 2027 public rollout, so the components above serve beta cohorts rather than a general-availability user base. Join the waitlist for the next cohort.
Maintained by hand
This page is written and updated by the team rather than generated from an automated monitor. Treat it as our published record of component state, and tell us when it disagrees with what you are seeing.
Cohorts hear directly
Beta agencies also get incident notices by email, sent to the agency principal and any operations contacts named during onboarding. You do not have to watch this page to find out.
No uptime figure yet
We do not publish an availability percentage during beta, because it would describe a small cohort rather than the platform at general availability. Availability commitments are set in the agreement at launch.
Component state answers whether a piece of the platform is working at all. For anything case-specific, the help center is faster than waiting on this page.
Scheduled maintenance
No maintenance is scheduled. The one recurring piece of planned work is the plan-year data load, and it lands ahead of the annual election period every year.
- Plan-year loads run ahead of AEP. Next year's plan, formulary, and provider data is staged and validated before the annual election period opens, so quoting switches over without a gap.
- Both plan years stay quotable. Loading next year does not disturb the current year, because the carrier library is versioned rather than overwritten.
- Underwriting rule updates are versioned too. A rule change is published as a new dated version, so a quote run last month can still be reconstructed against the rules that produced it.
- Work lands outside calling hours. Anything that has to interrupt quoting or enrollment is scheduled outside U.S. calling hours and announced here first.
Planned work, in short
- 72 hours
- Minimum notice for planned work that affects quoting or enrollment.
- Before AEP
- Plan-year data loads are completed and validated ahead of the annual election period.
- 14
- Components tracked on this page, intake through submission.
If something is not working
Three places to go, depending on what you need.
Help center
Category guides for intake, quoting, underwriting, enrollment, and compliance, plus how to reach a person during beta.
Open the help centerDocumentation
How each part of the platform behaves, including what a rejected submission usually means and how to correct it.
Read the docsTell us
Email contact@solvedenroll.com with the case and what you expected to happen. Beta reports go straight to the people building the platform.
Contact usFAQs
Status questions
How often is this page updated?
It is reviewed and updated by hand. Solved Enroll is in private beta, so the platform does not yet publish an automated status feed. If something is wrong and this page still says everything is fine, email contact@solvedenroll.com and we will correct it.
Will I hear about an incident if I am in a beta cohort?
Yes. Beta agencies get incident notices directly, by email to the agency principal and to any operations contacts you nominate during onboarding. This page is the public record; the direct notice is the one that reaches you in the middle of a selling day.
What counts as an incident during beta?
Anything that stops an agent finishing a case: quoting that will not return plans, drug pricing that will not price, a recommender that will not rank, a signature link that will not deliver, or a submission that will not reach the carrier. Slow response times are recorded as degraded performance rather than an outage.
Do you publish an uptime percentage?
Not yet. An availability figure measured during private beta would describe a handful of cohorts rather than the platform you would buy, so we report component state here and set availability commitments in the agreement at general availability instead.
When do you take the platform down on purpose?
Rarely, and outside U.S. calling hours when we do. Plan-year data loads are the one piece of scheduled work that touches quoting every year, and they run ahead of the annual election period. Planned work is announced here and by email with at least 72 hours notice.
Does a carrier problem show up here?
Only where it affects the platform. If a carrier submission endpoint stops accepting applications, the carrier submission component is marked degraded and the cohort notice names the carrier. A carrier that is slow to acknowledge an application it already received is a case-level question for support, not a platform incident.
Something else? Contact us
Seeing something this page does not show?
Email contact@solvedenroll.com or call +1 (866) 415-6192 during business hours. Beta cohorts get a direct line to the team through onboarding.