Splashtop SOS in TATER Ops

Start an attended support handoff from a TATER Ops device record.

TATER can create an attended Splashtop SOS support session from a device’s Ops detail panel. Splashtop handles the remote session; TATER creates the handoff and records who created it and which endpoint it concerns.

Plan and API requirements

Splashtop’s general Open API is documented for Enterprise. Splashtop SOS team settings also list third-party integration keys for Enterprise and SOS+ Attended Access. Confirm your subscription includes SOS third-party integration before setting this up. The technician API token needs permission to read account information and create PSA support sessions. Do not use a read-only token for session creation.

Configure the connection

  1. In Splashtop, create an API token with the minimum account and PSA permissions needed for the connection.
  2. In TATER Manage, open Connections → Integrations → Splashtop SOS.
  3. Select the Splashtop account region and enter the API token. Team ID and SOS channel ID are optional overrides; TATER discovers the team and uses the first available SOS channel when those fields are blank. The token is encrypted at rest and is never returned to the browser after saving.
  4. Save the connector and run Test connection. TATER verifies the account API, channel list, and session-log access. The API token needs both psa (create SOS session) and logs (refresh status and retrieve file-transfer logs) permissions, in addition to account lookup.

Start an attended session

  1. In Ops, open a device detail panel and select Splashtop SOS.
  2. Enter the end user’s name and a short issue description. TATER creates a Splashtop support session tied to the configured channel.
  3. Share the returned SOS download link with the end user. The user runs the SOS app; when Splashtop returns a 9-digit code, the TATER session dialog also offers Connect in Splashtop Business, which opens the signed-in technician app with the code filled in. The technician still has to start the connection in that app.

TATER records the operator and endpoint, and keeps the Splashtop session reference in a tenant- and organization-scoped session history. It does not store the SOS code or download URL. Use Refresh status & logs to pull session details and file-transfer entries after the endpoint starts or the session ends; the refresh is also recorded in the device change history.

This follows Splashtop’s documented help-desk flow: create a session/download link, have the end user run SOS, then let the technician connect from the Splashtop Business app. The Business app is required on the technician computer.

Deploy the persistent Streamer

Attended SOS support and unattended Streamer access are separate workflows. To make an endpoint available for unattended access, use Splashtop’s deployable Streamer package and TATER Manage → Endpoint Health → Software Deploy. The Windows preset uses MSI silent-install options; the macOS preset mounts the team-specific DMG and installs its bundled PKG. Both presets include SHA-256 values for the supplied Streamer 3.8.6.3 installers. Add an HTTPS download URL the endpoints can reach before saving the package. Your Splashtop subscription must include unattended endpoint seats.

Limits