#Slack Community29 人がディスカッション中

From what I've been seen so far, SlackCRM on Business+ V2 appears to require both the appropriate Slack subscription and compatible Salesforce licensing, but the publicly available documentation on the setup process and limitations seems quite limited.

For anyone planning a deployment, I would recommend verifying:

• Required Slack and Salesforce license types
• Admin permissions and authentication requirements
• Supported integration features on Business+ versus Enterprise Grid
• Sandbox and testing limitations
• Data retention, storage, and email-related constraints

If anyone from Slack or someone who has already implemented SlackCRM in production could share the official documentation or real-world experience, it would be extremely helpful for the community.

Hi Lorraine, sorry to hear that — losing the work email shouldn't have to mean losing the whole community. 

Invite links for the Ohana Slack do expire/rotate, so old ones from the community or Discord won't work — that's expected, not something specific to your account. 

The most reliable path is the official Slack Neighborhood page on Trailblazer Community, which is kept current:

If that page doesn't have a working join link when you check, post in this Trailblazer Community asking a Forum Ambassador or MVP to share a fresh invite — they regenerate these regularly since old links expire so often. Since you're no longer using the original work email, you'll likely want to join fresh with a personal email rather than trying to "regain" the old account.

The 8-user sandbox limit is definitely challenging for enterprise-level testing. A common approach is to use the sandbox for functional validation and smaller UAT scenarios, while running large-scale integration and performance testing in a dedicated Enterprise Grid test workspace that mirrors production as closely as possible. Automating repetitive test cases and using test accounts can also help maximize the limited sandbox capacity before deployment.

On a different note, if you're customizing Slack display names or team profiles, tools with fontes de letras can be useful for generating styled text for testing different naming conventions and visual formats.

Hi @DAEYEON KOO

, 

Congratulations on passing the Salesforce Certified Slack Administrator exam! 

As of now, Salesforce has announced the refresh for the Slack Administrator certification, but I haven't seen any official announcements regarding upcoming refreshes for the Salesforce Certified Slack Consultant or Slack Developer exams.

The best approach is to regularly monitor the Salesforce certification website and the official release notes, as Salesforce typically announces exam updates and maintenance requirements in advance. You may also want to keep an eye on the Trailblazer Community and certification-related communications sent to credential holders. 

If anyone in the community has received information about planned refresh dates for the Consultant or Developer exams, please share your insights. 

Good luck with your certification journey!

Hi there! Great questions, happy to help clarify what's available with the customer management feature in the new version of Slack Business+. 

Slack's built-in CRM tools let you build contact records, log customer interactions, and collaborate with your team — all within Slack. Under the hood, it relies on Salesforce Free Edition, which is automatically created when you set up a contact list.  

End-to-end setup process

• Click your profile picture → Preferences → Salesforce → Create New Salesforce Org
• This must be done by a Workspace Owner

Step 2 — Create your contact list 

• Import from Gmail, a CSV file, or build from scratch
• Access via: Home tab → Salesforce section in the sidebar → All Contacts

Step 3 — Assign access 

• Go to Admin → Manage Salesforce Organizations → select your org → Users tab → Add users to Salesforce org
• Up to 100 people can be granted access
• Permission levels are available via a drop-down menu

Key capabilities

• Log customer interactions (calls, emails, meetings) directly from a contact record 
• Share contacts in DMs or channels 
• Auto-sync Google Calendar and email events via Einstein Activity Capture 
• Customize contact fields (add priority, status, and more) 

Known limitations / constraints 

• Access is capped at 100 users
• Runs on Salesforce Free Edition — advanced Salesforce features/configurations beyond what's described in the help article are not part of this offering 

For the full setup walkthrough, check out the official help article: Manage customer contacts in Slack

Hey @Amanda Miller,

I can see why this would raise governance concerns, especially if actions performed during a 

Log In As session appear as though they were made by the impersonated user. 

In most cases, the safest approach is to tightly control who has the Log In As

permission and rely on audit logs to track when it's used. For organizations with stricter compliance requirements, it's often limited to a very small group of administrators or avoided in production unless necessary. 

I'm curious whether Salesforce considers this expected behavior for the Slack integration, or if there are any recommended controls to prevent posting while in a Log In As session.

Hello! I realize it's been a year, but I wanted to share the steps I've taken to notify the Slack user or record owner when the record is sent to a Slack channel.

I created a text field in the User object and filled it in by the Company member ID found in the Slack user profile.

1. )

2.)3. Then, I created a Text Template Resource and used this format to mention the owner of the record in Slack

<@{!$Record.Owner.Slack_Member_ID__c}>

4. Finally, I used the Text Resource as the value for the Slack Message field in my Flow Action.

This is the outcome of my Slack Flow.

I hope it helps

In the end contacted the Support team, 

the issue was that on slack sometimes it doesnt show on the left side. 

One has to go to: 

More -> Tools 

Then on the left top side it says "Agents"  

There you can click the Agent created, chat with it as requiered for the challange then finish.  

Now working and done with it

Hi @Ravit Appelboim-Hilb

I haven’t personally built this exact setup, but one thing that might help is using a unique identifier when you first add the message to the list (like message timestamp or a generated ID).

Then use that same value later when the reaction trigger fires to find and update the correct row. Without a consistent key, it’s usually hard for the workflow to match the right record.

If the workflow tools are still struggling with that mapping, it might be easier to handle this outside Slack workflows where you have more control over event matching. 

Hope this helps!