jetontrack.
Delivery notifications

Tell customers what changed. And what comes next.

Build useful delivery communication around meaningful events. Give every message a recognizable order, a clear explanation, and a reason for the customer to act—or wait.

Delivery notificationsIllustrative workflow · sample data
j.
Order contextJT-DEMO-1048
Latest known event

Actionable exception messages

“Is the team handling this, or do you need something from me?”

Next step
Review with the team
Milestone delivery updates
01 / Overview

What the workflow covers

Choose events that matter

Map shipment confirmation, out for delivery, delivered, and action-required exceptions to distinct messages. Repeated scans should not turn into repeated customer updates.

Write around the customer’s task

A progress update helps someone check an order. An address message asks for a specific response. Keep the next action visible instead of filling every template with the same text.

Review language and context together

Check the subject, status, tracking link, and support route as one message. A translated heading alone cannot explain a cross-border delivery issue.

02 / Delivery notifications

Follow the journey

Explore the workflow
  1. 01

    Select the event

    Choose the delivery milestone and decide what counts as a new, meaningful update.

  2. 02

    Define the audience

    Set the customer language and the communication preferences your process must respect.

  3. 03

    Preview the message

    Read the order reference, known fact, and next action together using a sample order.

  4. 04

    Review the edge cases

    Check missing data, repeated events, and an exception before agreeing on production delivery rules.

03 / Who does what

Who does what

Operations validates the trigger

Define which event is reliable enough to start a customer communication.

Brand and support review the words

Keep the tone familiar while making the required action and contact route precise.

When the journey changes

The same event appears twice

Define a deduplication rule using the parcel, milestone, and event identity before enabling a send process.

The language is missing

Choose an explicit fallback and check that the support contact can handle the language shown.

05 / Illustrative workflow · sample data

Explore the interactive example

Explore local sample records. Actions in this preview do not change a real shipment or send a customer message.

JetonTrackYour delivery workspace
Interactive sample

Make each update useful.

Choose an event and customer language to preview a message.

Shipment event
When this message would appear

When the sample parcel is with the local delivery driver.

Email preview
YOUR BRANDTo: alex@example.com
JT-1047

Your delivery is getting close

Hello Alex,

Your parcel is with the local delivery driver. Check the order page for the latest delivery update.

Example email. No message is sent.
Fictional orders. Changes stay in this demo.
Your next market starts here

Make the journey after checkout a reason to come back.

Tell us about your markets, shipment volumes, and customer experience. We’ll help shape the right JetonTrack setup.

Book a demo