User Story 1: Jira Ticket Adjustment Scenario: In a chat, a QA asks about adjusting a bug ticket. Flow Details: Dialogue Display: Show the actual conversation between QA and the Product Manager. Intent Detection & Action Card: An action card is embedded within the chat window displaying: Detected Jira Edit Request Ticket: MTR-12345 Action Requirements: Downgrade to P3 and move to release version 25.2.30 Draft Comment: "Agree, it is a corner case. Accept to downgrade to P3 and move to 25.2.30." CTA: “Update Jira Ticket” Virtual Flow: Upon clicking the CTA, expand the card to show a pre-execution preview, detailed execution steps (updating the Jira ticket), and final feedback (e.g., “Jira ticket MTR-12345 updated…”), followed by confirmation to send “@QA Done.” User Story 2: Scheduling a Meeting (Outlook Calendar Tool) Scenario: A team discussion about project timelines requires scheduling a meeting. Flow Details: Dialogue Display: Present the conversation among Venky, April, and other team members discussing the meeting. Intent Detection & Action Card: An action card appears in the chat with: Detected Meeting Request Meeting Title: AI Note Design Review Time: AI proposes 3 available time options Participants: Venky Iyer, April Huang, Vita Huang, Erik Liu CTA: “Schedule in Outlook” Virtual Flow: On clicking the CTA, display available time options, allow the user to select a preferred slot, confirm the selection, execute the scheduling, and then provide feedback (e.g., “Meeting scheduled for next Wednesday…”). User Story 3: Leave Request Scenario: A user communicates with their Manager regarding a leave request. Flow Details: Dialogue Display: Show the conversation between April and the Manager regarding the leave. Intent Detection & Action Card: An action card is embedded with: Detected Leave Request Time: Next Monday, 8:00 AM – 11:00 PM Type: Sick leave (proof optional) Reason: Doctor's appointment CTA: “Submit to Workday” Virtual Flow: When the CTA is clicked, present a pre-execution preview of the leave request, execute the submission to Workday, display feedback (e.g., “Ok thank you, I have submitted the Workday request”), and then confirm sending a notification to the Manager. User Story 4: Generating a PPT & Speaker Notes from Meeting Notes Scenario: Within Glip, team members capture project ideas and meeting notes, which need to be transformed into a presentation and accompanying speaker notes. Flow Details: Dialogue Display: Showcase the conversation between Efen, Kervin, and April discussing the project notes. Intent Detection & Action Card: An action card appears featuring: Detected Slide Generation Request Task: Generate a presentation based on shared note content Source Note: “Project Idea & Presentation Content” CTA: “Create PowerPoint Deck and Speaker Notes” Virtual Flow: Once the CTA is clicked, illustrate the process of generating the PPT and speaker notes. Display previews for each slide (e.g., Title Slide, Vision & Problem Statement, How It Works, User Story Examples, etc.), and provide a download link or embedded shareable preview.