# CompanyOS · The request is in

*Descriptive transcript · Narrated animatic with example data, not the final film.*

## 0:00–0:05

**Narration:** The request has arrived. But the work cannot start yet.

**Visual:** Text on screen describes the scene: A coordinator in a calm service office receives a request and starts to prepare the handover. On-screen text: “The request is in.”

**Sound:** Quiet room tone.

## 0:05–0:10

**Narration:** One document is missing. One question is still open.

**Visual:** In the CompanyOS window, a request from Jordan Taylor appears: “Could you review the scope using the document I mentioned in my previous message?” Marked as information needed: Referenced document. On-screen text: “What is missing?”

## 0:10–0:17

**Narration:** CompanyOS brings the available information beside the request and prepares the next question.

**Visual:** A printed note marked “document?” slides into the same position as the source card “New client request” in CompanyOS. A cobalt rule marks the handover. On-screen text: “A useful next reply.”

**Sound:** Paper set down on a table. Soft music begins.

## 0:17–0:23

**Narration:** Your team checks the wording and the source before anything goes further.

**Visual:** Beside the source, a draft reply waits for review: “Hi Jordan, we do not have the document mentioned in your message. Could you send it so the team can review the scope?” On-screen text: “Reviewed by your team.”

## 0:23–0:31

**Narration:** A named next step replaces the unclear handover. The missing information stays visible.

**Visual:** The reviewer saves the next step. Saved: Check the document when supplied, then assign the scope review. Status: Awaiting information. On-screen text: “A clear handover.”

**Sound:** Trackpad click.

## 0:31–0:39

**Narration:** CompanyOS. Turn incoming requests into work your team can move forward.

**Visual:** Closing screen: the CompanyOS logo, “Get the work moving.” and “Your company’s AI assistant”.

**Sound:** Soft handover sound, resolving note.
