TabTwinSupportTwin← Back to home
Subsystems/SupportTwin

Share

SupportTwin

Support the tab, not the desktop.

SupportTwin lets an agent see and guide only the customer-approved browser tab. Pointer guidance, highlights, masking, and optional controlled assistance replace the risky request to share an entire desktop.

01
Why this capability exists

From friction to a clear outcome

The user problem

Support calls slow down when customers must describe a visual problem or share their entire screen. Full remote control creates unnecessary privacy and trust concerns for both the customer and the support team.

The TabTwin answer

SupportTwin opens a consent-based co-browse session for one customer-approved tab. An agent can observe the same page, point to elements, and request narrowly scoped assistance without seeing the rest of the desktop.

02
Real-world scenario

Guide a customer through a complex account setup

  1. 1

    Send the customer a private support link

  2. 2

    Customer approves only the relevant browser tab

  3. 3

    Agent sees the page with sensitive fields masked

  4. 4

    Agent points, highlights, and explains the next action

  5. 5

    Customer closes or revokes the session when complete

03
End-to-end workflow

How SupportTwin works

  1. 01

    The agent sends a private support session link.

  2. 02

    The customer approves the selected tab and sensitive fields remain masked.

  3. 03

    The agent observes, points, highlights, and guides; optional actions require explicit permission.

04
What is included

Core capabilities

01

One-tab co-browse

Shares the approved product page while unrelated tabs and apps remain private.

02

Agent pointer

Lets support indicate the exact button, field, or navigation item to use.

03

Live highlights

Adds temporary visual guidance without changing the customer’s data.

04

Optional control request

Allows specifically approved actions when observation alone is not enough.

05

Sensitive-field masks

Keeps passwords, cards, tokens, and configured personal data out of the session.

06

Session record

Creates an optional support trail for quality, training, and follow-up.

05
Where it wins

Best use cases

  • ✓Account setup assistance
  • ✓Complex form or checkout guidance
  • ✓Troubleshooting customer portals
06
What the user gets

Expected outputs

  • →Consent-based co-browse session
  • →Guidance pointer and highlights
  • →Optional support session record
Business value

What changes for the team

  • ↗Resolve visual issues without asking for desktop screen share
  • ↗Reduce back-and-forth instructions and time to resolution
  • ↗Give customers visible control over what the agent can access
Built for control

Safe by design

  • ✓The customer explicitly approves and can revoke the tab session
  • ✓Observation, pointing, and control are separate permission levels
  • ✓Sensitive fields remain masked from capture and the agent view
Why SupportTwin is different

SupportTwin makes consent and tab boundaries part of the product, rather than treating privacy as a setting on top of full desktop access.

One shared technical foundation

Powered by the Browser Session Engine.

SupportTwin consumes the same structured DOM events, timeline, context, snapshots, and safe execution primitives as the rest of TabTwin—without requiring another extension.