Adding a concrete use case to the merged “Community chat in Conversations” request:

Please make GoKollab DMs a native messaging channel in the CRM:

• From a contact record, select “GoKollab” alongside SMS/email and send a private message to the linked community member.

• Sync incoming AND outgoing messages between GoKollab and Conversations, attached to the correct contact, with replies from either interface continuing the same thread.

• Add a “Send GoKollab message” workflow action and a “GoKollab message received” trigger, with dynamic fields, community/member filters and clear sending status.

Example: a member joins → a welcome DM is sent → their reply appears in Conversations → the team responds from the contact record and an appropriate follow-up workflow runs.

Please support a clearly identified, authorized team sender and keep unrelated member-to-member private chats private. Only sync the conversations the connected team is entitled to access.

The related automation request is here: https://ideas.gohighlevel.com/communities/p/add-kollab-community-dms-to-automations

This would connect community support, contact history and automation in one place.

I saw this request under many different post scattered around here. Perhaps one of the most requested features if you count these all together. This is a MUST.

Strongly agreed. Community chat should live inside conversations in the CRM. Right now, they are completely separated which makes record keeping for customer service, etc difficult when they initiate a community chat with our team.

Core Platform could you please consider this feature to be able to manage all conversations from one place (including also community chats)