21 August 2026
Most AI note takers dial into a call as a guest, and a guest can be turned away. On a client's own Zoom or Teams tenant, their IT decides who gets past the waiting room — and a growing number of companies block unknown bots by default, especially in finance, healthcare and legal. When that happens there's no transcript, no notes, and often no warning that anything was missed.
Most AI note takers work the same way: a bot with its own name and video tile dials into the meeting link like any other guest. That's fine when the call is on your Zoom or your Teams. It's a different situation entirely when the call is on the client's tenant, because the client's IT department set the front door, not you.
App allowlists, waiting rooms, and domain restrictions exist for exactly this reason. A bank, a hospital system, or a law firm that has a blanket policy against unrecognized meeting apps isn't making an exception for your note-taking tool. This is architecture, not an oversight you can route around with a settings toggle.
There's no graceful failure here. The bot either gets admitted or it sits in a waiting room until the meeting ends, and nothing about the outcome is retroactive — audio that was never streamed to the bot can't be recovered afterward, no matter how good the transcription engine is.
If the client hosts the call and records it themselves — a Zoom cloud recording, a Teams recording that lands in their SharePoint — you might get a transcript after the fact, if they choose to share it. That's a real option and worth asking for.
It's also a narrower one than it sounds. You get the words after the meeting, not notes that build while people talk, not a way to ask a question mid-call, and no action items pulled the moment someone says them. The recording lives in the client's tenant under their retention and consent policy, not yours, and whatever decisions got made in that room were made without any tool of yours shaping them in real time.
AVAY doesn't dial into anyone's meeting as a bot. The AI participant is native to a call that happens inside an AVAY room — it's not a guest asking for admission, it's part of the room from the first second. That's a strength when the call is yours to schedule, and a hard boundary when it isn't.
If the client picks a Zoom or Teams link on their own tenant, AVAY has nothing to see. There's no waiting room to get past because there's no bot trying — just a call that AVAY was never inside. The fix isn't a feature request; it's getting the client into an AVAY link, or accepting that this particular call stays outside AVAY's reach.
In practice this settles into a pattern fast. Calls a team controls — kickoffs, internal syncs, QBRs they're running — go out on an AVAY link by default, and get full transcripts, live notes, and decisions that stay current as people talk. Calls the client insists on running through their own platform stay on their platform.
For those, the ask is simple and often works better than expected: propose the AVAY link first, before the invite goes out on their Zoom. Clients who care about having real notes will frequently agree to it, especially once they've seen one meeting where the AI answered a question out loud mid-call. The ones who won't budge get a fallback — a shared recording if they'll provide one, manual notes if they won't — and everyone accepts that fallback means less than the real thing.
| Admission risk | Live Q&A during the call | What you keep afterward | |
|---|---|---|---|
| Bot dials into client's platform | Blocked by allowlists or waiting rooms often, especially at regulated companies | None if blocked, limited if admitted late | Transcript only if the bot got in and stayed the whole call |
| Client joins an AVAY link | None — it's your room, no bot to admit | Yes, ask the AI anything mid-call | Full transcript, live notes, decisions, searchable later |
| Manual notes, no tool at all | No risk, nothing to block | None | Whatever got written down, no audio record |
Only if the host's IT allows unknown apps and someone manually admits it from the waiting room — many corporate tenants block this by default. If it's blocked, the bot times out with no transcript and no warning that anything was missed.
Nothing is recorded. The bot sits in the waiting room until the call ends or someone lets it in, and there's no way to retroactively capture audio that was never streamed to it. Some tools email the organizer that the bot couldn't join; most just go quiet.
It depends on where the call happens and who's on it — some jurisdictions require all-party consent, others just one. That's a policy question for your legal team, not something a note-taking tool decides for you, and it applies whether the AI is a bot or built into the platform.
No — AVAY's AI runs inside AVAY meetings, not as a bot dialing into someone else's platform. If the call happens on the client's Teams link, AVAY has nothing to transcribe unless the client joins an AVAY link instead.
Then you take notes the old way, or ask them to share their own recording afterward if their platform makes one. Neither gives you live answers mid-call or a decision log that updates as people talk, but it's what's available when the tenant isn't yours.
AI note takers that dial in as a bot only work when the client's IT lets them through the door — assume that's a coin flip on any call you don't host, and get the client onto your own link when the meeting matters enough to need real notes.
AVAY is a video meeting platform that transcribes the call itself — no bot joins, because there is nothing to join. Start one at avay.ai, read how each part works in the documentation, or see what it costs.