Chatter Messages are a Chatter primitive. Configuration is mostly about permissions and compliance archival; usage is the daily activity of users.
- Confirm Chatter is enabled
Setup, Chatter Settings, ensure Chatter is on. Messages require the broader Chatter feature.
- Send a message from the Chatter UI
Open the Chatter tab, click Messages, click New Message. Pick recipients, write the message body, send.
- Configure compliance archival if needed
For regulated industries, enable Salesforce Shield Event Monitoring or integrate a third-party archival tool. Without archival, messages are not captured for compliance review.
- Restrict message-access permissions
Decide whether admins should be able to read messages. By default, only message participants can see them; View All Data grants broader access.
- Evaluate Slack as a replacement
For orgs with active collaboration needs, plan a migration to Slack. Chatter Messages are a legacy feature; Slack is the strategic direction.
- Train users on appropriate use
Document when to use a Chatter Message vs. a Chatter Group post vs. a Slack DM. Clear guidance prevents accidental sharing of sensitive content in the wrong surface.
- Chatter Messages are private by default. Even admins cannot read them without specific permissions.
- The participant list is locked at conversation creation. Adding participants later requires starting a new conversation.
- Regulated industries need compliance archival. Default ChatterMessage storage does not satisfy capture-and-supervision requirements.
- Salesforce''s strategic direction is Slack. Investing heavily in Chatter Messages is investing in a fading surface.