CARRIER_FOUND
intent CARRIER_REQUESTstate FOUNDlang env1
Template
Subject
Re: Load {load_number} — carrier
Hi {customer_contact_name},
Load {load_number} is moving with {carrier_name}.
Thanks,
{company_name}Variables used
- 🔒carrier_name
- 🔒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 — carrier
to john@acme-test.com
Hi John, Load 84721 is moving with Meridian Xpress. 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.