Configure Facebook Channel – Omnichannel (Dynamics 365 Customer Service)


To set up the Omnichannel –

To setup Facebook Channel,

Login to https://developers.facebook.com/, create a new account or use an existing developer account

Create a new Facebook App

Select the app type as Business

Provide an appropriate name and create the app.

Select Messenger as the Product for the app.

Next either  add an existing page or create a new one and then add the newly created page in the Messenger >> Settings

Here we created a new page and have added that page.

We can also Generate token for the page, which we will use while configuring Facebook Channel in Dynamics 365.

Click on Generate token and copy the token. Also, save the Page Id below the name of the page.

We will also need App ID and App Secret, which we can get from – Settings >> Basic

Next, we add a few test accounts to the app for testing/using the app. (we are not making the app publicly available or live, which would require and approval process)

Navigate to App Roles >> Roles >> Testers (Add Testers)

Back in Customer Service Admin Center, navigate to Customer Support >> Channels >> Messaging Accounts (Manage)

Add a New Account

Click Next and provide the App ID and Application Secret

Add Facebook Page to the account

Provide the Page name, Page ID, and the Page access token.

With the page successfully added, click on Next

Copy the Callback URL and the Token.

Paste this information in the Messenger product added.

Click on Add Callback URL.

Click on Verify and save

This adds the Webhooks details, click on Add Subscriptions for the Page added.

Select messages

We can see the account added.

Open the record, and navigate to the Facebook Pages tab, there we can see the Provisioning state as Running.

Next, we will create a Channel for this Facebook Account.

Navigate to Customer Support >> Channels >> Messaging (Manage) >> Add Channel

Select Channel as Facebook.

Add an existing workstream or create a new workstream.

Next, select the Facebook Page configured in the previous steps.

Language as English.

We can specify custom automated messages and Post Conversation survey settings here.

Specify the File attachments setting and message tag.

Review and if required edit the details and finally click on Create channel to create the Facebook channel

Next open the workstream created, to specify routing rules, work distribution, bot, etc. to route the customers to the queues/agents.

Here we can create a Route to Queue ruleset to route the messages on the Facebook page to a specific Queue.

Create the ruleset record.

Next, Create a rule. We can define the conditions here (right now we are keeping it blank) and routing to the Default messaging Queue (we can create a specific queue and add only the required users).

Make sure you have added users to the Queue and assigned Omnichannel Agent security roles.

We can update the default Work distribution properties.

Now sending the message from the Facebook Messenger, will pop up the notification for the agent logged into Customer Service Workspace.

Accept the notification to start the conversation.

Refer to the below articles-

https://learn.microsoft.com/en-us/dynamics365/customer-service/configure-facebook-channel?tabs=customerserviceadmincenter

Hope it helps..

Advertisements
Advertisement

Configure WhatsApp channel – Omnichannel (Dynamics 365)


To configure the WhatsApp channel, we need to set up the account in the Customer Service Admin Center.

Navigate to Customer Support >> Channels >> Messaging Accounts (Manage)

Select the New Account option there

Select WhatsApp as the channel

Next, we need Account SID and Authentication token.

To get this information we need to create a Twilio Account.

https://www.twilio.com/try-twilio

Navigate to the console and copy the Account ID and Authentication token

https://www.twilio.com/console

Enter Account SID and Authentication token click on Next

Next, we need to add the WhatsApp Name and Phone number

Navigate to Messaging >> Try it out >> Send a WhatsApp message to activate the WhatsApp Sandbox.

Follow the steps there to configure the Sandbox account. (scan the QR code send the Message, and test the Business and User-Initiated message/conversation).

Click on Sandbox setting tab to get more information

Copy the number.

Add the number and click on Next

Copy the URL

Paste that URL in the When a message comes in and save.

We can see our WhatsApp account created, open the record.

We can see our number being shown as Active

With the account active time to now it is time to set up the channel/workstream / queue.

Navigate to Customer Support >> Channels >> Messaging (Manage)

Click on Add Channel and add the details

Enter channel details

We are creating a new workstream

Add the WhatsApp number added

Select the language

Specify the Behaviour (automated messages and approved templates)

Specify the user features (attachments)

Review and Finish and Create the channel.

Open the workstream and specify routing rule/fallback queue/work distribution/associate bots etc details

We will create a ruleset to route the message to the queue

