When a port closes, a route changes, or weather delays a shipment, customers check the website first. They want to know what is affected, what they need to do, and when service will return to normal.
In many logistics groups, each regional office posts notices in its own format on its own site. The guides and FAQs that answer the next question sit somewhere else. On a disruption day, the most people visit at the moment the information is changing fastest.
One format for service updates
An admin sets up an advisories collection once, with fields for the affected service, region, dates, severity, and the notice itself. The collection is shared with every regional site. Each region's editors publish their own advisories, which stay separate from other regions'.
Customers see the same kind of notice in the same place on every regional site.
One search for notices, guides, and FAQs
Advisories, shipping guides, and FAQs can all go into one search. Customers type into one box and filter the results by service or region. Each result can show a notice's dates and severity straight away, so customers know what applies to them before they click.
Fast pages on the busiest days
Regional sites are built as static pages and served from 200+ edge locations. Publishing an advisory triggers a rebuild, so a new notice goes live when its build completes. The rush of visitors that follows meets pages that are already built.
What changes
Regional teams post updates themselves in a format the whole group shares. Customers find what they need with one search, and the sites stay quick on the days they matter most.
