Friday, Sep 11, 2026 The claims desk. Receipts included. POWERED BY LENZ ↗
IsThis

LiveKit agents can only process media streams that exist inside LiveKit rooms.

The Claim

LiveKit agents can only listen and respond to humans in meetings held inside LiveKit rooms, so a Google Meet or Microsoft Teams meeting must be bridged into a LiveKit room for a LiveKit agent to interact with the meeting audio/video.

Verified by Lenz ·

The Short Version

LiveKit agents are built to join LiveKit rooms and can only hear or publish media that exists in those rooms. So if a Google Meet or Microsoft Teams meeting is to be handled by a LiveKit agent, that meeting’s media must be relayed into a LiveKit room first. The caveat is that Meet and Teams also support non-LiveKit-native bot or interop approaches.

Caveats

  • The claim applies specifically to LiveKit agents, not to all bots or integrations for Google Meet or Microsoft Teams.
  • “Bridged” is a broad term here: the media can be brought into LiveKit through SIP, telephony, ingress, or other relay mechanisms.
  • Teams and Meet may offer their own native bot or interop frameworks, which do not require LiveKit at all.

The Receipts

  1. Introduction | LiveKit Documentation

    LiveKit Documentation

  2. Rooms, participants, and tracks overview - LiveKit Documentation

    LiveKit Documentation

  3. Connecting to LiveKit

    LiveKit Documentation

  4. Calls and meetings bots in Microsoft Teams

    Microsoft Learn

  5. Agents overview

    LiveKit Documentation

  6. Media workflows

    LiveKit Documentation

  7. Telephony overview

    LiveKit Documentation

  8. Twilio Voice integration

    LiveKit Documentation

  9. Telephony introduction | LiveKit Documentation

    LiveKit Documentation

  10. Build an Agent | LiveKit Docs

    LiveKit Documentation

+ 26 more sources — see the full list on Lenz

Filed Under

Google MeetLiveKitLiveKit AgentsLiveKit RoomsMicrosoft Teams