Routingconferencestable

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 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 Request agent 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 holdMusic (a music track from the Prompts & music library) plays until at least one other participant joins; entry/exit beeps and the per-leg mute flag are applied by the call platform 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) 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

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.

FieldLabelTypeRequiredDefaultNotes
conferenceNameConferenceconferenceRequired""Pick from your saved conference rooms. Manage under Setup → Queues & rooms (Rooms tab).
muteCaller joins mutedbooleanOptionalfalseUseful for listen-only town halls.
beepEnabledEntry/exit beepselectOptionalon_enterOptions: on_enter, on_exit, always, never.
holdMusicMusic while waiting for othersaudioOptional—A music track from the Prompts & music library. Plays until at least two participants are present. Blank = none.

Outgoing events: conference.participant.joined

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 until the caller leaves the room.

{
  "id": "join-standup",
  "type": "conference",
  "config": {
    "conferenceName": "team-standup",
    "beepEnabled": "on_enter",
    "holdMusic": "sys:music/default-hold"
  },
  "on": {}
}

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"
  },
  "on": {}
}

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.
  • Supervising is not a flow setting. Listening in, whispering to the agent or barging in on a live call belongs to a supervisor console outside flows, not to this node.
  • Hold audio plays only while alone. The platform automatically stops the holdMusic 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.
  • There is no "everyone left" or hang-up edge. The flow stays parked on the conference node until the caller leaves the room (then it continues on Joined); when the caller hangs up, the call is over. Put logic for afterwards under After the call ends.

See also