Home Assistant & displays
Your automations, aware.
Turn meeting, microphone or screen-sharing status into a trigger for your setup. From a hallway light to a desk dashboard, you decide what happens.
Your Teams tools. Still connected.
Teams changed.
Keep your setup.
Microsoft switched off the local connection your tools relied on. Call State brings it back for compatible tools. Teams Emulation reconnects your existing setup. Live status keeps your lights, dashboards and scripts in sync — from your microphone to your screen share.
Mac & Windows No credit card 7-day Paid trial
Your status. Not your conversation. No Microsoft login or Microsoft sign-in keys. No bot in your meeting. Call State reads only the button states in your Teams window. How your data is handled
Old setup or a fresh start — both have a place.
Teams Emulation, live status, CLI and REST are all part of Free. Paid only removes the daily sign-in.
Your status. Six signals.
Call StateDemo
Microsoft Teams Work laptop
In a call
Mic muted. Camera on. Your tools know.
SHARE
REC Not recording
CHAT Pane open
Try Mic, Cam or Hand. Choose Presenting to explore the other signals.
Share, Rec & Chat are status readouts here. Chat means pane open, not unread messages or chat content.
Interactive demo · simulated signals, not your actual status.
Connect
One status.
Plenty of possibilities.
Call State lives in your menu bar or system tray. It senses your Teams meeting, sends every change to the tools you choose — and takes commands back.
One account can connect several computers. Your active call stays in view. Teams on a remote desktop?
Microsoft TeamsDesktop app on Mac or Windows
Call StateMenu bar & tray
Home Assistant
Lights and scenes that follow your call.
USB Beacon
A light you build yourself with ESPHome.
Deck tools
Existing third-party Stream Deck and Touch Portal tools, through Teams Emulation.
CLI
Status and commands in your terminal.
REST
Your own integration on the Call State API.
Remote & virtual desktops
Teams runs elsewhere?
Control it from your desk.
Remote desktop, Citrix or a virtual desktop: run Call State next to Teams there and on your own computer. Your deck, Beacon and lights stay where you sit.
Remote or virtual desktop · shows you the screen
Your computer
The computer in front of you
- Call State app
- Deck
- Beacon
- CLI
Call State service
Your account
Remote computer
Remote or virtual desktop
- Call State app
- Microsoft Teams In a call
- You press mute at your desk. A deck button, your Beacon or the CLI on your own computer.
- The service finds your call. It sends the command to the computer that is in the meeting.
- Teams mutes over there. Call State on the remote computer presses the button. The new status comes back to both computers.
Built for the setup you built
Keep the useful parts.
Connect what comes next.
Home Assistant automations. Deck buttons. Your own scripts. Give your tools more than an “in a call” light — and send commands back.
Compatible deck tools
Keep your muscle memory.
Give compatible Stream Deck or Touch Portal tools their familiar Teams connection back. Mute, camera and hand controls stay part of your workflow.
CLI & REST
Build beyond the button.
Read status from your terminal or connect your own tools. Use one Call State account across your computers, and keep your active call in view.
Reconnect. Then get back to it.
A new connection.
A familiar workflow.
Keep the controls and automations you know. Call State supplies the meeting signals; your setup decides what to do with them.
Find your downloadInstall and sign in.
Install Call State and complete the permissions setup. The one broad permission it needs cannot be limited to a single program; Call State uses it only for the buttons in your Teams window. No Microsoft login is involved. A 7-day Paid trial is included.
Reconnect or build something new.
Enable Teams Emulation for compatible existing tools. Or connect your own automation using the status and control features.
Put it through a real call.
Check your status light, try your mute button and verify the features your tool needs. Then keep working the way you like.
Clear about your data
What leaves
your computer.
Not a Microsoft product, not inside your meeting. Call State reads button states in Teams and sends only small status data — never your content.
No Microsoft access
Call State never asks for a Microsoft login and never uses Microsoft sign-in keys. It is an independent tool and never signs in to Teams for you.
Not in the meeting
Call State does not join your call. Other people do not see it in the participant list, and it cannot hear or record anything.
Buttons, not content
Each button has a fixed name that Teams gives it, like “Unmute mic”. Call State reads that name and whether the button is on or off — never anything of yours: no text, messages, documents or pictures.
- Your Teams windowButtons and their state
- Call State appReads button states
- Call State serviceReadable to the service, no history kept
- Your devicesSigned in to your account
Never leaves your computer
- Meeting audio and video
- Your screen and anything you share
- Chat messages, files and attachments
- Transcripts and recordings
- Your calendar and your contacts
- Your Microsoft account and any Microsoft sign-in keys
Leaves your computer (small status data only)
- Whether you are in a meeting
- Muted, camera on, hand raised
- Sharing active, chat pane open, participant list open, recording indicator active
- When the current call started and when the status was last read
- Whether a control such as the mute button can be used right now
- A random device id (new on every start) and the name of your computer
Separately, your account stores your email, a value from your password and billing details — card details go only to Stripe. More questions about your data
A new connection for a familiar setup
Teams moved on.
Your tools can come along.
Microsoft retired the local connection many Teams tools relied on. Call State does not need it: it reads the state of the buttons in your Teams window, with no Microsoft login and no Microsoft sign-in keys. For compatible tools it can also provide a replacement connection.
See what changedMeet Teams Emulation.
A familiar connection for tools built around the retired Teams API. Keep the parts of your setup you love, without starting from scratch.
Try it with your setup in a real call
A small tool. A fair price.
Start free.
Keep your options open.
Everything is included in Free. Paid only removes the daily sign-in.
| Free €0/ always free Your own account. No credit card required. | Paid €12/ year €1 per month, billed yearly. Or €1.50 monthly. | |
|---|---|---|
| Desktop app for Mac & Windows | Included | Included |
| Live meeting, microphone & camera status | Included | Included |
| Commands and custom automations | Included | Included |
| CLI and REST access | Included | Included |
| Sign-in | Every 24 hours | No daily sign-in |
| Teams Emulation for compatible legacy tools | Included | Included |
| Billing | None | Monthly or yearly. Cancel anytime. |
| Get started free | Try 7 days of Paid |
Free accounts without any paid subscription are deleted after 30 days of inactivity. Accounts that ever paid are deactivated instead, so their invoices stay available.
Every new account includes 7 days of Paid. No card needed. After that, continue on Free unless you choose a subscription.
Good to know
A few things
you might be wondering.
Clear expectations make for a better setup.
Does Call State use my Microsoft account or Microsoft sign-in keys?
No. Call State never asks for a Microsoft login and never receives, stores or uses Microsoft access or refresh tokens — the short-lived keys an app uses to stay signed in. It is an independent tool, not affiliated with Microsoft, and never signs in to Teams for you. You sign in with your Call State email and password only. See what leaves your computer.
Why does the permission sound like it can read my screen?
Because the permission is broad: your operating system cannot limit it to one program. Call State uses it only to read the buttons in your Teams window — not to read other programs, and not to read your screen contents. You can take it away in your system settings; the app then cannot show your Teams status. See what leaves your computer.
Does Call State listen to my meetings?
No. Call State does not join your meetings, so it cannot hear or record anything. It does not record audio or video, take screenshots, read your screen, messages, files or documents, or create transcripts. It does not read your calendar or contacts either. It reads only the fixed names and on/off states of the buttons in your Teams window. See what leaves your computer.
What does Call State store about me?
Your account holds your email address, a value made from your password — never the password itself in readable form — and plan and billing details. The keys that keep you signed in are Call State’s own and stay in the password safe of your operating system. Payments run through Stripe: you type your card details on the Stripe payment page, they go straight to Stripe, and Call State never sees them.
Can Call State see my status?
Your status travels through the Call State service so your other devices can show it. The service handles it in readable form, protected on the way by the same encryption as any secure website. It is not a setup where only you can read it. The service only passes it on: no stored status, no history, no sale, no advertising. Only clients signed in to your account receive it.
Will my existing Teams tools work?
Not automatically. Your tool must support the retired local Teams connection, and compatibility depends on the features it uses. Test your own setup with Teams Emulation before you rely on it. The compatibility guide explains the retired API and the replacement.
What do I need to use it?
Start with the desktop app for Mac or Windows, Microsoft Teams and a Call State account. No Microsoft login is involved. Complete the permissions setup and connect your chosen display or automation. Status sharing and commands require a working connection to the Call State service.
Can I show my status on a tablet or second screen?
Yes. On Air is a free full-screen web display for your account. Sign in at onair.callstate.app with the same Call State account and the display starts. Live status needs the desktop app running, so keep it connected. The On Air guide covers the setup.
Are dedicated Stream Deck and Touch Portal plugins available?
Stream Deck: yes. The free Call State Stream Deck plugin is available for macOS and Windows with Stream Deck software 7.1 or newer, and it covers keypads and the Stream Deck + dial. Read the Stream Deck guide. Touch Portal: yes. The free Call State Touch Portal plugin runs on macOS (Apple silicon and Intel) and on Windows (x64 and arm64). Read the Touch Portal guide. Compatible third-party deck tools keep their path through Teams Emulation.
Are browser extensions available?
Browser extensions are planned, not available yet. Chrome and Edge are the first browser targets; Firefox and Safari remain under consideration. The desktop app is the starting point today.
Can I always control my microphone remotely?
Controls depend on a reachable Teams meeting interface. A blocking dialog, a minimized meeting window or missing permissions can prevent an action. Call State cannot guarantee control when Teams makes the relevant button unavailable. In the status data, “whether a control can be used right now” tells you whether the button can be pressed at this moment; if it cannot, Call State refuses the action instead of pretending it worked.
What happens after the free trial?
You move to Free unless you choose a paid subscription. The desktop app, CLI, REST and Teams Emulation remain available; the daily sign-in resumes. Free accounts without any paid subscription are deleted after 30 days without use; accounts that ever paid are deactivated instead, so their invoices stay available.