Notifications

Route order, billing, and tracking events to the right teammates and customers — and enable webhooks for system-to-system integrations.

chrt has three notification mechanisms that work together: notification groups for routing org-wide events to teammates, ad-hoc notifications for adding external recipients to specific orders, and webhooks for piping events into your own systems. This page walks through all three.

Before you start

  • Notification groups live at /settings/notifications and are managed by owners and admins.
  • Webhooks must be enabled at the org level before you can configure endpoints. The enable step is a one-click toggle on /settings/webhooks.

1. Notification groups

A notification group is a curated list of teammates that receives a specific set of events on specific channels (email, SMS, push).

Create a group

  1. Open Notifications settings.
  2. Open the Organization notification groups section.
  3. Click Create group and give it a name (e.g., “Dispatch”, “Ops weekend”, “Finance”).
  4. Pick the members who should be in the group.
  5. Configure which events the group should receive (order staged, order completed, task completed, invoice opened, exception events) and which channels to use per event (email, SMS, push).

Group settings are at the org level. Individual members can opt themselves out of a group’s notifications from their own notification settings without needing an admin to remove them.

Opt yourself in or out

From Notifications settings, open My notification groups. Each group card shows the events it covers and the channels available; toggle the rows you want on or off for yourself.

Members who’ve opted out appear in a collapsible Users who opted out section on the group’s admin view so owners can see at a glance who’s not receiving alerts.

2. Ad-hoc notifications on a specific order

Notification groups are good for routing org-wide events. For one-off recipients on a single order — typically the end recipient or a customer’s ops contact — use ad-hoc notifications.

Add an ad-hoc recipient

  1. Open the order at chrt.com/orders/<order-ref>.
  2. Switch to the Notifications tab.
  3. Click Add recipient and pick from your directory (or add a new contact).
  4. The recipient receives emails on the order-staged and order-completed events. Toggle off or delete the recipient any time to stop emails.

You can also use the bell icon on a contact card during draft creation (or on the order page’s stop details) to opt that specific contact into email notifications without leaving the draft builder.

3. Webhooks

Webhooks let you receive chrt events directly into your own systems — TMS, ERP, monitoring, anything that can accept HTTPS POSTs. chrt’s webhook delivery is powered by Svix.

Enable webhooks for your org

  1. Open Webhook settings.
  2. If webhooks aren’t already enabled, you’ll see the Enable Webhooks prompt with a short description of what enabling unlocks:
    • Receive real-time notifications.
    • Configure multiple endpoints.
    • View delivery logs.
    • Test endpoints.
  3. Click Enable Webhooks to flip the toggle for your org.

Enabling webhooks is an org-level setting. Once enabled, the webhook management portal is visible to anyone in your org who can see settings — endpoints, payloads, and signing secrets included.

Configure endpoints

Once enabled, the Webhook settings page shows the embedded webhook management portal. From there you can:

  • Add an endpoint — paste your HTTPS URL.
  • Subscribe to event types — pick which chrt events should fire to this endpoint.
  • Test the endpoint — chrt sends a sample payload so you can verify signature validation and basic plumbing.
  • View delivery logs — every delivery attempt, response, and retry shows up here.
  • Rotate signing secrets when you need to.

How to know it worked

  • Notification groups. Test by triggering a small event (e.g., stage and cancel a test order). Members of subscribed groups should get the corresponding email/SMS/push on the channels you configured.
  • Ad-hoc notifications. Stage the order — the ad-hoc recipient should get an email within a minute or two.
  • Webhooks. Use the portal’s Test endpoint action; you should see a delivery row appear in the log with a 2xx response.

If something looks different

  • You’re an admin and you can’t see the org-wide groups section. Confirm you signed in to the correct org and that your role is Owner or Admin.
  • A teammate isn’t receiving alerts. Check whether they’ve opted out of the group from their own notification settings; the Users who opted out rollup on the group’s config view lists them.
  • Webhook deliveries return 4xx. Check your endpoint logs first. Then in the portal’s delivery log, expand the failed delivery to see chrt’s request body and headers — most failures are signature validation mismatches or wrong content-type handling.
  • You don’t see the bell icon on a contact card. Confirm there’s an email address on the contact — the bell only enables when chrt has somewhere to send the notification.
  • Contact hi@chrt.com if you have issues.
  • Tracking shipments — the order-level Notifications tab is also a quick way to add ad-hoc recipients on a per-order basis.
  • Public tracking links — share the live map alongside notification emails for full visibility.
  • Add an organization member — members need to be in your org before they can join a notification group.