Skip to main content

ScreenMeet Remote Support Tool for Dynamics 365 Customer Service



I met Lou Guercia when he was president and CEO of Scribe Software, the leading CRM integration tool.  Scribe was acquired by TIBCO Software in 2018.  I recently reconnected with Lou and learned about ScreenMeet, the company he joined as chief operating officer.   The following is a description of the product provided by ScreenMeet:

ScreenMeet is a cloud-based remote support tool designed to integrate with Dynamics 365 Customer Service. By enabling customer service and IT support organizations to address critical technical issues directly from their CRM or ticketing platform, it streamlines the process and provides a fully browser-based support experience.

You can also use ScreenMeet with other CRM products or even on its own without a CRM.

Here is a short video demo of ScreenMeet with Dynamics integration:


ScreenMeet - Cloud-based Remote Support Integrated with Dynamics 365 Customer Support

Once integrated with a Dynamics 365 CS organization, the ScreenMeet widget appears on Case pages. It allows you to create and launch remote support sessions from the same location as the support agent’s CRM and ticketing platform. In addition, ScreenMeet captures a robust set of data from support sessions and stores it within the Dynamics Case object for use with auditing & analytics to improve support processes and self service initiatives.


ScreenMeet is 100% browser-based for the agent; after the end user connects to the session, the agent is prompted to join via a new tab. The following screen capture is of the viewer window with the associate suite of support tools:


These tools enable the support agent to solve the end user’s issue quickly and effectively. Some key features include:

     Cross-platform support from all modern browsers
     Permission-based escalation of agent privileges
     Local and domain-level Windows admin (UAC) escalation
     Windows and Mac tools & shortcuts
     Multi-agent URL invites
     Bidirectional file transfer
     Remote clipboard
     Reboot and reconnect
     Low bandwidth mode

The above is an example of one key feature, the Windows Tools menu, which agents can use to perform actions on the end user device directly. It also has a built-in search functionality, so you can find the relevant shortcut and execute it without digging through the UI or the end user’s system.

ScreenMeet Cobrowse and Dynamics Omni-Channel

Screenmeet also offers a no-download solution for ecommerce and B2B browser-based support use cases. It will enable you to guide your end user through site navigation - for example, completing purchases from the shopping cart. Cobrowse sessions can be launched from the Dynamics Omni-Channel workflow.


Once connected, the agent can guide the end user through site navigation similarly to the support solution--all from the browser!

Support Sessions: Records and Reports

After a support agent creates and completes a session, a new record is generated. This record tracks agent/user connection and disconnection, all mid-session actions taken by the agent via the ScreenMeet support tool suite and the system info retrieved from the end user’s device.


In turn, this data can be leveraged to create reports using Dynamics’ native reporting features to gain insights on key benchmarks--session activity by month, for example:

Conclusion

Combined with the Dynamics 365 Customer Service, ScreenMeet provides an integrated support and ticketing solution with a similar, case-based workflow. Feel free to trial ScreenMeet Remote Support on AppSource.

You can learn more about ScreenMeet’s solution and capabilities at a webinar on January 28th at 11:00am PST. Link to webinar registration available here.

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan