Slack CRM Integration: Channel Sync, Notifications, and Commands

Yes. Map the channel to a company or a deal with '/lumo sync here to company <name>', or on the Channel sync tab of the Slack settings page. Its messages then appear on that record's timeline under a Slack tab, in the record's Conversations widget, and as evidence Lumo can cite. Lumo has to be invited to the channel first with /invite @Lumo, private channels included.

New messages arrive within seconds. A newly mapped channel also pulls the last 90 days in the background, and '/lumo history' asks for everything instead. Slack limits how fast our app can read old messages, so a channel with tens of thousands of messages genuinely takes hours. That is the limit, not a stalled job.

'/lumo sync', '/lumo history' and '/lumo unsync' manage channel sync and are admin only. '/lumo status' and '/lumo help' work for everyone, and '/lumo private on' or '/lumo private off' lets the person who synced a channel limit who can read it. Everything else is a mention: '@Lumo <question>' asks Lumo, '@Lumo find <name>' searches privately, '@Lumo status' shows the mapping, and '@Lumo reset' clears the channel's conversation.

Yes. Mention it in a channel it has been invited to. Lumo reads the CRM with your Lumenbase access and answers in a thread everyone in the channel can see. Each channel keeps one conversation, it answers at most 5 mentions per channel per minute, it is read only, and it uses Lumo credits from the workspace's shared pool. An admin can switch it off under Settings, Workspace, Lumo, Settings tab, Lumo in Slack.

Eight, each an independent switch per channel: new deals, deal stage changes, deals won, deals lost, new activities, new tasks, tasks due, and tasks overdue. There are no value or stage filters on a subscription, so narrowing a channel means giving it fewer events.

Commands and @Lumo need your Slack member linked to a Lumenbase user, and linking is by email address only. An admin opens Settings, Workspace, Integrations, Slack, Users and selects Match users. If you still do not appear, your Slack profile email differs from your Lumenbase email.

No. The first notification about a record in a channel starts a message and every later notification about that same record posts as a reply under it, so one deal produces one thread. Threading is per channel, so the same deal in two channels keeps two threads.

No. Notifications are short text posts with no buttons and no link back to Lumenbase. Approvals, task completion and stage changes happen in the app.

A Lumenbase workspace admin, who also needs permission to install apps in the Slack workspace.