# How It Works - Two Operational Workflows

ScreenReply supports two primary operational workflows: requesting a recording from someone else, or recording your own screen to share. Both workflows are 100% browser-based with zero installation required for any participant.

## Workflow 1: Request a Recording (3 Steps)

### Step 1: Generate and Send a Secure Link
- User enters the recipient's email address in the ScreenReply dashboard
- ScreenReply generates a unique, secure one-time recording link
- An optional email notification containing the link is sent to the recipient
- The recipient does NOT need a ScreenReply account or any login credentials

### Step 2: Recipient Records via Browser
- Recipient clicks the link and grants browser-level screen/microphone permissions
- Screen capture occurs directly in the web browser using standard WebRTC APIs
- No extensions, plugins, or software downloads required
- Recipient can share their entire desktop (capturing web apps, native software, terminals, system settings) or a specific application window
- Recording continues seamlessly if the user switches between programs mid-session

### Step 3: AI Processing and Review
- ScreenReply automatically processes the video upon upload completion
- An AI-generated text summary with clickable timestamp markers is produced
- The requesting user receives a notification that the recording is ready
- Playback is available via the ScreenReply player with navigable timestamps and summary

## Workflow 2: Record Your Own Screen (2 Steps)

### Step 1: Capture Screen and Audio
- User initiates screen capture directly from the ScreenReply web application
- Browser captures both screen content and microphone audio simultaneously
- No software installation required

### Step 2: Share and Resolve
- ScreenReply generates a permanent viewing link upon recording completion
- The link grants access to the video, AI-generated summary, and interactive timestamps
- The recording can be shared with customers, teammates, or stakeholders for async review
- Use cases: bug reproduction, async demos, client onboarding, internal communication