Invisible changes are harder to trust
A status update or DND session feels more dependable when the exact transition remains visible after the moment has passed.
Activity history
See what ModePilot did over time.
ModePilot keeps a visible history of status changes, DND changes, mode switches, and triggered events so you can review how the day was interpreted instead of treating the automation like a black box.
Get startedAutomation should not feel like a black box
ModePilot changes Slack and workday boundaries on your behalf. You should be able to see what it did, when it happened, and what prompted the decision—without digging through technical logs.
Everyday questions deserve simple answers
Why did Slack change? When did focus begin? What ended the workday? The answer should not depend on reconstructing the calendar from memory.
A useful history is not a surveillance dashboard
The goal is confidence in your own automation—not employee monitoring, compliance reporting, or a wall of backend events.
Every change should stay explainable.
History is not surveillance.
Visible decisions are easier to trust.
A readable history of every user-facing change
ModePilot turns status updates, DND sessions, mode changes, schedule transitions, and overrides into a practical timeline you can understand at a glance.
Review the signals other people saw
See when Slack status, emoji, availability, or DND changed as the day moved through calls, focus, lunch, and after-hours time.
- Record visible Slack changes
- Show when they happened
- Keep the trigger legible
Status updatedCalendar context read 09:00Work state changed 09:01Connected signal updated 09:01
See when protection started and ended
Review each DND window alongside the meeting, focus block, break, or boundary that made Slack go quiet.
- Track protection windows
- Show start and end
- Connect them to context
DND sessionCalendar context read 09:00Work state changed 09:01Connected signal updated 09:01
Follow the workday from one state to the next
See when a configured mode began, when a break or schedule boundary took over, and what prompted the transition.
- Record starts and finishes
- Explain breaks and boundaries
- Keep schedule logic visible
Schedule transitionsMorning window 8:00–12:00Offline block 12:00–3:00Second window 3:00–6:00
Keep manual decisions distinct
Focus overrides, early finishes, breaks, and other intentional exceptions stay visible alongside automatic changes.
- Identify deliberate exceptions
- Separate manual from automatic
- Review overrides later
Quick controlsStart focusTake a breakEnd workday
See every automated change remain visible and explainable
The point is not abstract observability. It is being able to answer the practical questions that come up after the system already acted.
Booked call changes Slack
What changesA calendar meeting begins.ModePilot responseModePilot activates the matching meeting mode.
ResultHistory connects the event, mode change, and resulting Slack update.01Booked call changes Slack
What changesA calendar meeting begins.ModePilot responseModePilot activates the matching meeting mode.
ResultHistory connects the event, mode change, and resulting Slack update.02One-hour focus override
What changesA manual focus block starts for the next hour.ModePilot responseModePilot temporarily prioritises the override over the calendar-driven state.
ResultThe override and its later end appear clearly in the activity trail.
03Calendar clears early
What changesThe remaining events in the workday end early.ModePilot responseModePilot re-evaluates the day against the calendar and schedule boundary.
ResultHistory shows why after-hours behavior started earlier than a fixed timer would suggest.
04Out-of-office period
What changesAn out-of-office calendar block becomes active.ModePilot responseModePilot treats it as a distinct longer-away state.
ResultThe activity trail separates the transition from ordinary breaks or quiet periods.
Understand each change in your day
Activity history keeps automation explainable. It is lighter and more practical than the totals, targets, and forecasts in time tracking.
Time tracking and summaries
Manual · Rigid · Outdated fast
- Answer how much time was logged across the day or week.
- Support totals, forecasts, and target visibility.
- Center on work-time understanding rather than individual automation events.
Activity history
Adaptive · Contextual · Always current
- Answers what changed, when it changed, and what triggered it.
- Keeps Slack, mode, and boundary automation reviewable after the fact.
- Supports trust in the system without turning it into a reporting dashboard.
Slack status automation
See how status, availability, emoji, and DND changes become visible in Activity History.
Manual overrides
Read how quick focus, break, and end-workday actions sit on top of the broader automation model.
Calendar-based time tracking
See totals, forecasts, and weekly work-time visibility in Time Tracking.
After-hours boundaries
See how reviewable day-end behavior supports a trustworthy switch-off.
Frequently asked questions
Trust the automation because you can still inspect it.
ModePilot keeps a readable trail of what changed, when it changed, and why, so the product stays explainable even when the day keeps moving.
Get started
Google Calendar setup comes first. Slack can be connected later.