All guides

Inbox

The Inbox is your notification centre. Everything dpaperwork needs you to know comes here — and only here. No external Slack messages or emails for system notifications.

Updates arrive in real time — new signals, escalations, check-ins, and approval requests appear as they happen, no refresh needed. You can also get web push notifications for missed messages on your devices (enable them in Personal Settings → Notifications).

What you'll see

What the Inbox shows depends on your role:

Founder

  • Morning Brief — a daily digest of all Monitor signals from the past 24 hours, batched and prioritised. Arrives each morning.
  • Real-time Alerts — immediate notifications for time-sensitive exceptions (e.g. a deal closing today, a client overdue on payment). These fire the moment the condition is detected, not in the batch.
  • Check-ins — when a task goes overdue, the Monitor asks the assignee directly (see below).
  • Automation escalations — when a Playbook fails or gets stuck and no Domain Owner is assigned, the escalation comes to you.

Domain Owner

  • Automation escalations when a Playbook fails or stalls within their Domain.
  • Check-in responses from their team, when a blocked task needs unblocking.

Team Member

  • New Task assignments
  • Mentions in a Timeline
  • Notifications when a Playbook assigns them new work
  • Check-in requests on their tasks

Check-ins

When a task is at risk — typically overdue — the Monitor asks the assignee directly instead of waiting for the founder to notice. The assignee gets an email with a one-tap link to answer: Done, Blocked, or Need more time.

  • Blocked requires a short reason, which posts straight to the task's Timeline
  • Need more time asks for a new due date, and the task's due date moves
  • Every answer is undoable from the confirmation screen — a mistap never silently closes real work

Check-in answers update the task in real time, and open check-ins show up on Home until they're answered.

Monitor signals

The Monitor watches your Workspace on a regular schedule and surfaces risks. Signals it generates for the Inbox:

SignalDefault threshold
Deal with no Interaction logged14 days
Closed Lost deal dormant (re-engagement check)90 days
Cycle untouched in the first week7 days
Cycle entering final stretch with incomplete tasks5 days
Cycle closed without a delivery document sentimmediate
Project with all tasks overdueimmediate
Document sent but not opened48 hours
Task overdue → check-in asked of the assigneeimmediate

You can adjust the deal, workload, and budget thresholds in Settings → Monitor.

Escalations

When Automation is working through a Playbook and hits something it can't resolve — a missing field, an ambiguous condition, a required human approval — it escalates. The escalation appears in the Inbox of the Domain Owner for that Domain. If no Domain Owner is assigned, it goes to you (the Founder).

Escalations include the Playbook name, the step that failed, and the information needed to unblock it.

Approvals

Some Playbook steps (e.g. sending a client email, closing a Deal) require your explicit sign-off. These arrive as approval cards rather than escalations — they show exactly what the step is about to do, with inline Approve and Reject actions right in the Inbox. Approving lets the Playbook continue; rejecting stops the run and records why. See Playbooks → Approvals for the full picture.

Keeping Inbox clean

The Inbox is intentionally kept to things that need your attention. Monitor signals only appear when a threshold is crossed — not every day for every client. Real-time Alerts are reserved for genuinely time-critical items only.

Try it in a walkthrough

Walkthroughs follow one job end to end, in real Chat exchanges: