Skip to main content
OchroniLoginStart free trial
ProcessPricingQuestionsLoginBook a demoStart free trial
Home/Logistics incident customer messages

Logistics incident customer messages.

Write first, next, and last customer messages for one logistics incident. State facts, sources, impact, tasks, unknowns, and message times.

Start free trialBook a demo

Published August 3, 2026 · Reviewed July 18, 2026 · First · next · last messages · One incident · Active token link

Customer messagesFirst message · next message · last message

Synthetic example — not a customer case study.

Write the current status.

A responder writes each customer message. An authorized team member can publish it. Ochroni records the message, publication time, and incident event in the incident record. The status page shows published messages for one incident. Anyone with the active token link can open it without a login. Publication does not prove delivery, receipt, acknowledgement, or response.

07:14

Check one fact.

07:30

Write the next message.

07:45

Write a new message.

08:20

Write the last message.

Summary

A responder writes the text. An authorized team member publishes it. Ochroni records the publication time. Use other evidence for delivery, receipt, acknowledgement, or response.

The incident record and external evidence stay separate.

Customer messages

Write first, next, and last messages for one incident

Use checked information. Set a time for the next message. Use your legal process.

Message recordFact · impact · task · time
FirstFirst message fields

Fact

One fact · source · 07:14 CET

Impact

Current impact · scope unknown

Task

Replacement task

Unknown

Slot unknown

Next message

07:30 CET

Responder

One responder
NextNext message fields

Fact

New fact · source · 07:32 CET

Impact

Current impact

Task

Active task · team member

Unknown

Source conflict

Next message

07:45 CET

Responder

One responder
LastLast message fields

Condition

End condition

Source

Source · 08:20 CET

Status

Incident resolved

Risk

Remaining risk

Review time

22 July

Next task

Review task · team member

Keep one incident record

Record the source and time for each fact. Keep this message separate from delivery evidence in email, SMS, or another source.

1

First message

Record one fact, its source, current impact, active task, unknown fact, and next message time.

  • Record the fact.
  • Record the source.
  • Record the current impact.
  • Record the active task.
  • Record each unknown fact.
  • Record that time.
2

Next message

Record each new fact, source, impact, task, and message time for the next customer message.

  • Record a new fact.
  • Record the current impact.
  • Record each active task.
  • Record a source conflict.
  • Write a new message after each error.
  • Record the new message time.
3

Last message

Record the end fact, source, risk, next task, reopen time, and next message time.

  • Record the end fact.
  • Record the source.
  • Record the risk.
  • Record each next task.
  • Set the next message time.
Open the declaration pageDeclaration to closureOpen the incident roomIncident room guideOpen the pagePost-incident review

Message boundaries

What Ochroni records and what it does not

Separate product facts from source facts, invented examples, and limits.

Ochroni record

Ochroni records the message, publication time, and incident event in the incident record.

Status page publication

The status page shows each message for one incident. Anyone with the active token link can open it.

External evidence

Use other evidence for delivery, receipt, acknowledgement, or response.

Source fact

Record the source and time for each important fact.

Invented example

This example uses invented roles, times, and events.

Limit

Publishing a customer message does not send it by email or SMS. Ochroni sends other system emails.

Message checklist

Check before publishing

Check each message before an authorized team member publishes it.

  • Record the incident.
  • State the confirmed fact.
  • Record the fact source.
  • State the current impact.
  • Record each active task.
  • Record each unknown fact.
  • Record each source conflict.
  • Record the next message time.
  • Set the trigger for an earlier message.
  • Separate publishing from delivery, receipt, acknowledgement, and response.
  • Record the end condition for the last message.

Message rules

Choose facts before words

Use this guide for communication. Follow safety, law, regulation, contracts, and customer commitments.

Write one verified fact

Check one fact. Record its source. Record each unknown fact.

  • Record the source.
  • Record the unknown.

Set the next message time

Set an exact time and timezone. Write a new message.

  • State the next time.
  • Write a new message.

Follow the controlling process

Follow safety, legal, regulatory, contract, and customer rules. Use another team member when required.

  • Follow the required process.
  • Protect private incident data.

Product boundary

What Ochroni records

Ochroni records customer messages. External evidence stays separate.

Message record

A responder writes each customer message. Ochroni does not create the text. An authorized team member can publish it.

Status page

The status page shows customer messages for one incident. Anyone with the active token link can open it. The active token link requires no login.

Evidence limit

Publication does not prove delivery, receipt, acknowledgement, or response. Publishing does not send the customer message by email or SMS.

Corrections

A correction is a new message. The status page keeps both messages.

Source events

Ochroni receives events from connected source systems. It does not detect logistics conditions. A matching event can create a Signal for review.

Pricing

EUR 299 each month for the response team.

Use one customer message during the trial. Do not use customer or private information. Contact Ochroni about your process.

The public price does not include VAT. EU B2B reverse charge may apply.
EUR 299 each monthPay EUR 2,990 each year. Save two months.
  • Include all team members under fair-use terms
  • Use the incident room, tasks, incident record, and guest links
  • Use the product free for 14 days
  • Start without a payment card
  • Cancel renewal at any time

Fair-use terms apply to all team members and participants. The Terms of Service describe them.

Start free trialBook a demo

One plan

The price applies to the response team.

  • Include the response team in one plan
  • Start the trial
  • Use tasks and incident records
  • Publish customer messages

Review note

Customer message sources

Reviewed

July 18, 2026

What we compared

Sources cover incident messages and evidence. They do not endorse Ochroni.

Check these facts

Follow your safety, legal, regulatory, contract, and customer procedures. Check external facts at their source.

Contact us about a fact.
  1. 01
    Ochroni home

    Ochroni · checked August 1, 2026

    Public price and trial for Ochroni.

  2. 02
    Communicating during an outbreak or public health investigation

    U.S. Centers for Disease Control and Prevention · checked July 18, 2026

    The source guides early communication, known and unknown facts, and further updates. We adapt it outside public-health context.

  3. 03
    Traffic Incident Management Handbook

    U.S. Federal Highway Administration · checked July 18, 2026

    Transport-adjacent guidance on incident information, inter-agency communication, action review, and continuous improvement.

FAQ

Review these questions.

Who writes each customer message?

A responder writes each customer message.

Does publishing prove delivery?

No. Ochroni records the message and publication time. Use other evidence for delivery, receipt, acknowledgement, or response.

Does publishing send email or SMS?

No. Publishing a customer message does not send it by email or SMS. Ochroni sends other system emails.

Does a correction replace the earlier message?

No. A correction is a new message. The status page keeps both messages.

Does Ochroni detect logistics conditions?

Ochroni receives events from connected source systems. It does not detect logistics conditions.

Can teams keep Slack or Microsoft Teams?

Yes. Use Ochroni for incidents. Use Slack, Microsoft Teams, or email for other work.

Can guests join an incident?

Yes. Guests use guest links from a phone browser.

Where does Ochroni store customer content?

Ochroni stores customer content in the EU. Review the Privacy Policy and DPA.

Can we review security before a trial?

Yes. Book a demo for security questions before a trial.

OCHRONI

Review an incident.

Review the messages in the trial. Contact Ochroni about your process.

Start free trialBook a demo

Use no customer or private information in the trial.