Dynamics 365 Customer Service

Today the D365 customer service dashboard shows 'ThisWeek' time frame which shows data for all the 7days of this week. There is a need to show the data based on working days (Monday to Friday) as the default filter. This makes it necessary to set custom time frame every time user opens the dashboards. Could you please provide option to select workdays timeframe option in the dashboards.

Using the working distribution methods, please add a "ring all" functionality.

In case of emergency the workitem (call) will be offered to all available agents at the same time. The first agent who will accept this call can handle this one.

Special for Contactcenters with high priority workitems (like emergency, notifying of a death).

The "ring all" is a basic feature in all kind of phone systems...

To improve the efficiency and responsiveness of customer service agents, I propose the implementation of an audible beep signal that alerts agents when a phone call connection is successfully completed and the call is about to begin. This feature will enhance the omnichannel customer service experience by ensuring agents are immediately aware of incoming calls, reducing initial response times and improving overall customer satisfaction.

Benefits:

• Improved Agent Readiness:
• Agents will be more prepared and alert, leading to smoother call openings and more professional interactions.
• Reduced Customer Wait Time:
• Immediate awareness of call connection reduces awkward silences and unnecessary wait times for customers.
• Enhanced Customer Experience:
• A prompt and professional start to the conversation sets a positive tone for the entire interaction.
• Increased Efficiency:
• Streamlining the call connection process can lead to quicker issue resolution and better overall efficiency in handling customer inquiries.

As on any other Dynamics 365 App, when we do not have any dashboardid configured on the Application Tab Template, the user default dashboard should be the default shown (be the default dashboard a user or system).

The Teams collaboration feature in Dynamics 365 doesn't support guest user login.

By implementing this feature, users can operate efficiently.

We are currently using base and custom presence statuses in our system. However, we have identified a need to reorder these statuses according to a custom sequence rather than the default alphabetical order.

For example, we would like to arrange the statuses in the following order:

1. Teamlead
2. Buddy-work
3. Available
4. Chat
5. Busy
6. Busy-DND
7. Away
8. Offline

Unfortunately, the system currently enforces alphabetical sorting, and base presences cannot be edited, which limits our ability to implement a custom order.

We believe that allowing custom sorting for presence statuses would greatly improve user experience. We kindly request the addition of functionality that enables the manual reordering of presence statuses.

Currently, there is no functionality to know whether a record registered in the "Cases" entity has been read or unread.

Adding this functionality will improve convenience for users.

Enhancing Email Activity Statuses for Improved Collaboration in Customer Service

Background: 

In our use of both Customer Service and Omnichannel for Customer Service, we have identified a key limitation in the email activity handling, specifically related to the status reasons available for inbound emails. Currently, when an inbound email is received, the status is limited to “Received,” whether or not the email has been replied to. This limitation creates inefficiencies and challenges for teams collaborating in the Customer Service Inbox, as it becomes difficult to distinguish between emails that have been handled and those still requiring action.

Current Challenge:

• Inbound emails only display the status “Received,” even after an agent has responded to the email.
• The lack of visibility into whether an email has been responded to, and when it was responded to, makes collaboration across teams cumbersome. Agents have to manually check or rely on inefficient workarounds to determine which emails have been handled.
• This issue is particularly problematic for teams working in a shared inbox environment, as it hinders transparency and prevents effective task management. 
• Email response time is impractical to calculate based on the email activity's "Modified on" date since this parameter is affected by all types of adjustments, thus becoming unreliable in this specific context. 

Proposed Solution:

• We recommend adding an additional status reason to the inbound email activity that would update automatically when the corresponding outbound email activity (response) reaches the status of "Sent." For example, the inbound email status could be updated from "Received" to "Replied to" when the system detects that a response has been successfully sent. The replied to date should be saved and visualized on the activity record. 

Key Benefits:

• Improved Collaboration: This feature would give agents and teams immediate visibility into which emails have been handled, improving transparency and reducing the likelihood of missed or duplicated responses.
• Enhanced Workflow Efficiency: Teams can quickly filter and organize emails in the Inbox based on whether they have been responded to, which is not possible in today's setup. 
• Accurate Email Status Tracking: Adding more granular status reasons and visualization of when the email was responded to ensures more accurate tracking of each email's lifecycle, from reception to resolution.
• Streamlined Filtering and Reporting: This change would enhance the ability to set up filters and reports to track email responses and response times, thus improving overall service management.

How it Would Work:

• When an inbound email is received, it retains the status “Received.”
• Once an outbound email is sent (with a matching thread ID), the system automatically updates the inbound email’s status to “Replied to" and saves the date of when the reply was made. 
• This status update is triggered when the corresponding outbound activity reaches the "Sent" status.

Conclusion:

By introducing additional status reasons for inbound email activities, particularly a "Replied to" status, Microsoft can enhance collaboration, transparency, and efficiency for users of the Inbox. This improvement would help teams work more seamlessly, ensuring better customer service outcomes.

CRM internal header is containing period as below which is not following the HTTP header standard

"mscrm.returnnotifications"="true"

HTTP Headers defined by RFC2616, RFC2822, RFC7230 advise against the use of non-standard characters such as the period below:

Sec-Fetch-Site – Acceptable HTTP header delimiter usage ‘-‘.

accept – Acceptable HTTP header non-delimiter usage.

We should fix this one (maybe replace the period by hyphen for internal CRM header)

To enhance data privacy and compliance with GDPR regulations, it is essential to (re-)enable the deletion of personal or sensitive attachments directly from the new attachment grid in incoming emails. By allowing direct deletion of attachments within the grid, we can streamline the process, improve user experience, and ensure that only necessary data is stored. It is an improvement that we can use the preview function but I am disappointed with the decision to remove the delete functionality. It was very useful, and its absence has negatively impacted our workflow.