Inbox and Calendar
Inbox and Calendar are live operating surfaces that provide communication and time context for Chat, Contacts, and Automations.
Audience: Users managing communications, meetings, and follow-up work.
Current Version
1.0
Documentation aligned to the current operational build of Chat, Automations, Contacts, and workflow runtime.
Scope
1
A standalone documentation page with a stable URL you can share directly.
Quick Start
How the system is meant to be used
Step 1
Read the platform overview first so you understand how Chat, apps, and runtime work together.
Step 2
Start your first conversation in Chat with a real business outcome, not just a general prompt.
Step 3
Let Nexus turn that intent into a durable record, workflow, or next-step artifact.
Step 4
Connect the systems required for context, communication, and execution as setup requires.
Step 5
Move into the relevant app surface to review, manage, approve, and operate the resulting work.
Operating Principle
Chat compiles. Apps operate. Runtime executes.
Nexus is not a chatbot that happens to call tools. It is a structured operating system where conversational intent is translated into durable records, validated state, and auditable actions.
This docs site is the product-level reference for how that model works today and how the current 1.0 surfaces fit together.
Audience
Users managing communications, meetings, and follow-up work.
Inbox and Calendar
Inbox and Calendar are live operating surfaces that provide communication and time context for Chat, Contacts, and Automations.
Philosophy
Communication and time are not side data. They are core operating context. Nexus treats inbox and calendar as active work surfaces that should inform follow-up, relationships, and automation.
Technically Managed By
- Inbox and Calendar aggregate communication and scheduling context from connected providers.
- Messages and events should resolve back to canonical contacts and workflow context where possible.
- These surfaces provide live inputs that other parts of the system can use for drafting, follow-up, and automation.
How Users Should Use and Manage It
- 1Review messages and meetings in context instead of as isolated events.
- 2Use Chat when you want summaries, follow-up help, or action extracted from communication history.
- 3Use these surfaces as operational context sources for Contacts and Automations.
How It Fits in Nexus
- Inbox and Calendar are the communications and commitments layer of Nexus.
- They enrich Contacts, inform Chat, and create operational triggers for workflows.
- They help turn Nexus into a live operating system instead of a static dashboard.
What Matters
- Inbox and Calendar are meant to be operational context, not passive data views.
- Messages and meetings become more useful when they resolve back to contacts and workflows.
- These surfaces help Nexus connect communication, commitments, and follow-up work.
Reference Notes
Next Step
Use the docs as the product contract.
As new apps and runtime behaviors ship, extend this documentation hub first so users and internal teams have one clear reference for how Nexus is supposed to work.