We have the below route-to-queue rule created to route to the default queue which has all the omnichannel agents added to it. (In an actual scenario, we would add the conditions and create a specific Advanced Queue).

We are leaving the rest of the settings/configuration as default.

Now is the time to test.

Let us log in to the Customer Service Workspace as an agent and from the registered sandbox participant number added send a message.

We are done with our configuration.

Get all the details

Hope it helps..

Advertisements

Enhanced Case experience – Full case form – Dynamics 365 Customer Service


Enhance Case Experience is currently available only for the Customer Service Workspace app which targets to increase the productivity of the agent.

To enable it, navigate to Customer Service Admin Center >> Customer Support >> Case Settings >> Enhanced case experience (Manage)

Enable the options – Here we have enabled the Full case form experience.

The new case form will show up while creating a new record from an existing case or the case grid.

Clicking on Configure opens the form in the Maker Portal.

The new Full Case form has the following new components added to it –

Grid Control – Case Associations (showing associated knowledge articles, similar cases, merged cases, and child cases)

  • Attachment Control – For the Case table, the new attachment control gives the option to directly upload the attachment as well as shows all the attachments either uploaded directly or associated with the notes or emails of the case record.

More on Attachment control:https://nishantrana.me/2023/05/08/new-attachment-control-dynamics-365/

  • Shows Priority and Case Status as color-coded options.

Due Activities Control – shows activities due today or overdue

More on Due Open Activities Control - https://nishantrana.me/2023/05/09/due-open-activities-control-dynamics-365/

It shows the activities overdue

  • Queue control shows the details of the Queue the record belongs to along with Worked By field.
  • Notes control that allows taking notes before saving i.e. in a new record.

More on Notes control - https://nishantrana.me/2023/05/10/notes-control-dynamics-365/

  • It also displays the Customer Details section based on the Customer selected in the case, as well as recent cases created.

Get more details on Enhanced Case Form

Hope it helps..

Advertisements

Notes Control – Dynamics 365


We now have new Notes control for the Case table.

The new notes control allows us to associate/create note without the need to create the case record first.

Here we are adding the Notes control in our Case form.

Specify Pre Create Notes Id (Text) as Table Column for Bound Attribute.

Save and publish the changes.

On creating the record we can see notes added to the timelines.

Also, we can observe that the control now shows – “No Data Available”.

In the case of the Enhanced Case Form, we have a script that hides that section after creation.

Due Open Activities Control – https://nishantrana.me/2023/05/09/due-open-activities-control-dynamics-365/

Attachment Control  – https://nishantrana.me/2023/05/08/new-attachment-control-dynamics-365/

Hope it helps..

Advertisements

Attachment Control – Dynamics 365


The new attachment control allows users to upload , download, delete, and view attachments that are added to a table through notes or emails or directly (for Case Table).

Below we have 2 attachments added to the case record.

We can see both the attachments there in the Attachments control along with an additional attachment directly added (Direct Upload) .

We can perform a search as well as change the view.

The Tile view –

The Delete option is only available in the case of files directly uploaded not the ones showing up from notes / emails.

For the Case table, the table column property is mapped to the Pre Create Entity Attachments Id field, which allows uploading attachments even before saving or creating the case record. (This is only available for the Case table)

Below we have uploaded attachments to a new case record.

We can add the Attachment Control to other tables as well.

Below we are adding it to the Contact form.

For tables other than Case, it can only be used to View the Attachments, we do not get the option to upload there.

Get all the details here

Due Open Activities Control – https://nishantrana.me/2023/05/09/due-open-activities-control-dynamics-365/

Notes Control – https://nishantrana.me/2023/05/10/notes-control-dynamics-365/

Hope it helps..

Advertisements

Agents not receiving calls in Omnichannel Voice – Dynamics 365 Customer Service


Recently we saw a few of our agents were not receiving the calls/notification for incoming conversations.

Apart from checking the Routing Diagnostics, we can refer to the Omnichannel Ongoing Conversation Dashboard (available for the Omnichannel Supervisor role)

In our case, we realized that the ongoing conversation was in Wrap-up status for the agent.

And also as we had a work item limit of 1 along with assignment blocking defined through the capacity profile for that agent, the agent wasn’t receiving the incoming notifications.

So here we can ask the agent to close the session correctly.

Or as a supervisor, we can force close the conversation from the Omnichannel Ongoing Conversation Dashboard.

Force Close-

Hope it helps..

Advertisements
%d bloggers like this: