> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myfundingmachine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack opportunity mapping

> Keep the same support channel on Onboarding and Retention without blocking verification.

The Onboarding and Retention opportunities can both carry the same **Slack Channel ID**
and **Product Location ID**. Keep those fields on both records. A Retention copy does
not require another Slack channel or removal of the Onboarding channel ID.

For automatic verification, the CRM records must:

* Belong to the same Operations contact and product account.
* Agree on one valid Slack channel ID.
* Include exactly one matching opportunity in the Operations **Onboarding** pipeline.

The check uses that Onboarding opportunity as the setup source, regardless of the order
CRM returns the records. It then checks Slack normally. Matching CRM fields alone do
not prove the Operator has joined the workspace or private channel.
Cancellation or account-restoration holds recorded against either matching opportunity
continue to block automatic invitations and welcome messages, including when staff have
saved a specific source selection. The selection stays in place; holds are checked across
all records sharing that account and channel before setup and each external write.

## When staff review is needed

If the screen says **Your team needs to select the correct CRM opportunity for Slack**,
check for different channel IDs, multiple matching Onboarding opportunities, or a saved
source selection that no longer belongs to the account. Incomplete CRM searches and
unavailable pipeline metadata also prevent automatic verification.

Keep both valid opportunity records. Correct conflicting mappings after reviewing the
account, then use **Refresh setup connections**. Refresh may provision or reconnect the
channel when the configured gates permit it.

## Why the channel stays on opportunities

A contact can own more than one product account. Each account may have a different
private support channel, so one contact-level channel ID would be ambiguous. The
**Product Location ID** keeps channel evidence scoped to the right account. Records
with blank or different account IDs never supply this account's channel.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.