flow
PRODUCT CONCEPT · CURRENT VS PROPOSED

Good morning, Naman.

This prototype starts with today’s Notetaker, then demonstrates one proposed add-on.

TODAYMeeting audio → transcript, summary, and actionsWispr understands what people say.
→
MISSINGWhich exact screen or component “this” refers toThe visual reference is lost.
→
PROPOSALLink the comment to a screenshot and pointerOne clear visual action brief.
Up nextSynced with Google Calendar
11:30Now
NOTETAKER READY30 minGoogle Meet

Booking Flow Reschedule Review

Current Notetaker will transcribe the meeting and prepare notes.

NJSKAD+1
Naman, Suryansh, Aditi + 1
Next: optionally add proposed Screen Context
Later today
2:00

Growth weekly

8 people · 45 min

4:30

Product × Care sync

6 people · 30 min

RECENT

Your meeting memory

✦
Complete

Therapist availability sync

Notes, 4 decisions, 6 action items

Yesterday · 42 min
⌘
Concept

Proposed screen-aware review

Example of the optional Screen Context add-on

Future experience
＋

Start an ad-hoc note

Record a thought or capture a quick walkthrough.

● Private by default
OPTIONAL · SCREEN CONTEXT

Add the screen to this meeting?

Normal Notetaker is already ready. The proposed add-on lets Wispr connect comments such as “change this banner” to the exact screen being discussed.

◉What was said
＋
▣What was shown
→
✦Clear action

Add Screen Context?

Booking Flow Reschedule Review · Starting now

OPTIONAL
✓
Notetaker is already readyTranscription · Speaker detection · Summary · Decisions · Actions
ACTIVE
⌁

Only during this meeting. Flow understands only the source you choose. Pause it anytime without pausing transcription.

Meeting started00:00

Booking Flow Reschedule Review

Proposed Screen Context is linking important comments to the selected screen.

◉ Notetaker Transcribing · 3 speakers ⌁ Notifications hidden · Sensitive fields excluded NJSKAD3 voices detected
Allo OperationsShared by Naman
4 visual moments
Patients / Patient Profile⌕　?　NJ
AS
Arjun SharmaPatient ID #11842 · Therapy
OverviewAppointmentsSessionsPayments
12AUG
UPCOMINGTherapy session with Dr. MeeraTuesday, 12 Aug · 4:00 PM · Video consultation
◷
20 minutes to undo this changeThe patient can reschedule for free during this window.
✦
Visual moment captured“Make this background light yellow and bold the timer.”
◉Flow sees: Patient Profile → Appointments → 20-minute noticeCursor on policy banner
MEETING ENDED

Creating the visual action brief…

Linking each important comment to the exact screen it referred to.

✓ Normal meeting note ready✓ Important screen moments linked◌ Preparing actions for review
✓
PROPOSED OUTPUT READY

Meeting ended.
The visual action is clear.

Normal Notetaker prepared the notes. Screen Context added the exact screens behind the decisions.

Booking Flow Reschedule Review

19:59 · 3 speakers · 8 visual moments
Complete
What happened

You reviewed four booking states and approved the reschedule release after two visual changes.

3decisions
5actions
ALREADY IN NOTETAKERMeeting intelligence

Transcript · Speaker detection · Summary
3 decisions · 5 participant actions

PROPOSED SCREEN CONTEXT ADD-ONVisual action context

Important screenshots · Highlighted components
Clear visual action brief

▤
Visual action briefPrimary output · screenshots, changes, owners
Ready
▶
Short visual recapPossible later extension
Future
⌘
Reviewed agent packagePossible later extension
Future
FUTURE CONCEPT

Visual action briefs

A possible place to review screen-linked actions from past meetings.

3Ready to execute
14Actions created
42mSaved this week
Recent workflows
⌕
8 visuals
READYToday, 11:52 AM

Booking Flow Reschedule Timer Updates

Update booking and reschedule policy treatments across Patient App and Ops App.

▤ Implementation doc▶ 55-sec recap⌘ Agent package
2 of 5actions ready
40%
→
IN PROGRESSAug 5

Care Ops Dashboard Filters

4 visuals · 3 actions · Agent package

DRAFTAug 1

Therapist Availability Rules

2 visuals · 4 decisions · Document

✓ Saved
PROPOSED OUTPUT · SCREEN CONTEXT ON

Booking Flow Reschedule Review

Normal meeting notes plus the exact screens behind important decisions.

NJSKAD
COMPLETE

Meeting summary

The team reviewed booking, rescheduling, release, and change-mode flows. The current logic is approved for release after two visual updates to the grace-period notice.

3 decisions5 actions3 speakers
✓

Decisions

  • Keep one shared 20-minute timer across frontend and backend.
  • Rescheduling inside the grace period does not consume a session.
  • Release after the persistent notice and copy changes are verified.
→

Next steps

  • Suryansh: Apply the visual treatment across booking and reschedule states.
  • Aditi: Verify Patient App and offsite tick-mark states.
  • Naman: Run regression on release and change-mode flows.
12:45Suryansh

“Make this background light yellow and bold the timer. Keep the same 20-minute source of truth.”

PRIMARY PROPOSED OUTPUT · VISUAL ACTION BRIEF

Reschedule experience:
timer and policy updates

Each action shows what was said and the exact screen it referred to.

3 decisions5 actions8 screenshots
01

Executive summary

The team approved the current booking and reschedule logic for release. Before launch, make the grace-period notice unmistakable across Ops App, Patient App, and offsite booking.

✓

Primary decision
Keep one shared 20-minute timer across frontend and backend. Do not introduce a separate client-side counter.

02

Visual implementation instructions

Allo Operations · Patient Profile
20 minutes to undo this change1
UI CHANGE

Make the persistent notice unmistakable

  1. Apply the semantic warning-subtle background.
  2. Bold only “20 minutes” to preserve hierarchy.
  3. Keep the supporting line at 14px regular.
SKSuryanshOwner · Frontend
Reschedule modal
Reschedule appointment19:42 remaining2
DECISION

Keep the timer at 20 minutes

Continue reading from the backend expiry timestamp. The frontend renders the countdown but does not own timing logic.

SKSuryanshOwner · Full stack
03

Owners & actionables

ActionOwnerSourceStatus
Allo OperationsPatient Profile
20 minutes to undo this change
Make the persistent notice unmistakable.
Suryansh · “This needs to be much more obvious.”
03 · PERSISTENT NOTICE
00:3200:55
POSSIBLE LATER EXTENSION

Send the reviewed brief to Codex or Claude

Only after a person checks the screenshots, task, owner, and expected result.

Future
workflow.md
# Booking Flow Reschedule Timer Updates

## Objective
Update the booking and rescheduling experience shown in the attached evidence.

## Context
- The grace-period timer remains 20 minutes.
- Backend expiry is the single source of truth.
- Rescheduling inside the window does not consume a session.
- Changing appointment mode is always free.

## Tasks
1. Apply the warning-subtle background to the persistent notice.
2. Bold only the “20 minutes” policy copy.
3. Verify Patient App and offsite tick-mark states.

## Acceptance criteria
- Treatment matches screenshots `moment-03.png` and `moment-06.png`.
- All counters derive from the backend expiry timestamp.
- Existing release and change-mode flows pass regression.
- Mobile notice wraps without obscuring the dismiss action.

## Dependencies
- Confirm `warning-subtle` token exists in the shared design system.
- Activity mapping must land before communications are enabled.
8 annotated screenshots497 transcript moments3 linked decisions4 acceptance criteria
✓