# Use case

## Best Practices for Inbox

Inbox is most effective when you treat it as a daily ritual — a way to triage signals and return focus to real work.

<table><thead><tr><th width="179.4609375">Best Practice</th><th>Why It Matters</th><th>Examples</th></tr></thead><tbody><tr><td><strong>Make Inbox part of your routine</strong></td><td>Checking at the start or end of the day ensures nothing lingers unseen.</td><td>Each morning, scan Unread to clear yesterday’s updates; each evening, mark read to reset.</td></tr><tr><td><strong>Triage using the Unread filter</strong></td><td>Keeps your view focused on what needs attention now.</td><td>Filter by <em>Unread</em> to review only fresh signals, then mark them read once you’ve acted.</td></tr><tr><td><strong>Act where the work lives</strong></td><td>Notifications are pointers, not destinations — clicking through reduces duplication.</td><td>Click a “Task updated” notification to open the task, update status, or comment directly.</td></tr><tr><td><strong>Use “Mark all read” strategically</strong></td><td>Clears clutter so new updates stand out.</td><td>After catching up at the end of the week, mark all read to start fresh Monday.</td></tr><tr><td><strong>Tune email settings</strong></td><td>Prevents duplicate signals across Motion and your inbox.</td><td>Disable email alerts for mentions if you prefer handling them in Motion’s Inbox.</td></tr></tbody></table>

**Key principle:** Inbox is a signal layer — catch, act, clear. The goal isn’t to live in Inbox, but to use it as a safeguard that keeps you focused on the work that matters.

## Common Pitfalls & How Inbox Helps

Even with a central hub, it’s easy to slip into old habits. Inbox is designed to prevent the most common issues teams face with notifications:

<table><thead><tr><th width="276.81640625">Pitfall</th><th>How Inbox Helps</th></tr></thead><tbody><tr><td><strong>Badge fatigue</strong> → Notifications pile up, and users ignore them.</td><td>Inbox groups all updates in one place with filters and “Mark all read,” making it easy to reset and start fresh.</td></tr><tr><td><strong>Missed updates</strong> → Relying only on email or chat for alerts leads to gaps.</td><td>Inbox centralizes all Motion notifications, ensuring every change is surfaced inside the app.</td></tr><tr><td><strong>Clutter and noise</strong> → Too many non-critical notifications drown out important ones.</td><td>Users can tune subscriptions and email settings to keep signals clean and focused.</td></tr><tr><td><strong>Staying in Inbox too long</strong> → Treating it like another work surface.</td><td>Inbox is designed as a launchpad — click through notifications to act where the work lives, then clear.</td></tr><tr><td><strong>Over-reliance on memory</strong> → Forgetting to circle back to updates.</td><td>The Unread filter works like a “to-do” list for notifications, ensuring nothing slips through.</td></tr></tbody></table>

**Key idea:** Inbox isn’t where you *do* the work — it’s where you make sure no work is missed.

## Connections to Motion

Inbox isn’t an isolated feature — it’s the notification layer that ties the rest of Motion together.

* **Tasks** → Get notified when you’re assigned, mentioned, or when task statuses change. Click through to open the task directly and act.
* **Projects** → See stage changes, mentions, and status updates. Inbox keeps project shifts visible without having to manually check dashboards.
* **Motion Docs** → Get alerted when you’re mentioned in a Motion doc or a comment. Notifications link back to the exact spot for fast context.
* **Teams** → Invitations, mentions, and updates flow into Inbox, so team changes never go unnoticed.
* **Meetings and Bookings** → Notifications confirm bookings and surface completed meeting insights.

**Key idea:** Inbox isn’t where the work happens — it’s the **launchpad** that ensures you see what changed, then jump straight back into the work itself.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.usemotion.com/help/time-management/inbox/concept-inbox/use-case.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
