Notifications

chrt’s notification system is identical across roles: notification groups route org-wide events to teammates, ad-hoc recipients opt specific people into a single order’s events, and webhooks pipe events into your own systems. The UI lives at the same settings pages as for shippers. This page covers the courier-specific events you’ll typically subscribe to; for the full UI walkthrough, follow the shipper guide.

See Notifications for shippers for the full step-by-step on the three settings pages:

Notification groups — /settings/notifications
Ad-hoc notifications on a specific order — the Notifications tab on an order, plus the bell icon on contact cards.
Webhooks — /settings/webhooks, with the one-click org enable and the Svix-powered management portal.

The rest of this page covers the events couriers care about.

Courier-relevant events

When you create or edit a notification group at chrt.com/settings/notifications, configure the event rows below. Each row supports email, SMS, and push channels independently.

Dispatch events

Event	What it fires on	Who you’d typically route it to
Order assigned to org	A shipper or forwarder tendered you an order.	Dispatch group — needs to act.
Driver assigned to order	Your org assigned a driver to a task group.	Dispatch group — sanity check.
Order accepted	The driver accepted the job in the app.	Dispatch + customer service.
Order declined	The driver declined.	Dispatch — needs to reassign.
Driver started driving	The driver hit Start driving in the app.	Customer-service group — tracking is now live.

Milestone events

Event	What it fires on
Pickup arrived	Driver arrived at a pickup stop.
Pickup completed	Pickup stop completed with required artifacts.
Delivery arrived	Driver arrived at a delivery stop.
Delivery completed	Delivery stop completed (POD captured).
Order completed	Final stop completed; order ends.

Exception events

Event	What it fires on
Order cancelled	Order was cancelled by the shipper or your org.
Driver location stale	The driver app hasn’t reported a location in too long.
ETA breached	Live ETA crossed past the committed time window on a stop.

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.

Order completed is usually the single most-important event for customer-service groups — it’s the trigger for sending the customer their POD email. Many courier orgs route it to email plus push for the customer-service rep so they can immediately follow up.

Ad-hoc per-order notifications

For one-off recipients on a single order — typically the consignee, the shipper’s ops contact, or a third-party expecting POD — use the order’s Notifications tab to add recipients. See shippers/notifications for the full step-by-step.

The bell icon on a stop’s contact card during draft creation is the fastest way to opt a contact into pickup-and-delivery emails for one order without building a notification group.

Driver-facing app notifications

Drivers receive a separate set of push notifications on their phone through the chrt driver app. Those aren’t configured here — they’re managed in the driver app’s settings. See App settings in the driver-app docs for what drivers control on their side.

Webhooks

Webhooks let you receive dispatch and billing events directly into your TMS, ERP, or other systems. Couriers most often subscribe to:

task_group.assigned — feed it into your TMS to spin up a job record.
task.completed — record milestone progress in your own system of record.
statement.opened — pre-stage AP entries for incoming bills.
statement.paid — close out AR on the earnings side.

Enable webhooks at chrt.com/settings/webhooks — see shippers/notifications for the full enable-and-configure walkthrough.

Notifications for shippers — the full UI walkthrough; the courier UI is identical.
Dispatching — the dispatch events you’ll route here.
Billing — the billing events you’ll route here.
Tracking — the milestone events come from the tracking system.
App settings — driver-side push notifications (separate from this page’s org-level configuration).