Skip to content
Console

Connect a Client

Use this page when you are ready to connect one app, device, browser flow, or Thalovant Voice room client to a hub.

The smooth path is simple: create the connection, open the setup link, let the client pair once, then wait for Dashboard to show the first heartbeat.

  • you clicked Add connection and need the next step;
  • you need to set up Thalovant Voice on macOS, Windows, or Linux;
  • a setup link expired or did not open the client;
  • you are choosing between Voice, Web chat, Developer, or Embedded setup;
  • you want the no-manual-file path for the first connection.
QuestionSimple answer
Where do I start?Open Connections, then choose Add connection.
What should I choose first?Pick the connection type before the hub and access details.
What does the setup link do?It lets one client claim its identity once.
What is easiest for voice?Use Thalovant Voice and let the setup page handle pairing.
What should stay private?Setup links, connection files, and any copied commands with a setup link.

Confirm:

  • the hub you want this connection to use;
  • the type of connection you are creating;
  • a name that describes the app, room, device, or purpose;
  • whether the client only needs questions, status, or broader access.

If Add connection is locked, open Billing and Plans before changing setup. Limits are separate from pairing problems.

If you want the page that explains the Connections list, setup material, and common states, open Connections.

Voice client

Best for rooms, kiosks, and assistants that listen and speak through Thalovant Voice.

Web chat

Best for browser conversations without installing a desktop app.

Developer client

Best for CLI, API, diagnostics, automation, or local testing.

Embedded client

Best for hardware, firmware, and small-device provisioning.

  1. Open Connections. Choose Add connection.
  2. Choose the type. Start with Voice client unless another surface clearly fits.
  3. Choose the hub. Attach the connection to the hub it should use.
  4. Name the connection. Use a name like frontdesk-voice, demo-chat, or lab-device.
  5. Choose access. Keep the recommended narrow behavior unless this client needs more.
  6. Create the connection. Thalovant prepares a secure one-time setup link.
  7. Open setup. Follow the setup page until it shows connected.

For Voice clients, the setup page opens the easiest path for the computer you are using.

PlatformWhat the page offersWhat happens next
macOSDownload Thalovant Voice for macOS.Install the app, then open Thalovant Voice from the setup page.
WindowsDownload Thalovant Voice for Windows.Run the setup app, then open Thalovant Voice from the setup page.
LinuxCopy the Linux install command.Paste it in Terminal once to install, pair, and start the voice runtime.
SSH-only LinuxCopy the headless command from advanced options.Paste it over SSH with the setup link included.

Thalovant Voice has two runtime choices:

  • Satellite is the normal voice client for rooms, kiosks, and assistants.
  • Relay is a lighter advanced mode for deployments that need a relay runtime.

Keep the setup page open while pairing. It refreshes while the client claims the link and waits for the first heartbeat.

For platform-specific install steps, see Install Thalovant Voice.

Web chat, Developer, and Embedded connections use the same secure setup idea, but the target client owns the final handoff.

  1. Open the setup link if the target client can claim it directly.
  2. Copy the setup link when the client, browser surface, or provisioning tool needs it pasted.
  3. Keep the link private. A setup link can claim one identity and expires.
  4. Create a new link if the old one expired, was shared, or was already used.

Most first setups should use the setup link. It avoids manual file handling.

Some developer, embedded, or recovery paths may still ask for a private connection file. Treat that file like a password. Place it only with the client that needs it, and recreate the connection if the file is exposed.

If your team says “config file”, they usually mean the private connection file.

SymptomFirst check
Setup link expiredOpen Connections, select the connection, and create a new setup link.
Nothing opens after clicking Thalovant VoiceInstall Thalovant Voice, then use Open Thalovant Voice again.
Linux command was copied but nothing connectedPaste the full command once in Terminal and keep the setup page open.
Client claimed but is not connectedKeep the app running until the first heartbeat arrives.
Connection is still offlineOpen Clients and Connections and check hub, state, access, and live status.

The connection is ready when:

  • the setup link has been claimed by the intended client;
  • Thalovant Voice or the target client is running;
  • Dashboard shows the expected connection count or status;
  • Live Map shows the expected live state when live status is available;
  • permissions match what this connection should be allowed to do.

After one connection is live, review its access before adding another one.

Review permissions Install Thalovant Voice