Eric uses Console as his central assistant for coordinating calls with founders, LPs, and family offices across multiple time zones. When he tried scheduling, Console showed times in GMT with no clear way to change it. He realized a suggested time was wrong for his local timezone, and his confidence in letting Console “just handle scheduling” dropped sharply. If he can’t trust times, he has to double-check everything manually, which defeats the purpose of the product. User stories • As a new user, I want Console to ask for my timezone during onboarding, so that all my scheduling is correct from day one. • As a busy executive, I want to see my current timezone and change it easily in settings, so I can quickly fix issues when I travel or notice something off. • As a scheduler coordinating across time zones, I want Console to clearly show what timezone each proposed time is in, so I don’t accidentally book people at the wrong hour. Requirements • Onboarding step explicitly asking: “What’s your primary timezone?” with search + sensible default from system. • Clear timezone display in: ◦ Scheduling UI ◦ Event proposals ◦ Confirmation messages • Settings page to change timezone, with immediate effect on scheduling. • Remove “stuck on GMT” behavior; never default to GMT without explanation.
-
Zoom Integration for Scheduling Problem statement Console scheduling cannot yet create Zoom meetings, forcing users to leave the product and manually create links, which breaks the “agent handles logistics” promise. Customer story (Eric / remote-heavy meetings) Eric spends much of his day on remote calls with founders and other advisors. When he tried to understand how Console would manage his scheduling, he asked directly “So how does it integrate with Zoom?” and discovered it doesn’t yet. That means every time Console lines up a meeting, Eric still has to go into Zoom, create a link, and paste it into an invite—exactly the admin overhead he’s trying to escape. User stories • As a Zoom user, I want to connect my Zoom account to Console, so that Console can create Zoom meetings on my behalf. • As a meeting organizer, I want Console to automatically generate a Zoom link when it schedules a meeting, so I don’t have to create and paste links manually. • As a participant, I want the Zoom link included in the calendar invite and any confirmation messages, so joining the call is one tap. Requirements • OAuth-based Zoom integration in settings. • Ability for Console to: ◦ Create Zoom meetings ◦ Attach Zoom URL to calendar events it creates • Per-user preference: default conferencing provider (Zoom vs others later). • Clear indication in scheduling flows that a Zoom link will be created and attached.
-
Agentic Outbound Calling for Scheduling Problem statement Users want Console to actively call other people on their behalf to coordinate schedule, not just act as a passive assistant or Siri-like dialer. This is core to the “real EA” experience Eric is expecting. Customer story (Eric / “Connie” the assistant) Eric has named his Console agent “Connie” and imagines it like a human EA. In his ideal flow, as he’s moving through the day, he says: “Connie, call Alton and see if he’s free Friday at 2pm.” Connie then calls Alton, proposes times, negotiates, and books something—without Eric having to open a calendar. When told the current approach was more like regular calling, he strongly pushed for the more agentic version: he doesn’t want a Siri clone; he wants a proactive human-like assistant. User stories • As a user on the go, I want to tell Console (via voice or text) to call someone and find a time, so I can offload the entire scheduling conversation. • As a recipient of the call, I want to understand clearly that an AI assistant is calling on behalf of [User] to schedule a meeting, so I’m comfortable engaging and can quickly confirm or adjust times. • As a busy executive, I want Console to handle back-and-forth rescheduling via calls or messages, so I don’t have to manually coordinate. Requirements • Command pattern: “Connie/Console, call [contact] and see if they’re free [time window].” • Outbound call capability: ◦ Identify as “[User]’s assistant” ◦ Propose times based on user’s calendar ◦ Confirm chosen time and create calendar event • Post-call summary back to user: ◦ Whether it reached the person ◦ Outcome (confirmed, proposed alternatives, need follow-up) • Respect contact preferences (phone vs SMS/email in future) and local time windows. "