> ## Documentation Index > Fetch the complete documentation index at: https://docs.tryoto.com/llms.txt > Use this file to discover all available pages before exploring further. # Collaboration & notifications > Discuss an order on the order itself, follow everything addressed to you in the Communication Center, and choose which notifications you receive. Most of what goes wrong in fulfillment is discussed somewhere — a chat group, a reply-all, a note stuck to a monitor. The point of putting it on the order is that the next person to open that order can see it. ## The Communication Center Everything addressed to you sits in one place, reached from the icon in the header. It has three tabs and a two-pane layout: the list on the left, the detail on the right. | Tab | What it holds | | - | - | | **Notifications** | What the platform is telling you — an SLA breach, a failed delivery, a finished export. | | **Threads** | Conversations you are part of or following. | | **Order Comments** | Discussion attached to specific orders. | Each tab filters by **All**, **Read** or **Unread**, so the question “what have I not dealt with” is one click rather than a scroll. ## Talking on the order Comments live on the order itself. You can mention a colleague to bring them in, follow a thread to be told when it moves, and unfollow one that no longer concerns you. Read and unread state is tracked per person, so a thread being resolved for you says nothing about whether anyone else has seen it. > [!TIP] > > **The value is what happens six weeks later** > > A conversation in a chat group is gone by the afternoon. The same conversation on the order is still there when a customer disputes the delivery, when finance queries the surcharge, or when a new joiner asks why that order was handled differently. > > It also removes the worst question in operations — “who was dealing with this?” — because the answer is on the record rather than in someone's memory. ## Notification settings At **Settings → Notifications**, each person chooses what reaches them and how. **Nineteen notification types** across five groups, each with two independent switches — **In-App** and **Email**. Changes are committed with **Save** rather than applying as you toggle. ### Order Management System | | | | - | - | | **New Orders** | Newly received orders. | | **Order Need Confirmation** | Orders waiting on a confirmation step. | | **Order Missing Information** | An order arrived incomplete. See [address and data correction](https://docs.tryoto.com/modules/omnichannel-oms/order-data-correction.md). | | **Orders On Hold** | An order was placed on hold. | | **Order Returned** | An order is going back to origin. | | **Delivered Orders** | Orders delivered by the carrier. | | **Return Received** | A returned order has arrived. See [returns receiving](https://docs.tryoto.com/modules/return-management/returns-receiving.md). | ![The Order Management System group of OTO notification settings, each row with an In-App and an Email toggle](https://mintcdn.com/oto/YkJay8Y-1RDv8ciw/images/plat-1-notif-oms.png?fit=max\&auto=format\&n=YkJay8Y-1RDv8ciw\&q=85\&s=0419a467ededabe83665a463971c266e) Fig. 1 — Two switches per row, set independently. The pattern above is a realistic one — email for what needs acting on away from the screen, in-app for the rest. ### Shipping Management System | | | | - | - | | **Drop-off Shipment Reminder** | A daily reminder listing shipments waiting to be dropped off. | | **Shipment Created** | A shipment was booked with a carrier. | | **Shipment Creation Attempt Failed** | A shipment could not be created. The order is sitting still until someone acts. See [webhook events](https://docs.tryoto.com/developers/webhook-events.md) for the same signal delivered to your own systems. | | **Return in Progress** | An order is on its way back to origin. | | **Orders Held for Pickup** | Shipments awaiting collection. | | **SLA Breach** | A promise was missed. | | **Pickup Delay** | An order has passed its pickup date. | | **Warehouse Shipment Notification** | Notifies the *assigned warehouse* whenever a shipment is created, with the shipment's details — so the site that has to act knows without anyone forwarding it. | > [!TIP] > > **Two of these are the ones that catch silent failures** > > **Shipment Creation Attempt Failed** and **SLA Breach** both fire on situations where nothing else happens. A shipment that was never booked produces no status change, because nothing changed; a breached SLA produces no error at all. > > Every other notification here tells you about something that already worked. These two tell you about something that did not, which is why they are worth subscribing to even when the rest are muted. ### Payments and Charges | | | | - | - | | **Surcharge** | A shipment picked up an unexpected charge. See [invoice reconciliation](https://docs.tryoto.com/modules/shipping-management/shipping-invoices-reconciliation.md). | | **OTO Credit Balance** | Your credit has dropped below a threshold you set. The threshold itself is a **Minimum Credit Balance** field on the same row. | > [!WARNING] > > **Set the credit threshold high enough to be useful** > > This is the notification that prevents an operational stop: run out of credit and shipments stop being created, which looks exactly like an integration failure to everyone downstream. > > The threshold should cover more than a day's shipping, because it needs to leave time for somebody to notice, approve and pay. A number that gives you an hour's warning gives you no warning at all. ### Basic Warehouse Management System | | | | - | - | | **Low Stock** | An SKU has fallen below its minimum stock level. | | **Out of Stock** | A product has run out. See [inventory tracking](https://docs.tryoto.com/modules/inventory-management/inventory-tracking.md). | ### General Announcement | | | | - | - | | **Announcement** | Platform announcements from OTO. See [Announcements](https://docs.tryoto.com/platform/announcements.md). | | **Notification Sound** | How often a sound plays when a new notification arrives — **Single**, **3 times**, **5 times** or **Repetitive**. | ![The lower half of the notification settings screen, showing the OTO Credit Balance threshold field, stock notifications, and the announcement and notification sound controls](https://mintcdn.com/oto/YkJay8Y-1RDv8ciw/images/plat-2-notif-tail.png?fit=max\&auto=format\&n=YkJay8Y-1RDv8ciw\&q=85\&s=309af4a40138b32b9d68e2255ff13cf7) Fig. 2 — The credit threshold and the sound setting are ordinary rows on the same screen, easy to scroll past and worth setting deliberately. > [!WARNING] > > **Subscribe by role, not by appetite** > > The temptation on a settings screen full of switches is to turn everything on. Two weeks later the notification center is unreadable and the one that mattered — an SLA breach, a surcharge — scrolled past unseen. > > The durable pattern is to decide per role. A warehouse manager wants **Low Stock** and **Pickup Delay**. Finance wants **Surcharge**. Customer service wants **Delivery Failed**. Almost nobody needs **New Orders**, because the orders list already says that and says it better. > [!TIP] > > **Email for what needs acting on away from the screen** > > The two channels are independent on purpose. In-app is for someone already working in OTO; email is for reaching them when they are not. > > A useful rule: if a notification needs action within the hour and the person is not necessarily in the dashboard, send email too. Otherwise in-app alone, or the inbox stops being a signal. ## Related * [Announcements](https://docs.tryoto.com/platform/announcements.md) — platform news, and where it appears. * [Customer Notification](https://docs.tryoto.com/modules/customer-notification/overview.md) — the outward-facing equivalent, for customers rather than staff. * [Users, roles & permissions](https://docs.tryoto.com/platform/users-roles-and-permissions.md) — who exists to be notified. ## Related topics - [Platform announcements](https://docs.tryoto.com/platform/announcements.md) - [Webhooks for real-time updates](https://docs.tryoto.com/integrations/webhooks.md) - [SMS notifications](https://docs.tryoto.com/modules/customer-notification/sms.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.