How to send an invite link, what a guest sees before joining, and what to do when a guest cannot be seen or heard.
A guest enters your room through a link in a browser. They have no account here, they install nothing, and they need to know nothing technical beyond pressing Allow when the browser asks about the camera.
The podcast studio and the live studio carry the same invite button, and the same window opens in both. It produces a link in the form /join/ followed by a long random identifier, and offers three ways to send it: copy, WhatsApp and email. The link is also placed on your clipboard the moment it is created.
Three things worth knowing about it:
If the host disconnects the room does not close immediately: there is a minute and a half to come back, and guests wait in the meantime.
A guest does not drop straight onto the stage. A preparation screen opens: a name field, a choice of how to join, and a preview of themselves.
Four ways to join:
Under the preview is a microphone level meter that says it can hear you once sound arrives. This is the check that prevents the most common failure of all: a microphone chosen wrongly and discovered half an hour later. In the camera settings menu the guest can pick a specific camera and microphone, switch on background blur, flip between front and rear cameras and set the orientation — all before joining.
A guest who joins lands in your participant strip muted, and you decide when they reach the stage. A waiting room where you admit each arrival by hand is a setting you can switch on, not the default.
Every guest has a row of controls: mute and unmute, camera off and on, a separate volume, a display-name change, placement on screen, and removal from the room. Each of these is shown to the guest as a message, so they know the host muted them rather than assuming their microphone broke.
Screen sharing by a guest is off by default. The guest can ask, and you approve or decline; only after approval does the button appear for them.
A guest who joined as a listener can also be brought up to speak: the moment you unmute them their browser requests a microphone and joins them to the conversation, with no leaving and rejoining.
Each guest receives their own audio mix: you and all the other guests, without their own voice. That is what prevents echo and lets guests talk to one another rather than only to you. A mute you apply to a guest also enters that mix, so muting really mutes everywhere.
The system recognises the three common failures and tells the guest exactly what to do:
If the camera fails but the microphone works, the guest is joined with audio only rather than left outside.
A temporary disconnection handles itself: the connection retries at growing intervals, and the guest returns to the same place in your list instead of appearing as a duplicate participant.
If a guest picked the wrong microphone and has already joined, there is no device switch mid-call. The remedy is to leave the link and open it again, choosing the right device on the preparation screen this time.
The number of participants a room holds follows the host's plan. When the room is full the next guest is told plainly that it is full rather than being left on a loading screen. Call length is also capped on some plans, with a warning shown before the end.
No. The link itself is the ticket. The guest opens it in a browser, chooses a camera and microphone, and joins — with no sign-up and nothing to install.
Four hours from the moment it is created. After that it expires, and you can issue a fresh link from the same invite window.
Yes, that is how it is meant to work. The same link serves all participants; you do not need a separate one for each.
That is correct behaviour. A guest arrives muted in the participant strip, and the host decides when to bring them up. Give them a placement on screen and they appear.