> This page is for version Staging.
> For other versions, use one of these documentation indexes:
> - Prod (default): https://docs.chrt.com/prod/llms.txt
> - Staging: https://docs.chrt.com/staging/llms.txt
> - Dev: https://docs.chrt.com/dev/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.chrt.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.chrt.com/_mcp/server.

# Notifications

> Practical guide to current CHRT notifications workflows and saved-record checks.

## 1. Notification groups

Open [Organization Notifications](https://chrt.com/notifications/org) 1. A user with permission to manage groups can create a group 2, name it 3, add members 4, and configure event/channel choices. Select from the event rows 5 actually offered, such as **Order Placed**, **Order Completed**, **Driver Assigned**, and **Task Artifact Completed**. Available channels include Email, SMS, and Push.

![The Organization Notifications page with a Create Group button, one notification group showing 1 member and 4 events, the Events, Members and Settings tabs, and a table of events with Email, SMS and Push checkboxes; numbers mark Notifications > Org in the sidebar, Create Group, the group header, the tabs and the event table.](/_fern-files/_img/197f52d5ca2e19ec89e96c6f2906c36530d43f138ff58643f472c4c519078c46.webp)

*Notifications > Org, **Organization Notifications**. **1** **Notifications** > **Org** in the sidebar, **2** **Create Group**, **3** the group header, with the group name and its member and event counts, **4** the **Events**, **Members** and **Settings** tabs, **5** event rows with **Email**, **SMS** and **Push** checkboxes. More event rows continue below.*

## Personal preferences

Open [Personal Notifications](https://chrt.com/notifications/personal) to review your own groups, notification preferences, and SMS phone information. Group configuration and a person’s own preferences both matter when checking a missing alert. Check the saved preferences before repeating an event.

## 2. Ad-hoc notifications on a specific order

Review the contact and notification controls available in the order’s stop details. Use recipients intended for that shipment and check their email information. Do not assume an order notification was delivered because an address was added; verify the actual message with a test recipient.

## 3. Webhooks

Open [Webhook settings](https://chrt.com/settings/webhooks). If the page shows **Enable Webhooks**, enable them only when your team is ready to configure its integration. Once the management portal is available, configure the receiving endpoint and the event subscriptions it needs. Verify the endpoint receives a permitted test event and processes it successfully. Ask an administrator if the page is unavailable.

## Troubleshoot a missing update

Check the active organization, selected event, recipient membership, personal preferences, channel details, and any visible error. For webhooks, compare the portal delivery result with the receiver’s logs. A saved checkbox, a queued message, and a delivered update are separate outcomes.

### Billing events

| Event                         | What it fires on                                                        |
| ----------------------------- | ----------------------------------------------------------------------- |
| **Earnings statement opened** | A shipper or forwarder opened a statement against you (money in).       |
| **Earnings statement paid**   | A statement you opened was paid.                                        |
| **Expense statement opened**  | A driver or partner courier opened a statement against you (money out). |
| **Expense statement paid**    | A statement you owed was settled.                                       |
| **Statement disputed**        | A counterparty added a dispute message on a statement.                  |

## Webhooks

Webhooks let you receive dispatch and billing events directly into your TMS,
ERP, or other systems.

* **statement.opened** — pre-stage AP entries for incoming bills.
* **statement.paid** — close out AR on the earnings side.

## Related guides

* [Getting Started](/staging/couriers)
* [Creating Orders](/staging/creating-orders)
* [Drivers](/staging/couriers/drivers)
* [Dispatching](/staging/couriers/dispatching)
* [Marketplace](/staging/couriers/marketplace)
* [Billing](/staging/couriers/billing) — the billing events you'll route here.