Loom meeting agent not joining multi‑org calls with multiple Loom tenants

[Bradley Breedlove]

Hi all,

We’re seeing a recurring issue with the Loom meeting agent on multi‑organization calls and I’m trying to understand if this is expected behavior or a bug.

Scenario

• One recurring meeting with 7 people from 4 different organizations

• 3 of those organizations use Loom and each has its own Loom meeting agent

• When the meeting is scheduled, all 3 Loom agents are invited

Issue

For this specific meeting, the Loom agent often doesn’t join at all (no recording, no notes), and we don’t see a clear reason why.

Questions

1. Is this a known limitation or issue with Loom when multiple organizations’ agents are invited to the same meeting? (e.g., only one agent allowed, tenant conflicts, etc.)

2. What’s the recommended best practice for cross‑company meetings where several orgs use Loom? Should we only invite one org’s agent?

3. Is there any way for admins/users to see why the agent didn’t join a specific meeting (logs, status, error messages, known blocking conditions)?

Any guidance or documentation links would be appreciated.

Thanks!