Be on the same page as your customer
One script tag turns any support call into a guided session: your agent sees the customer's page live — with consent, in the customer's language, face to face and by voice. They point, scroll, and (within limits you set) click. Nothing to install, nothing recorded on our servers.
Try the idea right here
Drive either window: move your mouse, click a plan, type the invoice name — the other window follows, because both sides share the same live page. The real, end-to-end version (two browsers, WebRTC, consent, rights) is one click away in the live demo.
Choose your plan
Choose your plan
Three ways into a session — all consent-first
Already on the phone? The support code.
The customer taps “Show support code” and reads the short code aloud — minted on click, unique, gone after a few minutes. The agent enters it in the console and a consent card appears on the customer's page. Nothing is shared until they allow it.
Right now? They just call you.
One click on “start voice call” and the customer is talking to your team — straight from the page, no phone number, no dial-in. Every agent's console rings; answering opens the call, and the screen-share ask follows only if the conversation needs it.
Not yet? The callback.
The customer leaves their number and sees their place in line with an honest wait estimate. Your agent rings their phone straight from the console — no desk phone, just a headset — and in the same moment, “Anna from support is calling you and asks to view this page” appears on their screen, with Anna's photo on it.
It's a conversation, not a shared screen
Co-browsing shows your agent the page. These put the person on it — seen, heard, and speaking your customer's language. All on the same peer-to-peer connection, none of it through our servers.
See who's helping
Your agent switches on their camera and appears in a small, draggable bubble right on the page — a real face on a one-way video feed (camera only, no audio track). Or keep it to a photo. The customer moves it wherever they like and ends it anytime.
Talk it through
The customer clicks “start voice call” and speaks to your agent straight from the page — a two-way browser call over the same encrypted connection. No phone number, no dial-in. The mic prompt is their consent, and the audio never touches our backend.
In their language
The widget, the consent card and every visitor-facing surface speak English, German, French, Spanish, Italian or Dutch — auto-detected from the browser or pinned per page. The console even shows the agent which language the customer is in.
One console for the whole conversation
Your agents work the queue from a single browser tab — no phone system on the desk, no window juggling, no second tool.
Sessions dock right in
Sessions open as tabs inside the console — run several at once, switch with a click, minimize the whole thing to keep working the dashboard while a call carries on. Prefer a separate window per session? That stays one toggle away.
Call their phone from the browser
Connect your own SIP provider once, and every callback gets a “Call phone” button: the customer's phone rings, your agent talks through the headset — with the co-browse session running right next to the call. Mute, keypad for IVRs, done.
It rings like a phone
Incoming browser calls ring on every available agent's dashboard — a real ringtone plus a desktop notification, even in a background tab. Availability is heartbeat-honest: a closed laptop takes an agent out of rotation automatically.
Why this approach
Privacy by architecture
Session content travels only peer-to-peer over a WebRTC DataChannel. The TURN relay is a fallback for tricky networks — page content never rests on our servers, and session traces auto-delete.
Real DOM, not video
Built on rrweb DOM mirroring: the agent gets a real second cursor and remote clicks. Passwords never leave the page; any field can be masked with one attribute.
A ceiling, not a promise
Integration depth (see → point → scroll → type → click) is enforced on the visitor's side from your app's settings. Turning a capability off makes it technically impossible.
Stays live as they navigate
The session follows the customer across a full page load and through single-page routes — the Typo3-to-checkout journey stays one session, with no second consent prompt. Drop in the snippet or the <cobrowse-widget> element.
Simple, session-based pricing
Pay for guided sessions, not for seats you don't use.
Free
Try real co-browsing on your own site.
- ✓10 sessions / month
- ✓One app on one website (subdomains included)
- ✓Consent-first co-browsing, peer-to-peer by architecture
- ✕Standard widget only
- ✕English-only widget
- ✕No browser calls
- ✕No callback queue
- ✕No built-in softphone
- ✕No analytics events
- ✕Live help 24/7 only
- ✕No DPA signing
- ✓Two-factor auth & passkeys for your own login
Pro
For support teams that live in the queue.
- ✓500 sessions / month
- ✓Unlimited apps & websites
- ✓Consent-first co-browsing, peer-to-peer by architecture
- ✓Fully customizable widget (branding, texts, display mode)
- ✓Multi-language widget (6 languages, auto-detected)
- ✓Browser voice calls (VoIP) — customers call you from the page
- ✓Callbacks with live queue estimates
- ✓Built-in softphone — agents ring customers' phones from the console (your SIP trunk)
- ✓Analytics events into your own tool (self-service vs. agent-assisted)
- ✓Service-hours scheduling
- ✓Data processing agreement (Art. 28 GDPR), signed digitally
- ✓Two-factor authentication for your team
- ✓Extra sessions pay-per-use: €1 / session
Enterprise
Custom volume, custom terms, a human who answers.
- ✓Custom session volume
- ✓Unlimited apps & websites
- ✓Consent-first co-browsing, peer-to-peer by architecture
- ✓Fully customizable widget (branding, texts, display mode)
- ✓Multi-language widget (6 languages, auto-detected)
- ✓Browser voice calls (VoIP) — customers call you from the page
- ✓Callbacks with live queue estimates
- ✓Built-in softphone — agents ring customers' phones from the console (your SIP trunk)
- ✓Analytics events into your own tool (self-service vs. agent-assisted)
- ✓Service-hours scheduling
- ✓Data processing agreement (Art. 28 GDPR), signed digitally
- ✓Custom, enforceable MFA rules — part of your plan
- ✓Priority support & onboarding
Sessions are metered in tokens — one co-browsing session costs one token. Prices exclude VAT. Self-service checkout (Stripe) is coming; early-access workspaces run free.
Fair questions, straight answers
The things every support lead asks in the first call.
What does my customer have to install?
How is this different from screen sharing?
Can the agent see my customer's passwords or card numbers?
data-cobrowse-mask).What can an agent actually do on the page?
Is it GDPR-compliant?
How long does the setup take?
<script> onto your site (or drop in the <cobrowse-widget> element), allow-list your domain in the dashboard, done. Your team signs in, sets themselves available, and the widget starts offering live help.What happens when no agent is available?
Do my agents need a phone system?
Want the deep answers — interfaces, encryption, data flows, sub-processors? Read the technical & privacy FAQ →
See it in two browser windows
Open the demo as visitor and agent — code, consent, live mirror, rights clamp.