About ModePilot

Why ModePilot exists.

ModePilot began with a simple problem: important calls were being interrupted by Slack notifications. We built ModePilot so the calendar could protect those conversations automatically, with rules for different kinds of calls.

— The starting point for ModePilot

A small frustration pointed to a missing layer.

The idea grew into a configurable connection between the calendar and the tools people use throughout the day.

The calendar already knows what’s happening.

Your calendar already holds much of the plan: meetings, focus time, breaks and changing hours. ModePilot turns that information into actions across your tools, using rules you choose.

Different workdays need different rules.

Every workday has its own shape. One person needs DND during client calls. Another needs availability to follow focus blocks. Someone else works split shifts, changes their hours, or needs different rules for different kinds of meetings.

ModePilot’s design philosophy

Structure without prescription.

ModePilot provides the framework for calendar-driven automation, while leaving the rules—what changes, when it changes, and how it should behave—to the individual.

See how ModePilot fits your workday.

Add the missing layer.

ModePilot connects your calendar to the tools you use throughout the workday.

Get started

Google Calendar setup comes first. Slack can be connected later.