Why hosts want the meeting on their own site
When you send guests a bare meeting link, the experience leaves your brand at the exact moment it matters most. Guests click, a different window opens, and the thing they came to see no longer looks like you. The offer you mention during the session lives on another tab they may never find, and the list of who attended sits inside the meeting account rather than with your marketing.
Putting the meeting on your own site fixes the front door. Guests stay on an address and a page they recognise, your navigation stays in place, and everything you want them to do next is one click away. For companies, that means an all-hands or customer webinar that looks like the company. For coaches, consultants and creators, it means their masterclass happens in their world, not someone else's.
Three ways to do it
There are really only three routes, and each one suits a different kind of team.
- Link out from your site. Put a Join button on a page that opens the regular meeting link. It takes minutes and costs nothing, but guests still leave your site, and you capture nothing at the door.
- Build it yourself on a developer kit. Most meeting platforms offer a software kit for running meetings inside your own web app. You get full control, and you also own the authentication, the waiting logic, the start sequence, guest capture, testing across browsers and every future update.
- Use a branded meeting room. BrandedRooms runs the meeting you already host inside a ready-made page dressed in your brand, with the lobby, the start button, guest capture and follow-up already built. You configure rather than code.
What a branded room puts on your page
A BrandedRooms room is a full page built around your meeting. On a Branded Room, your logo and navigation sit at the top, so the page feels like part of your site. Before you arrive, guests see a branded waiting room that says you will be joining shortly, with a countdown and an add-to-calendar button. At the door they leave a first name and email, tagged by the event.
When you start the meeting in your meeting app and press Start the room, the meeting appears inside the page for every waiting guest at once, joined muted. On a Branded Room, a featured offers rail sits beside the meeting, opening programmes, products and forms in a slide-over. From the Generic Room up, you can fire confetti, applause and other effects over the meeting for everyone on the page.
On a Branded Room, the room also lives on your own domain or subdomain, such as a live address on your company's domain, so the address bar matches the brand on screen. Link to it from your main navigation, your event pages and your emails, and to guests it simply is your website's meeting room. The free 30-day trial and the Generic Room use a brandedrooms.com address.
Build or use a room: how to decide
Building your own page is the right call for some teams, and we would rather say so plainly. Choose a build if the meeting is part of a product you sell, if you need the video experience woven into your own app's accounts and data, or if you have engineers who will own it for years. Expect the work to include signing guests in securely, handling the case where the host has not started yet, managing passcodes, testing on phones and older browsers, and keeping up with the platform's kit when it changes.
Choose a branded room if what you need is an on-brand page for events and meetings, ready this week, maintained by someone else. The trade-off is that you work within what the room does: the waiting room, Start the room, effects, guest capture, offers, attendee list and follow-up. Five custom party features, each with your own effect, image and sound, come with Custom Deluxe, and white-label, single sign-on and custom integrations are available on request when a team needs more.
Where an on-site meeting room earns its place
Not every call needs to live on your website. A quick check-in with a colleague is fine on a plain link. The meetings worth moving onto your own page are the ones where the brand, the list or the next step matters.
For a company, that is the customer webinar where the product team wants every attendee tagged, the onboarding session where new clients should see the same logo they signed with, and the all-hands where internal comms wants the resources beside the meeting rather than buried in a chat. For a coach or creator, it is the free masterclass where the programme sits in the offers rail all session, the monthly community call people bookmark, and the launch party where the confetti goes off on everyone's screen at once. In each case, the page does a job the link could not.
Before you embed: a short checklist
Whichever route you take, these are the checks that save the day.
- Confirm which meeting account will host. Guests join the meeting configured in the room, and the developer app must belong to that same account.
- Know your participant limit. Everyone on your page counts toward your meeting licence, so plan a bigger licence or an overflow livestream for large audiences.
- Decide what guests give at the door. Name and email powers your follow-up; you choose for each room whether email is required.
- Write the waiting-room message. Say who is hosting, when you will start and what to have ready.
- Test on a phone and a laptop, signed out, in a private window, before the real event.
- Tell desktop-app fans the trade-off. They can still use the regular link, but they will not see your page, offers or effects.
What stays the same
Embedding the meeting on your site does not replace your meeting platform. Video, audio, screen sharing and recordings keep working the way your team knows, under the account and licence you already have. Effects play on the room page rather than inside the meeting, so the platform's recording will not include them; screen-record the room page if you want them in a replay. Your recordings and billing stay with your meeting account.