Slack is where many operational teams already spend their day. It is where support teams coordinate, where cross-functional questions get answered, and where urgent issues surface first. Risk and underwriting teams, however, are not always in the same place. They may be working inside Coris, while other teams rely entirely on Slack for visibility and updates.

This creates gaps. When risk events happen, teams in Slack do not always see them in real time. When support teams need to ask the risk team a question, the request often gets lost in messages, shared threads, or direct pings. And when volume grows, these manual handoffs become harder to track.

Our new Slack integration changes that.

Coris can now push real-time customizable alerts into Slack channels where teams already work. It can also receive structured requests from Slack and turn them into trackable alerts inside Coris. This removes copy and paste work, reduces missed communication, and brings risk workflows closer to the places where operators collaborate.

The result is faster awareness, clearer handoff workflows, and fewer moments where information is trapped in one system but needed in another.
‍

What we are launching

We have built a native integration between Coris and Slack that supports both outgoing alerts and incoming requests. It is live in the Slack App Marketplace, and customers can install and connect it without involving their engineering teams.

Once installed, the Coris Slack app can send risk alerts into any Slack channel in the customer’s workspace. Teams can choose which events should trigger alerts and what information each message should include.

The integration also supports the reverse direction. Support teams and operators can submit a structured request through the /risk request command in Slack. Coris receives the request and creates an alert that the risk team can track and resolve inside the Coris platform.

With this integration, Slack becomes a real-time communication layer for risk workflows, without replacing Coris as the core system of record.

‍

How the integration works

Simple setup

Customers can install the Coris Slack app directly from the Slack App Marketplace and connect it to Coris through OAuth. No engineering work is required. A Coris admin can:

• Authenticate the workspace connection
• Select default channels for alerts
• Install the app in the channels where alerts should appear
• Test the connectivity

After setup, Coris can send alerts to Slack and process requests coming from Slack.

Push Coris alerts into Slack

Risk teams can configure any rule or workflow inside Coris to send alerts to Slack. This includes event-based triggers, manual review alerts, or any risk rule they choose.

Within the alert settings, teams can define the content of each Slack message. Messages can include dynamic data such as:

• Account ID
• Business name
• Processing volume
• Link to the account in the Coris portal
• Any relevant custom fields

Static text and formatting can also be added so the alert appears with the right context.

Once configured, Coris pushes alerts to the specified Slack channel as soon as the rule fires. This gives operators and support teams real-time visibility without needing to open Coris.

Create requests in Slack that appear in Coris

The integration also supports inbound communication. If someone in Slack needs to ask the risk team a question or surface an issue, they can type:

/risk request

Slack opens a form where the user can enter:

• The merchant or account identifier
• The nature of the request
• Any details the risk team should know
  

When submitted, Coris receives the request and creates an alert. Risk teams can now track it like any other workflow item, instead of searching for it in scattered channels or direct messages.

This ensures all risk-related work stays inside Coris while still meeting teams where they already operate.

‍

Example workflows

1. Risk events surfaced to operational teams

A payout hold, risk rule trigger, or unusual activity is detected in Coris.
Coris sends an alert to the designated Slack channel with key data and context so the right teams know immediately.
Result: Faster awareness and no dependency on checking the Coris portal.

2. Support teams request input from Risk

A merchant reaches out to support with a question about payouts or onboarding.
Support enters /risk request, fills out the form, and submits.
Coris creates an alert that risk teams can track and close.
Result: Requests stay organized and no longer get lost in Slack threads.

3. Daily operational visibility

Teams that do not actively log into Coris can stay up to date on account activity through curated alerts in Slack.
Result: Shared visibility without duplicating tools or processes.

‍

Why this matters

The Slack integration is designed to make communication easier for teams that work around risk but are not always inside the risk platform itself.

With Slack and Coris connected:

• Risk alerts reach the right teams instantly
• Support teams can submit structured requests without leaving Slack
• Information no longer needs to be copied across tools
• Requests and alerts are tracked in Coris instead of scattered across channels
• Operators gain visibility without adding manual steps
  

Coris remains the central risk system. Slack becomes the communication layer that brings the right information to the right people at the right time.

‍

What is coming next

Phase one includes outbound alerts, inbound request creation, and full workspace installation through the Slack App Marketplace.

Next we are working on:

• Simple interactive actions inside Slack so teams can respond to alerts without switching tools
• Additional formatting and customization options for alert templates
• More control over how Slack requests map into Coris workflows

As these updates ship, teams will be able to handle more operational work directly in Slack while keeping Coris as the system of record.

The goal is straightforward. Less searching for information. More clarity about what is happening. A smoother path to resolution.