Abstract: A hub-and-spoke architecture for bidirectional connections between a first vendor and a second vendor, wherein the second vendor functions as a partner on a spoke to the first vendor functioning as a hub, an event-based architecture configured to transmit data between the first vendor and the second vendor based on a predefined event, a metadata sharing module configured to share authorized organizational metadata between the vendor and the one or more partners, wherein the metadata sharing module enables the first vendor to submit a request for access to one or more requested data fields from the second vendor, enables the second vendor to approve the request, to identify one or more corresponding data fields corresponding to the one or more requested data fields, and to integrate the granted data fields into the vendor's CRM system.

Abstract: Disclosed herein are system, method, and computer program product embodiments for capturing incoming communications from a sender across multiple channels, and determining whether to include those communications from the sender in an inbox using a waiting room. The waiting room lists unknown senders, and allows a user to add the senders to a blocklist, where the sender's communications are omitted from the user's inbox, or to a passlist, where a new CRM customer record is created for the sender. With the CRM customer record created, future communications from the sender are matched to the CRM customer record and permitted for inclusion in an inbox. This way, recipients can prioritize customers (or other high-value communications) within their inbox based on a corresponding existing CRM customer record, while simplifying the capture of those CRM customer records.

Abstract: Disclosed herein are system, method, and computer program product embodiments for capturing incoming communications from a sender across multiple channels, and determining whether to include those communications from the sender in an inbox using a waiting room. The waiting room lists unknown senders, and allows a user to add the senders to a blocklist, where the sender's communications are omitted from the user's inbox, or to a passlist, where a new CRM customer record is created for the sender. With the CRM customer record created, future communications from the sender are matched to the CRM customer record and permitted for inclusion in an inbox. This way, recipients can prioritize customers (or other high-value communications) within their inbox based on a corresponding existing CRM customer record, while simplifying the capture of those CRM customer records.