How a teammate joins a meeting

A MeetCrew teammate does not crash meetings. It joins only meetings a tenant administrator authorized, and it announces what it is the moment it arrives.

Authorization comes first

There is no self-service joining. A tenant administrator installs MeetCrew, creates one or more deployments, and authorizes those deployments to join meetings on the organization’s behalf. An administrator starts every join: right away, at a time scheduled in advance, or by having MeetCrew create the meeting and send the teammate into it — never the teammate deciding to attend on its own. Before any join, MeetCrew runs a pre-flight region check. On Teams, a join whose organizer tenant holds no supported assigned region is refused, fail-closed, and recorded. For a Teams short link, which does not name its organizer, MeetCrew relies on the launching administrator’s attestation that the meeting is organized inside your organization, and does not verify it. On Zoom, Google Meet and WebEx there is no organizer signal to resolve, so the check reads the dispatching deployment’s own assigned region instead.

Disclosure on arrival

Once joined, the teammate identifies itself three simultaneous ways, and none of them can be switched off:

• A named entry in the participant list carrying an AI designation, such as “Jim (AI Assistant).”
• A persistent banner composited into every outbound video frame, so recordings and screenshots capture it too.
• An audible self-introduction spoken within the first few seconds of joining, ending with the standing invitation that anyone can ask it to leave at any time.

When several teammates join together

Each teammate introduces itself when it joins, so a meeting with several teammates hears several introductions.