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. Joins are triggered by the calendar or by an administrator on demand — never by the teammate deciding to attend on its own. Before any join, MeetCrew runs a pre-flight region check; if the organizer’s region is out of scope, the join is refused, fail-closed, and recorded.

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

If multiple deployments from your tenant join the same meeting within a short coordination window, the first to arrive gives one combined introduction naming all of them, rather than each speaking separately. A teammate that arrives later gives its own brief introduction.