difference between customer chat and discussions
ART-3231_KNOWLEDGE_NODE-25
**Configure**.\n2. Fill in the configuration settings.\n\n   * **Command Names**: List command names that exist in the organization. Enter\n     one per text box (to add more text boxes, click \'**+**\').\n   * **Customer Chat Surfaces**: Select surfaces where the commands should be\n     available in the "Customer messages".\n   * **Discussions Surfaces**: Select surfaces where the commands should be\n     available in internal chats.\n3. Click **Save**.\n4. Click **Install** to activate the
Commands surface expander | Automate | Snap-ins | DevRev
ART-1997_KNOWLEDGE_NODE-30
opportunities to signal the necessary development work for closing the opportunity. Likewise, linked conversations represent dialogues between a sales representative and a customer concerning the opportunity's closure.\n\nOpportunities incorporate a discussion timeline to support real-time collaboration in advancing an opportunity. They play a pivotal role in prioritizing development enhancements.\n\n\xf0\x9f\x91\xa5 Contact\n---------\n\nA contact record represents individual prospects or
Computer for Growth Teams | DevRev
ART-2002_KNOWLEDGE_NODE-28
migrate your customer contacts from various platforms such as Hubspot, Salesforce, Zendesk, Jira, Linear, ServiceNow and more.\n\nCustomer records offer a place to do the following:\n\n* Find all conversations and tickets linked to a customer in one view.\n* Have internal discussions related to a customer.\n* Add description or notes about a customer.\n* Assign an owner or tags to the customer.\n\n![]()\n\nApart from customer records that get automatically created from your [Plug
Contacts | Computer for Growth Teams | DevRev
ART-2035_KNOWLEDGE_NODE-40
channel determines the sync location in DevRev:\n\n* **External/Connect channels:** Syncs with the **Customer Messages** panel.\n* **Internal channels:** Syncs with the **Internal Discussions** panel.\n\nSyncing different panels to separate Slack threads is not supported.\n\n![]()\n\nOnly shared tickets are synchronized between DevRev and Slack.\n\n### Follow-up and merged Tickets\n\nThe Slack snap-in supports follow-up and merged tickets.\n\n* When two tickets merge, and both have syncing
Slack | Integrate | Snap-ins | DevRev