Connect Slack

Decide what belongs in Slack

Slack works best as an action surface for time-sensitive work, not as a duplicate of every Bridgewerks record. Choose the workflows where a notification or action materially helps the team move faster.

Common launch choices include:

• New deal or material deal-stage updates.
• LOI and credit approvals.
• Deal questions and assigned tasks.
• Closing or scheduling alerts.
• Application, support, or operational alerts.

Choose owners and channels

Provide the Slack workspace name, a Slack administrator, and one business owner for each workflow. Map every approved workflow to a channel and decide whether it is public or private.

Prefer stable team channels over temporary deal-specific channels unless your operating model requires one channel per deal. Name an owner who will update the mapping when channels are renamed or archived.

Install and configure the app

Your Slack administrator installs or approves the Bridgewerks app through the secure implementation process. The Bridgewerks implementation lead configures the approved workflow-to-channel mapping for your deployment.

If a target channel is private, invite the Bridgewerks app to that channel. Do not paste Slack tokens into email, deal notes, tasks, or support messages.

Test each workflow

Use non-sensitive test data and verify each configured workflow end to end:

1. Trigger the event in Bridgewerks.
2. Confirm the message arrives in the intended channel and nowhere else.
3. Check that the message contains enough context without exposing unnecessary borrower information.
4. Test any approved buttons or actions and confirm the result in Bridgewerks.
5. Confirm the escalation owner for delivery failures.

Microsoft Teams may be captured as a future workflow requirement, but full Teams parity is not currently documented as an available setup path. Your implementation lead will confirm supported scope before launch.