Managing Sync in Slack Channel
Doti allows you to ingest Slack channel content as part of its searchable knowledge base - giving users the ability to ask questions based on discussions, decisions, and shared knowledge directly from Slack.
Admins can manually control which channels are synced or unsynced using Doti's Slack /
commands.
How Sync Works
When a Slack channel is synced, Doti:
Ingests messages from that channel
Makes them available to answer user prompts (based on permissions)
Shows the synced channel in the Doti Portal, where it can be assigned to agents
When a channel is unsynced, Doti:
Immediately stops indexing new content from that channel
Removes it from future answers
🚫 Unsynced channels are excluded from all responses, and their historical content is no longer used.
Commands: /doti sync
and /doti unsync
/doti sync
and /doti unsync
Doti supports two Slack slash commands:
/doti sync
- enable syncing for the current channel/doti unsync
- disable syncing for the current channel
⚠️ Only Doti admins can use these commands.
Possible Outcomes
Depending on the channel state, you may receive one of the following confirmations:
"Sync process for channel #channel-name has started."Doti will now allow users to get answers from content derived from this channel.
Sync successfully enabled
"Sync process for channel #channel-name is disabled."Doti will no longer include content from this channel in its answers.
Sync disabled (unsynced)
"Sync process is already enabled for this channel."For more details, visit Doti Portal
No change - already synced
"Doti is currently not a member of this channel."To initiate the synchronization process, please add Doti by typing @doti
in the channel.
Doti must be invited to the channel before syncing
Where to See Synced Channels
Once a channel is synced:
It will appear in your Doti Portal
You can assign it to any agent, making its content available to that agent’s prompt responses
You can manage collections, access, and visibility per agent
Best Practices
Sync only the channels that hold valuable, recurring knowledge (e.g., #product-updates, #customer-insights, #engineering-notes)
Avoid syncing channels with high-volume, low-signal chatter unless you need their historical context
Use agent scoping to ensure Slack content is only surfaced to the right teams
Last updated
Was this helpful?