Enrollment and e-signature
The application is built from the quote that produced the recommendation, signed the way the client prefers, and filed with the Scope of Appointment, the disclosures, and the signature already in order behind it.
Nothing retyped
The application is already written by the time you reach it.
Anyone who has filled out a paper application at a kitchen table knows where the mistakes come from: copying a Medicare number off a card for the third time, transposing a date of birth, spelling a medication differently than you did an hour ago. Solved Enroll does not ask you to do that step. The quote is the source.
- Pre-filled from the quote. Every field the fact-find already answered is populated, including the household, the medication list, and the doctors the client named.
- Carrier-approved forms. The document the client signs is the carrier’s own application for that plan year, not a generic wrapper that gets re-keyed later.
- One correction, everywhere. Fix an answer on the record and the application reflects it. There is no second copy to keep in step.
- No second vendor. Quoting, recommendation, and signature happen in one session rather than a handoff to a separate signing tool.
Solved Enroll is in private beta. Enrollment is live for the carriers in each cohort, and that list grows as cohorts onboard ahead of the 2027 public rollout. Join the waitlist to be included.
The enrollment sequence
The order matters, because the order is what a carrier or a reviewer asks about later. Each step writes its own entry as it happens.
-
1
Scope of Appointment, before anything else
The SOA is captured and timestamped before the sales conversation starts, with the product categories the client agreed to discuss. It is stored against the client record, so it is attached to the case rather than sitting in a drawer or a separate signing account.
-
2
Intake and quote on one record
The fact-find, health profile, doctors, medications, and budget are entered once. Eligibility, network, and underwriting rules are applied before plans appear, which is why the application later has nothing missing.
-
3
Plans presented, and logged as presented
The comparison you turn the screen around and show is recorded: which plans were on the screen, in what order, with what premium and benefit figures. If a client later asks why a plan was not offered, the answer is in the file.
-
4
Required disclosures at the point the rules call for them
CMS disclosures are presented and acknowledged where they belong in the conversation, not batched into a pile of paperwork at the end. Each acknowledgement is timestamped and attributed.
-
5
The application populates itself
The carrier-approved form for the chosen plan is filled from the quote. What is left for the agent is the handful of answers only the client can give, not a re-transcription of the last forty minutes.
-
6
Signature, delivered three ways
A texted link, a tablet handed across the table, or an emailed packet. Partial-save means a client who steps away, or who wants their daughter to look at it first, resumes at the same field instead of starting over.
-
7
Submission, tracked to acknowledgement
The application goes to the carrier and the status moves from submitted to carrier acknowledgement on one screen. You are not logging into portals to find out whether the case landed.
-
8
The case file, closed and retained
Everything above is already the case file. It exports as a single document on request and is retained for the period your carriers and your states require, then aged out on schedule.
Signature that meets the client where they are
Three delivery modes, one signed document. You can change your mind mid-appointment if the phone turns out to be easier than the tablet.
A texted link
The client signs on the phone already in their hand. This is the mode that works over the kitchen table and the mode that works on a phone appointment, which makes it the one most agents reach for first.
An in-person tablet
Turn the screen around and let the client read and sign in front of you. The same document, captured on your device, with the same audit entries written behind it.
An emailed packet
For the client who wants to read it tonight, or show it to a family member first. The case stays open, the status is visible to you, and nothing has to be rebuilt when they come back to it.
- Partial-save holds a half-finished application against the client record so the client resumes where they stopped, on any device.
- Each signature carries its timestamp, IP address, device, and the exact consent text that was on the screen.
- The agent sees whether a packet was delivered, opened, started, or completed, instead of calling to ask.
Compliance workflow
The audit trail is a by-product, not a second job.
The reason compliance paperwork gets done badly is that it is usually done afterward, from memory, by whoever has the most time. Here the record writes itself while the appointment happens, in the order the appointment happened.
- SOA before the conversation. Captured, timestamped, and stored on the client record, with the agreed product categories carried into the case.
- Disclosures in the right place. Required CMS disclosures are presented and acknowledged at the point in the flow the rules call for, and each acknowledgement is recorded.
- Ordered and attributed. Every entry names the agent, the time, and the action, so the file answers who did what rather than only what the outcome was.
- Nothing to reassemble. The case file export is built from the entries the workflow already wrote.
| Scope of Appointment | Product categories agreed, client and agent identity, capture method, and the timestamp that establishes it came before the sales conversation. |
|---|---|
| Disclosures | Which required disclosure was shown, the wording shown, when it was presented, and when it was acknowledged. |
| Plans presented | The plans on screen during the comparison, with the premium, benefit, and cost figures as displayed at that moment. |
| Plan chosen | The plan the client selected, the effective date, and the recommendation factors that accompanied it. |
| Signature | Delivery mode, timestamp, IP address, device, and the consent text presented at the moment of signing. |
| Submission | When the application was sent, to which carrier, and each status change through carrier acknowledgement. |
These are workflow controls and recordkeeping, described as they are built. They are not a substitute for your own compliance program, and nothing here should be read as a completed audit or certification. Our security program is described on the security page.
After you hit submit
The part of the job that usually happens in portals, spreadsheets, and follow-up calls.
Submission tracking
Each application moves from submitted through carrier acknowledgement on one screen, with the date of each change. Chasing a case does not mean remembering which of six carrier portals it went to, or which password you used last October.
Case file export
One request produces one document: SOA, disclosures, the comparison presented, the application as submitted, and the signature record, in order. It is what you send when a carrier, a principal, or a reviewer asks for the file.
Retention controls
Retention periods are configured to match the carriers you are appointed with and the states you write in. Records are kept for that window and aged out on schedule, rather than accumulating forever because nobody set a policy.
Enrollment is one part of the workflow. See how it connects to Medicare quoting, life field underwriting, ancillary attach, and the AI Plan Recommender, or read the full walkthrough.
FAQs
Questions about enrollment
Does the client have to sign in person?
No. There are three delivery modes and they all produce the same signed, carrier-approved document: a link texted to the phone in the client's hand, a tablet you turn around at the kitchen table, or an emailed packet they open that evening. You pick the one that fits the appointment, including switching mid-case if the phone is easier than the tablet.
What happens if a client stops halfway through the application?
The application partial-saves. Everything answered so far is held against the client record, and the client resumes from that point on any device. Nothing is retyped, and the agent can see exactly where the case stalled instead of guessing whether the packet was ever opened.
How is Scope of Appointment handled?
Scope of Appointment is captured and timestamped before the sales conversation begins, and it is stored against the client record rather than in a separate folder. The product categories on the SOA travel with the case, so what was agreed to and what was later presented sit side by side in one place.
What is actually in the audit trail?
The SOA, each required disclosure and its acknowledgement, every plan presented, the plan the client chose, and the signature event with its timestamp, IP address, device, and the consent text shown at the moment of signing. Entries are in order and attributed, so the file answers who did what and when, not just what the outcome was.
Can I hand a carrier or a reviewer a complete case file?
Yes. A case file exports as a single document on request, covering the SOA, disclosures, the comparison presented, the application as submitted, and the signature record. It is assembled from the same entries the workflow already wrote, so there is nothing to reconstruct after the fact.
How long are enrollment records kept?
Retention is configurable and set to match the requirements of the carriers you are appointed with and the states you write in, which are not always the same period. Records are held for that window and aged out on schedule rather than kept indefinitely by default.
Something else? Contact us
Enroll in the same session you quoted in.
Beta agencies are onboarded in cohorts, and preferred pricing is locked in at general availability.