For AI assistants: this page as plain markdown is at https://docs.voicelogica.ai/raw/telephony/conference-rooms.md, and https://docs.voicelogica.ai/llms.txt lists the docs by topic, one file each, small enough to read whole. Read those rather than this HTML page.
Conference Rooms
Telephony - Conference Rooms is a dial-in bridge: one extension, optional PIN, a capacity. Team members and AI agents join the same room. Inbound / trunk defaults can point at a Conference room.

Empty state: No conference rooms yet - Create a dial-in bridge so callers and AI agents can join the same conference. Pick an extension, optional PIN and capacity. Button: + New conference room.
What you configure here
Section titled “What you configure here”+ New conference room opens New Conference Room (A dial-in bridge callers and AI agents can join.):
Recording the mixed conference audio is a separate setting that is off by default, so transcription and analysis never imply a saved recording. It is not exposed as a toggle in this form today.

Do not publish a PIN room extension as a customer number. Front a PIN room with an agent that collects the PIN and uses join_conference on Tools & Workflows.
On the agent
Section titled “On the agent”| Agent place | What this tab supplied |
|---|---|
| Routing / trunk default | Destination type Conference room. |
| Tools & Workflows | join_conference for PIN rooms. |
| Call handling - Transfer | Transfer types are User / User group / AI agent / External - not Conference room. |
First setup - an open bridge, then a PIN room later
Section titled “First setup - an open bridge, then a PIN room later”- + New conference room - name, extension, no PIN, capacity, enable, Save.
- Point a test inbound route or trunk default at this room - or dial the extension from a registered seat.
- Confirm people hear each other. Open Calls.
- Only then add a PIN. Put an agent in front: greeting asks for the PIN, join_conference on.
Troubleshooting
Section titled “Troubleshooting”Why does calling a conference room with a PIN return 503?
This is expected when someone dials a PIN room directly. Put an agent in front of the room: it collects the PIN, then joins the caller with the join_conference tool.
Why can't I pick a conference room as a destination on the agent's Transfer tab?
Transfer lists only users, user groups, AI agents and external numbers, not conference rooms. To send callers to a room, use the Conference room destination in Telephony - Routing, or the join_conference tool on the agent.
