There are a number of ways to mitigate this risk with Rescue: 

Company Pin Code Validation 

To address this problem, you can utilize a feature called company pin code validation. This feature locks pin codes only to one approved site, such as your support page. If a malicious actor were to give your employee or customer their Rescue pin code, and they were to enter that code onto your support site, Rescue would block the connection.   

Calling Card 

In internal IT cases, and some customer support cases, you might not have full unattended access on your end users devices, but you can have them install a calling card, which serves as a shortcut for direct support, without needing an additional download. These can work either by allowing users to fill out information and request support directly from the calling card, or by letting them enter a pin code provided by an agent, and can be customized to your specific branding. Should you use the pin code method, you can restrict the calling card to only support pins from your organization.  

How do these help? 

In the scenario from before, if the user went to enter the scammer’s pin either on your website or in the calling card, the code would be rejected since it didn’t come from you. If you are dealing with employees, you can also block the generic logmein123.com website, so they can only request help from your self-hosted support page or calling card.