Customer support
Give customers a direct route to a support call
Put a visible Meeto call button beside your help content or inside a support page. Visitors can open a browser room without an app, while your team keeps a written fallback for cases that need asynchronous help.
A support flow that starts where the customer is
- Place the entry point beside help. Use an inline room on a dedicated support page or a floating bubble on pages where a customer may need assistance.
- Label the room honestly. A “Talk to support” button can open a named shared room. Explain expected response hours if the room is not monitored continuously.
- Keep the call lightweight. The visitor can grant camera or microphone permission, join in the browser and use chat or screen sharing when describing a problem.
- Provide a fallback. Keep email, chat or a form visible for visitors whose browser, network or device cannot establish a media call.
If support must be a private scheduled session, link to an online booking page instead. A shared room and a scheduled booking solve different problems.
Configure the widget before sending traffic to it
| Mode | Best for |
|---|---|
| Floating bubble | A call option that should remain available while a visitor reads several help pages |
| Inline room | A dedicated support page where the call surface has its own space |
| Named shared room | A stable support or sales destination used by a team |
| Booking page | A private appointment where the visitor selects an available time |
- Create an embed key. Add the production support hostname to the allowed-origin list in the widget dashboard.
- Test both sides. Open the support page in one browser and join from a second device. Check camera permission copy, audio, screen sharing and the close button.
- Write the expectation. Say whether someone is available now, which hours are covered and where to go when the room is closed.
The browser key is origin-restricted and safe to include in client markup, but server credentials must stay on your server. Meeto branding remains on the widget on every plan.
Set expectations before the first call
Shared means shared
A named support room is a common destination. Do not describe it as a private queue or promise that every visitor receives a dedicated host.
Browser access has conditions
Guests do not need an install, but they do need a current browser, a compatible network and permission to use the selected devices.
Record with consent
Cloud recording requires a paid host, is opt-in and shows a visible indicator. Tell participants before capture starts.
Use the support guide for permission and joining troubleshooting, and the privacy overview for current data-handling language.
Frequently asked questions
Can support visitors call without an account?
Yes. A visitor can open the Meeto widget or room link in a current browser and join as a guest. They do not need a Meeto account or a download.
Does a widget create a private support ticket for each visitor?
No. A named widget room is a shared destination. Use a booking page when each visitor should choose a time and receive a separate scheduled meeting.
What should we do when a visitor cannot use video?
Keep an email, chat or support form next to the widget. Camera and microphone permissions or a restrictive network can prevent a real-time call, so the fallback should be visible.
Put it to work
Open your Meeto account to set it up, or explore the working product first.