Request connections with any carrier through the Noyo App or by API

You can now request a connection with any carrier directly in Noyo, whether the carrier is already in Noyo’s network or not.

Previously, connecting with an out-of-network carrier required a separate process and coordination with the Noyo team. Now, all connection requests can be submitted over API or in the app, giving you one consistent way to get started.

When you request an out-of-network carrier, our team will first vet the request to determine whether the carrier can be supported. You can then follow the request directly in Noyo as it moves through the connection process, giving you visibility into its progress.

We’ve also made it easier to provide the information needed to get started, including renewal dates and relevant carrier and employer contact details—helping reduce back-and-forth and keep implementation moving forward.

A clearer view of every connection’s status

We’ve enhanced the connection lifecycle to make it easier to understand the current state of a group’s connection with a carrier.

• Not Connected: The connection is not currently active.

• Initiated: A connection has been requested and is waiting to begin setup.

• Vetting: An out-of-network carrier is being evaluated to determine whether the connection can be established.

• In Setup: The connection is actively being configured and prepared to go live.

• Active: The connection is live and exchanging data.

• Disconnecting: The connection is in the process of being disconnected.

• Disconnected: The connection has been successfully disconnected.

The lifecycle reflects the overall state of the connection, rather than the status of a specific group setup or disconnect request. This gives you one consistent view of where the connection stands over time.

Cancel setup requests directly in the Noyo App 

You can now cancel an in-progress setup request directly in the Noyo app—removing the need to contact the Noyo team or submit a support request.

Whether a carrier is no longer needed or a request was submitted by mistake, you can cancel the setup as soon as you know it’s no longer needed. Before cancelling, you’ll see a confirmation explaining the impact. Once cancelled, the request cannot be resumed. But if you need to re-establish the connection later, you can simply initiate a new request.

Cancelled requests remain in your connection history and are clearly distinguished from requests that could not be completed, giving you a more complete record of what happened and why.

More context for every connection

Updated banners, history, and timestamps give you a clearer view of where a connection stands, what’s happened along the way, and what comes next.

• Clearer banners: New banners surface relevant context about the current state of a connection, including when a connection is initiated, vetted, in setup, or being disconnected.

• More complete history: Connection views now bring setup and disconnect activity together in one history, including previous setup attempts, cancellations, and disconnections. This makes it easier to understand how a connection reached its current state.

• Timestamps: Connection views now show key events, including when setup began and when syncs occur, so you have a clearer timeline of the connection.

What's next?

These updates lay the foundation for a more unified connection management experience. We're continuing to build toward clearer progress tracking, more control over workflows, and a more complete view of every connection.

Stay tuned for more updates as we continue making it easier to manage connections from start to finish.