The live view

A staged demo proves nothing. Live View exists so the demo is the product itself: you talk to the agent on a real call, and the site shows the conversation and the work behind it in real time. It is also the transparency mechanism, the way you check what the agent actually does on a call instead of taking our word for it.

The connection between your phone call and a browser is called a bind, and the dialpad is how it happens:

1. 1The screen shows a codeEvery browser on /live gets its own 6-digit code, shown on the on-screen phone. A code is good for 10 minutes; when it expires, the page mints a fresh one on its own.
2. 2The caller keys it inDuring a call to (855) 552-8611, press *, the 6 digits, then # on your dialpad. That keypress is the caller's deliberate choice to be shown; no code, no live view.
3. 3The viewer must acceptThe browser that owns the code asks “incoming call wants to appear here. show it?” and warns that captions can include what the caller says, including personal details. The viewer has 45 seconds to accept or dismiss. This on-screen confirmation is a safety boundary: someone who shoulder-reads a code cannot project your call onto a stranger's screen, because that stranger's screen has to say yes.

• The conversation, live. Captions of what the caller and the agent say stream onto the on-screen phone word by word as they are spoken, and mirror in large type beside it.
• Simple status labels. Plain-english call states like “ringing”, “live”, and “call ended”, plus a speaking indicator.
• The work behind the call. A feed of what the agent is doing while it talks, as short fixed labels with a status mark: “checking the calendar”, “openings found”, “booking the appointment”, “appointment booked”, “sending the confirmation text”, “confirmation text sent”, and their honest failure versions.

The browser never receives the call's raw event stream. It subscribes to a projection built through a strict allowlist, and only for the one call it confirmed. Deliberately absent:

• Phone numbers. The caller's number and caller ID never reach the page, anywhere.
• Tool data. The action feed carries only the fixed labels above, never the arguments or results behind them; no calendar contents, no message bodies, no internal identifiers.
• Spoken screen codes. If an active bind code is said out loud on a call, it is blanked to “[code]” in the captions before they leave our systems, so hearing a code read aloud does not let anyone else use it.

The feed marks the call ended, picks up any trailing captions, and freezes. The pane beside the phone shows a short recap: call length, whether an appointment was booked, and whether a confirmation text went out. Every viewing session is one-time: watching another call means a fresh code and a fresh confirmation.