Keep identity outside the conversation.
Account and workspace identity remain explicit in the application. A conversational request uses that established context when it reaches a connected service.
All case studies
Case study / Nova
From a conversation to a useful next step.
A voice-first personal assistant that connects conversation with calls, calendars, email, notes and research, while keeping the state of each action visible.
The context
A thought can become a connected action.
A request can start as a spoken thought and involve several tools. The conversation needs to stay natural while the account, relevant context and connected services remain consistent underneath it.
The engineering challenge
Understanding a request is one step. Carrying it into a connected tool requires the right account, permission and action history. A request being accepted and its outcome being confirmed are different states.
- Product focus
- Voice-first personal assistance
- Focus
- Conversational AI · Connected tools · Action history
Design + engineering
The decisions behind the workflow.
Separate history from working context.
Retained conversations and the information relevant to the current turn serve different purposes. The assistant can use selected context without treating every past exchange as part of every new request.
Give actions a record of their own.
Tool receipts retain the action and its state beyond the immediate response. They distinguish a submitted request, work still in progress and a confirmed result.
Inside the workflow
Follow the work through the system.
Conversation · Context · Connected actions
- 01
Conversation
Start in natural language.
A voice or text request enters the same personal workspace. The experience keeps the request at the center while connected tools handle the next step.
- 02
Context
Carry the right account forward.
The application supplies account and workspace identity to the runtime. Relevant context accompanies the request into connected actions.
- 03
Connections
Bring everyday tools into the flow.
Calendars, contacts, email, tasks, reminders, notes and research can take part in the conversation. Available actions follow the connected services and their permissions.
- 04
Action
Keep the request and result distinct.
A tool receipt records what was requested and what the service returned. Calling also depends on the configured voice service and number.
- 05
Continuity
Let the next conversation pick up the thread.
Conversation history and action records provide continuity. Selected working context keeps each new turn focused on the request in front of it.
Product scope
Everyday tasks, connected by a conversation.
Voice and text
Speak or type into the same assistant experience, with conversation history available across sessions.
Connected actions
Work with calendars, contacts, email, tasks, reminders and notes through connected services and their permissions.
Calling
Place calls through a configured calling service and number, with the request and its progress kept in view.
Research
Gather information as part of a request and carry relevant context into the next step.
Relevant technical work
The system beneath the experience.
Account and workspace context carry through the tool runtime.
Connected tool execution uses configured providers and account permissions.
Conversation history and selected working context have separate roles.
Durable action receipts preserve tool progress and returned outcomes.
The finding
A conversation connected to everyday tools.
A natural conversation needs a dependable action model underneath it: explicit identity, relevant context and a record of what happened.
Discuss a similar move