Skip to content

QuickSupport ​

DATAZONE QuickSupport replaces TeamViewer QuickSupport. You use it to help customers whose computer has no Control agent. The customer starts a small file, with no installation and no admin rights. They tell you an ID, and you connect from Control. The customer must confirm every connection.

How it works ​

  1. Under Overview › QuickSupport, click Copy link for customers and send the link to the customer (https://control.datazone.de/quicksupport).
  2. The link detects the customer's system. On Windows they download DATAZONE-QuickSupport.exe and start it (since v3.72.2 the file name carries the company name from the branding instead of "DATAZONE", e.g. medheads-QuickSupport.exe), for Linux and macOS see below. They see a window with a 9-digit ID, e.g. 482 117 903. They can also enter their name.
  3. The customer shows up in the list right away, and a notification appears at the top right. Click Connect, or type the ID into the search (Ctrl+K) and press Enter.
  4. The customer is asked “Name from DATAZONE wants to connect”. You only see the screen after Yes. The customer has 5 minutes; without an answer the request is declined.
  5. During the session a bar at the top of the customer's screen shows who is connected. The customer can end the session at any time with Trennen (disconnect).
  6. After disconnecting, Session ended appears with the button Record in ERP. It opens the session in the QuickSupport journal of the ERP, where the dialog Record activity opens right away, prefilled like in the phone journal: customer, date and time, duration (rounded up to 15 minutes), technician, ticket and the text “Fernwartung computer”. You check and save. With Later, or if the viewer is already closed: the session is in the History tab with Record in ERP, and a notice at the top of the overview reminds you of unrecorded sessions.

When the customer closes the window, the ID becomes invalid at once. If only the connection drops, the ID stays valid for 10 minutes.

On iPhone/iPad you control the QuickSupport session by touch and have an on-screen keyboard, see Remote control: iPhone and iPad.

Several technicians ​

With Join you connect to a customer a colleague is already working on. The customer is asked again. Every technician has their own bar with Trennen on the customer's screen.

Restart with admin rights ​

If something needs admin rights, click Admin rights in the viewer and enter user and password of an admin account (COMPANY\admin for domain accounts, .\Administrator for local accounts). QuickSupport restarts as this user with admin rights:

  • The ID stays the same. You are reconnected automatically, and the customer does not have to agree again.
  • For normal admin accounts Windows shows the prompt “Do you want to allow …” once. The customer confirms it with Yes. You cannot see it because it appears on the protected desktop. The built-in Administrator account skips the prompt.
  • The password only goes to QuickSupport and is neither stored nor logged. The audit log only contains the user name.
  • Only the technician who started the restart reconnects without a new prompt (recognised by their Control user, not by name), and only within the next 5 minutes.
  • From v3.65.13 QuickSupport starts a fresh copy in its own folder under C:\ProgramData that only the customer, administrators and SYSTEM may write to. Before starting it, QuickSupport checks the signature “DATAZONE GmbH”. A file another user of the computer placed there is never started.
  • From v3.69.4 not even malware in the customer's own account can swap the copy: the customer may only read it, and QuickSupport keeps it locked until it has started.

Alternatively the customer clicks Mit Adminrechten neu starten in the window.

Customer detection ​

Control assigns the ID to a customer:

  • via ticket invitation: the customer opened the invitation link from the ERP ticket (see below).
  • same computer in Control: the serial number belongs to a computer with an agent (Windows, Linux or macOS).
  • via ERP asset: If the computer is not in Control, Control asks the ERP for an asset with this serial number. If it belongs to exactly one customer, that customer is assigned and the list shows the link “Open asset in ERP”. Requires the active ERP coupling.
  • by public IP: the public IP belongs to a firewall or computer of exactly one customer.
  • manually: otherwise click Pick customer.

You need the customer for time tracking. Users bound to a customer only see QuickSupport sessions of their customer.

Computer already has an agent ​

Since v3.65.0, Control uses the serial number to detect whether the computer already has an agent in Control (Windows, Linux, macOS). The list then shows Agent: name · online below the computer name. Click it to open the host.

Via agent starts the regular remote control through the installed agent instead of QuickSupport. Whether the customer has to confirm depends on the host or customer setting. The button is greyed out if the agent is offline or too old, or you lack the Remote control permission for the module; the tooltip tells you why.

Invitation from the ERP ticket ​

Since v3.65.0 the ERP creates an invitation link on the ticket:

  1. You send the customer the link from the ticket.
  2. The customer opens it. The page greets them with the contact name, your name and the ticket and offers the QuickSupport download.
  3. If the customer starts QuickSupport from the same network within 2 hours, the ID takes over customer, contact (as display name) and ticket. You get a notification that stays until you dismiss it.
  4. Every connection then carries the ticket, and it ends up in the ERP journal.

If the customer starts QuickSupport from a different network, the notice Invitation opened, no QuickSupport recognised yet appears at the top. Pick the matching ID there. Customer and ticket then also go to connections of this ID that have already ended but are not yet recorded; they are reported to the ERP journal again.

The link is signed with the ERP coupling secret and valid for at most 8 days. A modified or expired link shows a notice; QuickSupport can still be started.

Invitation from a call ​

From v3.69.7 the QuickSupport invitation button also exists in the ERP call list. The link then carries the call. The ERP journal links the connection to that call without guessing.

Without an invitation from the call, the ERP only suggests the matching call when you record the activity: same technician, same customer, close in time. You confirm it or pick another one. If the call already has an activity, you extend it instead of creating a second one. In the ERP, call, activity and QuickSupport journal then show each other.

Chat with the customer ​

From v3.66.0, Chat in the remote-control window of a QuickSupport session opens a chat panel on the right. The customer sees your message in their QuickSupport window and can reply.

  • The chat works as long as QuickSupport is running at the customer, also before or after you are connected.
  • While the chat is closed, the button counts new customer messages. The QuickSupport list shows Chat n at the ID.
  • Your messages show read once the customer has seen them.
  • Text only, up to 2000 characters per message. Enter sends, Shift+Enter adds a new line.
  • The history during a connection is added to the ERP journal.

On the customer's side (QuickSupport 3.69.4 or later):

  • Windows: when you write, a chat window opens next to the QuickSupport window and the taskbar button flashes. If the customer closes it, the Chat button brings it back and shows the number of unread messages.
  • Linux: your message appears in a small dialog with a reply field (zenity or kdialog, otherwise only as a notification).
  • macOS: its own chat window like on Windows (Mac app from 3.69.11).

Older QuickSupport versions do not show the chat.

Take over as agent ​

If the computer should be managed permanently, from v3.66.0 you install the normal Control agent straight from the session:

  1. Click Take over as agent in the remote-control window.
  2. Choose the customer and, if there are any, the site. The customer of the ID is preselected.
  3. Windows (QuickSupport 3.69.4 or later): QuickSupport asks the customer in a separate window ("Set up permanent remote support?", No is preselected; without an answer it counts as No after a few minutes). If they agree, the normal DATAZONE installer starts and Windows asks for administrator rights. The customer sees the progress in a PowerShell window.
  4. Linux, macOS or older QuickSupport: you get the command to run. The easiest way is to type it with Send text into a terminal or an administrator PowerShell.
  5. As soon as the agent checks in, the dialog shows Agent is here and the list shows Agent: name. From then on you connect via the agent.

Good to know:

  • The button only works from your own connected session, so the customer is at the computer.
  • Control shows the command only once. If you open the dialog again later, Create new command creates a new one and the old link becomes invalid (from v3.69.3).
  • Control creates an installer link for exactly this computer: usable once, valid for one day, customer and site fixed. If the customer declines, the link becomes invalid at once.
  • The installer checks the signature (DATAZONE GmbH) of the agent and the updater and stops if it is wrong.
  • You need the right to create installer links for the customer (Manage customers or View onboarding).

History and time tracking ​

The History tab lists all sessions of the last 90 days with customer, technician, duration, billed minutes, activity and ticket. Declined requests are listed there too. If a session was interrupted (e.g. by the restart with admin rights), the record combines all parts into one billing entry.

Journal in the ERP (from 3.61.0, recording in the ERP from 3.62.0): Every finished session automatically goes to the QuickSupport journal of the ERP, declined and interrupted ones too. Recording happens in the ERP: parts of the same ID are combined into one activity, further sessions are attached there via Link to object › Activity, and failed attempts are closed there via right-click Close without billing. Control takes over the state from the ERP: the ERP column in the history shows the activity (e.g. ZE-000123), “no billing” or “not recorded”. If you delete the activity in the ERP, the session counts as unrecorded again. Requires the active ERP coupling.

What QuickSupport can and cannot do ​

WorksDoes not work
Screen, mouse, keyboard, key combinationsCtrl+Alt+Del
Send text, clipboardSeeing UAC prompts and the lock screen (the picture comes back once they are gone)
Several monitors (choice in the viewer; on Windows since v3.70.0 also each monitor in its own window)Access without the customer at the computer
Several technicians at onceFetching files from the computer
Dragging files onto the screen (Windows, since v3.70.0)

Monitor in its own window (Windows, since v3.70.0): the window icon next to the monitor number in the toolbar opens that monitor in a separate browser window, as in agent remote control. The customer is not asked again; QuickSupport checks this itself as well. The second window is not a connection of its own, time is counted by the first. Closing the first window closes the others.

Dragging files onto the screen (Windows, since v3.70.0): drag a file from your explorer onto the picture. It lands on the desktop of the user QuickSupport runs as; if the name exists it becomes "name (2)". Only while your connection is up and the customer agreed. After a restart with admin rights QuickSupport runs as the admin account; it then refuses the file with a note instead of putting it on a desktop the customer does not see. The upload is in the audit log (quicksupport_file).

Both need QuickSupport 3.70.0 at the customer; older copies update themselves on the next start.

UAC prompts and the lock screen run on a protected desktop that a normal program cannot see. If the customer has to change settings with admin rights, they click Mit Adminrechten neu starten (restart with admin rights) in the window. The ID stays the same.

For permanent support, install the normal Control agent, straight from the session with Take over as agent or with an installer link of the customer.

Linux ​

On Linux the customer starts QuickSupport in a terminal as a normal user (not root):

sh
curl -fsSL https://control.datazone.de/api/quicksupport/linux.sh | sh

This downloads the program to ~/.cache/datazone-quicksupport and starts it. The ID appears in a small window (zenity, on KDE without zenity a kdialog window). The screen is shared on X11 and on Wayland (GNOME, KDE). On Wayland the desktop also asks which screen to share; this needs the package gst-plugin-pipewire or gstreamer1.0-pipewire. On Linux there is no name field and no admin rights, and only one technician can be connected at a time. The bottom of the window shows the company name and website from Branding and the server. QuickSupport reports the serial number for customer detection only if the system allows reading it without admin rights (not on many distributions).

macOS ​

On a Mac the customer downloads a ZIP file via the link, opens it and starts DATAZONE QuickSupport. The app is signed by DATAZONE and checked by Apple (notarized). Like on Windows it shows the ID, a name field and the status. As of v3.65.1 it looks like the Windows version: a header band with logo and color from Settings › Branding at the top, and at the bottom the company name with website link and the server it is connected to. It also reports the Mac's serial number for customer detection.

At the first start macOS needs two permissions that only the customer can grant: Screen Recording and Accessibility. QuickSupport opens a window with buttons that lead straight to the right place in System Settings. After granting Screen Recording, macOS offers “Quit & Reopen”; QuickSupport then restarts with a new ID. Without Accessibility the technician can only watch.

On a Mac there are no admin rights via QuickSupport, and only one technician can be connected at a time.

The window shows the logo and colour of the instance at the top. You set both under Settings › Branding (upload logo, primary colour). Use a PNG with a transparent background that reads well on the primary colour (as on the login page). QuickSupport cannot show an SVG logo; if a PNG with the same name lies next to it, it takes that one. Without a logo the company name from Branding is shown. The bottom of the window shows the company name and website from Branding (website as a link) and the server QuickSupport is connected to, e.g. control.datazone.de, so the customer sees who is calling.

The start page (/quicksupport) shows the same logo.

Signature and other instances ​

The Windows file is signed by DATAZONE GmbH (Microsoft Trusted Signing). At start Windows shows the publisher “DATAZONE GmbH” instead of “Unknown publisher”. With new certificates SmartScreen may still ask once during the first days.

There is one Windows file for all Control instances. Which instance it calls is stored in a stamp that the instance puts into the signature on download, as an additional certificate next to the certificate chain. The signature stays valid, also on hardened computers with EnableCertPaddingCheck. DATAZONE signs the stamp per instance with the license key. QuickSupport only accepts stamps with a valid DATAZONE signature; a foreign address cannot be written into it. Without a stamp QuickSupport connects to control.datazone.de.

For a customer instance (e.g. medheads):

  1. DATAZONE creates the stamp: python scripts/license_generator.py qs-stamp --server https://control.customer.com (the address from the instance setting base_url).
  2. An admin of the instance opens Overview › QuickSupport › Stamp and pastes the line. Control checks the signature and that the address matches the instance.

A stamp is valid for 2 years. 60 days before expiry the instance shows admins a notice; DATAZONE then creates a new one. QuickSupport no longer accepts expired stamps. This way nobody can later take over the address of an abandoned instance and redirect a signed DATAZONE file to themselves.

As long as a customer instance has no valid stamp, it does not offer the Windows file and, from v3.65.13, the Linux file either, and admins see a notice at the top. On Linux the instance appends the stamp to the file at download. On Windows, Linux and macOS QuickSupport only accepts an address given with -server when it matches the stamp (without a stamp: control.datazone.de), so the signed file cannot be redirected to a foreign server via the command line either. The Mac app has no stamp yet and always connects to control.datazone.de.

Updates ​

At start, QuickSupport asks Control for a newer version. If there is one, it downloads it, checks the checksum and, from v3.65.13, the DATAZONE signature (Windows: publisher “DATAZONE GmbH”, macOS: Apple signature of the DATAZONE team, Linux: DATAZONE signature with the license key), and only then replaces itself. An update without a valid signature is discarded and the existing version keeps running, so an old copy on the desktop stays current. If the server does not answer within 5 seconds, the existing version starts.

Permissions and audit ​

  • Permission QuickSupport (quicksupport.use): see the list and connect. It is part of the roles Operator and Support. Two-factor sign-in is required.
  • Connecting, session end, customer assignment, time tracking and "Take over as agent" are written to the audit log. Chat messages are not in the audit log but in the history of the ID and in the ERP journal.

DATAZONE Control Documentation