DMI Reminder Workflow Update - Now Includes Immigration and AI/AN Status
If you've been manually tracking clients with immigration-related Data Matching Issues or American Indian/Alaska Native status, that workload just got lighter. The DMI Reminder workflow has been updated to handle both automatically — with new templates, tagging, and deadline countdowns built in.
What's New: Expanded DMI Coverage
Immigration and AI/AN Status Added
The DMI Reminder previously focused on citizenship-related document requests. It now includes two additional categories:
Immigration Status — clients with immigration-related DMIs get their own dedicated reminder sequence
American Indian/Alaska Native (AI/AN) Status — new templates have been built specifically for this group
These aren't minor additions. Both statuses involve distinct documentation requirements, and having separate sequences means your clients get the right message — not a generic one that may not apply to their situation.
Workflow Structure
The workflow is now organized into clearly separated sections:
Citizenship
Immigration Status
Loss of Coverage
American Indian/Alaska Native Status
Each section runs independently, so a client with an immigration DMI won't receive citizenship-specific messaging.
Why This Matters
DMIs don't resolve themselves. When a client has a Data Matching Issue, the clock is ticking — and if the right documents don't get submitted before the deadline, their coverage is at risk. The more precise your reminder sequences are, the better your chances of getting documents in on time.
A generic DMI reminder sent to an AIAN client or an immigration-status client may create confusion, slow down the process, or get ignored entirely. The right message, for the right situation, sent automatically — that's what this update delivers.
How It Works
You don't need to configure anything. The workflow runs automatically based on the DMI type associated with each contact. Here's what happens behind the scenes:
Client is identified as having an Immigration or AIAN-related DMI
Workflow assigns the appropriate tags to the contact
Automated emails are sent using the new status-specific templates
A countdown sequence runs, escalating reminders up to two days before the document deadline
How Clients Exit the Workflow
There are two ways a client gets removed from the drip campaign:
Documents are uploaded directly — the system detects the upload and removes them automatically
Documents are emailed instead of uploaded — update the opportunity status to "Won" in the Service Pipeline, and the workflow will remove them from the drip
The second path is important. If your team receives documents by email and doesn't update the pipeline status, the client will continue receiving reminders even after you have what you need. Make sure your team knows this step.
A Note on Making Changes
This workflow is complex. The automation logic is layered, and editing one section can have unintended effects on others. Unless you have a specific reason and understand the full structure, leave the workflow as-is. If something seems off, flag it rather than attempting a fix.
What's Next?
DMI coverage is now more complete across the major status categories. As enrollment patterns shift and new edge cases emerge, additional templates or triggers may be added. Check back for updates, and make sure your team is briefed on what's changed before the next enrollment period.
Want to see this in action? Watch the full walkthrough video here.