When an enrollment problem occurs, identifying the root cause is often the hardest part—requiring ben-admin teams to piece together carrier errors, enrollment records, and other systems to understand what to fix.

Today, we're introducing the Field Guide for Issues—a new experience that helps ben-admins quickly identify the exact data that's causing a problem and how to fix it.

The Field Guide displays the Snapshot body that triggered an Issue directly within the Issue details page and visually highlights the data tied to the problem. Instead of manually reviewing raw errors and payloads, users immediately see which fields require attention.

Bringing enrollment problems into focus

The highlighted paths within the Field Guide are defined on the backend so the same Issue targets the same fields every time.

The Field Guide supports four types of annotations:

• Invalid: Noyo has identified the specific field that caused the Issue. For example, an invalid benefit class, bill group, or other carrier configuration value. The highlighted field is the field that needs to be corrected.
  
  

• May Be Invalid: Noyo has determined that one or more highlighted fields are causing the Issue, but cannot know which specific value is incorrect. For example, a ZIP code and state mismatch, or a duplicate enrollment where two records conflict. The highlighted fields help narrow the investigation to the relevant data.
  
  

• Missing: Required information was not included in the Snapshot. Examples include omitted coverages, missing carrier configuration values, volume amounts, SSNs, event blocks, and more. Missing fields are inserted into the view and highlighted. If Noyo knows what specific values should have been included, we'll insert those too.
  
  

• Related: Additional context that may help explain or resolve the Issue. These fields are not necessarily invalid or missing, but provide useful information for investigation. For example, coverages associated with an Evidence of Insurability (EOI) review that require additional action to complete the enrollment.

For situations where the underlying error does not provide enough detail to confidently identify specific fields, Noyo still displays the full Snapshot body. This allows users to investigate the problem without navigating to additional pages.

Support for field-level guidance is rolling out for all Issues created from Snapshot Validations and Premier carriers.

Visibility into every stage of enrollment processing

Raw and Processed Snapshot view

Users can toggle between the Raw Snapshot, which shows the exact data submitted by the ben-admin, and the Processed Snapshot, which reflects the enrollment payload after Noyo applies mapping rules, resolves carrier configuration values, and builds the final request sent to the carrier.

Visibility into both is important because some Issues originate from values that are resolved during processing rather than data explicitly included in the original inbound request. Users won't need to think about this complexity—the Field Guide always defaults to the most relevant view of the Snapshot.

However, both views are available, providing deeper insight into where problems occur.

Omitted coverages

The Field Guide also provides visibility into omitted coverages.

Ben-admins set an omitted coverage handling policy (reject, continue, terminate), which tells Noyo what to do when active coverages are not included in a Snapshot. Depending on the policy, these coverages may still be processed and trigger Issues.

When omitted coverages are relevant to an Issue, the Field Guide highlights and labels them, including highlights for any invalid data. This creates a clear visual distinction between Missing data that was unintentionally left out and Omitted coverages that were excluded based on the omitted coverage handling policy.

Contextual annotations

The Field Guide also includes annotations throughout the Snapshot body to make it easier to interpret and navigate.

Examples include:

• Carrier names alongside carrier IDs

• Plan names alongside plan IDs

• Member names alongside identifiers

These annotations reduce the need to cross-reference other systems so its easier to resolve problems from a single view.

What's next

This release is the foundation for some exciting enhancements. Noyo often knows the correct values or the available options for missing and invalid data. We're exploring ways to surface intelligent recommendations directly within the Field Guide, removing as much friction between problem and action as possible.

Want to learn more about modern data reconciliation with Noyo? See the original Issues release or reach out for a demo.