Channels & Messaging
Drive your CAD workstation from Microsoft Teams, WhatsApp or Telegram — from the shop floor, a customer meeting, or the train home. Every request runs on your own PC, with the AI you chose there, exactly as if you had typed it into the SphereHarness chat.
Do my messages go through SphereHarness?
- Microsoft Teams: your messages to the SphereHarness Teams app are relayed through SphereHarness to your own PC, and the answers back; they are never stored — no message, answer, picture or file is written to our database, our disk or our logs. We keep only the link between your Teams account and your SphereHarness account.
- Microsoft Copilot: when you connect a Copilot agent to SphereHarness, the requests Copilot sends for you are relayed through SphereHarness to your own PC, and the results back; they are never stored — no request, result, picture or file is written to our database, our disk or our logs. We keep only your sign-in for that connection, which you can revoke. See Use SphereHarness from Microsoft Copilot.
- WhatsApp: you use your own Twilio number. Each message is passed through SphereHarness, unchanged, to your PC (or your organisation’s server) and is never stored. Your Twilio auth token never leaves your PC or your organisation’s server, and we keep no phone number. (WhatsApp paired with your own phone by QR code goes straight to your PC.)
- Telegram: your own bot talks to your PC or to your organisation’s server; nothing passes through SphereHarness.
Unless you choose the optional SphereHarness server AI, SphereHarness runs no AI on its servers. Details: privacy policy, section 11 and What goes where.
The three channels at a glance
| Microsoft Teams | Telegram | ||
|---|---|---|---|
| What you use | The SphereHarness Teams app, one app for everybody | Your own Twilio account and number, or your own phone by QR code | Your own bot from @BotFather |
| Who sets it up | Your Teams admin adds the app once (or you sideload it where allowed); each person switches it on in the agent | You (just me) or the tenant administrator (company number) | You (just me) or the tenant administrator (company bot) |
| How a message reaches the PC | Microsoft → SphereHarness server (relay, memory only) → your PC | Twilio → your permanent SphereHarness relay address → your PC or your organisation server, unchanged | Your PC or the organisation server fetches it from Telegram |
| Port, tunnel or public address on your PC | None | ||
Teams: the SphereHarness Teams app
Every person uses the same SphereHarness Teams app. Your Teams administrator uploads the app package once (it is not in the Teams Store), you sign in to the agent with the same e-mail as your Microsoft work sign-in, turn on Settings → Channels → Microsoft Teams via SphereHarness, message the app, and click Allow when your PC asks. With several PCs, /pc chooses which one answers. Your own Azure Bot for Teams is not offered any more. Everything: Microsoft Teams: the SphereHarness app.
WhatsApp and Telegram: two modes
For WhatsApp and Telegram the channel setup dialog asks first: “Who is this for?” — Organisation - one bot for everyone, run on our organisation server or Just me.
| Organisation | Just me (personal) | |
|---|---|---|
| What | ONE company number / bot for everyone, on your company's own organisation server | Your OWN number / bot, to YOUR PC |
| Who sets it up | The tenant administrator, once | You, on your PC |
| How a message reaches a PC | WhatsApp: Twilio → the SphereHarness relay address → the organisation server, over a connection it opens out to SphereHarness. Telegram: the organisation server fetches it. The server checks it, finds the sender's paired PC and keeps it until that PC collects it | WhatsApp (Twilio): Twilio → your SphereHarness relay address → your PC. WhatsApp (QR) and Telegram: your PC connects out itself |
| Inbound port on a member's PC | None — no port, no firewall rule, no tunnel | |
| Who may send | Each person, only to their own PC, after proof (a pairing code) | Only you: your own id; everyone (*) is refused |
| Where the secret lives | On the organisation server only, encrypted | On your PC only, encrypted for your Windows user |
Which one do I need?
- Your company has an organisation server and the admin set up a company number / bot → Organisation. You install nothing; pair once from Settings → Organisation.
- You are the admin and several people should use it → Organisation.
- You are on your own, or your company has no organisation server → Just me.
- Quickest to try: Telegram Just me — a bot from @BotFather in two minutes, no address, no cost.
How the company number / bot reaches the right PC
- The tenant administrator connects the company number / bot to the organisation server once.
- Each enrolled PC registers itself and waits for its own messages. Settings → Organisation → Company channels shows a pairing code (6 characters, 15 minutes, 5 tries; one code serves both channels): “Send ABC123 to +number on WhatsApp”, “
/start ABC123to @bot in Telegram”. - You send the code. It arrives with your real WhatsApp / Telegram identity (checked with Twilio's signature and the company token, or the server's own Telegram connection), and the server binds that identity to your PC: “Connected: your messages now reach PcName.”
- From then on your messages run on your PC only. Nobody else's PC ever receives them.
| The company number / bot says | Meaning |
|---|---|
| “Open Settings → Organisation on your SphereHarness PC and send me the code shown there.” | Not paired yet |
| “That code is not valid - open Settings → Organisation on your PC for a fresh one.” | Expired or mistyped |
| “Too many wrong codes - wait 15 minutes, then send the code shown in Settings → Organisation on your PC.” | Five wrong codes within 15 minutes: even the right code is refused until they are over |
| “Paired with PcName: your administrator approves the connection, then your messages reach it.” | Approval is on: paired, waiting for Approve |
| “Your connection to PcName is waiting for your administrator's approval - your message was not sent.” | A message sent before the approval |
| “Your connection to PcName was disabled by your administrator - your message was not sent. Ask your administrator.” | The administrator disabled your route |
| It says you use your own number / bot on PcName | That PC runs your own WhatsApp / Telegram for the channel (“Just me”): message your own |
| “Your PC NAME is not reachable right now (last seen when). Start SphereHarness on it and send your message again.” | Your PC is off, or SphereHarness is not running on it |
| “Your organisation's SphereHarness server is not connected right now. Please try again later.” | Company WhatsApp number only: the organisation server is not connected to SphereHarness |
| The organisation server's licence has expired | See the licence |
Pairing from a second PC moves you to that PC; the first one's route is disabled. An administrator can require that every pairing is approved before messages flow: Settings → Organisation, signed in as administrator → Company channel connections lists each PC with Approve, Disable and Enable. Each is a licensed change and shows in the block's Audit list.
Organisation and personal on one PC
- One binding per channel per PC: a channel on a PC is the company number / bot or your own, never both at once.
- Organisation first: when the PC is enrolled and the organisation set up a channel, the dialog opens on Organisation for it.
- Personal is still allowed unless the administrator switched it off.
- Not enrolled → only Just me (“enrol in Settings → Organisation first”).
The licence
Teams via SphereHarness and personal WhatsApp / Telegram work for any SphereHarness account with an active licence or trial. The Tenant Admin licence gates the company channels on the organisation server: changing a company channel and approving a pairing are licensed writes, and delivering messages and pairing need an active (or expiring) licence. When it has expired, a message to the company number / bot gets a reply naming the expired licence, and nothing is lost: every pairing is kept.
What the AI does for you — and what only you do
Ask the chat “set up Teams” (or WhatsApp / Telegram). The assistant opens the channel setup dialog (open_channel_setup), drives the Twilio Console with the browser tools where it can, and saves with channel_setup_save (channel and mode, never a secret) behind one approval card that only a person can allow.
The channels
- Microsoft Teams — the SphereHarness Teams app: your Teams admin adds it, you connect once. Needs a work or school account.
- Microsoft Copilot — add the SphereHarness address to your Copilot agent and sign in once; Copilot asks, your own PC does the CAD work.
- WhatsApp — the company Twilio number, or just me (your own Twilio number, or your own phone by QR code).
- Telegram — the company bot or just me. No address needed, no cost.
- Slack — your own Slack app over Socket Mode, just for you. No address needed, no cost.
What a reply can contain on each channel
- Telegram — plain text, 4,000-character parts. Screenshots arrive as photos; other files as documents, up to 50 MB.
- Slack — plain text, parts under 4,000 characters; direct messages and @mentions only. Files are not sent yet (the reply says so).
- Microsoft Teams — bold, simple lists and links; a status line names the PC that works. A small picture (up to 80 KB) is shown inline; larger pictures and other files come as a one-hour link. In channels and group chats only messages that @mention the app are read; it routes by the sender.
- WhatsApp — plain text in 1,500-character parts. Through Twilio a screenshot comes as a one-hour link; the QR path sends text only; pictures sent from the phone are not read.
Rules for every channel
- The desktop agent must be running on the PC that does the work.
- One Telegram bot, one poller. A bot token is fetched by ONE place only — your PC or the organisation server. A second place gets
409 Conflictand messages go missing.
With a coding agent on your own account
When the chat on your PC is answered by a coding agent (Claude Code, Codex, Gemini CLI…) signed in with your own account and no API key is set for it, SphereHarness treats it as your personal subscription: Telegram, WhatsApp and Slack are not started (a running one stops when the chat switches to such an agent) unless you turn on Allow Telegram, WhatsApp and Slack with my coding agent (at my own risk) in Settings → Channels. Teams keeps running for the account holder only: SphereHarness delivers only the messages of the Teams account linked to you and allowed on this PC. With an API key nothing changes.
While Telegram or WhatsApp is held off this way, the channel setup dialog (and the Organisation page's channel block and the status window) says so in words — “Telegram cannot start on this PC: your chat is answered by … on your own account (no API key) …” — with two buttons, Use your own API key (Settings → Coding agents & MCP → API model) and Allow at my own risk (Settings → Channels). Saving still stores your setup, but nothing says “starting” and no pairing code is issued until the channel can start.
Security
- Every message is checked: Teams by Microsoft's Bot Framework token on the SphereHarness server; WhatsApp by Twilio's
X-Twilio-Signatureon your PC or organisation server, with your token (SphereHarness never has it); Telegram because the bot is fetched by its one owner. - Teams: a message is delivered only to a PC signed in as the SphereHarness user the Teams account is linked to, and runs only after Allow on that PC.
- Organisation mode: a PC receives only messages from identities it proved. The company secrets exist once, on the organisation server, encrypted. Member PCs listen on no port.
- Nothing stored: relayed Teams and WhatsApp messages live in the SphereHarness server's memory only while they are handed over; a larger picture or file waits in memory for at most one hour. Nothing is written to a database, a disk or a log. Where every kind of data goes: What goes where.