Why a real test matters
Your room settings can look perfect and still hide one missed switch. The only way to know what guests will see is to be a guest. A test on a second device walks the exact path your audience will take: the door, the lobby, the moment the meeting opens, the effects and the follow-up.
Run it once when you first set up, again after you change anything in your meeting account or room settings, and again the day before every important event.
What you need
You do not need anything special for a good test, only a second screen and a few quiet minutes. Gather these before you start.
- Your host computer, signed in to the meeting app as the host of the meeting saved in your room.
- A second device, such as a phone, tablet or another laptop. A private browser window on your own computer works if nothing else is to hand.
- A test name and an email address you can check, so you can see the guest arrive in your list and your follow-up.
- Your host control panel open in a browser tab.
- Headphones on one device, so the two do not echo each other.
The test, step by step
Do these in order, as if the event were real.
- On the second device, open your room address and enter the test name and email at the door.
- Check that you see your waiting room, with your name and the message that you will be joining shortly.
- On your host computer, start the meeting in the meeting app as host. In the room running today that is the Zoom app.
- In your control panel, press Start the room.
- Watch the second device. Within a few seconds the page should switch to the live meeting by itself, joined muted.
- Fire an effect with one of keys 1–5 and check that it plays, with sound, on the guest's screen.
- Find the test guest in your attendee list, and on a Branded Room check they reached your CRM or email tool with the right tag.
If something fails
Each failure points to a specific fix, so note exactly what the guest saw.
- Signature is invalid, or code 3712: the Meeting SDK is not switched on, the Local Test step was skipped, or the developer app is in another account.
- Meeting has not started, or code 3008: the meeting was not started in the meeting app as host before you pressed Start the room.
- The meeting opens but asks for a passcode, or refuses the guest: the passcode in your room settings is out of date, or is the long pwd= code rather than the typed one.
- Effects play but you hear nothing: the guest device is muted, or the browser has not been touched yet. Tap the page once and try again.
A quick phone check
Many guests will join on a phone, so do one pass on a phone even if your main test used a laptop. Check that your logo and waiting room look right on a small screen, that the meeting opens in the browser, and that offers or forms on a Branded Room open beside the meeting without sending anyone away. If you can, try one phone on mobile data rather than office wifi.
After the test
Close the room from your control panel, leave the meeting in the meeting app, and note anything you changed. Your test guest will appear in your guest list and export, so tag or remove them before you send any follow-up. Then add the test itself to your first event checklist, the day before, so it becomes a habit rather than a rescue.
Zoom is named on this page only to describe the setup. Zoom is a trademark of Zoom Communications, Inc. BrandedRooms is an independent product and is not affiliated with or endorsed by Zoom.