Installing the Widget
The Widget on Mobile and Responsive Layouts
How the Convot widget behaves on small screens and how to hide it on mobile if needed.
The Convot widget is responsive by default. It adapts to screen size automatically - no extra configuration is needed for most sites.
Default behavior on mobile
On small screens (phones and narrow tablets), the widget:
- Shows as a floating launcher button in the corner, the same as on desktop.
- Opens as a full-screen overlay when tapped, rather than a side panel.
- Closes back to the launcher when the visitor dismisses it.
The full-screen experience on mobile is intentional - it gives visitors enough room to read and type comfortably.
Hiding the widget on mobile
If you want to suppress the widget entirely on mobile devices, turn on Hide the chatbox on mobile devices under Settings → Apps → [your app] → Chatbox → Behavior.
When this is on, the launcher and widget do not appear on any device narrower than the desktop breakpoint. Visitors on phones will not see the chat bubble at all.
Hiding on mobile means mobile visitors cannot contact you through the widget. Consider this carefully if a significant share of your traffic is on mobile.
Controlling visibility with JavaScript
You can open or close the chat window from your own code with the Convot JavaScript API:
Convot.open(); // open the chat window
Convot.close(); // close the chat window
To hide the widget on specific pages (rather than just open or close it), use page rules under Settings → Apps → [your app] → Chatbox → Restrictions. To hide it on mobile, use the Chatbox Behavior toggle described above.
Position on screen
By default the widget sits in the bottom-right corner. To move it to the bottom-left, turn on Reverse the position of the chatbox under Settings → Apps → [your app] → Chatbox → Appearance.
The left/right position applies on both desktop and mobile.
Next steps
- Colors and branding - change the widget color and launcher style.
- Launcher and position - control where and how the launcher appears.
Was this article helpful?
Thanks for your feedback!