LogStat
Collaborative

SHIPMENT_STATUS_NOT_FOUND

intent SHIPMENT_STATUSstate NOT_FOUNDlang env1

Template

Subject

Re: Load {load_number}

Hi {customer_contact_name},

We couldn't locate load {load_number} in our system.

If you can send the BOL, PRO, or PO number, we'll track it down right away.

Thanks,
{company_name}

Variables used

  • 🔒company_name
  • customer_contact_name
  • 🔒load_number

Highlighted are required — §64 fails the render rather than substituting a blank. 🔒 marks identifiers §65 forbids translating; a localised load number is a support ticket.

Preview

Re: Load 84721

to john@acme-test.com

Hi John,

We couldn't locate load 84721 in our system.

If you can send the BOL, PRO, or PO number, we'll track it down right away.

Thanks,
LogPac Operations

Available fields

customer

  • {customer_name}
  • {customer_contact_name}
  • {customer_reference}

shipment

  • {shipment_id}
  • {load_number}
  • {status}
  • {eta}
  • {current_location}
  • {carrier_name}

stops

  • {pickup_location}
  • {pickup_date}
  • {pickup_time}
  • {delivery_location}
  • {delivery_date}
  • {delivery_time}

documents

  • {document_name}
  • {document_type}
  • {document_date}

organization

  • {company_name}

Editing, versioning and per-customer overrides (§60) need the template table in prisma/schema.prisma applied — the catalogue is currently code, not data. Preview runs through the same renderTemplate the pipeline uses, so what you see here is what would actually go out.