# Pre-Dispatch
## Overview
You can send out automated communication to customers for all events within the pre-dispatch process (for example: production steps, warehouse handling scans, and order confirmation) using the following methods:
* Triggered alarms - time-based emails sent by parcelLab based on order information and not receiving inbound scans from the carrier. The following alarm types are used for triggered alarms:
* Internal delay - labels that are not created in time (that is: an order record has been created in the parcelLab system but no label information has been added within a threshold defined by the shop)
* Invalid tracking - labels that are not activated (that is: a tracking number has been created but it has not been confirmed by the carrier)
* Delayed dispatch - the inbound scan did not happen in time (that is: a tracking number has been created and confirmed in time but there was no inbound scan by the carrier, which means the parcel is not with the carrier yet)
{% hint style="info" %}
If there are no delays, the triggers do not activate (that is: you can have the feature set up even when the issue only occurs infrequently).
{% endhint %}
* Pre-dispatch communication - emails sent by parcelLab to keep the customer informed based on specific information you provide (for example: if an order involves a production process or if products are sold out)
## Configuring the Pre-Dispatch Feature
The following sections describe the configuration required for the Pre-Dispatch feature.
### Customer Requirements
To integrate triggered alarms in email communication, you need to provide the following information to parcelLab:
* The order data (that is: order number) as soon as it is created
* Agree to the content of the communication
* The thresholds of the alarm types
{% hint style="info" %}
You can use the parcelLab default thresholds (for example: 36 hours after label creation for the internal delay alarm type).
{% endhint %}
To integrate pre-dispatch communication in email communication, you need to provide the following information to parcelLab:
* The necessary events (for example: production steps) and information you want to base the communications on
* The corresponding recipient data, including the email address, delivery location, tracking number, and the event itself
{% hint style="info" %}
The tracking number is not available before dispatch so can be provided when you have it. In this case, parcelLab need the order number to match the tracking number with the initial recipient and pre-dispatch information. The data transfer can be file-based or via webhook as often as needed (for example: each hour or each day).
{% endhint %}
* Agree to the content of the communication
### Implementation Process
When parcelLab has the required information, the setup process can begin. The information provided allows parcelLab to set the thresholds for the alarm types and configure the specified events to send for pre-dispatch communication.
{% hint style="info" %}
For more information on the scope and requirements for implementing this feature (for example: providing the events for pre-dispatch communication is not recommended via BCC), please contact your parcelLab representative.
{% endhint %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.parcellab.com/docs/engage/messages-and-journeys/overview/pre-dispatch.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
