How it works

A short path from the owner’s Mac to one useful answer.

Meeting Pulse is deliberately split into two surfaces: the owner app does the observing, and the viewer does the reading.

Start with the Mac app What stays private
01

Install Station

The owner installs the native macOS app and grants the Accessibility permission needed for supported detection.

Install guide
Meeting Pulse onboarding window on macOS
Setup starts in Station.
02

Watch a supported meeting state

Station observes the supported call surfaces locally. It does not upload meeting content or turn the browser into a sensor.

Why Accessibility?
Meeting Pulse Station showing an available state
The owner can see what the detector knows.
03

Pair the person who needs to know

Station creates a private viewer path. The person checking in opens that link on a phone or laptop without creating an account.

Pair a viewer
Meeting Pulse Station showing paired viewers
The owner chooses who gets the link.
04

Read the state, not the story

The viewer checks the current signal periodically. If the signal is stale or unavailable, the viewer says so instead of guessing.

Troubleshooting states
Meeting Pulse viewer showing unavailable meeting status
“Meeting status unavailable” is an honest answer.
Meeting Pulse is not a realtime presence system.

The owner heartbeat and viewer polling are periodic. That is why freshness and unavailable states are part of the product language.