The DT Client runs on each users PC and provides a single unified CRM + Phone interface for the user. The client contains browser with CRM, telephony toolbar and necessary connections to CRM (Dataverse SDK) and Phone System (various telephony APIs, see below)

The DT Client is installed using ClickOnce technology from Microsoft. This means the client is installed simply from a URL. Once installed, the client automatically updates in background from our install servers. This way, we have the advantage of SaaS but the performance of locally installed applications.

We can also provide an MSI based install if you prefer.

For organizations requiring complete control, an on-site licensing server can be provided.

Licensing is controlled from our servers too. However, the licensing server can be uncontactable for a configurable number of days without affecting the client. This means that network outages and the like will not prevent the DT Client from functioning.

For SIP based systems, Asterisk and FreePBX, the DT Client includes a built-in softphone. Users use this via a headset on their PC. For Genesys, TAPI, Cisco (Finesse) or Avaya (CCT or TAPI), you use your normal deskphone or softphone provided by the phone system

Architecture Notes

During normal operation, the DT Client does not communicate with our servers. The client only communicates with Dynamics 365 and the phone system.

The Dynamics Telephony system does not require any server, local or remote, for operation. All settings and required data are stored in your own Dynamics 365 CRM. So all data is in your own Dynamics 365. None of your data is sent to our servers.

Our install servers are located in Ireland. You have the option of deploying an install server in your own infrastructure. Our licensing server is in The Netherlands.

The DT Client is fully compatible with the resiliency features of CRM and the various phone systems. This is usually via a single managed address for CRM and one for phone system.