Answers for the forwarder tracking workspace.

The first MVP focuses on forwarder shipment tracking. You can track supported AWBs, retain shipment context in your tenant workspace, and inspect the resulting ONE Record-aligned operational graph.

Open the protected workspace and enter an AWB in the format 000-00000000. aiXuberance validates the number, requests current tracking data, and saves the canonical shipment record for your organisation.

Operational data is tenant-scoped. Authentication identifies your user and organisation so saved shipments, conversations and support tickets remain within the correct workspace.

Use three carrier-prefix digits, a hyphen, and eight serial digits: 000-00000000. Spaces and a missing hyphen may be normalised, but the complete 11 digits are required.

The AWB may be new, unsupported by the connected source, temporarily unavailable, or not yet published by the carrier. Retry later and create a support ticket when the issue persists.

The displayed status reflects the latest result returned by the connected tracking source at the time shown. Carrier data can arrive late or change after the request.

It presents the saved shipment as connected logistics objects and events rather than a flat tracking response. The view keeps the operational summary readable while preserving canonical JSON-LD resources.

Application data is scoped to the authenticated tenant. Support administrators only receive access through protected administrator groups, and internal support notes are never returned to the user ticket centre.

Include the affected AWB, the approximate request time, what happened, and the result you expected. Do not include passwords, API keys, access tokens or other secrets.

Open the Support centre in the protected workspace. It shows your tickets, replies, workflow status and resolution history.