Project

The Microsoft Dynamics 365 Contact Center is transforming customer engagement through Generative AI technology across various communication channels. It serves as an Copilot-first contact center as a service (CCaaS) solution compatible with preferred CRMs or third-party (3P) software. This add-on enables customers to leverage Dynamics 365 Contact Center along with AI functionalities within their preferred CRM system.

Built upon the Microsoft Azure, Power Platform, and core Dynamics 365 infrastructure, Dynamics 365 Contact Center extends its capabilities by seamlessly integrating CCaaS and AI features with existing 3P solutions. Agents have the flexibility to utilize the add-on in either Embedded mode, where the 3P CRM serves as the primary user experience (UX) with CCaaS/AI functionalities embedded, or Standalone mode, where Dynamics 365 Contact Center plus AI capabilities take precedence while maintaining connectivity with 3P CRM data.

Prerequisites

Set up D365 Contact Center embedded experience
Install Node latest version
git clone https://github.com/microsoft/dynamics-365-contact-center.git

CTIDriver Setup

The CTI driver serves as a bridge between the Microsoft Omnichannel Add-on and Salesforce CRM, allowing for the integration of telephony features into the CRM environment.

Note: These steps can be omitted if the default CTIDriver file is used.

CTIDriver Extention for Salesforce and ServiceNow

Salesforce Extension

Navigate to /samples/SFExampleCTIDriver
Run command npm install
Open the file /samples/SFExampleCTIDriver/src/SFExampleCTIDriver.ts
Implement your desired functionality within any of the methods provided by the ICTIDriver interface. Refer to the Salesforce OpenCTI Methods Documentation for available methods and their usage.
Run command npm run build, dist/SFExampleCTIDriver.js file will get generated inside /SFExampleCTIDriver folder
Host the compiled file (dist/SFExampleCTIDriver.js) on a CDN and include the CDN URL as a query parameter in the CCaaS URL.

Note: It does not need to be a CDN URL, any URL with public access will also work

The format of the URL should be:

https://<example-ccaas-domain>/widget/index.html?dynamicsUrl=https://msdynccaasdev.crm.dynamics.com&ctiDriverUrl=<CDN-url>

example-ccaas-domain: https://ccaas-embed-prod.azureedge.net

Replace <CDN-url> with the actual URL of the hosted compiled file on the CDN.
Update the Salesforce Call center definition file (imported in prerequisite) by replacing the <ctiDriverUrl> parameter with the URL generated in Step 6.
Your Salesforce Extension integration is now complete and ready to use.

ServiceNow Extension

Navigate to /samples/SNExampleCTIDriver
Run command npm install
Open the file /samples/SNExampleCTIDriver/src/SNExampleCTIDriver.ts
Implement your desired functionality within any of the methods provided by the ICTIDriver interface. Refer to the ServiceNow OpenFrame Methods Documentation for available methods and their usage.
Run command npm run build, dist/SNExampleCTIDriver.js file will get generated inside /SNExampleCTIDriver folder
Host the compiled file (dist/SNExampleCTIDriver.js) on a CDN and include the CDN URL as a query parameter in the CCaaS URL.

Note: It does not need to be a CDN URL, any URL with public access will also work

The format of the URL should be:

https://<example-ccaas-domain>/widget/index.html?dynamicsUrl=https://msdynccaasdev.crm.dynamics.com&ctiDriverUrl=<CDN-url>

example-ccaas-domain: https://ccaas-embed-prod.azureedge.net

Replace <CDN-url> with the actual URL of the hosted compiled file on the CDN.
Add the above url in the respective OpenFrame Configuration as shown in the screenshot below:

Url to the list of OpenFrame Configuration: https://<ServiceNow-domain>/now/nav/ui/classic/params/target/sn_openframe_configuration_list.do
Your ServiceNow Extension integration is now complete and ready to use.

ServiceNow setup Document

CTIDriver Implementation for Generic CRM

Configuration

Navigate to samples/GenericExampleCTIDriver.
Run npm install to install the project dependencies.
Navigate to GenericExampleCTIDriver/src/GenericExampleCTIDriver.ts.
Implement the methods defined in ICTIInterface according to your CRM requirements.
Run npm run build to compile the project.
Host the compiled file on a CDN. Include the CDN URL as a query parameter in the CCaaS URL. For example, the CCaaS URL format should be: https://<example-ccaas-domain>/widget/index.html?dynamicsUrl=https://msdynccaasdev.crm.dynamics.com&ctiDriverUrl=<CDN-url> Replace <CDN-url> with the actual URL of the hosted compiled file on the CDN.

Note: It does not need to be a CDN URL, any URL with public access will also work

example-ccaas-domain: https://ccaas-embed-prod.azureedge.net
Incorporate this URL into the phone/softphone settings of your CRM.

Communication between Generic CRM and CTIDriver

Use window.postMessage to communicate from CTIDriver to Generic CRM.

embedSDK.conversation.onConversationLoaded((conversationData: IConversationLoadedEventData) => {
    console.log("Embed SDK Conversation Loaded", conversationData);
    window.parent.postMessage(conversationData, "*");
    presenceAPIs(embedSDK);
    getFocusedConversationId(embedSDK);
});

Use document.getElementById("iframeId").contentWindow.postMessage to communicate from Generic CRM to CTIDriver.

// code required to send message on Generic CRM side
document.getElementById("iframeId").contentWindow.postMessage(JSON.stringify({messageType:"clickToDial", messageData: {number: 8208654321}}),"*");

// code required to listen for message event on CTIDriver side
window.addEventListener("message", (event) => {
    const {messageType, messageData} = JSON.parse(event.data);
    if (messageType && messageType === "clickToDial") {
        const clickDialPayload = {
            number: messageData.number
        };

        callbackFunction(clickDialPayload);
    }
})

CCaaS SDK APIs

Refer to the CCaaS SDK README for details on available APIs and how to integrate them.

License

adekola/D365CC_SF

ErrorLooks like something went wrong!

About

Resources

License

Code of conduct

Security policy

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Languages

Error
Looks like something went wrong!

Packages