AnyDesk Integrator

Manufacturer: NorthCom Technologies
The ultimate tool for any company that provides remote services through AnyDesk & Softone
SKU: NC-SW-003
i h


The AnyDesk integrator was implemented in order to properly monitor the remote sessions we provide to our customers.

We built an Outprocess program with a combination of Custom S1 Objects and managed without any "human" monitoring to record all the sessions of our typists - Technicians inside the softone.

AnyDesk installed on the client and on us with a Professional license is required. (very low value compared to other competing programs).

The technician-machinist, through the customers' view, connects to any of the customer's PCs with one click and as soon as he is finished writes the comments of the session online, outProcess undertakes to inform SoftOne about the duration and purpose of the session.

It provides contracts, time charges, complete control of the technicians' time, informs the client by email about each session and the total time spent and much more..

Description of use ..

After installing the application a new menu will be added.

In the client's view we register all the AnyDesk Ids belonging to the client with a description that will characterize his terminal. e.g. Server, Billing, etc Next to the ID there are three dots where they act as a button to create a session with the client's terminal.


When the session with the customer ends, anydesk will ask the user to describe the services he offered, in this description the technician can use special tags that can characterize the services in particular.

1) When the description starts with numbers e.g.x. [1, antivirus installation ] means the technician with id=1 did this task, if the description does not start with a number the integrator will look to find the technician id from the table of support points or the AnyDesk id from Computer connected.

2) ~ Means that the session will be held for review by the administrator or that the session will be a part of some future ones. e.g. we had to log out and log back in later after maybe a restart.

3) # Means that the client will not be charged for this session.

4) {xx} where xx is the time we will charge in minutes.

5) If there is no description, the session is left for review.

The application is designed to support various billing models, the user can create "Contracts" templates and link them to the customer.

The two basic models are

1) with a negative charge, i.e. the client pre-purchases time and with our sessions we subtract this time from him.

2) with positive billing, i.e. the client does not pre-purchase any time, we simply add the time we supported him to each session and at the end of a period of time we catch all the sessions and charge him in total. (we usually call it indefinite)



In the image above we give the necessary parameters to the billing model [indefinite time] .

Specifically, for the first 30 seconds the customer will not be charged anything and until he reaches the first 10 minutes we will deduct or add 10 minutes (depending on which model we choose later), at the threshold of 11 minutes we will deduct or add only 10 minutes and after 20 minutes they will be subtracted or added in 10 minute increments

00:00 - 00:30 = No charge

00:31 - 09:59 = 10 minutes

11:00 - 19:59 = 20 minutes

20:00 - 29:59 = 30 minutes

Below we see the template from the email that will reach the client at the end of the session

* To avoid multiple emails being sent, we have a timer that we set (e.g. every hour), it will try to send the messages en masse, so if we connect to a customer more than once within this period, we will send him an email with all of the sessions.



The template is highly parametric, with the possibility to inform the client (me tokens %xxxx%) about the time consumed, the total sessions, total time, how much was charged for the specific session and in the event that the time runs out to inform him to choose a new contract etc.


In the image below we see how we connect the contract with the customer.

We define the duration, the pre-purchase hours (if it concerns a pre-purchase model), we can also designate a subcontractor partner so that he can also inform his client of the sessions we will provide.

Positive session charge if YES Indefinite contract.

Positive charge for sessions if NOT Contract with pre-purchase.

Below we see the list of sessions that are automatically updated by the integrator.


and each one in detail.

Below we see the detailed description of the session,


  • Which technician connected
  • On which client and on which terminal
  • Inception
  • Expiry
  • Duration
  • With which contract will he calculate the charge
  • the amount of the charge
  • the document with which we billed the session
  • the comments of the technician
  • List of all sessions you may be taking part in e.g. a series of sessions to be billed as one.

  • No charge = session closed with # in comments
  • Changes have been made = we made changes to the session and if it is up for review the next time the integrator checks it will re-evaluate it. e.g. will charge and email
  • Active session = session is in progress no changes allowed
    With the following task we automatically create the documents for the open-ended contracts

Some images from outProcess



Product tags