In this series we’ll aim to layout the foundations of the Unified Service Desk client including getting a test implementation running, covering some best practices for performance and usability, and covering the client’s myriad of included adapters and controls.
Let’s start Part 1 with a brief overview of the USD client and its associated architecture.
USD In Brief
Let’s lay the groundwork for what we will be working with.
“The Unified Service Desk or, USD, is best used when you have a call center (or more than one) that must open multiple applications to handle incoming calls effectively.”
We’ve written about the value proposition of USD in previous articles but for our purposes here we’re going to assume that you’ve already decided to use USD or are close to making that decision. It is important to remember that while we usually consider USD in Call Center implementations the client may be successfully leveraged in other instances as well such as for bank tellers, POS stations, manufacturing floors, or anywhere that multi-session capabilities plus systems orchestration can be of value.
Fundamentally we should think of USD as the following…
a. This is not a web based client. This is traditional software… downloaded and installed on each workstation.
2. A container for CRM and other embedded applications
a. You will still be doing your regular web-based Dynamics project. You will then implement USD on top of (or in parallel to) Dynamics.
3. Customized through the UII development framework (you need a developer)
a. The UII development framework is part of the CRM SDK
4. Included with your regular CRM licensing (likely)
a. This tool is likely available to you as part of your Dynamics subscription. While it takes work to configure and properly use there is usually no additional licensing concers.
USD comes pre-packaged with a suite of tools and controls.
1. Package Deployer Software
a. Administrative software for updating USD configurations
2. USD Framework
3. Session Management
4. Framework for 3rd party integrations
5. The USD Client itself
a. Installed on each user machine
6. Hosted Applications (https://msdn.microsoft.com/en-us/library/dn864943.aspx#Types)
a. Hosted Controls
b. Web hosted application
c. External hosted application
d. Remove hosted application
7. Hosted Controls (https://msdn.microsoft.com/en-us/library/dn864910.aspx)
a. Connection Manager
b. Global Manager
c. Agent Scripting (Call Scripts)
d. CRM Dialog
e. CRM Page
f. CTI Desktop Manager (Telephony Integration)
h. Panel Layout
i. Popup Notification
j. Session Lines/Tabs
k. User Notes
l. Session Timer
8. Other components
a. Configurable toolbars
b. Note capture
c. Status capture
d. Audit trails
e. Call timing
f. UX Themes (xaml style sheets)
10. Hosted Application Toolkit (aka HAT)
At a glance this is what a high-level USD implementation could consist of. This may vary between implementations but the main takeaway is that USD becomes the user’s main utility. USD then pulls data and integrates with systems from within the USD framework.
And there we have the basics! Join us for Part 2 where we’ll step through the installation and configuration of a test USD environment.