ACA open enrollment reminders and follow-up for health insurance brokers
Open enrollment compresses a year of client contact into a few weeks. We build a workflow that sorts your ACA clients by what is changing on their plan, sends a personal open enrollment reminder email and text, logs consent and opt-outs, builds a call list of clients who need a review before the December 15 deadline for January 1 coverage and records every contact. Licensed agents still review plans with clients. A typical build costs $1,000 to $2,500 and takes about three to four weeks.
The problem
Why open enrollment follow-up overwhelms brokers
On HealthCare.gov, open enrollment for 2027 coverage runs from November 1 to January 15, and clients must choose a plan by December 15 for coverage to start January 1. A broker with hundreds of clients cannot call everyone in time, and the clients who most need a review are often the ones who never open the carrier's letter.
The paperwork is strict. CMS requires agents and brokers to document consumer consent, including its scope, date and how to rescind it, and to keep that documentation for at least ten years. Texts need consent and must honour opt-outs. Follow-up has to be fast and well recorded at the same time.
What we build
What our open enrollment reminder automation includes
Client sort by change
Clients grouped by what is changing, such as a discontinued plan or a large premium change, using a threshold you set.
Personal reminders
An open enrollment reminder email and text in the agent's name with the deadline and a booking link.
Review call list
Clients who need a conversation listed by priority, with the reason attached.
Consent and opt-out log
Consent records and STOP replies logged and honoured across every message.
Booking link
Clients book a review call directly into the agent's calendar.
Contact record
Every reminder, reply and call outcome recorded for the file.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Book loaded
The client list and plan data are loaded from your CRM or enrollment platform export.
-
02
Automated
Clients sorted
Clients are grouped by plan change and priority.
-
03
Automated
Reminders sent
Personal reminders go out with the deadline and a booking link, respecting consent.
-
04
CSR or account manager review
Agent calls
Agents work the call list and book reviews.
-
05
Licensed agent or principal decides
Plan choice
Plan recommendations are made by a licensed agent with the client, never by the workflow.
How it behaves
How open enrollment follow-up behaves
What the client sees
- A personal reminder from their agent with the deadline
- A link to book a review call
- No further texts once they reply STOP
What agents see
- A call list sorted by priority and reason
- Booked reviews in their calendar
- A contact record for every client
What the automation does
- Sorts clients by plan change
- Sends reminders only where consent allows
- Logs every contact and opt-out
Edge cases and fallbacks
- No consent for texts on file
- Email only, and the client is placed on the call list.
- Client replies with a coverage question
- Routed straight to their licensed agent.
- State marketplace with different dates
- Messages use the dates for that state.
- Email bounces
- The client moves to the call list.
- Messaging provider outage
- Sends pause and resume; nothing is sent twice.
Architecture
ACA open enrollment follow-up at a glance.
- Input
- Logic and services
- Output
- Data
- People
How it flows
- 1 The client book and plan data are loaded from your CRM or enrollment platform export.
- 2 n8n sorts clients by plan change and sends personal reminders, checking consent first.
- 3 Replies, bookings and opt-outs update the call list and the consent log.
- 4 Licensed agents work the list and review plans with clients before the deadline.
Project planner
How the project runs, phase by phase.
ACA open enrollment follow-up project plan
Typical time to launch: about 3 weeks, then support
-
01
Discovery
2 to 3 days
Book size, data sources, consent records, current reminder wording and calendar setup.
-
02
Design
2 to 3 days
Sorting rules, message wording, call list format and logging.
-
03
Build
About 1 week
Data load, sorting, reminders, booking link, consent log and call list.
-
04
Shadow run
2 to 3 days
Messages go to a test inbox while agents check the sorted list.
-
05
Launch
1 to 2 days
Send in batches and watch replies.
-
06
Support
Ongoing
Daily checks through the enrollment period, then a reset for next year.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Data sources, sorting rules and wording.
$200 – $400
-
Build
Sorting, reminders, booking, consent log and call list.
$500 – $1,300
-
Integrations
CRM or export, messaging and calendars.
$150 – $400
-
Testing and shadow run
Test-inbox run and list check by agents.
$100 – $250
-
Launch and training
Batch launch and agent walkthrough.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Messaging, calendar and n8n costs are billed to you directly. The workflow is reusable each enrollment season.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees, and about $1.15 a month per local number (Twilio's published US pricing). US A2P 10DLC registration fees also apply.
- n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
US: open enrollment dates
HealthCare.gov open enrollment for 2027 coverage runs November 1 to January 15; enrol by December 15 for coverage starting January 1.
Source: www.healthcare.govUS: CMS consent documentation
Under 45 CFR 155.220(j)(2)(iii), agents must document consumer consent (scope, date, names and how to rescind) and keep it for at least 10 years.
Source: www.law.cornell.eduUS: texts need consent
Marketing texts need prior express written consent under the TCPA rules, and opt-outs must be honoured.
Source: www.law.cornell.eduFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
ACA open enrollment follow-up questions, answered.
On HealthCare.gov, November 1, 2026 to January 15, 2027. Clients must choose a plan by December 15 for coverage to start January 1. State marketplaces can set different dates.
The deadline, why the client should review this year, a booking link and the agent's name and contact details. We write it with you and keep advice out of it.
No. It sorts clients and books reviews. Plan recommendations are made by a licensed agent.
Consent records are checked before any text, STOP replies are honoured across every message, and contact history is logged for your file. CMS requires consent documentation to be kept for at least ten years.
Yes. The workflow is reset with the new dates and data each season.
Reminders sent, replies, reviews booked, clients re-enrolled before December 15 and opt-outs.
Free 20-minute call
Want this for your insurance broker?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for insurance brokers
All servicesInsurance agency CRM & sales pipeline automation
Every quote request, referral and cross-sell opportunity in one insurance agency CRM pipeline linked to your AMS, with fast first replies, follow-up tasks and a weekly report by source and line.
From $1,000 · About 4 weeks Details
Renewal pipeline & client information requests
Build the renewal pipeline from AMS expiry dates by line, send information requests months ahead, chase replies, highlight changes since last year and give account managers time to market the risk.
From $1,000 · About 4 weeks Details
First notice of loss intake & claim updates
Capture the facts of a loss in a structured form, pass the notice to the carrier the same day, chase photos and documents and keep clients updated, with coverage questions left to people.
From $1,000 · About 4 weeks Details