A calendar that reads your sentence.
Type “Thursday 3pm coffee with Hannah at the depot” and TAO drafts the event with the right attendees, location, and customer link. You approve. It writes back to Google or Microsoft.
What the calendar page does differently
Three panes — month, week, day — and four states for every event (draft, proposed, confirmed, done). Operators move events between states; the workflow record updates with them.
- Natural-language entry across the top of every pane.
- Drafts and proposed events look different from confirmed ones — visually obvious.
- Customer-attached events show the customer’s record beside them.
- Two-way sync with Google Calendar and Microsoft Outlook.
How Andy fills the calendar
Andy reads the workflow and proposes the next event. You see the proposal in your calendar grid; you confirm, edit, or dismiss.
- Proposes follow-up calls based on conversation gaps.
- Books prep blocks before significant meetings.
- Respects working hours and team availability rules.
How the company brain feeds it
The brain remembers when your team actually does its best work, which customers prefer mornings, and how long a particular workflow’s meetings usually run.
- Preferred meeting lengths per workflow type carry forward.
- Customer time-zone and venue preferences are remembered.
- Patterns of double-booking surface before they happen.
For technical readers
The calendar module exposes the same operational record to every other module — so a change here ripples into the relevant workflow, contact, and Andy context automatically. All writes back to providers (where applicable) go through the Approvals queue unless an operator-defined auto-approve rule applies.
Want to see this running on the apps you already use? Apply for the beta, or tell us what your team is trying to run from one place.