Use this article to automatically send consignment status updates from TransVirtual to customers or external systems.
This guide explains how to notify recipients when key delivery events occur, such as when a consignment is on delivery or approaching the destination.
In Transvirtual, there is the ability to create Consignment Status Export EDI (Electronic Data Interchange) rules that send out status update information about a consignment, to a location via FTP, Email, etc. This page can be found under Import/Export > Data Export > Status Updates.
This article runs through a common setup that most Transvirtual users implement, sending On Delivery notifications to a customer (indicating their freight has been loaded and is on its way).
This example selects "OnDelivery Email Notification to customer" as the rule name and Email as the export framework.
The data filter is the driving force behind when the rule will and won't apply to a consignment.
This example selects Status Name in Select Field, Equal in Logic and OnDelivery in Select Value field.
If notification emails should only be sent for a specific consignment customer, add an extra line to the Data Filter that specifies the desired customer: select Customer Name in Select Field, Equal in Logic and then the Customer's Name in Select Value. This example sends notifications for all customers, so it uses only the first line of logic.
The details can be updated as follows:
The FTP, Email, Webservice, Printer, Account Package and SMS settings can all be customised using the Settings button.
Export Framework Setting
The @Model.ConsignmentTracking URL is a special coding function that sends a link the customer can select to view the tracking of their consignment. Ensure this code is spelt exactly as shown above.
The Validate button at the bottom of this window can be used to preview what the email will look like, and it also checks that any coding functions are correct and will not cause issues. Use this button to confirm the setup is correct.
The Memo and Email EDI Errors fields are not mandatory, so this example leaves them blank.
Any successful EDI rules that have triggered on a consignment will appear under the communications tab of that consignment.
The example above shows this consignment currently has a status of On Delivery; therefore, it is eligible for this EDI rule.
In addition to the above, Transvirtual also has the ability to send out notifications to consignment customers, senders and receivers to provide notifications when their consignment is roughly 30 or 15 minutes away from being delivered.
This setup is normally done via SMS, and the example below uses that method; it is also set up under the Status Updates page, which can be found under Import/Export > Data Export > Status Updates.
The Route Optimisation module must be enabled for this process to work.
SMS sending in TransVirtual is a paid function. Each text message sent from the account will incur a charge. Further information can be found in the Rates and Modules page of the account: go to Configuration > Transvirtual Account > Rates and Modules.
Data filters in Transvirtual determine when an EDI rule will and won't apply to a consignment.
These values determine when this EDI rule applies to a consignment.
In this example, the data filter section uses Customer Name in Field, Equal To in Logic and Customer Name (Transvirtual) in Value. This Data Filter applies to consignments for a nominated customer where the consignment status is MobileDeliveryIn15Mins.
It may be a good idea to add another condition to the Data Filter, as below, if a similar rule is set up for 30-minute notifications:
To add this, the logic is Previous Status (Any), then Not Equal, then Mobile - Delivery ETA 30mins, then Add Rule.
Note: Adding this extra condition/line to the Data Filter is useful if a 30-minute delivery notification version of this rule is also set up. In that case, both a 30-minute and 15-minute SMS notification may not be wanted. This extra line means the 15-minute text notification will only occur if the system has not previously sent a message/SMS at 30 minutes.
This can help avoid the cost of sending both a 30-minute and 15-minute SMS notification. If only one EDI rule exists, this condition does not apply and can be disregarded.
Field Information
Framework Setting
This example enables the toggle for Send to Consignment Receiver Phone.
To check the consignment receiver phone number, open the consignment and go to the consignment details section to check the Receiver information as shown below.
@Model.ConsignmentNumber is a special coding function that automatically populates the consignment number for each consignment this rule triggers against. It is very important that this code is typed exactly as shown above for it to work properly.
If necessary, use the Validate button to check the setup is correct — the screen will turn white and display an example SMS if the setup is correct.
The more credits used, the higher the cost, so it is best to keep the message short to minimise costs.
Once set up, the rule will work automatically to apply to any consignments where Transvirtual is the customer (for this example) and the current status is "Mobile - Delivery ETA 15 Mins".
This status is achieved by Transvirtual communicating with the driver's mobile device. Each device (as long as it is turned on and GPS is enabled) sends back GPS data periodically to Transvirtual, letting the system know its location. When Transvirtual receives this information, it can calculate how far away a driver/device is from a location, and if 15 minutes away, the system assigns applicable consignments the status of "Mobile - Delivery ETA 15 Mins", which then triggers the sending of an SMS to the client, informing them that their delivery will arrive shortly.
Important to note: If for some reason a driver is unable to complete the delivery, they must ensure they 'fail' the delivery so that this export rule does not keep attempting to send the SMS. For help with this, watch this video on failing a delivery, or see the delivery and pickup issue troubleshooting article.
Issue: Status update emails or SMS are not being sent
Cause: The rule is disabled or the consignment does not meet the data filter conditions.
Resolution: Ensure the rule is enabled and the status in the data filter matches the consignment status.
Issue: ETA SMS alerts are not triggering
Cause: Route Optimisation or GPS is not enabled on driver devices.
Resolution: Confirm Route Optimisation is active and drivers have GPS turned on.
Issue: SMS sent to the wrong phone number
Cause: Sender or receiver phone details are incorrect.
Resolution: Check phone numbers in the consignment details.
Issue: Tracking link does not work
Cause: The tracking URL field is missing or entered incorrectly.
Resolution: Ensure @Model.ConsignmentTracking is correctly entered in the message.