Meeting Unstick — live-call tech rescue¶
| Field | Value |
|---|---|
| Status | Exploratory — concept logged (2026-07-13) — not top-priority product building |
| Type | Consumer / B2C2F / SMB product concept — AI sidecar for live video calls |
| Access surface | Phone call / SMS / iMessage helper beside Zoom, Teams, FaceTime (not a new meeting app) |
| Working names | Meeting Unstick · Call Rescue (either could ship; wiki slug stays meeting-unstick) |
| Revisit | If a family/SMB pull appears; not the 2026-08-22 Beads / Where Am I? lane |
One-line brief¶
An AI tech concierge for live video meetings — when audio fails, screen share is stuck, a photo can’t be found, or chat is missing, someone can call or text a helper that unsticks them for Zoom, Teams, FaceTime, and similar — without building another conferencing client.
Problem (observed)¶
The stuck moment is mid-call, not “learning AI”:
- Audio — mute, mic permissions, wrong input, “can you hear me?”
- Screen share — can’t find the button, wrong window, permissions denied
- Photo / attachment — can’t find the image to send into the meeting
- Chat — can’t open or find the in-meeting chat
Happens in work (Zoom / Teams) and family (FaceTime / similar). The meeting stalls; everyone becomes unpaid IT. The model/intelligence of any AI tool is irrelevant — the interface friction is the product.
Core product thesis¶
Not “another meeting app.” A sidecar helper that:
- Knows common failure paths for Zoom vs Teams vs FaceTime
- Guides step-by-step in plain language (or co-pilots quietly for the stuck person)
- Offers alternate paths when automation can’t (photo of the screen, guided taps, remote family assist)
- Meets people on a surface they already trust — phone / text — especially when the meeting UI itself is the obstacle
Fits the goals thesis: trusted access in a high-stress moment + durable trust if it never embarrasses the user mid-call. Not a pure UI-polish play.
Candidate wedges¶
| Wedge | Who pays | Why it might work |
|---|---|---|
| Family FaceTime / Zoom helper | Adult kids | Parents derail holiday calls; kids already do unpaid support |
| SMB meeting rescue | Small business / front desk / sales | Downtime mid-call is expensive; staff aren’t IT |
| Senior / accessibility adjacency | Family or facility | Same audience neighborhood as projects/triviabalance; different job from projects/buddyline / Meela.ai companionship |
What this is not¶
- A Zoom / Teams / FaceTime clone
- Generic “AI customer support SaaS” with no channel wedge
- Pure remote-desktop as the whole product (permission hell; commoditized)
- BuddyLine / Meela me-too — that lane is companionship; this lane is meeting unstick
Hard constraints (design risk)¶
- Needs OS / accessibility permissions or a human-in-the-loop guidance path
- Host UIs change; brittle click-automation dies — prefer diagnosis + guided steps over full UI control for v1
- Mid-call trust bar is high (mic/camera adjacency) — identify as AI; minimal permissions; no surprise recording
- Stay out of regulated medical claims even if seniors are a wedge
MVP sketch (if un-shelved)¶
- One entry: call or text a known number when stuck mid-meeting
- Scripted playbooks for the top 4 stuck moments (audio, share, photo, chat) × top 3 apps
- Human gate optional for early learning — AI drafts steps; Darcy or a helper can take over until playbooks are solid
- Success metric: unstuck in under ~5 minutes without ending the call
Where this fits (see goals)¶
- Seat 2b (AaaS) candidate wedge — productized “meeting rescue” agent for a client vertical
- Seat 5 adjacency — consumer voice / calm help surface, but job-to-be-done ≠ BuddyLine companionship
- Explicitly not pulled into the current focus window (ECE app / Crusty / Operator creative lane)
Why exploratory (not active)¶
Logged from a 2026-07-13 strategy chat. Pain is real; no prototype or paying pull yet. Keep light. 2026-08-22: current exploration is projects/where-am-i (Beads), not this sidecar.
Open questions¶
- Telephony vs iMessage vs in-OS Accessibility Assist — which channel first?
- Family-paid vs SMB-paid as the first monetization path?
- How much vision (screenshot of the stuck UI) vs pure voice guidance?
- Overlap / handoff with existing family tech-support habits (do people already call a kid)?
Related¶
- projects/buddyline — phone-first senior companion (shelved; Meela incumbent); different job (companionship vs unstick)
- projects/triviabalance — shared senior-audience adjacency if family wedge wins
- goals — trusted access + useful problem-solving; filter against wrapper theater
- What-Im-Working-On — lives under Context / other lines during the focus window
Meta¶
- Created: 2026-07-13 from product-opportunity discussion (Zoom / Teams / FaceTime friction → AI sidecar opportunity).
- Next review: when a family/SMB pull appears — not competing with projects/where-am-i.