Waiting & follow-ups

The things other people owe you

Mark an action as waiting, name the person, pick a follow-up date. Zephyr keeps the clock and drafts the chase — then waits for you to approve it.

The waiting problem

Half your workload is other people's

Nothing in a normal task list represents "I asked for this and it hasn't come back". So it lives in your memory, and it's the first thing to go.

Mark it waiting, then stop thinking about it

Set an action to waiting, name the person, and pick when you'd want to chase. That's the whole interaction. Zephyr holds the clock.

When the follow-up date passes, it surfaces the item, drafts a follow-up message in your voice from the original context, and puts it in front of you with the approve step attached. You edit it or you send it. You never come back to an outbox full of things it sent for you, because it can't.

  • Waiting-for view. Everything outstanding, by person, oldest first.
  • You promised. The mirror image — commitments you made that someone else is waiting on.
  • At risk. Items whose deadline is close and whose dependency hasn't moved.
  • Drafts, never sends. Generating the follow-up and sending it are two different steps, and only one of them is automatic.

External communication always requires approval. This is not a setting. In the current release there is no configuration, plan or automation level that lets Zephyr send an email or a message on its own — the capability does not exist in the backend.

A note on notifications. Follow-ups surface in the app's own inbox — the bell on the Today screen. Background push notifications while the app is closed are a deliberate not-yet: they need an extra dependency and a notification permission story that hasn't been designed. It's on the roadmap.

See it on your own work.

Zephyr is in development for iOS and Android. Join the early access list.