Join conference

Drops the caller into a shared conference room. Anyone else who joins the same room hears them — useful for team standups, multi-party support calls, or m…

What it does

Joins the caller's leg into a named Telnyx conference room. Anyone else who is already in that room — or anyone who joins it later from another flow, an outbound dial, or an admin barge tool — hears the same audio. Conferences are identified by name, so dropping multiple legs into the same conferenceName is how you build any multi-party call: a town hall, a moderated panel, a three-way with a supervisor, or a paging room that broadcasts to a set of speakers.

This node only joins one leg: the caller's. The flow does not fan out to other extensions on its own. To stage a real multi-party scenario, the other participants need to enter the same room separately — typically via a parallel Ring extensions flow targeting the same room name, or via admin tooling that originates a fresh leg into the conference. While the caller is alone in the room, the optional holdAudioUrl plays until at least one other participant joins; entry/exit beeps and the per-leg mute flag are controlled by Telnyx using the values you set here.

When to use it

• Run a recurring team standup or all-hands where everyone dials a single internal number and lands in the same room
• Build a "join the bridge" pattern for support escalations — a Tier 2 agent enters the conference from their own flow while the caller and Tier 1 agent are already inside
• Stand up a listen-only town hall (mute: true, supervisorRole: monitor) where attendees can hear the speakers but don't broadcast
• Pipe a paging announcement into a room that desk phones permanently hold open, so any speech in the room reaches every speaker
• Capture a supervisor coaching session: drop the supervisor in with supervisorRole: whisper so they can talk to the agent without the caller hearing

Configuration

Drops the caller into a shared conference room. Anyone else who joins the same room hears them — useful for team standups, multi-party support calls, or moderated rooms.

Outgoing events: conference.participant.joined, call.hangup

Examples

Simple multi-party room

Join the caller into the team-standup room with an entry beep. While they're alone, hold music plays. The flow stays parked on the node and follows call.hangup when the leg eventually drops.

{
  "id": "join-standup",
  "type": "conference",
  "config": {
    "conferenceName": "team-standup",
    "beepEnabled": "on_enter",
    "holdAudioUrl": "https://cdn.example.com/hold.mp3"
  },
  "on": { "call.hangup": "end" }
}

Listen-only town hall

Attendees join muted with no beep. Combine with a separate flow that brings the speakers in unmuted to the same conferenceName.

{
  "id": "town-hall",
  "type": "conference",
  "config": {
    "conferenceName": "all-hands-2026q2",
    "mute": true,
    "beepEnabled": "never",
    "supervisorRole": "monitor"
  },
  "on": { "call.hangup": "end" }
}

Gotchas

• One node = one leg. This node joins only the caller. A "two people on the same call" scenario needs at least two legs entering the same conferenceName — typically arranged by running a second flow (or a requestAgent chain elsewhere) that lands its participants in the same room.
• Conference rooms are created on first join. There is no pre-existing list of rooms. The first leg to enter a name creates it; the room disappears once the last leg leaves. Typos in conferenceName silently create a new, empty room — double-check the name across every flow that should share it.
• supervisorRole is for special listen/coach flows. monitor, whisper, and barge change Telnyx's mixing rules so the supervisor either hears everything silently, can talk only to the agent, or can fully participate. Leave on none for normal callers — the wrong value here can flip a regular participant to mute or audible-only-to-one-side.
• Hold audio plays only while alone. Telnyx automatically stops the holdAudioUrl playback as soon as a second participant joins the same room. If you want music throughout (e.g. between speakers in a town hall), use a separate playAudio step on a side flow.
• The flow waits on call.hangup. There is no "everyone left" event surfaced to the node. The flow remains parked on the conference node until the caller's leg drops, then follows the hangup transition. Use a sub-flow with wait if you need a max-conference-duration cap.