How can we help?

MeetCrew is an AI meeting participant that joins Microsoft Teams, Zoom, Webex, and Google Meet as a named, disclosed teammate — an avatar, a voice, and persistent cross-meeting memory that fronts the chat agent you already run.

In the admin console choose Create deployment, give it a name and wake word, pick a character and voice, connect your backend, and authorize the meetings it may join.

Microsoft Teams, Zoom, Webex, and Google Meet. Available in the US (excluding Illinois) and Canada in v1.

A teammate joins only meetings a tenant admin authorized, and only in supported regions (US excluding Illinois, and Canada). Check both, then contact support if it still won't join.

Yes. A teammate discloses itself three ways — a named participant with an AI badge, an on-screen banner in every frame, and an audible self-introduction — and the disclosure can't be turned off by end users.

Say '[Name], please leave' or 'don't remember this conversation.' It's honored immediately and logged.

Topics, decisions, action items, open questions, and commitments — carried from one meeting to the next, scoped by your admins.

No. MeetCrew never creates or stores voiceprints or any voice-derived biometric. Cross-meeting recognition uses Microsoft Entra platform identity, never voice.

Each deployment is pinned to a region with no cross-region replication, and meeting content stays inside the Azure boundary.

No. The capture layer runs Zero Data Retention by default — the bot vendor stores no recording at any point, and access is real-time stream only. Your durable meeting memory exists only in your MeetCrew tenant store, under your retention policy.

Never. Customer meeting content is not used to train any model, ours or anyone else's.

Email privacy@meetcrew.ai. Retention is enforced to the statutory ceiling and expired records are cryptographically shredded.

Yes. On an admin-mediated data-subject deletion request, the individual is removed from the memory teammates and people can query and search — their name is regenerated out of the structured records and the semantic index, not merely hidden — and a durable marker keeps a later re-extraction from reintroducing it. The raw source transcript is kept as a bounded, non-queryable record and is deleted when the request asks for it.

In the deployment's Configuration, bind Copilot Studio, Microsoft Foundry Agent Service, or a custom endpoint. Credentials are stored as Azure Key Vault secret references.

Tenant administrators authorize meetings and decide which teammates exist and who can configure them.

Per named teammate, not per seat. Each plan includes monthly meeting-hours; see the pricing page for details.

Yes — each teammate is a deployment you manage in the admin console. Adding one may move you to the next plan.

Copilot Studio, Microsoft Foundry Agent Service, any OpenAI-compatible endpoint, or a custom webhook.

They let your own agent read structured meeting memory — decisions, open questions, action items, statements, and topics, with Entra-based attribution and timestamps — and act on the workflow records: close an action item, resolve an open question, or update a decision. There's no delete, and nothing can alter a transcript, a statement, provenance, or the audit log.

Only an agent your organization authorizes. Access runs under a Microsoft Entra service principal your admin grants in the console, and MeetCrew authenticates every call against that identity — there's no shared key or MeetCrew-side access to your memory.

No. Every call is scoped to a single tenant and enforced on our servers, not by the client — a caller can't read or change another tenant's memory, including by guessing record IDs.

No. Attribution comes from Microsoft Entra platform identity, not voice. The interface exposes no voiceprints, no speaker audio, and no biometric data, and the memory stays within the Azure boundary.

By default, reads and actions are scoped to a single named deployment — one teammate. Cross-deployment access is denied unless an admin grants an explicit opt-in, which you control from the console.

Yes. Every read and every action over the MCP server and API is logged and attributable to the Microsoft Entra identity that made it, so you can see who did what and when.